Windows activation status might be incorrect after a full system restore
After using Tivoli Storage Manager (TSM) Backup-Archive Client to restore a Microsoft Windows Vista or later Windows operating system, the Windows activation status might be incorrect. Windows Update also might not function correctly.
During backup of the operating system boot drive (usually C:), the profile files for two internal Windows accounts, "Network Service" and "Local Service", are excluded from backup by TSM. These files are:
If a full system restore is performed, these files cannot be restored because they are not backed up. New versions of these files will automatically be created by Windows after the restored system is started. However they might lack the necessary permissions for license activation status or Windows Update to work properly.
Further details for this problem can be found in APAR IC89666.
The following TSM Backup-Archive Client versions are affected by this problem:
- 184.108.40.206 - 5.5.x.x
- 220.127.116.11 - 6.1.x.x
- 18.104.22.168 - 6.2.4.x
- 22.214.171.124 - 126.96.36.199
- 188.8.131.52 - 184.108.40.206
Conditions for the problem to occur:
The problem can occur when the following steps are performed:
- An affected TSM Backup-Archive Client versions is used to back up the boot drive for any of these operating systems:
- Microsoft Windows Vista
- Microsoft Windows Server 2008
- Microsoft Windows 7
- Microsoft Windows Server 2008 R2
- Microsoft Windows 8
- Microsoft Windows Server 2012
- A full restore of the system is performed.
Note: It is not possible to predict in advance if the problem will actually occur on a given restored system.
How can you tell if you are affected?
Any Windows system that is backed up with one of the affected TSM Backup-Archive Client versions is potentially affected. Under most circumstances this has not been known to impact full system restores. However, if a restored system is affected, possible symptoms include:
- The Microsoft Windows activation status, as shown in the Computer "Properties" dialog, may be incorrect or "unknown".
- The Windows Update utility might not work correctly.
If your system exhibits these symptoms following a full system restore, examine the permissions for the following registry keys:
Make sure that each of these keys is configured with these users and allowed permissions:
|Group or user name||Permissions|
|SYSTEM||Full Control, Read|
|LOCAL SERVICE||Full Control, Read|
|Administrators||Full Control, Read|
The TSM Backup-Archive Client has been fixed so that the two NTUSER.DAT files can be backed up during backup of the Windows boot drive (usually C:). Perform the following steps to ensure that the files are included in future backups:
- Install one of the fixing TSM Backup-Archive Client levels (shown in the table below)
- Ensure that the TSM Backup-Archive Client is configured to use the TSM Open File Support (OFS) feature. OFS is enabled by using this option in the client options file (dsm.opt): snapshotproviderfs vss
- Ensure that you do not exclude from backup any files named NTUSER.DAT or USRCLASS.DAT
- Back up the system. A full backup is not required. The next scheduled incremental backup operation should back up the necessary files.
- After the backup completes, check the dsmsched.log file to ensure that NTUSER.DAT files are backed up. As an alternative, you can use the TSM Backup-Archive Client to query the backups, and verify that backups of these files were created.
|TSM Backup-Archive Client affected releases||First level with fix|
|220.127.116.11 - 5.5.x.x||Install one of the 6.2, 6.3, or 6.4 fix levels|
|18.104.22.168 - 6.1.x.x||Install one of the 6.2, 6.3, or 6.4 fix levels|
|22.214.171.124 - 6.2.4.x||126.96.36.199|
|188.8.131.52 - 184.108.40.206||220.127.116.11|
|18.104.22.168 - 22.214.171.124||126.96.36.199|
- A fix is not planned for the version 5.5 and 6.1 Backup-Archive Clients. If you are currently using the version 5.5 or 6.1 client, you must upgrade to one of the version 6.2, 6.3, or .6.4 fixing levels.
- Make sure you install a fixing level that is supported with the version of your TSM Server (see client and server version compatibility table).
Translate this page: