After Deploying an image taken from a machine with the Symantec Management Agent installed, the Symantec Management Agent (SMA aka Altiris Agent) service is being disabled.
After the client machine is done re-imaging, and booted to production, there is a need to manually change the service from Disabled to Automatic (Delayed Start).
While looking at DSTasks.log, we see:
[2022/03/31 10:48:50.220 1344:752 INFO] Deploy Image Task: Starting application 'X:\Program Files\Symantec\Deployment\Ghost\GhRegEdit64.exe' with command-line ' addvalue C:\Windows "HKEY_LOCAL_MACHINE\System\ControlSet001\Services\AeXNSClient" "Start" REG_DWORD 4' in 'x:\program files\Symantec\Deployment'
then
[2022/03/31 10:48:50.613 1344:752 <TRC>] Deploy Image Task: Read production OS registry value 'HKEY_LOCAL_MACHINE\System\ControlSet001\Services\AeXNSClient\Start': dword:00000004
[2022/03/31 10:48:50.613 1344:752 INFO] Deploy Image Task: AeXNSAgent.exe location found: C:Program Files\Altiris\Altiris Agent
which the code means:
dword:00000001=boot
dword:00000002=automatic
dword:00000003=manual
dword:00000004=disabled
ITMS 8.5, 8.6
DSAgent plug-in (Deployment Plug-in for Windows) was not installed on the client machine where the image was taken from.
DSTasks.log looks fine. That 00000004 is correct - means the disabled service state.
There was something in their environment or process that leads to missing DSAgent plug-in and ConfgiService.exe on the machine.
If there is no DSAgent plug-in, then there is no ConfigService.exe in the image.
What's happening after the image restore is:
Then machine reboot should follow and the following thins should occur during the boot:
Install the DS Agent plugin on computers before capturing an image:
1. Go to Settings>All Settings>Agent/Plug-ins>Deployment>Windows(x64) and either enable or target this plug-in to the machine that you are using to capture your image.
2. and after the DSAgent plug-in is installed then capture the image again and see if the issue persists or not.
Note:
The following is provided as a guidance on what to consider while troubleshooting an issue like this:
ConfigService install
and Try starting the service:
net start configservice
Check if ConfigService.log created. There should be a failure at some step.