Skip to main content

Software Update Management- SCCM 2012

The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1.  WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This  link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. Unde

Operating System Deployment-SCCM 2007 Step By Step Procedure

This post explains the step by step by procedure (flow) to build, capture and deploy Operating System to a bare metal machine.

It covers:

A] Preparing SCCM Server for OSD
B] Building and capturing OS image
C] Deploying Operating Systems.

There are two methods to capture OS image.
a] Using Task sequence to capture  the OS from a reference machine.(Automating BUILD as well)
b] Using Manual method.( build an operating system and then capture using SCCM)

Here, I am building and capturing the image through Task Sequence. And also not using any USMT to migrate data since it is a plain bare metal deployment, not an upgrade.

A]. Preparing SCCM Server for OSD:

1. Install WDS server role
WDS
2. Install and configure PXE service point.
PXE Service Point
3.General Supported Configurations.

4.Create and set Network access account. 
5. Create and distribute the Configuration Manager 2007 package, all the relevant KB updates as packages.
This post helps to create the SCCM 2007 Client package:

In the same way, KB977384 - Advanced Client Hotfix and other hotfixes can be packaged for deploying to the client.

6.Enable Command support and distribute Boot images to Distribution Points.
   Link

B] Building and capturing OS image

1. Source Files and Image folder structure:

In order to build a machine, we would need the Operating System source files that we want to deploy. Get the  Source files and copy it to a shared folder.. preferably on SCCM server itself.
Create another shared folder for storing the captured image after the build is complete. An example folder structure that I have created in the LAB environment.

\\SCCM1\OSD_Source\Windows7\ - Consists the Source files for Windows 7 OS and it is shared folder.
\\SCCM1\OSD_Deploy\Windows7\ - shared folder that will store the Windows 7 image files( WIM file) once the capturing is  done.

2. Adding the Operating System Install Package:


To build a reference machine with the Windows 7 Operating System, we need source files. So copy all the files and folders of Windows 7 content to \\SCCM1\OSD_Source\Windows7 shared folder.

The below steps explain how to add the Operating System Install Package:

a] In SCCM 2007 Console, go to "Operating System Install Packages" under OSD node of the computer management. Click on "Add Operating System Install package".

b]On "Data Source" tab, enter the shared network path where the source files are present as shown in the below screenshot. Click Next.




c] On  General tab, enter the name, version and comments. Click Next, review summary and click on close to complete the wizard.



3. Distributing the Windows 7 Install Package:

a] In SCCM 2007 Console, go to "Operating System Install Packages" under OSD node of the computer management. Expand the previously added Windows 7 Install image and select Distribution points.

b] Click on " New Distribution Points' , click next on the Welcome screen. On the "Copy Package" tab, select all the available applicable DP's. 

c]Click Next and click close to complete the wizard

**Note that the SMSPXEIMAGES$ Share should be used only for Boot Images and  not for any other software packages.**




4. Creating a task sequence to "Build & Capture Win7 Reference machine"

Please follow the steps in this link to create the task sequence for build and capture of the Windows 7 Reference machine.

After the creation of the task sequence following the steps in the above link, the next thing that has to be done is advertising the task sequence to computers.

5.Advertise the task sequence to Unknown Computers

This OSD specific advertisement will run when we boot a machine to get this advertisement. If PXE Service point is installed, it will automatically fetch the OS image through network boot.
This post explains the step by step procedure to advertise the Task sequence to Unknown Computers.


6.Boot the reference computer:

As PXE Service point is already installed and DHCP is configured, just boot the reference computer. Just make sure that the reference computer is on the same network. 
The steps and the process to capture the image is detailed in this link.

OK,now the OS image is finally captured and is waiting to be deployed.

C] Deploying Operating Systems

The OS Reference image is successfully created and is available to be deployed to the clients.We can further customize by adding other software applications and drivers into the OS.

1. Create OS Image Package:


a] Open the SCCM 2007 console and navigate to Site Database / Computer Management / Operating System Deployment, from the actions menu. Click on “Add Operating System Image”.

b] On the “Add Operating System Image Wizard” , Data Source Tab, enter the Network path for the WIM image that is created.
Here the path is \\SCCM1\OSDeploy\Windows7.wim
Click Next to continue

c] On the General Tab, enter the appropriate name and the version.


Click Next  and click close to complete the wizard.

2. Distributing the image to DPs:

a] Expand  the newly added Operating System Image " Windows 7 Ultimate-32 Bit", go to Distribution Points>>>> Click  on "New Distribution points" from the Actions menu.

b] On the New Distribution wizard, click next on the welcome screen then on the "copy package"  tab select the applicable DPs.
Note that SMSPXEIMAGES$ Share is only for Boot images and not for other OS or software applications.


c] Click Next and click Close to complete the wizard.

3.Creating a Task Sequence to deploy Operating System:

To create a task sequence to deploy OS, follow the steps from this link.

4.Advertise the task sequence to Unknown Computers

This OSD specific advertisement will run when we boot a machine to get this advertisement. If PXE Service point is installed, it will automatically fetch the OS image through network boot.
This post explains the step by step procedure to advertise the Task sequence to Unknown Computers.

Once it is  advertised, boot a new machine that is on the same sub-net.  
The booted machine will download  the boot file , install OS ,software and joins the computer to domain as specified in the Task  sequence.
We can also use scripts to rename the computer using a Task sequence variable.

For troubleshooting OSD Task sequence issues, check SMSTS.LOG


Comments

  1. Hi Santosh, I find this post very useful for the deployment of 70 machines at our company. Thank you so much.

    Dhananjay Naldurgkar
    IT Manager
    ITAD Group, Pune

    ReplyDelete
  2. Hi Santhosh,

    Great post, but you still need to update the blog by providing more information about Advanced Deployment like using ZTi & LTi. And troubleshooting steps.

    Thanks for your future post.

    ReplyDelete
  3. Thank you so much for this wonderful article really! Please Visit:

    sccm implementation
    16 bit applications
    application packaging

    ReplyDelete
  4. Thanks for this blog. I have found some interesting blogs on google. You can check these blogs also which are related to technologies…..
    Avast Login
    garmin.com/express
    avg login
    bullguard login
    mcafee.com/activate

    ReplyDelete
  5. Wow very nice post from you. I like this and its really sharable content and great as well as. Get know of me . Office Login Must go on this link for the support help regarding the Microsoft office.

    ReplyDelete

Post a Comment

Popular posts from this blog

Registering SPN for SQL Server for SCCM

If using a domain account to install SQL server 2008 R2 for SCCM, you have to register a SPN (Service Principal Name) in Active Directory for that domain account. Two SPNs for the account should be registered,     1. For NETBIOS name of the SQL Server     2. For the FQDN of SQL server. The procedure to do that is as follows 1. Log on to a domain controller; open a command prompt with administrative privileges. 2. Type the below commands replacing SQL server name. setspn –A MSSQLSvc/< SQL Server NETBIOS name >:1433<Domain\Account> setspn –A MSSQLSvc/< SQL Server FQDN >:1433 <Domain\Account> 3. As shown in the below screenshot, the server name here is  CM2012 for NETBIOS name and CM2012.CONTOSO.COM 4.  Verify the registration of SPN by typing the below command Setspn –L  <domain\account>

Consistency validation for SQL Server registry keys failed error -SQL for SCCM

During installation of SQL server, "Consistency validation for SQL Server registry keys failed” error pops up in the below scenarios. 1.   Previous installation of SQL exists. 2.   Inappropriate permissions on the registry keys of Microsoft SQL server. Solution that worked me is explained below. A. Identify the issue: 1. Go to %Program Files%\Microsoft SQL Server\100\SetupBootstrap\Log\”date  and time of installation” 2. Search (in Detail_GlobalRules.txt) for lines containing the following string "Could not fix registry key" 3. Run “regedit”, s et full control permissions for the appropriate registry keys mentioned in "Detail_GlobalRules.txt" file. Re-run the installation. B. Modifying the registry: 1. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry. (To open registry, run “regedit”) 2. Right click and go to Permission 3. Click on Advance tab and c heck the below options.     i. Include i

Checking MSXML Version

Below steps explain on how to check the version of the MSXML 1.        Go to Run , type “%windir%\System32” 2.        Search for the dll file “msxml(NUMBER).dll”, right click on it and select properties. (Where number= the version ,   check for the highest number available in system32 folder) 3.        Click on Details tab, it will show the version of the MSXML. Here, the product version is 6.30.7601.17988. The minimum MSXML version should be 6.0.3883.0 for SCCM .