nov1ce

Hi, Why 'Bulletin ID=MS' criteria? There are some updates without MS in the bulletin name... Thanks.

Hey, I'm sure there are other more elegant ways, but what we do is we keep so called "golden image", which is a virtual machine with no drivers but Windows OS + local system tweaks (like profile cloning). When we receive a new physical PC, we use this image as a base image to deploy an OS, and feed relevant drivers along with all available Windows updates during the OSD stage. Most of the drivers nowadays support silent installation, hence that's the only time consuming part, but once it's tuned it just works like a charm. Hope it helps.

bump same here with SCCM 2012 R2 SP1 (5.0.8239.1403) server and Windows 7 SP1 x64 clients. No errors reported during the OSD stage though and ccmrepair.exe does the trick. Could it be that you've done some tuning of the golden image (like disabling unnecessary services) because I have a blank Windows 7 image from last year and it works without any issues.

Hello, I'm trying to capture Windows 2003 R2 SP2 x86 server using Capture media with SCCM 2012 R2 (CU4). The 2003 server is a virtual server (VMware) with all latest patches and VMware Tools installed. It's not in the domain and there is no AV software installed. I copied sysprep files from http://www.microsoft.com/en-us/download/details.aspx?id=14830 to C:\Sysprep directory, however when I run capture wizard from the capture CD and provide network path for the image it fails with the error: Task Sequence: Image Capture Wizard has failed with the error code (0x0000007F). The WinPE 3.1 boot image (OS version: 6.1.7601.17514) used for the capture CD is indeed x86 with vmxnet3 x86 drivers injected. There are a lot of errors in smsts.log (attached), but I'm not quite sure where to start from. Any hints would be greatly appreciated. Thank you. smsts.log

Thank you Nick. The source folder is \\SRV-SCCM\sccm\Win XP Critical\ and I can access it. Other software update packages are under \\SRV-SCCM\sccm\ as well -- no issues there. Are there any logs I can check? It seems it only happens with one particular update for Windows XP.

Hello, SCCM 2012 R2 For many days, I get the following error from the SMS_DISTRIBUTION_MANAGER: The source directory "\\SRV-SCCM\sccm\Win XP Critical\094b52b7-9deb-4dda-bd7a-84fb03387037" for package "PKG00030" does not exist. The operating system reported error 2: The system cannot find the file specified. Solution: Make sure you have specified a valid package source directory on the Data Source tab in the Package Properties dialog box in the Configuration Manager Console. If you specify a local path, it must be a local path on the site server. If you specify a path on a network drive, verify that the path exists and that the path is typed correctly. Retry Interval is 30 minutes, number of retries left is 26. Distribution Manager failed to process package "Win XP Critical" (package ID = PKG00030). Possible cause: Distribution Manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it. I double-checked permissions and re-downloaded it but it doesn't seem to help. Other updates are fine, it's the only one causing the error. Any hints would be greatly appreciated.

Hi Paul, Thank you, but I think I'm missing something. Let me rephrase the question. - I deploy a virtual machine (we're using VMware ESXi) and install Windows 7 SP1 X64 with all latest updates, software packages, tweaks. I also install VMware Tools to get the NIC working. This is going to be my reference image which is later going to be used to deploy physical machines (I'm aware about adding drivers for physical machines). - I prepare a capture CD for my reference image and use the boot image with VMware drivers injected so my NIC is identified. - I run my capture CD on the reference image and get a wim file. So, at this stage VMware Tools were already captured? How to avoid it? Thanks.

Thank you! We're using VMware, which means I have to install VMware Tools in a reference image to get the NIC running, right? How do I get rid of it during the deployment to the physical machines? Do you mean I'll need a task sequence to uninstall VMware Tools and then apply proper drivers?

Hello, Sorry if this is a stupid question, this is my first experience with SCCM (SCCM 2012 R2). I'm working on a reference image for our new PCs. They are all physical PCs with the same motherboard, so I installed a PC running Windows 7 SP1 64bit (+updates and drivers). Then I created a new boot image in SCCM and attached LAN drivers. I used this boot image to create a capture CD. I ran it on a reference PC and managed to capture the image. So far so good. My question is, what's happenning to the reference PC after the capture? After I reboot it, it asks me to setup a user account like it's a new installation. All drivers/updates are there, but some settings are gone (for example local Administrator is disabled, KMS keys are no longer deployed, IPv6 is enabled and etc.). Is it because of the sysprep? I was expecting to have the same state before the capture, so I can use it to build another image (with additional software installed), but it looks like I have to reset some settings every time I run the capture. Is it expected? And another question: once I add and distribute my newly created image in SCCM, where exactly I configure it to join the domain? Many thanks!