Here is what we used to use. Format and Partition Disk [cid:[email protected]] We would use an 80GB partition for the OS and applications. That was starting to come up sort as some of our larger applications became even larger. So I don’t think 30GB is ever going to work. Personally, if it were me, I would use at least 100GB for the OS partition, at least. In our environment we started to install applications on the Data partition simply because the OS partition wasn’t big enough. Our decision to go with 80GB 7+ years ago wasn’t enough any longer.
In the properties of the OS-APPS partition we would specify a variable for SCCM to track the drive letter. Just like Andrew said in his email. [cid:[email protected]] Finally, in the Apply Operating System action we specified to apply the image to the drive stored in that variable (just like Andrew). [cid:[email protected]] Again though, it was a lot of headaches to maintain dual partitions. It required a lot of special code on our part to “handle” it in our task sequence. For example, since the goal of the dual partition was that the users’ folders were redirected on a rebuild we would leave that partition untouched. So, that meant we could not repartition the drive (or we would lose all the users’ data). We had to put all sorts of checks and conditions and custom scripts that would allow the tech building the machine the option to reparation the drive, turning on/off USMT backups, backing up only application settings off of the C drive while ignoring D, manually formatting the C drive… It goes on and on. Using just a single partition simplified it for us. Every build repartitions the disk and the tech just has to decide if they want to use USMT to migrate data and settings. No special scripts to handle one partition or the other. Hope this helps. Mike From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Thursday, July 21, 2016 6:32 AM To: [email protected] Subject: Re: [mssms] RE: SCCM OSD task sequence - W10 with OS and DATA partitions It is true. I can tell you from experience that multipartitions can be a headache. I only recently was able to convince work to go back to a single partition and it simplifies our build so much. I’ll be in the office shortly, so I can send you what we were doing if that will help. From: <[email protected]<mailto:[email protected]>> on behalf of Andreas Hammarskjöld <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, July 21, 2016 at 2:38 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [mssms] RE: SCCM OSD task sequence - W10 with OS and DATA partitions +111111 the rest of the world stopped with multipart after NT4! The some people didn’t get the memo and continued for a while with 2000/XP. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: den 21 juli 2016 02:50 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SCCM OSD task sequence - W10 with OS and DATA partitions Why, oh why? Do you like causing pain? 30GB is not nearly enough anymore more an OS volume and having 2 volumes on anything but a server will cause you endless pain in the future and provide zero benefits. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Fast, David D. Sent: Wednesday, July 20, 2016 3:36 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] SCCM OSD task sequence - W10 with OS and DATA partitions I am trying to create a bare metal / wipe and load task sequence for SCCM OSD of Windows 10 for deployment to systems with Legacy BIOS/MBR. I need to configure the OSDrive partition for a set size of 30GB, with all remaining space assigned to an NTFS data partition. How do I need to configure the partition settings in the task sequence? I have a task sequence that runs all the way through to completion with no errors, but when the system gets rebooted there is “no operating system found”. Thanks, David ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
