This article has been archived. It is offered "as is" and will no longer be updated.
In the past, the Package Command Manager (PCM) has been installed as aservice (Pcmsvc32.exe) on Systems Management Server logon servers, but onlyas an application (Pcmwin32.exe) on Systems Management Server Windows NTclients. Because the client version runs as an application, packages thatare run from PCM are run in the security context of the currently logged-onuser.
You can now install PCM as a service on any computer running Windows NTWorkstation or Windows NT Server stand-alone (Intel or Alpha) that is amember of a Windows NT Server domain and is a Systems Management Server 1.2client. In addition to the new Pcmsvc.exe file, the Pcmwin32.exe file hasbeen changed and will need to be replaced on the client computers.
The PCM service requires a user account that has:
Administrator privileges on the client computer.
Domain user authority to read a PCM instruction file on the Systems Management Server logon server and to run a setup program in the package directory on the Systems Management Server distribution server.
Because it works through a user account with administrative privileges, thePCM service can perform tasks that the PCM application cannot. For example,it can install files into secured directories or make changes to securedregistry keys.
You can download installation instructions and file updates on thefollowing Microsoft Web site:
Click Download to download the Pcmupdte.exe file to your computer. Inaddition to the files necessary for running PCM as a service, this self-extracting executable file also contains an Install.doc file that containscomprehensive information about how to install and use PCM as a service onclient computers that are running Windows NT.