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

Install and configure PXE service point

PXE Service Point:

Definition:
PXE service point is a site system role in SCCM 2007 that is used to deploy Operating Systems. This role  initiates the OSD process and responds to network PXE boot requests.

Ports used :

Client to PXE service point: 
  • DHCP- 67 and 68
  • TFTP-69
  • Boot Information Negotiation Layer-4011
Site Server to PXE Service Point:
  • SMB- 445
  • RPC Endpoint Mapper-135
  • RPC-Dynamic port allocation
Creating PXE service point:

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems, select the SCCM server where the PXE Service point has to be installed and click on new roles as shown,

Enter the FQDN of the SCCM server and click next.





2.  On the System Role selection page, select PXE Service Point.Click  Next.
When you click Next, a pop up will appear saying that "enabling this site system role will open the above mentioned ports". Click yes.




3. On PXE-General tab, do the following:

  • Check the option "Allow this PXE point to respond to incoming requests", this will allow the computers  to use this.
  • Check  " Enable  unknown Computer support" to enable  the support for computers when the computer information is not imported or discovered in SCCM.
  • Check the require password option if any password is required to start the process. Note that for unattended installation, this option should be unchecked.
  • Select the Respond to all network interfaces default option.


4. On the PXE-Database tab, specify the account to be used and the certificate creation details. Here, I am going with the default selections.
For more information on PXE-Database Account, go through the below link.
http://technet.microsoft.com/en-us/library/bb633094.aspx

Click Next and close  the wizard  to complete  the installation.





Verifying the installation Of  PXE-Service point

To verify whether the PXE Service point is installed or not, check the below logs.
Location of these logs is "Configuration Manager Installation directory\Logs"

  • PXESetup.log : Provides information about the PXE service point and is generated when the PXE service point site server has been created.Check for the string " Installation was  successful".
  • PXEmsi.log : Provides detailed information.
  • PXEcontrol.log : Tells  us whether the PXE service point is working fine or not.. Check for the string " PXE Test Request succeeded".



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

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 .