How Operating System Deployment works (PXE/Media Intiated)

Here are the some of the points which  are summarized on how operating system deployment works in PXE/Media intiated.

How OSD Works on a bare metal System when Media Intiated:

1. Administrator imports the information about the bare metal system to the SCCM database using ”import computer information wizard” If you are not running SCCM 2007 on R2.SMS provider inserts computer info into SCCM Databse (for more info look at SMS provider.log)

2. Admin prepares the task sequence for installation and targets to a collection which contains bare metal machines.If you are on SCCM R2 with service pack ,you can advetise to all Unknown computers.

  2.1  When Admin prepares the TS for OS deployment ,TS provider wakes up to begin processing Task sequence addtion(more info look at task seuence log file).

SMS provider processes TS addtion information. SMSDBMON wakes up and writes .PKN notifacation file to wake up Distrubutoin manager .DP manager process the flag file and furhter process the task sequence addtion.

3. System is booted from SCCM OSD image installation CD .

Wizard retrives and displays list of avilables task sequences. OSD Install CD polls management point for list of avilable task sequence informaiton .

MP retrives assigned  poliies from SCCM Databse. Policy containing the Task sequnce advertisement return to the wizard .Admin selects which to apply.

Task sequence exectues and installs the New OS on target machine.

when the TS engine executes ,it formats the hard disk and apply operating system with Windows and network setings with Drivers and Config Mgr client installed.

How OSD Works on a bare metal System when PXE Boot Intiated:

1. If you have not configured PXE Role on SCCM server,Admin enables PXE service point on WDS Server

2 .Administrator imports informaiton about bare metal system to the SCCM Databse using import computer information wizard,If you are not running SCCM on R2.

3. Admin prepares the task sequence for installation and targets to a collection which contains bare metal machines.If you are on SCCM R2 with service pack ,you can advetise to all Unknown computers.

4.System is PXE Booted(Admin press the F12 during thesystem startup to intiate Network Boot and gets the IP from the DHCP.

System attches to PXE,PXE point intercepts call and provides boot image to begin OSD install process(more info look at wdsserver.log and pxe log)).

5.System is PXE booted from SCCM OSD installation Boot medis.wizard is displayed.

6. When Admin prepares the TS for OS deployment ,TS provider wakes up to begin processing Task sequence addtion(more info look at task seuence log file).SMS provider processes TS addtion information. SMSDBMON wakes up and writes .PKN notifacation file to wake up Distrubutoin manager .DP manager process the flag file and furhter process the task sequence addtion.

7.  System is booted from SCCM OSD image installation CD .

Wizard retrives and displays list of avilables task sequences. OSD Install CD polls management point for list of avilable task sequence informaiton .

MP retrives assigned  poliies from SCCM Databse. Policy containing the Task sequnce advertisement return to the wizard .Admin selects which to apply.

Task sequence exectues and installs the New OS on target machine.when the TS engine executes ,it formats the hard disk and apply operating system with Windows and network setings with Drivers and Config Mgr client installed.

For more information look at http://technet.microsoft.com/en-us/library/bb632767.aspx

5 Responses to "How Operating System Deployment works (PXE/Media Intiated)"

  1. nitishkolwankar@gmail.com · Edit

    Yea, PXE is not the problem but what about the boot media certificates?

    What do I do if one of my Boot Media certificates expires? How do I figure out which is the associated boot media for which I will have to create a new Boot Media?

    Reply
  2. nitishkolwankar@gmail.com · Edit

    Thanks for your reply Eswar.

    I am basically trying to write up a document to extend expired certificates. PXE Service Point date extension is easy and I have already written that part but when I started analyzing the Boot Media certificates I could not see an easy process to extend it (like PXE).

    I currently have around 10-12 Boot Media certificates for one of my site and 7 of them would expire by the end of December. Now I do not know which certificate belongs to which Boot media and how should I extend these certificates?

    (I tried checking all sources to see if we can get a Boot Media Image to Boot Media certificate mapping but there was no information about this)

    Reply
    1. you will have to extend the certificate in PXE service point and then try to create new boot media.I am not sure if there is way to extend the certificate in already created/existing boot media.
      Changing the certificate expiration date in pxe service point would also change it in registry and where ever they are registered.

      Reply
  3. nitishkolwankar@gmail.com · Edit

    When I go to the Boot Media section I see lot of Boot Media Certificates in there. Some of them are approaching expiration.

    Suppose one of the certificates does expire then how do I identify which Boot Media image ie belongs to?

    While recreating the certificate how can I be sure about which Boot Media image to select?

    Reply
    1. how many boot images do you have with certification expire ? for 1 or 2 boot images,you can simply extend the certificate expiration time.
      can u provide me more info on what you are trying ?

      Reply

Leave a Reply