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

Installation Of SQL Server 2008 R2 for SCCM 2007

The below post explains the steps to install and configure the SQL server for the SCCM 2007.

Pre-requisites for Installing SQL server

 * Decide whether to install it using a domain account or a local account.
* Reboot your machine prior to starting the SQL Server installation process to make sure that you do not have any pending reboot requests which will block the SQL Server installation process.
* Install Dotnet 3.5 SP1 and Windows Installer 4.5
* Create Service Accounts in the Domain: Here it  is contoso\SQLSA

SQL Download Link and supported configurations link

http://www.microsoft.com/en-us/download/details.aspx?id=8158

http://technet.microsoft.com/en-in/library/ee344146.aspx

Installation :

Initiate the SQL media setup.exe .Select "New Installation or add features to an existing installation"  and click  on "run" when a  pop-op window opens.

It will check for the setup support files and show up the status for those support files.




Check for any issues and if the status is fine,Click Next and select "Setup Role" as "SQL Server Feature Installation"





Click  Next to go to "Feature Selection" and select 
* DataBase Engine Services
* Reporting Services
* Management Tools

Choose the Drive where to install it( C or D drive)



It will then check for the rules and provide a status report of these rules.



Next is Instance Configuration, select the " Default Instance". Leave the Instance ID default and change the root directory to the desired drive.


Review the Disk Space Requirements.


Click Next, provide the SQLSA( service account created for SQL earlier in AD) and password. Change the  Startup type to "Automatic" as shown.


In DataBase Engine Configuration, retain the default authentication mode of "Windows Authentication mode" and current user, multiple users can be added by clicking on add.


Click Next, on Reporting Services Configuration ,retain the default "Native Mode"


It will again check for rules and to find out if anything will block the installation.


Click Next, it  will take approximately 15 to 30 minutes depending on your server configuration to install SQL. Once installed, click close and you are ready to go for SCCM.


Labels:

Comments

  1. Unknown24 August 2013 at 12:20

    Hi,nice Installation method for Installing SQL Server 2008 R2.Thanks.....

    -Aparna
    Theosoft

    ReplyDelete

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