Microsoft KB Archive/139339

= CPS Does Not Profile License Logging Service =

Article ID: 139339

Article Last Modified on 10/31/2006

-

APPLIES TO


 * MSPRESS Microsoft Windows NT Resource Kit 3.51

-



This article was previously published under Q139339



SYMPTOMS
Computer Profile Setup (CPS) does not profile the License Logging Service.



WORKAROUND
To work around this problem:


 * 1) Using UPLODPRF.EXE, upload the Master system. For details on running UPLODPRF.EXE read Volume 1, Chapter 3 of the "Windows NT version 3.51 Resource Kit."
 * 2) Run Registry Editor (REGEDT32.EXE).
 * 3) From the HKEY_LOCAL_MACHINE subtree, go to the following key:

\SYSTEM\CurrentControlSet\Services\LicenseService
 * 1) Choose the Save Key option from the Registry menu to save the LicenseService Key to a file (for example: A:\LICENSE.TMP).
 * 2) Choose the OK button.
 * 3) Make sure the HKEY_LOCAL_MACHINE window is highlighted by selecting it.
 * 4) Choose the LOAD HIVE option from the Registry menu to load the registry of the Distribution System.
 * 5) In the Load Hive dialog box, specify the filename that was uploaded to the distribution server and choose the OK button: %SYSTEMROOT%\SYSTEM32\CONFIG\SYSTEM
 * 6) When prompted for Key Name, specify "Distribution System" (without quotes) and choose the OK button.
 * 7) Go to the key: \Distribution System\CurrentControlSet1\Services
 * 8) From the Edit menu, choose Add Key.
 * 9) Specify LicenseService as the key name.
 * 10) Choose the OK button.
 * 11) Go to the following key: \Distribution System\CurrentControlSet1\Services\LicenseService
 * 12) Choose the Restore option from the Registry menu and specify the file saved in Step 4 above (for example: A:\LICENSE.TMP).
 * 13) Select the Distribution System key.
 * 14) Choose the Unload Hive option from the Registry menu.
 * 15) Run WINNTP.EXE from the target system. For details on WINNTP.EXE, read Volume 1, Chapter 3 of the "Windows NT version 3.51 Resource Kit."

NOTE: The License Logging Service only applies to Windows NT Servers. Make sure the Target system does not violate your Windows NT Server license agreement. You can verify the licensing configuration from License Manager or from the Licensing section of Control Panel.



STATUS
Microsoft has confirmed this to be a problem in Windows NT version 3.51. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: prodnt

Keywords: kbsetup KB139339

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.