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

Create a task sequence to "Deploy Windows Operating System"

The below post explains the steps to create a Task Sequence for Deploying Windows 7

1. In the SCCM 2007 Console, navigate to Site Database / Computer Management / Operating System Deployment and right-click the Task Sequences node and select New – Task Sequence.

2. On the New Task Sequence Wizard, in the Create a New Task Sequence screen, select Install an existing image package and then click Next.


3. Task Sequence Information: On this screen, enter the appropriate task sequence name, comments and select the Boot Image that has to be used. Here, I am deploying 32 bit OS and I have selected X86 boot image as shown. 
Click Next to proceed.


4. Install Windows : On the Install the Windows Operating System screen, at the Package field, select Browse.Select the Operating System Install Package i.e. Windows7 32 Bit OS 1 en-US ( here).

On the Edition field, use the drop-down to select image :  1-Windows 7 or appropriate edition.

Product key can be entered later and this can be left empty.

Select the option Always use the same administrator password ; enter and confirm a password.
Click Next to continue.


5. Configure Network: On this screen, select Join a Domain and Click on Browse to select the domain( here it is contoso.com). 
Considerations:
  • Don't use in-built containers
  • Use OU's instead of containers like "Computers"
  • Leave the OU field blank if you are not sure, it will add the computer to Computers container.
Here, I have created a  separate OU named " OSD Computers". I have entered this in the field of OU.




6. Install ConfigMgr: On this tab, click on browse and select the Configuration manager 2007 Client package that was created previously as per this link.



Click Next and uncheck the capture user setttings on the state migration tab since it is not an upgrade but a bare metal deployment

7. Include Updates : On the Include Updates in Image screen, select Don’t Install any Software updates and click Next.

Note: Unless the Software Update Point role has been installed, and Software Update deployments and packages have been created, the Install Updates task will not do anything.

8. Install Software: On this screen, click on the yellow star button to add software packages if needed. Here, I am adding KB977384 Package as part of the task sequence. Other packages or organization specific or custom softwares can be added here in order to customize the OS.



Click Next, Next and click on close to complete  the Task sequence wizard.

The task sequence is now created and we need to make some minor modifications to this task sequence to suit our requirements.

Editing the Task Sequence:

1. In the SCCM console, select Task Sequences and locate the task sequence just created in the Details pane. 
2. Right-click the task sequence Windows7 OSD and select Edit.
3. In the task sequence editor, select the task: Partition Disk 0 and in the Volume section, highlight the Default (Primary) volume and select the Edit button.

4. On the Partition Properties screen under Formatting Options, check the box: Quick format and then click OK to save it.





The next task is to  advertise the Task sequence to unknown computers.

Comments

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

Collection query to find Machines--based on GUID Criteria

You can use the below SQL query to create a new collection based on GUID. select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SMBIOSGUID = " 18764D56-C91F-83A5-51FB-4AD4B6699D04 " Replace the GUID with the one that you intend to delete. This is particularly useful when performing OSD related tasks. To know how to create a collection , go through this link .