walsallf

On the properties of the Boot Image, under Optional Components, add the Powershell Components. Note: NetFx is a prerequisite. Then in my Task Sequence, I have to format disk 0, so that it will receive the script package, in case there are no existing partitions. Then it deploys the CountDisks script: $TSenv = New-Object -COMObject Microsoft.SMS.TSEnvironment #get the physical disks in the local system $disks=Get-disk $physicaldisks=Get-PhysicalDisk #enumerate the number of disks $NumberOfDisks=($physicaldisks | measure).count $TSenv.Value("osdDrives") = $NumberOfDisks $TSEnv.Value('OSDDiskIndex') = Get-PhysicalDisk | Select FriendlyName,MediaType,DeviceID | Where MediaType -eq 'SSD' | Select -ExpandProperty DeviceID Then use osdDrives and OSDDiskIndex as Task Sequence variables to filter the steps. So if it's a single disk machine, osdDrives = 1, so format Disk 0 and continue as normal. If osdDrives = 2, and OSDDiskIndex = 0, then it has 2 disks and the SSD is Disk 0. In that case, clean the partitions off Disk 1 and format Disk 0. If osdDrives = 2, and OSDDiskIndex = 1, then it's vice versa. Then later on in the Task Sequence, after the Setup Windows and ConfigMgr step, run the script to format the second disk and rename the drive letter. There may be a better way to do this, but I finally got it working this way.

In case it helps anybody, I managed to get it working by adding the Powershell components to the Boot Image and then writing a Powershell script to count the number of disks instead of a VB script. Works like a charm.

Hi, In relation to the above, we have just had some new kit in which has 2 drives, 1 x SSD and 1x spinny disk. I've managed to get the Task Sequence working to deploy Win 10 1703 to the PC and install Windows on the SSD and format the spinny disk and rename it to V: I have an original task Sequence which works on single disk machines, but I now need to combine the two, where I have just 1 task sequence which can figure out how many disks are in the machine and then format the machine and install Windows accordingly. The guy preceding me had written a VB script to count the number of disks before formatting, but this fails with "GetObject - Permission Denied". I amended the script to use sWBEMLocator, which I found in another post, but again this comes back with permission denied. Is there anybody else that has done anything similar to this? I have upgraded everything to the latest, so we are on SCCM Current Branch 1703 and MDT 8443. Thanks

Finally managed to crack it. Posting here for others with the same issue. Basically, further down in your guide, you've got: if you get any errors about packages not being found then enable the following setting in Data Access for all packages in your task sequence including the boot image:- copy the contents in this package to a package share on distribution points Note: once you have enabled the setting above your Deployment distribution settings gets a new drop down menu choice, access content directly from a distribution point when needed by the running task sequence and then try again.. our client is being built I did this and hey presto, it worked, woo hoo!! You may want to move this bit further up in your guide, as people like me who experience these errors, will not read further on and see the above until they've got the issue sorted. Thanks

Is it anything to do with where it say's "TFTP Download: boot\x64\pxeboot.n12", where the screen in your guide shows "TFTP Download: smsboot\x64\pxeboot.com"?

Yes, WDS is started and it is located on the same server as the Primary Site. I must mention that I also have a CAS, where I am carrying out most of the configuration work and using the Primary as the DP.

Any ideas on the above Niall?

So, basically, I'm getting exactly the same as emvsnorc, (except for the IP Address) before the page above, i.e.:

Hi, First of all I'd like to say this is a great guide. Secondly, I need help as I am getting the exact same error as amvsnorc, namely: I have been stuck on this for the past few days now and ready to pull my hair out. I've tried recreating the task sequence, the client package, etc. I've tried re-deploying. I've tried stop/starting the WDS service, DHCP service, the server itself, but I still keep getting the same error. Please can somebody help!!