System Center Configuration Manager (SCCM) is an awesome instrument to take off Windows 7. Microsoft gives a lot of documentation, in certainty so much documentation that it turns out to be difficult to really comprehend what ought to and ought not be finished. To keep things straightforward, I’ll focus on an extremely basic, yet additionally exceptionally basic situation.

Microsoft supplies a lot of documentation, actually so much documentation that it becomes difficult to really understand what should and shouldn’t be accomplished. To keep things easy, I will focus on a Really simple, but also very typical situation:

Windows 7 has been installed on new hardware, or hardware that is re-used. In the procedure the entire PC is wiped clean and a brand new OS is set up.

This is describe a rather straightforward and efficient process to utilize SCCM to roll out Windows 7.

For this you’ll need:

Windows 7 venture (this the quantity license version. Even though most of the functions with retail versions too, the detection and permit issues are distinct). You do not strictly require this, but a few of the tools are actually quite helpful. The procedures explained here don’t rely upon the MDT 2010.

Standardisation is vital: attempt to prevent creating to a lot of distinct configurations. It’ll save yourself time and effort from the rollout, in addition to reduce encourage burdens if everybody (as far as you can) has exactly the same set of configurations and applications.

Set policies: if you’re able to configure some thing with group policy, then configure it like that. It’s simpler to handle and may be altered later on.

Hardware: Be sure all hardware is current, has at least 2GB of RAM. Additionally, avoid having a lot of unique versions. Additionally, hardware from leading manufacturers will probably be less painful to work with because they have better driver support.

Base picture: make the bottom image on the most elementary part of hardware (or perhaps better a VM in VMWare) you’ve got access to. Additionally, this picture should just comprise the OS, a few spots and possibly some customizations. Nothing more. Though the USMT is a superb instrument to migrate user’s settings and data it also includes a bug with a specific hotfix (which can be installed on correctly patched XP, Vista and Windows 7 servers), which demands a second hotfix on every computer, on the server also throughout the setup. In addition to this USMT is configured with XML files so this is something that demands a lot analyzing to get it to function how you want it to. If you are able to stay away from it, then maintain your sanity and do this. Every step from the procedure ought to be documented. I attempt to keep things easy, but for manageability purposes it is essential that the entire system is totally documented. I can’t stress that enough.

Production Of The Base Picture

I enjoy producing the base picture on VMware since it permits me to shoot snapshots along the way and that I will actually keep it to the host for a foundation for future pictures (for example and upgraded picture with SP1 on etc).

While the MDT supplies a job sequence to construct and catch. It is not that much more work, more elastic and contains in generally turned out to be more secure also. As stated before, I love to get this done on VMware, however, that is not a necessity. It is best to utilize the most easy hardware (preferably desktopcomputer, something without a great deal of exotic hardware requiring motorists) for it.

Throughout the range of the partition, then delete all current partitions and make NEW partition. In this last case, Windows 7 will make two partitions and this may expedite the entire procedure. It is easier with a single partition and for that you need to make it.

Follow regular installation. Don’t join to domainname. After the setup is finished, empower the admin accounts and then log in using it.

Delete the first user account that was created through the setup procedure. This is accomplished in two areas. C:programdataStart Menu comprises the “All Clients” start menu. You’ll have to remove the refuse permissions to have the ability to edit it (place them back later). Additionally edit the C:usersdefaultstart menu. This comprises the default user launch menu and everything is recorded here will likely be included for each new user that logs in. You would like to delete the shortcuts to apps which you don’t need in the start menu. Do not delete the entire folder structure! For instance: imgv1.0.txt. This could be my variant 1 picture. Why do so? This document may be inventoried by SCCM and that way you are able to run reports and determine which version of this picture is used. Whenever you make modifications to the picture, you also need to increment the model number on the picture. It is not mandatory, but really beneficial.

We’re now prepared to catch. This is the Way to make it:

Select “create activity sequence media”.

Choose “catch websites” because the media type. Click next. In the event of USB stick you are going to want a recent, fully empty USB. In the event of CD/DVD you’ll have to define where the ISO file will be saved. Click next

choose the boot picture. It should not matter if you select x64 or i386 for it. The boot image will have to have the necessary drivers to operate the network in your picture computer. For distribution stage, just select the closest. Typically, you need to be provided to conduct the capture wizard.

This wizard is really simple and simple to comprehend. Only 1 thing, where you’re asked for the route for the picture supply a full UNC path to the host AND include the picture name (use.wim as the expansion for your picture). Complete the wizard and it’ll capture the picture. This typically requires at least approximately 1 hour and entails sysprep plus a reboot. Only let it do everything. Do not touch this machine. Additionally, it is a fantastic idea to make a dedicated folder to your server especially for these OS pictures.

Establishing the OS image bundle

As soon as you’ve captured the picture you want to turn it in a real package.

Visit “computer supervisor – functioning system setup – functioning system graphics”. Select “add working system picture

supply the route towards the wim file. The document must have a.wim expansion and file name ought to be contained in the trail.

Following a Few occasions and you also have an OS image. Do not forget to replicate this on your supply factors. (no need to bring this into the PXE points in the event you’re using these. The PXE points just require the boot pictures).