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
4 comments

Enable Command Support & Distribute Boot Images-OSD SCCM 2007

To initiate Operating System Deployment and in order for machine to use WinPE Boot images, the boot images available in SCCM should be first distributed to all the available Distribution Points. The below post explains how to enable the command Prompt support and distributing Boot images.

Command Prompt support helps in troubleshooting OS deployment issues. When F8 is  pressed during the OS Deployment or capturing process, a command prompt window pops out which can be used to view the SMSTS.LOG.

Enable Command Prompt:

In the SCCM Console, go to Boot images under OSD node of Computer management. Select "Boot image (x86)" ,Click on properties from Actions menu and select the "Windows PE" tab.

Check the " Enable Command Support" ( Testing Only) to enable command prompt support. Click OK, it will pop up a dialogue box asking to update DP's.
Click  yes and click Ok.The “Manage Distribution points Wizard” will appear, click Next to continue.
When the boot image update is completed, click Close


Repeat the same steps for "Boot image (x64)" as well.

Distributing Boot Images:

After the above images have been modified, expand the boot image, right click "Distribution Points" and select "New Distribution point".

Click  Next . On Copy package wizard, select all available DP's. If PXE Service point is installed, select the SMSPXEIMAGES$ Share folders for storing these Boot images.


Click Next and click  Close to complete the distribution of the OSD boot  images. It is important to note that both x86 and x64 boot images have to be distributed even though we are  using only one kind of architecture.

Repeat the steps for X64 Boot image.
Labels:

Comments

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>
1 comment
Read more

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
6 comments
Read more

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 .
Post a Comment
Read more