Task copies imaged machine's Administrator profile?
Created: 25 Sep 2012 | 5 comments
In 7.1,
I configure the machine using the Administrator account. In my unattend file, CopyProfile is set to True. In theory, shouldn't this copy everything to the Default profile and then delete it?
When I capture the above image and deploy it to the other machine, if I go into C:\Users, it lists the Administrator account from the other machine along with the local Administrator account, with the old one being followed by the computer name.
In 6.9, when I used the same unattend file, it would correctly copy the profile to the Default user account, and delete the Administrator account.
Is there something different about the task that Altiris uses to Sysprep?
Thank you
Discussion Filed Under:
Comments 5 Comments • Jump to latest comment
In case anyone's curious, below is the unattend file that is used in the capture process:
Any thoughts on this?
I tried deleting the extra Administrator account on the laptop and recapturing the image, but when deploying it, it still has both the Administrator and Administrator.PCname listed.
You should take a peek at the unattend file that is on the system immediately prior to reboot and see if it has been modified. We modify the unattend file a couple of times, so don't assume what you used during capture is there on deploy. Just check on the actual system right before reboot to see if your custom changes are still present or not.
Then let us know.
Thomas Baird
Principal Technical Support Engineer
Endpoint Management - Deployment Sol
Hi Thomas,
Thank you for the suggestion. Earlier in the process, I was having difficulty getting the image to apply the configuration at all. Finally, I found out that I needed to replace the unattend file located in the following directory:
\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Deployment
Once I was able to do that, the configuration applied as it was supposed to.
When I now deploy that image, it has the same unattend file located in \Windows\Panther of the machine.
I hope that is helpful.
Tom
The way i do this since I don't want all users to have the same profile as the local admin one what i do is as follows.
1) log onto my base system as a different user with Admin rights and right click and drag the admin profile and make a copy of it.
2) I then rename it to admin - copy and change the security so it is not inherited and that only the administrators group and system have full control rights.
3) Run sysprep as usual without having it copy the admin profile to the default profile, and it is set to have the local admin log on once after the mini setup.
4) As part of my image drop job after the reboot to production task I run a log off task then run a script that basically replaces the Administrator profile with the copy I made.
This is the script.
rd C:\Users\Administrator /s /q
ren "C:\Users\Admin - Copy" Administrator
ICACLS C:\Users\Administrator /GRANT Administrator:(CI)(OI)F
A little cumberosme but it works great as long as you remember to have the admin - copy profile in your base image if you ever update it.
Would you like to reply?
Login or Register to post your comment.