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