This project is read-only.

Windows 7 Deployment Wizard


I created this website to allowing any system admin to deploy the Windows 7 image at their own speed.15_thumb1

This website is still a work in progress so new features will be added as I have time.

Website Directions:

Go to (Website)

Once there you will see this at the top of the screen (Figure1)

Enter the machine name exactly as it is spelled. 2_thumb

Then chick submit, it will change to “Processing Please Wait!” and the block with become transparent gray (Figure 2)

After 30-60 seconds you will get something like this (Figure 3) if the machine name exists in SCCM .3_thumb

If you do not get figure 3 please see SCCM Error section below.

Notice the “Is Client Obsolete”, It should say No.

If a machine is found to be obsolete you will get a warning message to contact an SCCM admin like in (Figure 5).


Note: Please contact your SCCM team and they will remove the duplicate entry causing the obsolete recorded.

Obsolete records should be deleted every night at 12am so the only time you should see this is if you reimage a machine more than once in a 24 hour period.5_thumb

Once you get the above screen ( Figure 3), select the OS you want deployed to the system and click deploy.

You will notice the Deploy button changed to Processing, Please Wait! and the block with become transparent gray (Figure 4)

After about 15-30 seconds you will get a window on the right side of the screen. (Figure 6)


Once the counter hits “0” the screen will refresh and you can add your next machine name. (Figure 7)


The whole thing should look like this when it is completed.


SCCM Error

If the machine doesn’t exist you will get a screen like this. (Figure 8) If you get this screen check the name and try again. If you get this screen again you can try the regular PXE Boot Process.


What is this website doing?

This website console uses the Deployment Webservice that do the following in the background:

  1. Checks the SCCM Database to see if the machine name you entered exists:
    1. Checks to see if it is valid or obsolete
      1. If it finds that the first entry is obsolete it try’s the second find with the same name.
      2. If it is found valid (not obsolete) then it continues
  2. Next it allows the admin to choose what OS to deploy
    1. This is done though a pre defined list of OS’s
      1. These connect to predefined Collections in SCCM 2007
  3. Next it adds the machine to the correct collection associated with the OS deployment you choose
  4. Next it check to see if the machine needs the PXE deployment cleared and clears if needed
  5. Lastly it send a refresh to the systems machine policy via Roger Zanders SCCM Client Center automation dll via one of Maik’s Deployment Webservices
    1. This causes the deployment to kick off as soon as possible instead of waiting 90 minutes for a policy refresh.
    2. This step only works if the machine is turned on when the wizard is run.

Last edited Oct 16, 2011 at 6:06 PM by Chrstauffe, version 2


No comments yet.