Sunday, March 25, 2012

SCCM 2007 R3 OSD Deployment

Through SCCM, OS can be deployed on multiple numbers of computers simultaneously. In SCCM, operating system can be deployed on machines using PXE boot method. This method is used to deploy OS on bare metal machines. OS deployment feature can be also used to upgrade an existing OS on the system. Multiple set of customised OS images can be created. As per the requirement, different OS images can be used for deploying on a particular set of computers.

In this section, the complete procedure for deploying OS is provided. Operating System deployment consists of the following configurations which have to be carried out as given below:-
· Installation of Pre-requisites for PXE boot method
· Installing PXE Service point role on SCCM server
· Creating a separate Collection for OS deployment
· Configuration of Boot Images
· Creating Computer Association for bare metal computers
· Capturing customised OS image from a reference computer
· Creating OS image package
· Creating Task Sequence for OS image
· Advertising Task Sequence on the Collection for deploying OS



2.1 Installation of Pre-requisites for PXE boot method

For machines on which OS has to be deployed through network boot method, the following pre-requisites are required to be installed and configured:-
· DHCP Service
· Windows Deployment Service (WDS)
· Configuring DHCP server
· Client machines should have network bootable LAN cards and PXE boot should be enabled in BIOS
DHCP server should be installed and a scope should be created for assignment of IP addresses. DHCP should be present on any one server in the network and should be properly configured.
NOTE: - Do not install WDS before installing and configuring DHCP server. Check whether DHCP is providing proper IP address to client machines in the network.
The next step is to install WDS on the SCCM server. WDS should be installed on the SCCM server only. Do not install WDS on any other server.
To start Server Manager, click: Start Menu -> All Programs -> Administrative Tools -> Server Manager. The Server Manager window opens.


  • Right click on Roles and select Add Roles.
  • Click on Next on the Roles Wizard window as shown above.

  • Select Windows Deployment Services and Click Next.

  • On WDS overview page click Next.

  • On Role Services page Select all and Cick Next.

  • On Confirmation Page. Select Install.

After rebooting the computer, go to Administrative Tools>Windows Deployment Services. WDS console will open as shown above.
NOTE: - Do not configure WDS server.

2.2 Installation of PXE Service point role

PXE Service point Role is already configured as above.


PXE service point is now installed and appears in the console as shown above.

2.3 Creating a new collection for OS deployment

Create a new collection for deploying OS in SCCM. The machines on which OS has to be installed should be moved in this collection. To create a new collection, Right click on Collections and select New Collection as shown below:-





  • In the New Collection Wizard, provide a name as ‘Kalina IT – Windows 7 Deployment’ for the new collection and click on Next.

  • Do not add or create any membership rules, since all the machines will be added manually to this collection.

  • Click on OK in the pop up window which appears on the screen as shown above.

  • Click on Next in the ‘Advertisement’ option window as shown above.

  • Keep default settings in the Security options and click on Next.
  • Click on Close to complete the wizard to create a new collection.
The new collection‘Kalina IT- Windows 7 Deployment’ is created and appears in the console as shown above.
The next step is to configure boot options in Operating System Deployment in SCCM. The boot files are present and configured in SCCM console. The boot files have to be updated to the distribution points.
After installation of PXE role a new distribution point gets created.

Boot images required for the client machines for booting and to connect to SCCM server for OS deployment are pre-configured in the SCCM server. The boot images have to be updated to the distribution points on the SCCM server. Go to Computer Management> Operating System Deployment> select Boot Images as shown below:-



  • Go to Boot Images>Boot image (x86)> select New Distribution Points as shown above.

  • In the New Distribution Points Wizard, click on Next in the welcome page

  • In Copy Package window, select the distribution points as shown above. The distribution point MUMBKCSCCM002is the default server distribution point and MUMBKCSCCM002\SMSPXEIMAGES$ is the new distribution point which gets created after installation of PXE service point role.

  • Click on Close to complete the wizard.
The distribution points are now configured and appear in the console.

Also check the package status after adding the distribution points. The package status should be ‘Installed’

2.5 Creating Computer Association

Computer association has to be created for bare metal computers on which the OS will be deployed. The information of the bare metal machines like MAC address and GUID should be provided to create computer association. The computer association creates the set of computers which will be assigned to a collection. The OS image will be deployed only on the collection in which these computers are present.

Create a csv file with the list of computer names and MAC addresses as on which the OS has to be installed and save it in a specific location as shown below:-





  • To create a computer association, in SCCM console go to Computer Management>Operating System Deployment> Computer Association as shown above.

  • Right click on Computer Association and select Import Computer Information as shown above.

  • In the Computer Information Wizard, select ‘Import computers using a file’ and click on Next.
Select the CSV file.

  • This will import the information and then click on Next.

  • In Data Preview window it will display the computer information as shown above. Click on Next to continue.

  • Click on Next after providing the collection as shown above.

Click on Next on the Summary window.
Click on Close to complete the Wizard.


Go to the collection ‘Kalina IT- Windows 7 Deployment’ and update the collection membership and it will display the computers as shown above. OS deployment will take place on this collection and only on the computers which are the members of this collection.

The next step is to configure a reference computer and capture the image. A reference computer is a machine installed with the OS and all the default applications used in the organisation. To capture the image of this reference computer, a new Build and capture Task Sequence Needs to be created.


2.6 Capturing Image of Reference Computer

To capture the image of a reference computer, a capture CD has to be created in SCCM. To create a capture CD follow the below given steps:-

  • In the New Task Sequence wizard, select ‘Build and Capture a reference operating image’ and click on Next.

  • Provide a name for the Task Sequence and click on Browse to select a ‘Boot Image’ and click on Next.
Here the boot image selected is for machines having x86 architecture.

  • In Install Windows, click on Browse to select the OS image package. Select to partition and format the target computer. Provide the product key and server licensing mode. You can also provide the local administrator’s password for the target machine as shown above. Then click on Next to continue.

  • In Configure Network window, select whether the target machines should join a Workgroup or Domain. Here it has been selected to join machines in workgroup ‘WORKGROUP’ as shown above.

  • In Install ConfigMgr tab, click on Browse and select the package for installing SCCM client agent.
NOTE: - You need to create a package in Software Distribution of SCCM for ConfigMgr client agent which is mandatory before creating a Task Sequence for OS deployment.

  • In State Migration window, since OS will be deployed on bare metal machines, remove all the check marks as shown above and click on Next.

  • In Include Updates tab, as the updates will be installed after the OS is deployed, select ‘Don’t install any software updates’as shown above and click Next.

  • In Install Software tab, you can select any other application package during the setup of OS otherwise click on Next to continue.

Click Next on System Preparation screen.
Click Next on Image Properties screen.

  • Assign the path for image to be captured. And give the account details.


Click on Next in the summary page.
Click on Close to complete the Task Sequence wizard.


The Task Sequence is created and will appear in the console as shown above. The next step is to advertise this Task Sequence on the‘Kalina IT – Windows 7 Deployment’ collection.


2.7 Creating OS Image Package

To create a package of the captured OS image, go to Computer Management>Operating System Deployment>Operating System Images as shown below.
Right click on Operating System Images and select Add Operating System Image as shown above.
The wizard will open and in the Data Source window click on Browse and provide the path for the captured OS image file as shown above and click Next to continue.







In the General tab, provide a Name and Version for the image package as shown above and click Next.



Click on Next in the summary window.


Click on Close to complete the wizard.
The OS image package is now created. Now you need to add and update the distribution point.
Right click on Distribution Points and select New Distribution Points as shown above.
Click on Next in the Welcome page of the wizard as shown above.
In the Copy Package window, select the default server distribution point as shown above. Select the default Server distribution point for OS deployment.
Click on Close to complete the wizard.
After adding the new distribution point, go to Package Status and check that the status should be ‘Installed’

Task Sequence is a set of rules or parameters used for deploying the OS. It consists of the information for pre-installation parameters required during the deployment of Operating System. To create a task sequence for the OS image package, go to Operating System Deployment>right click on Task Sequences>New> Task Sequence as shown below:-

In the New Task Sequence wizard, select ‘Install an existing image package’ and click on Next.
Provide a name for the Task Sequence and click on Browse to select a ‘Boot Image’ and click on Next.
Here the boot image selected is for machines having x86 architecture.
In Install Windows, click on Browse to select the OS image package. Select to partition and format the target computer. Provide the product key and server licensing mode. You can also provide the local administrator’s password for the target machine as shown above. Then click on Next to continue.
In Configure Network window, select whether the target machines should join a Workgroup or Domain. Here it has been selected to join domain ‘PRAZ.LOCAL’ as shown above.
In Install ConfigMgr tab, click on Browse and select the package for installing SCCM client agent.
NOTE: - You need to create a package in Software Distribution of SCCM for ConfigMgr client agent which is mandatory before creating a Task Sequence for OS deployment.
In State Migration window, since OS will be deployed on bare metal machines, remove all the check marks as shown above and click on Next.
In Include Updates tab, as the updates will be installed after the OS is deployed, select ‘Don’t install any software updates’ as shown above and click Next.
In Install Software tab, you can select any other application package during the setup of OS otherwise click on Next to continue.
Click on Next in the summary page.
Click on Close to complete the Task Sequence wizard.
The Task Sequence is created and will appear in the console as shown above. The next step is to advertise this Task Sequence on the‘Kalina IT – Windows 7 Deployment’ collection.
The Task Sequence which was created in the previous section should be advertised on a collection. To advertise the task sequence, right click on the Task Sequence and select Advertise as shown below:-
The OS will be deployed only after the Task Sequence is advertised on a particular collection. You need to be very careful during advertising the Task Sequence, since it will wipe out the complete disk and install a new Operating System on the machines.
In the General tab of New Advertisement Wizard, provide a name and for ‘Task Sequence’ option, click on Browse to select the Task Sequence. Then for ‘Collection’ option, click on Browse and select ‘OS Deployment’ collection on which the OS has to be deployed.
NOTE: -Make sure to check mark the option ‘Make this task sequence available to boot media and PXE’
If you do not check mark this option then the client machines will not receive the task sequence after booting through PXE boot option. Then click on Next to continue.
In the Schedule window, click on the flower (orange)button and a new window will open.
Select ‘Assign immediately after this event’ and click on OK to continue.
Keep the Priority option as ‘High’ and set the Program rerun behaviour as shown above.
In Distribution Points tab, select the options as shown above and click Next to continue.
In Interaction window, select ‘Show the task sequence progress’ and click Next to continue.
Keep default settings in Security page and click on Next as shown above.
Click on Next in the summary window.
Click on Close to complete the advertisement wizard.
The task sequence has been advertised on the Kalina IT – Windows 7 Deployment collection. The machines present in this collection only will receive the OS package. Go to ‘Advertisements’ in SCCM console and check that the task sequence has been advertised as shown below:-
Go to the client machines and enable the PXE boot option in BIOS. Boot one client machine through PXE boot option and check the installation of the OS. Once the OS gets installed successfully then you can deploy the image on multiple computers simultaneously.
NOTE: If OS has to be deployed across two different VLANs and if DHCP server is present in another VLAN then for OS deployment to work across VLANs you need configure the switch by adding the following commands as given below: -
ip helper-address pxeServerIPAddress
ip helper-address dhcpServerIPAddress
ip dhcp relay information trusted

A stand-alone Operating System media can be created for deploying OS image which can be done without connecting the client machines to the SCCM site server.
To create a stand-alone OS media right click on the task sequence created for an OS as shown below: -
Select ‘Create Task Sequence Media’ as shown above.
A new wizard will open. Select Stand-alone mediain select media type window as shown above.
In the Media Type option, select media size and provide the path to save the .iso file as shown above.
In Security option, remove the check mark to protect media with password and click on Next.
The next window will show the properties of the task sequence. Click on Next to continue.
In Distribution Points, select the distribution points which contain the OS image and also the boot images. Here select both the distribution points and click on the Add button.
After adding the distribution points click on Next to continue
Variables for the media are not required. Click on Next to continue.
Click on Next on the Summary window as shown above.
The media creation process will begin and this will take some time.
Click on Close to complete the creation of the OS stand-alone media.

Browse to the location of the .iso file. The Windows7x86.iso file here is ready. Burn this .iso file on a DVD and check with the installation of the Operating System. This DVD is a bootable DVD hence it can be used to deploy OS on new machines also.


-------------------------------------------------------------------------------------------------------------------------




2 comments:

  1. I want to have the functionality in my task sequence that at the last step it should give a window to the administrator with all the packages listed and whatever they choose should be installed on the machine before exiting the task sequence.

    ReplyDelete

Azure Policy support for remediating tags for existing resources

Use Azure policy to remediate tags for existing resources. https://azure.microsoft.com/en-us/updates/azure-provides-at-scale-tags-managem...