Microsoft has tested the use of PCM service for installing several applications and operating systems. Clean installations were tested, as well as upgrades. The tests used client computers running Windows NT Workstation and Windows NT Server, version 3.51 with Service Pack 5 and version 4.0 with Service Pack 1.
This section provides you with special-case information gathered in these tests.
For both Windows NT Workstation and Windows NT Server, versions 3.51 and 4.0, the files for Office 95 are installed correctly by the PCM service. While Office 95 is being installed, it makes no difference which account is logged on at the computer, or even whether anyone is logged on at all. Job status usually remains Active even after the job is completed, although in some cases it correctly changes to complete.
If the computer is running Windows NT 4.0, Office 95 items are not generally added to the Start menu.
If the computer is running Windows NT 3.51, no program groups or icons are created for Office 95.
In all cases, the Office 95 components work correctly when run from the executables (for example by double-clicking the MSACCESS.EXE file in File Manager or in Windows NT Explorer).
For both Windows NT Workstation and Windows NT Server, versions 3.51 and 4.0, the PCM service installs the files for Office 97 properly. While Office 97 is being installed, it makes no difference what account is logged in at the computer, or even whether anyone is logged in at all.
If the computer is running Windows NT 4.0, Start menu items are created as expected, and they apply to all accounts. However, if a new account is added after Office 97 is installed, that account will have two sets of Start menu items: one in the lower, common program groups section, and another in the upper, individual section. The items in the common section work properly. The items in the individual section do not work properly, and should be removed manually. (From the Start menu point to Settings, then choose Taskbar and go to the Start Menu Programs tab.)
If the computer is running Windows NT 3.51, no program groups or icons are created for Office 97.
In all cases, the Office 97 components work correctly when run from the executables (for example by double-clicking the MSACCESS.EXE file in File Manager or in Windows NT Explorer).
In the PCM tests, Office 95 was first installed manually, to simulate the typical case in which the applications are already installed.
The upgrade using the PCM service is fully functional. Items for Office 97 applications are added to the common Start menu. In addition, an account that already had Office 97 applications in its Start menu now has these items in both the lower, common portion of the Start menu and in the upper, individual portion of the Start menu. All of these items function properly.
Most Office 95 files are replaced with proxy files that invoke the equivalent Office 97 application when double-clicked. The Office 97 directory tree is fully populated, and the files there work correctly when double-clicked.
The Office 97 directory tree is fully populated, and the files there work correctly when double-clicked, from any account. Most Office 95 files are replaced with proxy files that invoke the equivalent Office 97 application when double-clicked. However, no new program groups and icons are created for the Office 97 applications, and the old program groups and icons point to the Office 95 executable files. Since the Office 95 executable files have been replaced with proxy files, clicking the icons does not start the applications. To change the icon so that it points to the new files, select the icon and choose Properties from the File menu.
The upgrade process works as usual when upgrading Windows NT Workstation 3.51 (Service Pack 4) to Windows NT Workstation 3.51 Service Pack 5, or from Windows NT Server 4.0 (no Service Pack) to Windows NT Server (Service Pack 1).
If you will be using the PCM service to upgrade from Windows NT 3.51 (Service Pack 5) to Windows NT 4.0, edit the command-line properties in the Windows NT upgrade PDF, replacing ntencap.exe /NTw with start. Because the NTENCAP.EXE program cannot detect a system reboot from a service, any job involving a reboot would fail to complete if you use NTENCAP. Therefore it should not be used with the PCM service.
Note When using PCM service to upgrade to Windows NT 4.0, there will be no detailed status report on the job. Also, the job may never be reported as Complete, even after it has completed successfully. This is because jobs that require a reboot may not provide PCMSVC32 enough time to write a complete status back to the logon server. In addition, if the PCMSVC32 polling interval is set to a value that is too fast, it may attempt to process an instruction a second time following the reboot, before the site has had time to process the completion of the first execution. This condition should correct itself in time, but can be prevented by keeping the PCMSVC32 polling interval set at one hour or more and the site response speed at "Fast" (the default.)