Deployment Solution

 View Only
  • 1.  Capturing a SYSPREP image and redploying it

    Posted May 06, 2011 09:20 AM

     

    Capturing a SYSPREP image and redploying it

    Has anyone successfully captured and redeployed a SYSPREP image?

    The project I support has a requirement to capture an image from a Dell M6400 or M6500 Laptop with Win7 Pro, deploy that to another computer, sysprep the image on the new computer and then deploy that image to 125+ M6400 and M6500 laptops on a regular basis.

    To date I have not been successful.  I can run the sysprep on the laptop from the MS directory then capture the image and push that image back out.  But it does not set the name correctly or rejoin the computer to the domain.

    Also I have run into an issue that just capturing an image from a computer will corrupt the Agent.

    I have been working with Symantec Tech support but it is moving slow. 



  • 2.  RE: Capturing a SYSPREP image and redploying it

    Trusted Advisor
    Posted May 06, 2011 09:29 AM

    Are you trying to copy default user info using copy profile?  If so, dont boot into audit mode. this caused a lot of problems for me.  Just enable admin account and do your changes.

    Also, you shouldn't need to touch sysprep on the computer itself - use "prepare for image capture"

    if that doesn't work, I'd try same steps but don't use win7 SP1 since symantec doesn't officially support it yet (I had weird join domain issues when using SP1, but it may have been also because I was doing captures in audit mode).

    Also, how are you trying to rename computers (I'm looking for tips on this).. thanks



  • 3.  RE: Capturing a SYSPREP image and redploying it

    Posted May 09, 2011 08:46 AM

    I was finally able to sysprep, capture and redeploy an image on Friday.  This was after hours on the phone with Symantec Tech Spt.  I will post the Jobs and their task on another comment once the network is back up.  It is down for documentation.

    This was accomplished on a Dell M6400 and M6500.  I captured the image on the M6500 and redeployed it to the M64000.  There were drivers missing but working on that.  Not capturing user profiles as these computer get redeployed to different users on each exercise.

    Now I need to find an option or setting so the computer doesnt ask for the network connection location (IE: Home, Work, or Public) on first boot up and log on.

    We are using DS7.1SP1 with NS 7.1, host server is Server 2008 R2 64Bit.  Once I have fully documented all the issues I ran into I will post them. 

    But one big issue is the way it handles licenses:  any new license overwrites an older one.  You can combine them online but it will not display multiple license files, just one file.



  • 4.  RE: Capturing a SYSPREP image and redploying it

    Posted May 09, 2011 03:31 PM

    You can set the network connection location in your sysprep file. It had a bug in it prior to SP1 where it didnt listen to it but after sp1 it was fine. Depending on how many machines you have a KMS server may be easiest to manage the licenses if you only plan on having a total of 125 machines on 7 though it may not be worth it. You only need 25 machines to activate the server if you have a KMS license key. Its a little funky how it works but if you go that route the one thing I would mention is DO NOT use a KMS license key to license your OS as it will make every machine with it a KMS server that key is only for use on the server. You can find the correct KMS client key on the internet by searching google or whatever for Windows 7 KMS client key. 



  • 5.  RE: Capturing a SYSPREP image and redploying it
    Best Answer

    Posted May 16, 2011 08:48 AM

    Thanks.  The License issue I mentioned was for the Clients on Altiris Deployment Solution.  It will not add in new licenses it will only overwrite.  I had to get Symantec to combine my licenses into 1 file.  The program I support had bought licenses on 4 seperate occasions.  So if u get a new set of license to add to your existing ones it will overwrite the file and only give u credit for the new ones.  The only way around this I have found is to combine the license.  This cause the additional issue of truncating the expiration date for the new license to the date of the previous license.

     

    Anyway this is a subject for a different posting.

     

    I am able to capture and deploy a syspreped image.  But still have the issue of the systems not booting into automation or WinPE properly when I start the process.  Still working on that one.

    Also trying to find where to change the wait time on boot up selection to 10 vice 30 seconds.  Right now I have to change it on the computer after it boots but.  Somewhere in the Altiris configuration it is setting it to 30 seconds.