Installations are more successful when no user is logged on because no applications are running and no files are in use. And since there are fewer scenarios to consider, errors are less likely and testing is easier. Furthermore reboots are less likely - which will speed installations. Despite of its advantages, this scenario is not well supported by the standard tools - this is where PackageShell comes to help:
Control of user logon state
PackageShell helps the user to correctly log off and makes sure he can only log on when the installation is completed.
By default, installation dialogs are not visible when the user is not logged on. This is because Windows uses a separate desktop during the logon phase. PackageShell takes care the installation is always performed on the currently visible desktop. Even under Vista and Windows 7.
PackageShell stores information about what was executed locally on each client. This information is reported by inventory into the SMS database, where it is available for queries and web reports. The native SMS/SCCM reporting technology using status messages is not well suited as a long term reference of what is present on a client.
Integration of reboots
Reboots are still a common requirement during software installations. Unfortunately, the Windows Installer (MSI) does not support a reboot action. PackageShell can perform a reboot as part of a package routine - execution of the remaining steps is resumed immediately after the reboot. This is similar to an SCCM Task Sequence only better.