Setup Windows and ConfigMgr question (Full Version)

All Forums >> [Management Products] >> Operating System Deployment

Message

---

igregory -> Setup Windows and ConfigMgr question (10/6/2008 1:37:14 PM) Hi, Our PC build guys are complaining that it takes longer to build a PC using SCCM OSD than it used to with SMS 2003 OSD. One reason for this seems to be the issue addressed in KB955955 where a delay of 90 seconds occurs between packages, and I'm testing out the hotfix for this. But something else that puzzles me is that the 'Setup Windows and ConfigMgr' task takes well over 5 minutes (which may not seem like much, but I'm trying to speed this up as much as possible), including a reboot, even though the ConfigMgr client is preinstalled in the image - the correct version, with the certificate deleted (and even including the Trusted Root Key). I can see from the logs that the task sequence completely reinstalls the client regardless of the fact that it's already there. Does anyone know why, and whether it can be prevented from doing this? (Of course if you disable that whole step it just crashes the task sequence...) TIA, Ian

---

rbennett806 -> RE: Setup Windows and ConfigMgr question (10/7/2008 1:07:08 PM) If you're using OSD in SCCM 2007 then it's not really recommended to have the client pre-installed in the OS .WIM image. So maybe try one without the client being pre-installed...

---

igregory -> RE: Setup Windows and ConfigMgr question (10/9/2008 12:10:25 PM) Hmm, fair enough, but if you use the standard SCCM task sequences to build and capture an image, and to deploy the image, it installs the SCCM client in the image... and then installs it again when it deploys the image. I can't quite see the point of that! In any case, KB955955 has worked well for us and speeded up the builds considerably, so it's not as big an issue as it was.

---

mniehaus -> RE: Setup Windows and ConfigMgr question (10/9/2008 1:08:46 PM) Are you using an OS installation package or an OS image package? In the case of an OS installation package, the "Setup Windows and ConfigMgr client" step has to run Windows Vista SETUP.EXE which adds some time to the overall process (it applies the whole WIM, among other things). If you use an OS image package, the bulk of the work is dong earlier by the "Apply OS" step, leaving the "Setup Windows and ConfigMgr client" step with very little work to do. -Michael

---

igregory -> RE: Setup Windows and ConfigMgr question (10/10/2008 4:15:24 AM) Sorry, I should have been more specific, it is an XP OS Image Package. Using the standard 'build and capture' TS, the SCCM client is preinstalled in the image. Using the deployment TS, it seems to reinstall the whole client again from the package source. It may work differently with Vista. Just got hold of SCCM R2, so I'll see if that makes any difference. Thanks, Ian

---

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.1875