Windows 7 sysprep

Permabanned
Joined
28 Dec 2009
Posts
13,052
Location
london
What is the recommended way to do a corporate windows 7 image. I was reading this from microsoft. http://support.microsoft.com/kb/828287

I was going to sysprep the installation after copying over the default profile but now I see that it is not supported, this creates additional work for myself. Now all of the auto configuration has to be done with scripts. I was going to use clonezilla and pxeboot and after syspreping it. We don't have sccm and using group policy to and login scripts to do auto configuration would mean that users would have to wait on first login for all the software and scripts to run. Very amateur. The other way which seems like a purposelly poorly designed ui. http://theitbros.com/sysprep-a-windows-7-machine-–-start-to-finish This seems like the approved way but it is also rubbish because you don't know if it has worked until after the installation is complete. This means that we either deploy an image that is not support by microsoft or spend hours testing the auto configuration via the itbrosmethod or have users wait 30 mins on first login.

I will probably end up just copying over the default profile. What do you think?
 
I use this:
http://www.fogproject.org/
To deploy images which are stored on the server itself. A client machine is pxe booted registered with the fog server, the image is deployed, the machine will change its hostname to the name registered in the fog server and then automatically join the domain.
 
Sorry to hijack, but is SCCM free for VLK customers? I've only just spotted it in the downloads list and mentions it doesn't need a key. If i decide to use it do we have to add it to what we pay for in the licensing at the end of each year?
 
I do not think that SCCM is free. But MS licensing makes little sense to myself. Have to ask someone with a certification in Microsoft licensing.

I doubt that i will be able to convince the people i work with to use fog because it runs on linux.

I tried to sysprep a windows 7 machine with an unattended.xml that added the pc to the domain automatically after manually specifying the computer name and the pc won't boot, just loops.

For the people that used WDS and MDT did you have to manually configuring each pc. Based on MS recommendations, on deployments with less 100 pcs, they recommend manually installing each pc and configuring it manually. LOL.

http://technet.microsoft.com/en-us/library/dd919185(WS.10).aspx
 
The unattended xml files can be a bit funny, it took me quite awhile to configure one which worked with my images.
 
I tried to sysprep a windows 7 machine with an unattended.xml that added the pc to the domain automatically after manually specifying the computer name and the pc won't boot, just loops.

For the people that used WDS and MDT did you have to manually configuring each pc. Based on MS recommendations, on deployments with less 100 pcs, they recommend manually installing each pc and configuring it manually. LOL.

The way i did it is install my reference machine with Office & everything else i wanted. Then imaged it using MDT.

Then deployed it via MDT & had it join the domain etc, all i have to do when PXE booting is specify a machine name.

I followed a tutorial when doing it I'll try to find it.

Edit:

This was one of the tutorials i used.
 
Last edited:
Sorry to hijack, but is SCCM free for VLK customers? I've only just spotted it in the downloads list and mentions it doesn't need a key. If i decide to use it do we have to add it to what we pay for in the licensing at the end of each year?

SCCM is not free, but it doesn't require a key when installing :)

Assuming you are on an enterprise agreement then yes you would need to declare it come trueup time.

You need a license for each Primary site server (secondary sites however you don't have to purchase a license for), which will also involve a SQL license somewhere (either bought as part of 'SCCM with SQL' product, or by using a seperate licnese altogether).

You then need either Client or Server cals depending on what your managing with it.

A little info here http://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-pricing-licensing.aspx
 
If you want to use WDS then I would suggest creating a thick image. You can still copy the default profile in windows 7, you just use a different method. Download WAIK, and use WSIM to create an unattend file to copy the default profile.
 
I have managed to get sysprep to prompt for computer name only and just testing auto join of domain. After I have got the sysprep to work I am going to try and create an image with clonezilla and try to pxeboot with that. Then I am going to create a default network profile using a method that is probably not supported, but i don't care :D

lets hope it works...
 
What is the recommended way to do a corporate windows 7 image. I was reading this from microsoft. http://support.microsoft.com/kb/828287

I was going to sysprep the installation after copying over the default profile but now I see that it is not supported, this creates additional work for myself. Now all of the auto configuration has to be done with scripts. I was going to use clonezilla and pxeboot and after syspreping it. We don't have sccm and using group policy to and login scripts to do auto configuration would mean that users would have to wait on first login for all the software and scripts to run. Very amateur. The other way which seems like a purposelly poorly designed ui. http://theitbros.com/sysprep-a-windows-7-machine-–-start-to-finish This seems like the approved way but it is also rubbish because you don't know if it has worked until after the installation is complete. This means that we either deploy an image that is not support by microsoft or spend hours testing the auto configuration via the itbrosmethod or have users wait 30 mins on first login.

I will probably end up just copying over the default profile. What do you think?

How many workstations are you talking about here?
 
SCCM is not free, but it doesn't require a key when installing :)

Assuming you are on an enterprise agreement then yes you would need to declare it come trueup time.

You need a license for each Primary site server (secondary sites however you don't have to purchase a license for), which will also involve a SQL license somewhere (either bought as part of 'SCCM with SQL' product, or by using a seperate licnese altogether).

You then need either Client or Server cals depending on what your managing with it.

A little info here http://www.microsoft.com/systemcenter/en/us/configuration-manager/cm-pricing-licensing.aspx

Thanks,

I'm having trouble understanding exactly what it is that needs to be licensed though, i understand the $579 cost of system center configuration manager 2007r3 but i don't understand what the MLs are for..... i keep reading it as if they're talking about each individual client on a network but i'm sure it can't be that as it'd be a ludicrous cost.

If i'm simply running SCCM to manage windows updates, software deployment and OS deployment what other costs are involved? I'm assuming i have to install the client software on each PC on the network, correct? (as of this setup i'm completely new to SCCM so it's a bit of a learning curve over the individual WSUS/WDS etc. facilities i was using previously.
 
Thanks,

I'm having trouble understanding exactly what it is that needs to be licensed though, i understand the $579 cost of system center configuration manager 2007r3 but i don't understand what the MLs are for..... i keep reading it as if they're talking about each individual client on a network but i'm sure it can't be that as it'd be a ludicrous cost.

If i'm simply running SCCM to manage windows updates, software deployment and OS deployment what other costs are involved? I'm assuming i have to install the client software on each PC on the network, correct? (as of this setup i'm completely new to SCCM so it's a bit of a learning curve over the individual WSUS/WDS etc. facilities i was using previously.

Yup you need a CAL/client license for each machine you are managing.

We used to license it by having the 'desktop pro' bundle package in our enterprise agreement.

Worked out at £150 per machine I think and that got you Windows and Office Pro software (on SA so up to the current version), as well as your cals for Windows Server, SCCM, Exchange and Sharepoint.
 
Interesting thing here then is that as an educational site we are on the new microsoft volume licensing cost scheme where by you pay per FTE rather than by client

I wonder how SCCM prices will work out on this basis.
 
Well I guess same as how you would license Exchange, Server etc :)

Best thing to do is jsut speak to your reselelr/account manager and see what their line is. Might not be right, but it's a start :)
 
Well I guess same as how you would license Exchange, Server etc :)

Best thing to do is jsut speak to your reselelr/account manager and see what their line is. Might not be right, but it's a start :)

Aye i think i'll do that.......got to try and remember who we renewed our VLA through now :p

I've spent the better part of 2 days going through the WSUS part of the setup with a fine toothcomb, configuring it as well and in as much detail as possible so it'd be a bit of a kick in the teeth to find out we can't afford it :D
 
Back
Top Bottom