Sysprep tool may cause SSE Client failure at next logon
Description:
This article discusses issues you may run into when utilizing the Windows Sysprep tool on a SSE Client, and a workaround.
PRODUCTS
SAFsolution Enterprise 1.1 (all service pack levels)
- Microsoft Sysprep tool
ISSUE
When using the sysprep tool to reinitialize a Windows XP or 2000 client with SAFsolution Client installed, the next logon after the initial setup results in an Internal Error. This tool is often used to prepare a client prior to using imaging software such as Symantec Ghost or Power Quest Disk Image (PQDI).
PROBLEM
The exact cause of this problem is undertermined. Certain things are changed/reset in an XP or 2000 client when the Sysprep tool is used, including user and machine Security IDs and domain/workgroup information. One or more of these changes may affect the behavior of the SAFsolution Client.
RESOLUTION
REPRO:
OS: Win XP Pro
Machine: COMPUTER01
Domain: DOMAIN.COM
SSE Client: 1.1 SP2
1. Run Sysprep tool
2. Leave default Shutdown option (Shutdown).
3. Click Reseal.
4. Sysprep warns that the SID will be changed, click OK.
5. Once finished, system will automatically shutdown. Turn it back on.
6. Upon the machine coming back up, go through the initial setup and enter new machine account information.
7. After setup is finished, the system allows you to logon. The Saflink GINA is being used at this point. Invoking CAD will end in the Internal Error.
WORKAROUND:
Start with same working setup as above:
OS: Win XP Pro
Machine: COMPUTER01
Domain: DOMAIN.COM
SSE Client: 1.1 SP2
1. Run Sysprep tool.
2. Change Shutdown option to Quit. (This allows you to make specific changes after tool finishes.)
3. Click Reseal.
4. Sysprep warns that the SID will be changed, click OK.
5. Change GinaDLL value to MSGINA.DLL (could use an exported .reg file)
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon]
From:
"GinaDLL"="SAFGINA2.DLL"
To:
"GinaDLL"="MSGINA.DLL"
6. Shut system down, and then turn it back on. (This step is also where you may choose to image the machine)
7. Upon the machine coming back up, go through the initial setup and enter new machine account information.
8. After setup is finished, the system allows you to logon. Microsoft GINA is being used at this point. Login.
9. Once logged in, change GinaDLL value to SAFGINA2.DLL (could use an exported .reg file...also, see notes below for automating this process)
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon]
From:
"GinaDLL"="MSGINA.DLL"
To:
"GinaDLL"="SAFGINA2.DLL"
10. Restart the machine.
11. Next logon will use SAFsolution GINA. It works now.
Merging a .reg file to change the value back to SAFGINA2.DLL could be automated through the use of a logon script (initial logon will still use MS GINA, but after script is executed, subsequent will use Saflink). Another suggestion is, after step 5 above, you could generate a shortcut in the Startup program group that executes "regedit /s safgina2dll.reg", where the /s parameter allows it to run in silent mode, and safgina2dll.reg would be the exported registry file containing the "GinaDLL"="SAFGINA2.DLL" value.
Something to keep in mind is that this workaround requires that a local admin account is used during initial logon so that the registry changes can be applied.
ADDITIONAL INFORMATION
For information about using the sysprep tool, please go to the following website:
http://www.microsoft.com/windowsxp/pro/using/itpro/deploying/introduction.asp
Keywords:
sse ssw safsolution client internal error gina sysprep imaging ghost pqdi
Description:
This article discusses issues you may run into when utilizing the Windows Sysprep tool on a SSE Client, and a workaround.
PRODUCTS
SAFsolution Enterprise 1.1 (all service pack levels)
- Microsoft Sysprep tool
ISSUE
When using the sysprep tool to reinitialize a Windows XP or 2000 client with SAFsolution Client installed, the next logon after the initial setup results in an Internal Error. This tool is often used to prepare a client prior to using imaging software such as Symantec Ghost or Power Quest Disk Image (PQDI).
PROBLEM
The exact cause of this problem is undertermined. Certain things are changed/reset in an XP or 2000 client when the Sysprep tool is used, including user and machine Security IDs and domain/workgroup information. One or more of these changes may affect the behavior of the SAFsolution Client.
RESOLUTION
REPRO:
OS: Win XP Pro
Machine: COMPUTER01
Domain: DOMAIN.COM
SSE Client: 1.1 SP2
1. Run Sysprep tool
2. Leave default Shutdown option (Shutdown).
3. Click Reseal.
4. Sysprep warns that the SID will be changed, click OK.
5. Once finished, system will automatically shutdown. Turn it back on.
6. Upon the machine coming back up, go through the initial setup and enter new machine account information.
7. After setup is finished, the system allows you to logon. The Saflink GINA is being used at this point. Invoking CAD will end in the Internal Error.
WORKAROUND:
Start with same working setup as above:
OS: Win XP Pro
Machine: COMPUTER01
Domain: DOMAIN.COM
SSE Client: 1.1 SP2
1. Run Sysprep tool.
2. Change Shutdown option to Quit. (This allows you to make specific changes after tool finishes.)
3. Click Reseal.
4. Sysprep warns that the SID will be changed, click OK.
5. Change GinaDLL value to MSGINA.DLL (could use an exported .reg file)
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon]
From:
"GinaDLL"="SAFGINA2.DLL"
To:
"GinaDLL"="MSGINA.DLL"
6. Shut system down, and then turn it back on. (This step is also where you may choose to image the machine)
7. Upon the machine coming back up, go through the initial setup and enter new machine account information.
8. After setup is finished, the system allows you to logon. Microsoft GINA is being used at this point. Login.
9. Once logged in, change GinaDLL value to SAFGINA2.DLL (could use an exported .reg file...also, see notes below for automating this process)
[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon]
From:
"GinaDLL"="MSGINA.DLL"
To:
"GinaDLL"="SAFGINA2.DLL"
10. Restart the machine.
11. Next logon will use SAFsolution GINA. It works now.
Merging a .reg file to change the value back to SAFGINA2.DLL could be automated through the use of a logon script (initial logon will still use MS GINA, but after script is executed, subsequent will use Saflink). Another suggestion is, after step 5 above, you could generate a shortcut in the Startup program group that executes "regedit /s safgina2dll.reg", where the /s parameter allows it to run in silent mode, and safgina2dll.reg would be the exported registry file containing the "GinaDLL"="SAFGINA2.DLL" value.
Something to keep in mind is that this workaround requires that a local admin account is used during initial logon so that the registry changes can be applied.
ADDITIONAL INFORMATION
For information about using the sysprep tool, please go to the following website:
http://www.microsoft.com/windowsxp/pro/using/itpro/deploying/introduction.asp
Keywords:
sse ssw safsolution client internal error gina sysprep imaging ghost pqdi