Apophis

Unfortunately the script does not help. And I don't know how the decision was made, but I do get to make it work or I would've probably done as you would have. And also I don't have more time to throw at this little project so I'll just keep it as is for now. Thanks for the help though.

Simple: because I have too. 2 3D CAD designers are going to use them. SSD for OS/apps, HDD for scratch data. I was wondering if this was a first because I couldn't find any info. I will try the script. Thanks for that. Any idea what triggers/causes this feature? Or if it is known @ MS?

Do you want to add the workstation to an AD-group during OSD so that admin have access? If so, this PS-script may help you out. $ComputerName = gc env:computername $GroupPath = "LDAP://CN=ADM_SCCM_Workstations,OU=Groups,OU=System,OU=GMSC,DC=internal,DC=gustomsc,DC=com" $computerPath = "LDAP://CN=$ComputerName,OU=Desktops,OU=Workstations,OU=GMSC,DC=internal,DC=gustomsc,DC=com" $Group =[ADSI]"$GroupPath" $Group.Add("$computerPath") $Group.SetInfo() Save the script as a PS1 file. Make sure you put it in your TS after you have network connection and the machine has been added to the domain. Mine runs from a share. Run it with the following command-line: powershell.exe -executionPolicy Bypass -file .\desktops.ps1 If this is not the Script you are looking for, perhaps this may help: http://blogs.technet.com/b/heyscriptingguy/archive/2014/10/03/adding-local-users-to-local-groups.aspx

Hi all, Before I start off. This is a best-practice type of question. The situation below works but I'm unhappy because I need to enable the Continue on Error option for it to work and I was wondering if anyone has a better way of achieving my goals. In our organization we normally have 1 disk per system, be it workstation or laptop. All systems are Bitlockered during OSD. This week we purchased 2 new workstations however with 2 disks: 1 500GB SSD (Boot, OS - disk 0) and 1 2TB HDD (disk 1). I built a TS for OSD. Tweaked some steps for Bitlocker. Ran OSD. Crashed and burned. Status so far: - Pre-provisioning works for disk 0 and disk 1 - Bitlocker fails to encrypt disk 1 The failure code is : 0x000000FF (255) Log file and a screenshot of the TS are included. Short explanation of the TS. - Disk 0 is partitioned with a 300MB bootpart and remaining space is the OS partition. The latter receives variable: OSPART - Disk 1 is 1 partition, variable: DISK2 - @ Enable Bitlocker OS drive has the following options: Current OS drive, TPM only, ADDS backup, wait for BL to complete... - @ Enable Bitlocker D: Specific drive: D:, ADDS backup, wait for BL to complete... The step that fails (oddly) is the Enable BL OS Drive step, with the following message: Failed to run the action: Enable BitLocker OS Drive. The extended attributes are inconsistent. (Error: 000000FF; Source: Windows) TSManager 29-May-2015 11:58:29 3836 (0x0EFC). If you then boot to OS the funny thing you find is that the failure results in the OS drive being fully encrypted but the other disk has BL suspended. So technically it fails to encrypt the other disk. When the Continue on Error option is ticked at the Enable BL OS drive step: All good! Everything is encypted as it should be. Please have a look at the excerpt of the smsts.log and if anyone has any ideas: I'm all ears. BL.log