Altiris 7.1 Deploy Image Task not Sysprepping
In 6.9, I had a Deploy Image task that contained a series of .img files. I could run this task on any machine and it would image Windows 7 onto it. Not only that, but the image was sysprepped, so when it finished imaging, it was ready to login with the Administrator account already enabled.
In 7.1, when I run a Deploy Image task on a machine, it images to Windows 7 just like it should, but when it is finished and I reboot to production, it acts like it has not been sysprepped. It asks for an account name, password and product key, which should not be happening. I would like it to be like it was in 6.1, where this one Deploy Image task brought the actual sysprepped image across, with the Administrator account enabled.
Any thoughts or suggestions on this? I am not sure if I am missing a step here.
Thank you.
Comments 16 Comments • Jump to latest comment
Hello,
I have not used DS 6.9 and not sure how image is being syspreped there.
But in 7.1 & onwards there is a separate task 'Prepare for Image Capture' which essentially need to be executed on client before running create disk image task. It is applicable for both windows & Linux.
For Windows, user has to specify: OS type, Product key, user credentials & boot method.
You have to recreate a sysperped image again by running 'prepare for image capture' & then use that to deploy across clients.
I hope this will help.
Thanks,
Sachin
If this suggestion helps to resolve your issue then please mark it as Solution.
Sysprep is the same no matter what deployment tool you use. What matters with Windows 7 is,
The problem with delivering 6.9 images with 7.x appears when you have agents in the image. The 7.x agents are completely different beasts to their 6.x cousins, and do not upgrade terribly well. If you therefore have the 6.x agents installed in your image (rather than through the unattend.xml) then you will have to re-sysprep.
If your don't have the agents in your image, then I would look to your unattend xml files. It is likely something is amiss here. You can post your XML here if you'd like some help deciphering what might be going wrong.
Kind Regards,
Ian./
Ian Atkin, IT Services, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads
Thank you for the information, ianatkin.
Would I have to re-sysprep the entire image, or could I just remove the 6.9 agent, install the 7.1 agent, and recapture?
If you look at the log files in
you may find sysprep has run but, like Ian says, doesn't have an unattend xml file with sections for the passes involved, specialize, auditSystem and auditUser.
Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.
Connect Etiquette: "Mark as Solution" posts that fix your problem, thumbs up for useful
I ran the Prepare for Image Capture ask, which seemed to work. When it rebooted, applied system settings, etc, I was prompted with the Administrator account. However, when I tried logging into it, it said that the account had been disabled. Is this normal?
Disabling the built in Local Adminsitrator account is the default for Windows 7 sysprep. Normally you'd join a domain and log in with a domain account.
Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.
Connect Etiquette: "Mark as Solution" posts that fix your problem, thumbs up for useful
Here are the steps I have taken so far:
- In 6.9, I deployed an image created in 6.9 to a laptop. When it was finished, I was able to log in as the administrator normally. I removed the 6.9 agent from the laptop and made sure that the 7.1 agent was installed.
- I ran the Prepare for Image Capture task in 7.1 on the same laptop. It seemed to run fine, as it came back to apply system settings, check video performance, etc. When it came back to the login screen, the Administrator account was there. However, when I tried logging into it, it reported that the account was disabled.
- I am now running the Capture Image Task. Once this is done, I will try to create a Deploy Image task and see if I can image another machine with the freshly created image. Ideally, I will be able to login to the machine with the Administrator account.
Here is an update on what I have done:
I set up a laptop with the 7.1 agent/software, etc. and ran the Prepare for Image Capture task.
After this, it PXE booted and I ran the Capture Image task
When this was finished, it rebooted, applied some settings, and then when I logged into Windows, Sysprep opened.
I then took a PC and PXE booted, and am currently running a "Deploy image" task with the image that I just captured. I am curious as to what may happen here.
Are there any additional steps that I should have taken in order to make this work better?
You need to add a Configuration Task to get it to join the domain otherwise you won't be able to log in because the default for Windows 7 is to disable the built in Local Administrator account.
Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.
Connect Etiquette: "Mark as Solution" posts that fix your problem, thumbs up for useful
As Andy says, the default windows behaviour for Windows 7 is to disable the local administrator account. In my XML for windows 7 I always create a new local administrator account, or alternatively you could have your XML enable the disabled admin account.
As I said before, it would be useful to see the unattend XML files you are deploying your image with.
Kind Regards,
Ian./
Ian Atkin, IT Services, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads
I have a custom unattend file that enables the Administrator account.
I got the machine to image successfully. However, after my Prepare for Image Capture task, it PXE booted. That is when I sent the Capture Image.
Now when I drop that image onto a machine, it will Check Video for Performance, Install Devices for several minutes before it takes me to the login screen, where I am able to login as the Administrator. However, when the Desktop loads, Sysprep pops up and asks what System Cleanup Action I want to perform and gives me Shutdown options. I thought this part should have been done within the Prepare for Image Capture task?
Did I miss a step?
/OK -this is certainly odd. The "Prepare Image For Capture" task puts the Symantec Management Agent into a clonable state, runs sysprep and then reboots the machine.
From the fact you are doing a hardware detection (and of course have been suffering the disabling of the local admin account!!) says to us that sysprep is indeed being run. Your steps are therefore fine (from what you report here).
Can you provide your XML here so we can take a look.
Kind Regards,
Ian./
Ian Atkin, IT Services, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads
Have you been doing anything in Audit Mode with this image? One possible explaination for this is that you have been using audit mode at some point in this process and are then using Altiris to "prepare" the machine too.
You see, Windows 7 automatically runs sysprep when you start the operating system in audit mode.
Ian Atkin, IT Services, Oxford University, UK
Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads
It looks as if the unattend file was to blame. Thank you for your help guys.
More specifically, the unattend file located in: NSCap\bin\Win32\X86\Deployment
Needed to be overwritten with the correct file. This is the unattend that the Prepare for Image Capture task uses.
Would you like to reply?
Login or Register to post your comment.