We recieved some HP 2740's recently and we order them with Solid State Drives. In the last batch we ordered there were a lot of "Failed to save environment to (80070057)" errors in the SMSTS.log. Online I found doing f8 for the command prompt and then typing diskpart -> select disk 0 -> clean should fix it. My case it didnt untill I did format fs=ntfs quick and install went fine. In the task sequence there is already a format set. Just curious if SCCM doesnt play nicely with SSD or certain model drives?

i wonder are they advanced format drives ? you can test for that using this tool if they are, then you should align them with a disk partition script like so:- Select disk 0 Create partition primary align=1024 Format fs=ntfs Quick Active Assign Exit Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

I will check, but if it is an advanced format can I do a check in SCCM for this specific model and run the above? I have a task sequence doing WMI Queries to determing the model and install the WIM of that tablet. So the task sequence is built for 15-20 different tablet models. Or does it do harm to run diskpart on all systems anyway?

very easy to check for it, use the '42' program above, add a step to run a script to check for that value, if found diskpart the disc, if not, use the standard partition and format disc step. Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

I will try it out. Thanks.

create a run command line step to run the following script cscript "%SCRIPTROOT%\check_AFormat.wsf" have a Use Toolkit Package step before this to make the step aware of %scriptroot% the check_AFormat.wsf script can be like so: <job id="checkAFormat"> <script language="VBScript" src="..\ZTIUtility.vbs"/> <script language="VBScript"> Option Explicit Dim oWsh, ScriptPath Set oWsh = CreateObject("WScript.Shell") ScriptPath = Replace(WScript.ScriptFullName, WScript.ScriptName, "") If(oWsh.Run(ScriptPath & "IsAdvancedFormat_X86.exe", 0, True) = 42) Then oEnvironment.Item("AFDISKPRESENT") = True oLogging.CreateEntry "Found AF Disk, setting AFDISKPRESENT to True", LogTypeInfo Else oEnvironment.Item("AFDISKPRESENT") = False oLogging.CreateEntry "Could not find AF Disk, setting AFDISKPRESENT to False", LogTypeInfo End If </script> </job> add that script to your scripts directory in your Toolkit package and redistribute it to your dp's, then test it ! it sets a variable, so you can have a format Advanced Drive if present step which only runs if AFDISKPRESENT=True on the options tab, otherwise do a normal format and partition disk step cheers Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

This may sound silly but "add that script to your scripts directory in your Toolkit package and redistribute it to your dp's, then test it !"... What does that mean? I dont know that I have Toolkit package or a scripts directory. When you say Scripts directory do you just mean the location I store everything for SCCM packages? Also is this right or do I need to move the check_AFormat.wsf under the Restart in Windows PE? I am guessing after... This will be the first time running a non-package in OSD for me...

what i mean is 1. integrate MDT 2010 update 1 with ConfigMgr, plenty of guides around to help you, it's simple takes minutes. 2. create a MDT task sequence in ConfigMgr, go through the wizard, you don't need to use that task sequence, you only do this to create the needed MDT toolkit and MDT settings packages, 3. copy the '42' exe and the script above to the Scripts folder in your MDT toolkit package 4. redistribute the MDT toolkit pacakge to your distribution points 5. add a Use Toolkit package step immediately prior to the step to run the CheckAFormat.wsf script these steps must happen after restart in WinPE as your disc(s) don't have anything on them do they ? does that help ? cheers niall Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

This tablets come pre-loaded OEM Windows 7. We, for the next 15 days and counting, are still using Windows XP. We will be moving them to Windows 7 after that, but still will reload them. I do beleive I have MDT integrated just have done nothing with it. Thanks for the help Niall.

well test this out first with a simple task sequence to see if it does what you want, then move the changes to your production task sequence when ready Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

Naill, Sorry I have not had time to get the MDT setup and build in what you posted above... more time pressing things came up. But I will and thanks for your help.

Hi Niall when I run the script testing on an HP Envy I get a script error Variable is undefined "oEnvironment"