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

OSD-SCCM 2007-Error Code (0x80070035)

During the image capture process of Operating System Deployment in SCCM 2007, there will be lot of error messages and seems like everything is on a trial and error basis. Here is once such find for an error code that roughly translates to "The network path was not found". But this is more generic. We can also check the smsts.log in root directory of the reference machine for any errors.
The error snapshot is attached below for your reference.


The issue is because of the missing network drivers on the Windows PE image or the Boot image that is being used in SCCM.
Solution is to inject the required network drivers into the the boot image and update the distribution points.

Steps to import the driver:

1. Locate the appropriate driver for the Operating System that you are trying to capture.
2. Go to OSD Node under computer management, click on Drivers node. There will be "import" option under actions or when it is right clicked. Provide the path where the driver has been stored and click next


3. Select the appropriate options as shown and if required add " categories"

4. Select all the applicable DP's and the check the option " Update distribution point when finished" to update the DP's with the driver.
( I have skipped  the "Add driver to package" tab as I am not created any driver  packages )



Click Finish and try capturing the image again. Hope this helps.


Labels:

Comments

  1. Anonymous30 May 2015 at 01:11

    I was experiencing the same error with SCCM 2012 R2 when trying to build and capture a Win 8.1 x64 image. The solution was that I was trying to save the image to a NetBIOS name of the server (i.e. \\sccm\capture). Once I changed this to the IP address (I believe that the FQDN of \\sccm.contoso.com would have worked as well) like \\192.168.1.5\capture then the capture process worked.

    ReplyDelete

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

SQL Queries for SCCM Sites

The below queries are useful for assessing the site and hierarchy information from SCCM Site servers. 1.Site Roles select SiteCode , RoleName , ServerName from SysResList 2.Hierarchy information including site version select * from sites 3.Total Secondary sites select CAST ( Version as varchar ) 'Category' , count (*) 'SiteCount' from v_Site ( NOLOCK ) where Type <> 1 group by Version UNION select 'Total Primary Sites' 'Category' , count (*) 'SiteCount' from v_Site ( NOLOCK ) where Type <> 1 ORDER BY Category DESC 4.Client count by site select sms_assigned_sites0 , count ( distinct name0 ) from v_RA_System_SMSAssignedSites ass join v_R_System sys on ass . resourceID = sys . resourceID where client0 = 1 and obsolete0 = 0 and active0 = 1 group by sms_assigned_sites0 order by count ( distinct name0 ) desc 5.MP Communication Status in last 7 d...
2 comments
Read more