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

SCCM 2007 OSD- Boot the Reference Machine & Capture the Image-Process

The following post shows the process how the reference machine image is captured.

 The below components are already in place.

 1. PXE Service Point is installed.
2. DHCP  Server is configured for automatic IP assignment.
3. OSD Source specified and distributed the package to all DP's

 Steps:

 1. Start the Reference machine and allow it to boot from the network.

 In this phase- it gets the IP Address from DHCP Server, IP address of SCCM Server, checks the architecture( whether it 32 or 64 bit) and contacts the SCCM Server for further actions.


2. Next it downloads  the BOOT.WIM  File from the DP and the process is shown as " Windows is downloading the files".



3. After the download is complete, it opens  the "Task Sequence Wizard". Enter the password and click next to retrieve the policy.

 Press F8 Key to get the Command Prompt support as shown.

4. The Task Sequence Wizard will appear displaying a list of task sequences available, select the " Windows7 Reference Machine" task sequence to proceed. Click Next.



5. The task sequence will start here.Next it will check for any dependencies and resolve them. It also verifies the content location.


6. The next running action is " Formatting the machine drives"

7. Set up Windows and Configuration manager:

Windows will be installed in this phase and the system will reboot several times and the process may take up to 30-45 minutes.


Once the process is complete, the machine will be at the Windows screen asking to setup. You can shut it down.

On the site server, verify that the WIM file has been created under:

\\SCCM1\OSD_Deploy\Windows7\- the capture path that was entered while creating the task sequence.





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

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