Upgrade to Windows 7 With SCCM, the simple way

SCCM is an excellent tool to reveal Windows 7. Microsoft provides a large degree of documentation, in reality a huge amount of documentation so it becomes hard actually understand what should and may stop done. To stay things simple, I'll think about a simple, but additionally quite typical scenario:

Windows 7 is a component of new hardware, or hardware that is certainly re-used. During this process the complete PC is wiped neat and a good solid OS is installed. I'm not taking care of data migration. I'm certainly working on the assumption that most of results are copied to your network (by reason of roaming profiles or folder redirection).

Here is explain a reasonably basic and effective solution to use SCCM to reveal Windows 7.

For this you will want:

1. Windows 7 enterprise (this the amount license version. Alot of of that works in concert with retail versions likewise, the activation and license issues differ ).



2. a working SCCM installation (you should use PXE boot points, etc but I cannot enter into details ways to set this up)



3. Microsoft Deployment Toolkit 2010. You are able to download this from Microsoft. You do not strictly need this, however some belonging to the tools tend to be quite useful. Particularly explained here usually do not rely on the MDT 2010.



4. The required drivers for everyone hardware



5. All software installation packages ready and tested.

When doing Windows 7 rollouts, maintain your following under consideration:

1. standardisation is vital: avoid creating to most different configurations. It should not waste time as well as inside the rollout, and reduce support burdens if everyone (wherever possible ) gets the same set of two applications and configurations.



2. group policies: if you possibly can configure something using group policy, configure it because of this. It is actually advisable manage and will be changed at some point.



3. hardware: guarantee all hardware is recent, has no less than 2GB of RAM. Also, avoid having just too many different types. Again, standardisation is essential. Also, hardware from major manufacturers would be safer to use like they have better driver support.



4. base image: create the beds base image on the most elementary component of hardware (a beachside lounge chair a VM in VMWare) you need to get. Also, this picture should only have the OS, some patches and even some customizations. No more.



5. User state migration. Even though the USMT is a superb tool emigrate user's data and settings furthermore, it includes a bug by using a particular hotfix (and that is set up on properly patched XP, Vista and Windows 7 machines), which requires another hotfix on each computer, on the server and through cellular phone. Beside that limitation USMT is configured using XML files thus, making this whatever demands a lot testing to obtain it to get results how you would would like it to. If you possibly could cure it, preserve your sanity and achieve that.



6. documentation: Any change you will be making for the default image must be documented. Each step along the way has to be documented. I aim to maintain things simple, expressly manageability purposes it can be crucial the whole product fully documented. I cannot stress this enough.

Creation of your base image

I like creating the beds base image on VMware simply because it allows me to try snapshots as you go along and so i may well make it on the server to provide a grounds for future images (like and updated image with SP1 on etc).

While the MDT behaves as a task sequence to develop and capture. I like the subsequent method. It's not necessarily too much more work, more flexible possesses in generally shown to be more stable in the process. As pointed out, I prefer use this on VMware, that is not just a requirement. It's better to make use of the most straightforward hardware (preferably desktop, something wthout using number of exotic hardware requiring drivers) in this.

1. Install Windows 7 from installation media. Throughout the range of the partition, delete all existing partitions that NEW partition. Would not have the installer create the partition for your needs (by deciding on the free space to set up ). In that , last case, Windows 7 can create 2 partitions as well as complicate the full process. It's simpler with one partition and with you might want to create it.



2. Follow normal installation. Usually do not join to domain. Right after the installation is done, encourage the admin account and join to it.



3. delete the primary user account that is created within established process.



4. install security updates, service packs etc.



5. If required, clear a symptom menu. It's done this way by 50 percent places. c: programdataStart Menu has the "All Users" start menu. You must take off the deny permissions to enable you to edit it (stick them back afterwards). Also edit the C: usersdefaultstart menu. This offers the default user start menu and whatever shows up here will undoubtedly be included for each new user who logs in. You intend to delete the shortcuts to programs that you do not want with the start menu. Don't delete all of the folder structure! To illustrate look plan to take off the shortcut for "Windows Media Center", "Windows fax and scan" etc.



6. Create a text file within the Windows folder. Like: imgv1. 0. txt. This is my version 1 image. Why this? This file are usually inventoried by SCCM knowning that method for you to run reports and then determine which version of one's image is utilized. Should you make changes for the image, it's also advisable to increment the version number on the image. It certainly is not required, but invaluable.

We are actually prepared to capture. For this we utilize the SCCM capture disk. That is the way to form it:

1. login to SCCM, and open the ConfigMgr console.



2. right-click "task sequence" under Computer Management - Operation system deployment. Select "create task sequence media".



3. select "capture media" as the media type. Click next.



4. select whether you will need a CD/DVD or USB stick. In the instance of USB stick you will want recent, completely empty USB. In the case of CD/DVD you've got to specify in which the ISO file are going to be stored. Click next



5. Select the boot image. It shouldn't matter whether you decide on x64 or i386 for this particular. The boot image should have hidden drivers to perform the network onto your image computer. The use of VMware, the product quality boot image as it would be forwarded to SCCM works all right. For distribution point, just choose the closest.



6. Next, once or twice you'll also find a CD (or USB stick). You might be VMware, mount the ISO file (like it absolutely was a CD), otherwise, insert the disk into the image PC. Normally, you must be accessible to run the capture wizard.

This wizard is actually comparatively basic easy to recognize. One thing, what your address is sought after the way with the image gives a full UNC route to the server Including the look name (use. wim as the extension for your image). Obviously produce a username and password with usage of the share on the server. Finish the wizard and will capture the picture. This typically takes not less than about An hour and involves sysprep including a reboot. Just allow it to needlessly do its thing. Don't touch the device. It is equally aware of build a dedicated folder on the server especially these OS images.

Creating the OS image package

After you've got captured the picture you must transform into a true package.

1. go to "computer manager - operation system deployment - main system images". Select "add the gw990 image



2. provide the road to the wim file. This will a UNC path. The file ought to have a. wim extension and file name ought to be part of the path.



3. next next a few times and an OS image. Remember to replicate this for your distribution points. (no reason to add this within the PXE points if you're using those. The PXE points simply need the boot images).

Creating a job sequence

Now we're also reaching to crucial part: introduction of the position sequence to run the look. The MDT manual instructs one to create an MDT taks sequence which is certainly very and handle a truly great deal of scenarios. It is usually challenging to understand and troubleshoot if you do not actually know very well what each step does. Hence, I like to prevent it simpler simply because it will make it a lot quicker to troubleshoot.

1. under "computer management - operation system deployment - task sequences". Right click "new - task sequence". Don't use the "create Microsoft Deployment Task sequence" (it can be done down the road, when you're a player at task sequences).



2. Select "install and existing image package".



3. Give it a reputation: "standard Windows 7 deployment". Give a meaningful comment explaining what this program.



4. select the boot image. More often than not the built-in SCCM boot image is fine fine. You must discover the same architecture as the image that you are installing. Any time you captured a x64 image, make certain to purchase a x64 boot image additionally. The boot image needs the drivers for network and disk (SATA) or rrt's going to fail. Existing one contain SCCM works fine generally brand hardware and definitely will only supply you with problems when you've got something really new. There are out subsequently in testing if it works or. Click Next



5. Select the graphic. It's adviseable to specify the license key of course, if you need to test an administration password you could should you because well. (you could change all of these settings afterward additionally ). Click Next



6. Here yourrrre able to join to somewhat of a domain, so specify where you can add the account and specify a account to attend the laptop. Best practise is to try to add isn't even close to account from a an OU that's got all require policies assigned (the last OU as they say ). You should never improve the overall "computer" folder, that may be a legacy folder that with a modern Active Directory installation has to be empty. Towards the user account, components an admin account. Be certain to result in a dedicated account that merely has the essential permissions to incorporate computers to AD but doesn't even need permissions to login to any machine. Click Next



7. Select mobile phone package for those SCCM client. (any time you dont' have this package you have got to create it. However installing SP2, R2 or R3 on the SCCM server will likely create this package. ) Click next.



8. uncheck lots of capture check boxes. This is certainly only run for those who would advertise this sequence to existing computers. This involves purchasing testing and is also away from scope of things am aiming to do here. Click next



9. Select "don't install any software updates". This may occasionally seem contradictory, but it surely actually can certainly make the build faster (also likely your overall settings for updates wouldn't work together with this anyway. ). Ensure the updates are installed shortly after the build is done though. Click Next.



10. Select the technology you'd like installed. It is easy to only select programs which happen to have the tick box ticked for "Allow this method to get installed from your Install Software task sequence without having to be advertised" and will run even if an individual is logged in or otherwise. Click Next



11. Click Next. The responsibility sequence is currently created.

Right-click the job sequence and choose EDIT. You might want to watch a fairly short task sequence but it will be rather clear what the items actually does.

The belongings in bold are group entries and begin doing anything themselves. However, you may disable all tasks inside a group by disabling the group entry. More useful that you may have group entries run dependant on particular conditions. By way of example, you could potentially result in a friends called "laptop software", under options squeeze in a condition this should only apply on laptops (the industry chassis type) and add all laptop specific software in that particular section. Similarly you should utilize that install software to particular type of hardware, computers in a very particular subnet (regional differences), etc. It's extremely powerful, in the vicinity of scope want to know ,, but by making use of groups and scenarios you could set up a task sequence that could address most situations.

Another thing to remember would be the following: the "Setup Windows and ConfigMrg" installs the SCCM client. Following that, your OS is extremely beneficial for installed and for that reason the system installation actions should come following this point.

Deploying the job sequence

Let's buy this onto some type of computer.

Again, I'll focus on the easiest way:

1. create a different collection. I think of it as "image deployment", nonetheless, you can it is known as whatever you fancy. Ensure it's empty.



2. select the job sequence and advertise it to this very collection. You can take an important advertisement nevertheless, you before you decide to. Whether it is not mandatory you'll really need to select it all through the build process (that is definitely an extra step). It's useful should you have multiple task sequences (including during testing). Otherwise, as the reveal starts, it's best to allow it to be mandatory.



3. right click "computer management - the gw990 deployment - computer association" and choose "import computer information". You'll need the MAC address or GUID in the computer and include it with your collection notebook created.



4. right click "computer management - operating-system deployment - task sequences" and choose "create task sequence media". Select create "bootable media" and refer to the instructions.



5. Boot this new PC aided by the task sequence media or USB stick. Whenever the advertisement is mandatory it ought to be completely unattended. After about 30-45 min you need to have a completely built PC.

Further refinements

1. you might use a PXE boot point. Itrrrs likely that, you don't need to make task sequence media, nevertheless, you will surely have to find "Make this sequence there to boot media and PXE" when advertising.



2. use the "unknown computer support". For this particular you encourage the "unknown computer support" from the PXE point settings, and advertise the process sequence to your "unknown computers" collection. So, you will end up asked use a PC name.



3. you changes the setting picture rrnside your boot image to something branded to your computer. It's not necessarily much, yet it is cool nonetheless. You can discover the establishing the properties on the boot image. Yourrrll make a bmp type file.

All from this should purchase your started. It is employed to discover how to use conditions within your task sequence. There's a lot of web data in regards to the hardware that may be provided within installation which could be previously used to further refine your installation. I'll address that within a future post, however it is not difficult enough to search out by Googling it.

In case you wonder how much the MDT 2010 is employed for. Well, for example nobody has SCCM with their environment. So, in addition to Windows Deployment Services, MDT might be a solution in those cases. MDT can also be useful if you want to pass through specific information for a build process. This is very important when for instance creating complex sequences that want to pay regional and language differences, language pack installations etc. MDT may also be employed to create OEM builds.

I've experimented with keep things as fundamental as possible. This walk-through provide the picture and also anyone to do the installation for the machine and also that within a a small number of hours. Possibly you may need a wide range of customizations and all in your task sequence.

.