clickmaster

Hello everyone, thanks for this great how-to article! I have some questions regarding the ADR and client behaviour. When the ADR runs the next time and updates the existing software update package with the content of the newly created software update group, do the clients have to download the whole package again or do they scan the SUP like they do in a WSUS environment to download only the needed updates? As far as I know, in a task sequence an update package has to be downloaded completely, before the required updates are installed, right? Is the software update package getting bigger everytime the ADR finds new updates? I don´t want my clients to download the complete package again and again, especially when its getting bigger every patchday. Thanks in advance for any information.

Hi folks, today I ran into an issue with a HP G800. I started a Windows 7 task sequence with PXE and the only step that was done was the OS installation. The reason was a wrong/missing network driver in the x86 boot image. Doing some troubleshooting I asked myself when exactly the task sequence leaves the WinPE environment and continues in Windows. Because after installing Windows 7 the client does a reboot into windows. After that...is there any step in WindowsPE again? Can somebody describe the process in which WinPE handles over the NIC driver from the boot image to Windows 7 OS? There has to be a point in the task sequence where the deployed OS gets the NIC driver from the boot image, right? In most cases if I forgot to inject the NIC driver into the boot image, WinPE can download the windows .wim file. So I guess WinPE doesn´t need a specific NIC driver because it can use the NIC without the vendor driver. The problem occurs later in the OS with the consequence that no software is installed and the client is not member of the domain. The main reason to inject a NIC driver into the boot image seems to be that WinPE has to copy the driver to the OS after deploying the .wim file. Is this correct? I know how I get this to work, but I want to know why I have to do this . Thanks a lot! Regards...

Hi guys, this is my first topic here . I´m new to SCCM 2012 R2 and there is one thing I don´t understand. What´s the sense of a build and capture task sequence? Why should I go through this complex process of building packages and doing some scripting just to capture an image after that? Instead of doing this I could easily do a manual Windows 8.1 installation and run a capture only task sequence. Or is there something I forgot to think about? Don´t get me wrong. I understand the logic behind a package based task sequence. You have total flexibility and can modify the sequence very easily. But why should I use this just to get an image? Any help would appreciated .