So, just to clarify, the Setup Windows and ConfigMgr task is much more than just installing the ConfigMgr client agent. It is mainly about installing Windows and initiates the Windows setup process. Once that's complete, then it initiates the installation of the client agent. What was described below is a highly customized use of the task sequence engine outside of its intent or design.
So, going back to the original question, what are you trying to accomplish? Are trying to deploy Windows without deploying the ConfigMgr client Agent? J -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Olsson Mats Sent: Thursday, April 17, 2014 1:26 AM To: [email protected] Subject: SV: [mssms] Can I have OSD TS without sccm package In a sort of way. Yes you can but functionality will be very limited. I have done it during transition from XP and a custom deployment system to W7 and SCCM. In that Scenario we used SCCM to boot into PE, prepare the harddrive and load the custom image from the old deployment system. We ended the SCCM TS with a reboot. The custom image was sysppreped so it booted and used the scripts from the old soloution to complete the installation. We had to have a capability to install XP:s after killing the old deployment system but the expected number was so low that the cost to convert the custom functions to SCCM was too high. Therefore this workaround -----Ursprungligt meddelande----- Från: [email protected] [mailto:[email protected]] För Hun boy Skickat: den 16 april 2014 20:48 Till: Sms Ämne: [mssms] Can I have OSD TS without sccm package Can I disable sccm client package step in TS and test deploy?? Sent from iPhone....sorry for typos
