Deployment and Imaging Group

I understand that the "Prepare for Image capture" task should be stripping the Altiris Agent GUID from the client when an image is made that has the agents installed, but that isn't happening for me (DS7.1 SP1a MR1).

In addition, I noticed a few other bugs with the "Prepare for Image capture" / "Deploy Image" tasks:

1. A "C:\Setup" folder is created during "Prepare for Image capture".  This contents of this folder makes me believe that it is a mistake and should be created at: C:\Windows\Setup
2. The unattend.xml file in the C:\Windows\Panther folder is not tokenized after a "Deploy Image" task is run if "custom Sysprep configuration file" is specified in the task.
3. If you change the custom "Sysprep Configuration" file, you cannot Save the changes in the task until you make another change to the task.
4. As mentioned, the "Prepare for Image capture" is not striping the agent GUID as it should, now every computer I derive from this image has the same GUID.

I can get past all the three first bugs easily enough, but can someone point me towards documentation on how to properly (manually) strip the GUIDs (or reset) and do any other necessary cleanup for the 7.1 agents before imaging?

In 6.9 I used to do the following:

1. Stop Altiris Agent service
2. Stop Altiris Client service
3. Delete all files in Altiris Agent\Client Policies
4. Delete all files in Altiris Agent\Queue\<srvrname>
5. Delete all files in Altiris Agent\Tasks\Aextaskschedulerlock\
6. Delete all files in Altiris Agent\Software Delivery\
7. Delete Altiris Agent\AeXUserMonitorLog.xml
8. Delete all files in Altiris Agent\Logs\
9. Delete HKLM\Software\Altiris\Altiris Agent\MachineGuid
10. Delete HKLM\Software\Altiris\Altiris Agent\Inventory\PrimaryUser
11. Delete HKLM\Software\Altiris\Altiris Agent\Inventory\PrimaryUserRecordDays
12. Delete HKLM\Software\Altiris\Altiris Agent\Servers\<svrname>
13. Delete HKLM\Software\Altiris\eXpress\MachineGuid
14. Delete HKLM\Software\Altiris\eXpress\NS Client\MachineGuid
15. Delete HKLM\Software\Altiris\Client Service\NSMachineGUID
16. Delete HKLM\Software\Altiris\Computing Edge\Notification Server\MachineGuid

Would love to know the specifics for 7.1

Thanks!

On one of these clients, if I run "AeXAgentUtil.exe /resetguid", the clients looses it's GUID, then after a few minutes and having the client check back in, it receives the same GUID again.

Shouldn't I be receiving a new GUID after running /resetguid?

In DS 7.1, you need not to worry about agent guid, this guid is generated using client hardware info.

probably, you are using Windows Xp/2003 machine, c:\setup is created in these OS. Vista and above its under c:\windows\system32\panther

Also, check if you are getting same guid for all clients, does console displays all your client under Manage > Computers as one computer ir they are displayed identically. if the computer after deploy is displayed as differnt computer, then you need not to worry.

The same GUID issue only comes if the "Backup" image of any OS has been deployed to other hardware even its been syspreped; which is not required and recommended.

Just to do double check for my own understanding please let me know that you have done "Prepare for Image Capture" and than "Disk" image of the OS; and deployment of that same image is creating same GUID for all computers?

I have this same issue. I was running the 'prepare image for capture' task at the wrong point.

I later found out to run this task when the computer is logged in at the desktop, after that it will reboot to automation/pxe and your image can be captured and deployed.

I also found the first image u deploy is identical to the one that was captured but after that the computers all receive different guids.

i had to rebuild the referance machine and 'prepare for image capture' then go through creating the image agian.

not yet found a way to fix the ones that have been deployed already, and the ones that were all seem to receive the same tasks and mess up in one way or another.

How many computers are affected here "not yet found a way to fix the ones that have been deployed already, and the ones that were all seem to receive the same tasks and mess up in one way or another."

May be someone could provide you the solution for this issue but you will need to start a new thread for this