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

Configure a management point-Post SCCM Installation -Configuration Task 1


Management Point –Definition: 

The management point is the primary point of contact between Configuration Manager Clients and the site server. Management points can provide clients with installation prerequisites, client installation files, configuration details, advertisements, and software distribution package source file locations. Additionally, management points receive inventory data, software metering information, and status and state messages from clients.

Configure a management point:

Prerequisites:

1. IIS component should be installed.

2. Obviously, SCCM should be installed. :P

3. Enable WebDAV extension in IIS and configure WebDAV else the management point installation will fail.

WebDAV should be downloaded and installed for Windows 2008 
Use this link for WebDav Configuration.

Installation:

1. In the Configuration Manager console of the primary site server, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name> / Site Settings / Site Systems / <site system name>.

2. Right-click <site system name>, and click New Roles to start the New Site Systems Role Wizard.

3. On the General tab, you have the options to do the following:
  • Specify a Fully Qualified Domain Name (FQDN) for intranet-based clients to communicate with this site system. This configuration is recommended, but not required. 
  • Specify a Fully Qualified Domain Name (FQDN) for Internet-based clients to communicate with this site system. This option is required for supporting Internet-based client systems.
  • Select the account to install the site system files. The site server machine account is used if a Windows domain user account is not specified.
  • Enable the site system as a protected site system if required( Not enabled here in LAB) 
  • Configure communication between the site system and site server to be initiated only by the site server.




4. On the System Role Selection page, select Management point.





5. Click Next and Click Yes if it prompts to make the site system “default management point”

6. Leave the default settings. Site Database and MP's computer account are  default choices


7. On the Summary page, review the settings,click Next and close. 
Installation Of Management Point is done.


Verifying Installation of Management Point:


1. Check MPSETUP.LOG to see if the MP is installed or not.
Location: SCCM Installation Directory\Logs\ folder
The log file should look like this and “Installation was successful” should appear.
2. MPMSI.LOG- Provides complete detail and useful for MP setup      troubleshooting. 
   Location: SCCM Installation Directory\Logs\ folder

3. MPControl.log- provides the status of MP whether the MP is working fine or not. Location: SCCM Installation Directory\Logs\ folder 
The below lines should be present.


Reference:http://technet.microsoft.com/en-us/library/bb632400.aspx
4. Check for class “mssmsmanagement point” in AD “System Management" container.


Labels:

Comments

Post a Comment

Popular posts from this blog

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. ...
4 comments
Read more

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...
5 comments
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