Chat now with support
Chat with Support

NOTICE! We are upgrading our support telephone services, implementing Genesys, starting the week of May 26, 2025

KACE Desktop Authority 11.2.1 - Reporting Guide

Service Pack Deployment (Computer Management)

Service Pack Deployment

The Service Pack Deployment object allows you to deploy service packs for all 7/2008/2008 R2 clients and servers (64-bit operating systems included).

A few items to note regarding service pack deployment:

  • Computer Management Service Pack Deployment will only install service packs to 7/2008/2008 R2 clients and servers if connected over a LAN connection.
  • Computer Management Service Pack Deployment will never downgrade the currently installed service pack on a computer.
  • Computer Management Service Pack Deployment will only install the requested service pack if the client/server has an older or no service pack installed.
  • Computer Management Service Pack Deployment will not attempt to install the requested service pack if the client/server does not have enough available disk space on the drive that hosts the %temp% folder. The engine determines the amount of available disk space before the service pack is installed. By default, 1.4G (1400mb) of disk space must be available to install any service pack. This default can be overridden by defining a value in the global or profile definition file.

The variable $ServicePackFreeSpaceNeededInMB is used to override the available disk space amount. Select Global Options > Definitions or select the Definitions tab on the profile's settings.

Example:

$ServicePackFreeSpaceNeededInMB="1000"

  • Computer Management Service Pack Deployment will run all service packs in unattended mode, will force the computer to close other programs when it shuts down, and will not back up files for uninstall purposes.
  • Computer Management Service Pack Deployment will not install service packs on any Windows Embedded operating system.

Desktop Authority can bypass the automatic installation of service packs on specific computers. If you have specific computers that you would never like Desktop Authority to install a service pack on (such as a development station), create a file called SLNOCSD in the root directory of the System Drive. This allows you to generally apply service packs based on Validation Logic, while providing for special-case exemptions based on individual systems.

Settings

Service Packs settings
Operating system version

Select an Operating System version from the list. Valid selections are Windows 2008, Windows 2008 x64 and Windows 7.

Operating system language

Select a language from the list. This language should specify the dialect of the operating system installed on the client/server as well as the service pack. If the languages do not match, the service pack will not be installed.

Update to

From the list, select the service pack to be deployed. Service Packs displayed in the list are filtered based on the OS Version selected.

Location of Update.exe /Spinstall.exe

Enter the complete path and filename where the installation executable exists or click Browse to locate the executable’s path. The installation executable may be called either spinstall.exe or update.exe based on the operating system being installed. The service pack install file is called spinstall.exe in Windows 2008.

Example: 

     \\server1\installs\W2KSP1\Update.exe

The executable file downloaded from Microsoft is an archive that must be extracted at a command line by using the -x switch. This will extract the service pack into multiple folders among which you will find the update.exe or spinstall.exe executable.

The following parameters are used when installing service packs from the Computer Management Service Pack object:

Execution Options 

Balloon
Show Balloon message to users before element executes

Check this box to show a pop up message from the system tray before each Desktop Authority element is executed on the computer. Enter a message into the text box to be shown in the popup message.

Permission
Ask user's permission to execute element

Select this box to pause execution and request permission via a message box to execute an element on the desktop. Enter a message into the text box. This text will be used on the on permission message box.

Message box will timeout after xx seconds

When permission is requested from the user, the message box will be displayed for the number of seconds specified here.

Default answer if message box times out

If there is no response during the timeout period, the message box will be accepted or dismissed based on the specified default answer.

Authorized by

Optionally enter then name of the person who authorized the specified configuration to take place.

Reboot
Reboot after element executes

Select this option to determine the timing in which a reboot will take place, if required, by the executed element.

Reboot type
Reboot immediately without user interaction

Allow the required reboot to happen immediately following the element configuration.

Remind user that a reboot is required (will not reboot unless user approves)

Select this option to delay the reboot to a time that the user deems acceptable.

Reboot with count down (machine will reboot when countdown dialog comes out, unless postponed)

The user will be provided a countdown timer before the reboot event occurs. Specify the number of seconds for the countdown in the Seconds until reboot box.

Reboot timeout
Seconds until reboot

Enter the number of seconds to count down until reboot occurs.

Allow users to postpone reboot

Select this box to allow the user to postpone the impending reboot.

Timing  

Select the Timing tab to configure when this element will be executed. Computer Management objects can execute at computer Startup, Shutdown, defined Refresh intervals or based on customized Schedules.

Validation Logic

Select the Validation Logic tab to set the validation rules for this element. Service Packs may only be applied to computers classified as a Desktop, Portable Tablet PC, Member Server and Domain Controller. Operating System and Connection type are disabled.

Notes

Select the Notes tab to create any additional notes needed to document the profile element.

Description

When adding or modifying a profile object element, the description appears above the settings tab. Enter a description to annotate the element. The default value for new profile elements can be changed by going to the system Preferences.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating