How to proceed with the issue when after successful deployment, the target system is being system patched on every reboot

This article applies only to:

• Acronis Snap Deploy
• Acronis Snap Deploy 2.0
• Acronis Snap Deploy 3

Symptoms

An image is deployed successfully, but a special system patcher starts on every system reboot and the system is stuck in a loop. View sample screenshot.

Cause

System patching usually takes somewhere from five to ten minutes to complete and may require several (two or three) reboots, after which the deployed system starts successfully.

In most cases the issue is with a specific deployed image. This means it will happen on every computer you deploy from that image.

The possible causes are:

• Acronis Snap Deploy cannot access Windows registry (e.g. an antiviral application is blocking it);
• Acronis Snap Deploy cannot access an existing gina.dll key (e.g, CISCO VPN Client that uses csgina.dll and executes automatically on logon before the system patcher);
• The system patcher malfunctions.

Solution

1. See if there are any applications that might be blocking the access to the registry such as antiviruses, antispyware, etc. programs on the source system (which was imaged). Try disabling those prior to image creation;
2. Try deploying the image with the Change Security IDs option disabled and see if the issue still persists;
3. Delete the GINADLL value in the Windows registry of the deployed system:
   1. Start the Windows registry editor (Start -> Run -> Regedit)
   2. Delete the value GINADLL from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon -> GINADLL (ds_gina.dll)

More information

The security identifier (SID) is a data structure of variable length that identifies user, group and computer accounts. Every account on a network is issued a unique SID when the account is created. Internal processes in Windows refer to an account's SID rather than to its user or group name.

If the issue still persists, please do the following:

1. Collect the following infromation from the source system:
   1. Windows System Information File
   2. Export from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon registry key (Start->Run->Regedit, right-click on registry key and choose Export from the menu)
2. OS_patcher logs:
   1. A copy of the %Windows%\Debug\ folder from the restored system (after boot up);
   2. Logs of the patcher, the names of which are similare to os_patcher[dd.mm.yy].log and are located in the %Windows%\System32\ folder
3. Contact Acronis Support with the collected information and a reference to this article.