none
Windows 7 deployment keeps failing

    Question

  • I keep getting errors when trying to deploy Windows 7 Pro x64 from the source files that I imported in MDT.  Below is a snippet of my smsts.log file.  It looks like it is having a problem saving the environment and that there may be a program issue.

    Has anyone else had this problem?  If so, what did you do to get around this.  The only thing I can think of is that after importing windows 7 source files and going through the unattend.xml file, there are two deprecated entries in there by default.  I didn't remove them, but I also didn't think they would cause issues like this.  I'm not sure if in fact these deprecated values are the issue or not.

     

    Failed to save environment to  (80070057)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
    TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
    Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
    SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
    Failed to persist execution state. Error 0x(80070057)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
    Failed to save execution state and environment to local hard disk    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)

    Thursday, March 25, 2010 8:58 PM

All replies

  • Is this a MDT/SCCM deployment or just an MDT deployment (SMSTS.log?)

    Ensure that the Windows PE image has the correct Mass storage drivers for the target computer

    Ensure that there is enough free space on the target computer

    verify that all setting in the customsettings.ini are correct.

    the BDD.log should give more info

     

    Friday, March 26, 2010 10:54 AM
  • It's MDT Lite Touch only.  The log entries I posted above are from smsts.log.  We use Intel DX58SO motherboards in our systems which use the same RAID driver for XP and 7.  there is a new Intel RAID driver that I am going to try.  Customsettings.ini settings are unchanged from deploying XP images, which have no issues.  There's over 100 GB of space on the PCs, so that is not a problem.  I'll add this new driver and try it again.  If I still have this problem, I'll post the logs.  Thanks.
    Friday, March 26, 2010 12:20 PM
  • A quick check to see if it is Mass Storage Drivers in Windows PE is to change the SATA controller from RAID/AHCI to Legacy. You will need to play around different BIOS have other names for this setting.

    If windows PE carries on you know it is the raid drivers. If you are using MDT 2010 you need Win 7 drivers 2008 needs vista drivers. (pretty much the same thing)

     

    Friday, March 26, 2010 12:30 PM
  • I just tried it and got the same thing.  I get an error message during Windows setup that says:

    Setup was unable to create a new system partition or locate an existing system partition.  << This message appeared while I was at this screen , only the first stage of it, not stage 2 as this picture illustrates.

    I'll post log entries in a minute...

    Friday, March 26, 2010 1:13 PM
  • That message is MASS Storage.

    In MDT be sure to import the Mass storage Drivers into the Driver Library BOTH X64 and X86 drivers for the controller

    On your WinPE settings (X86 and X64) Make sure the checkbox for Mass storage controllers is checked

    Update your deployment share and make sure your LiteTouchPe.WIM file has a new timestamp Both X86 and X64

    If you use WDS update your boot images, BOTH X86 and X64

    If you boot off CD USB, burn a new CD / Create New USB Media

     

     

     

    Friday, March 26, 2010 1:29 PM
  • The only error in the bdd.log is that it was unable to map a network drive to the logging share, even though it does eventually.  The last line of bdd.log is:

    About to run command: "\\server\e$\DeploymentShare\Operating Systems\Windows 7 x64\Sources\setup.exe" /noreboot /unattend:C:\MININT\unattend.xml /m:"\\server\e$\DeploymentShare\$OEM$"    LTIApply    3/26/2010 9:04:23 AM    0 (0x0000)

    There are a few occurrences of this error in smsts.log:

    Creating directory C:\_SMSTaskSequence    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)
    uRet == ERROR_ALREADY_EXISTS, HRESULT=80070003 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,916)    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)
    Failed to create C:\_SMSTaskSequence (3)    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)
    Failed to create user-specified local data path C:\_SMSTaskSequence. Error 0x80070003    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)

    And around 7 occurrences of this:

    Failed to save environment to  (80070057)    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)
    TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842)    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)
    Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)
    SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420)    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)
    Failed to persist execution state. Error 0x(80070057)    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)
    Failed to save execution state and environment to local hard disk    TSManager    3/26/2010 9:03:15 AM    1852 (0x073C)


    Friday, March 26, 2010 1:59 PM
  • Well, we are only working with 64 bit Windows 7, so I shouldn't need to do anything on the x86 side.   I imported the latest RAID driver from Intel into MDT.  I selected that driver folder in my Win7 selection profile and then made sure this was set in the x64 Components tab of MDT properties and also in the TS Driver injection task sequence.  I updated my deployment share and pulled the boot.wim from the ISO and inserted it into my USB drive media.  The ISO time stamp is recent.  I did all of this before posting these log entries.
    Friday, March 26, 2010 2:04 PM
  • The strange thing is that c: exists even after getting this error.  I can get into c:\minit and c:\_smstlogs (or whatever this directory is called) with no problem.  That's how I was able to copy all of the logs to my network share and parse them with trace32 for errors.  The logs posted above are the only errors listed.
    Friday, March 26, 2010 2:06 PM
  • When WinPE first loads press F8 to get a command Window

    In the command Window go to C: and check if it is infact your primary hard drive by doing a dir and checking capacity, also make sure you can create a folder or file on the disk.  If it is not your C: check if D: or E: are your primary Hard Drive.

    The BDD.log file should be located at C:\minint\SMSOSD\OSDLogs\ or X:\minint\SMSOSD\OSDLogs\ depending on where the TS is breaking.

     

    Friday, March 26, 2010 2:10 PM
  • Roger, I think you are right though, it does read like a storage driver issue, I'm just so used to the 7B stop error when this is a problem.
    Friday, March 26, 2010 2:11 PM
  • Ya Windows PE wont give you a stop error because the HD is not a critical device.

    If you need still stuck post me the BDD.log file (Location Above) and I will work through it for you.

     

    Friday, March 26, 2010 2:40 PM
  • Now, I don't think that it's mass storage drivers.  I realized after developing images on several machines that my problem deploying windows 7 is only on one PC.  The strange thing is, is that this PC is the same configuration as a couple of others that I deployed Windows 7 to successfully.  Windows loaded fine on the other systems, but not this specific one.  When it gets to the windows setup, I get the error about it not being able to find the system partition to install to.  When I get this error, I press F8 for a command prompt and check for c: and it is there!  So it thinks that there is no system partition when there is, but only on this one system.  These are Antec chassis with an Intel DX58SO motherboard, Core i7 920 processor, 6 GB ram, 2x Western Digital Velociraptor set at RAID 0.

    I updated the BIOS on this trouble system, but I get the same error during Win7 deployment.

     

    Setup failed applying image \\ocs\e$\DeploymentShare\Operating Systems\WIN7V2\WIN7V2.wim, rc = 31    LTIApply    4/13/2010 8:52:13 AM    0 (0x0000)
    ZTI ERROR - Non-zero return code by LTIApply, rc = 31    LTIApply    4/13/2010 8:52:13 AM    0 (0x0000)

     

    Tuesday, April 13, 2010 2:12 PM
  • I changed the format step in my TS to NOT do a quick format.  The Windows 7 image seems to apply correctly with no error about not finding the system partition.    Before I did this, I noticed that a system which W7 image was deploying to just fine also started throwing the error about not finding the system partition, until I forced a full format.  I'm not sure why this would be.  After a quick format, I can access c: via F8 and make directories and such, so I don't know why deployment couldn't see the partition to apply the image.
    Friday, April 16, 2010 8:46 PM
  • Ok, so now for some reason, forcing a full format doesn't work either, I get the same message as before.  I currently have the 'Nothing' selection profile set in my x64 components tab of the deployment share properties.  I switched it to WinPEx64 selection profile which contains the Windows 7 RAID driver.  We'll see how that goes.  Suggestions welcome though.

    Wednesday, April 21, 2010 1:37 PM
  • Ok, so now for some reason, forcing a full format doesn't work either, I get the same message as before.  I currently have the 'Nothing' selection profile set in my x64 components tab of the deployment share properties.  I switched it to WinPEx64 selection profile which contains the Windows 7 RAID driver.  We'll see how that goes.  Suggestions welcome though.


    I am also having the same trouble.  I don't have this problem with a DVD ISO in another deployment point nor with the network boot from a CD, only the network boot using a USB.  I'm sure it must be confused because of the USB stick.  I am trying with a full format now and will let you know if that works for me.
    Friday, April 23, 2010 5:55 PM
  • Hi

    I Have the same problem using DVD media.

    under the SMStst.log i got:

    Set command line: "OSDApplyOS.exe" /image:Z00001DD,1 "/config:Z00001B7,unattend.xml" /target:%OSPART% ApplyOperatingSystem 05/13/2010 4:45:23 PM 1448 (0x05A8)
    ((g_Target.Disk > 0) || (arg == L"0")) && (g_Target.Partition >= c_MinPartition), HRESULT=80070057 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,252) ApplyOperatingSystem 05/13/2010 4:45:23 PM 1448 (0x05A8)
    The /target parameter specifies an invalid target location. ApplyOperatingSystem 05/13/2010 4:45:23 PM 1448 (0x05A8)
    ParseCommandLine(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,316) ApplyOperatingSystem 05/13/2010 4:45:23 PM 1448 (0x05A8)
    Process completed with exit code 2147942487 TSManager 05/13/2010 4:45:23 PM 1396 (0x0574)
    !--------------------------------------------------------------------------------------------! TSManager 05/13/2010 4:45:23 PM 1396 (0x0574)
    Failed to run the action: Apply Operating System Image. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 05/13/2010 4:45:23 PM 1396 (0x0574)
    _____________________________________________________________________________________________________________

    at the BDD.log  I got:

    Validating connection to \\smscentralsrv\ACMData\Logs zticopylogs 05/13/2010 4:45:30 PM 0 (0x0000)
    No physical adapters present, cannot deploy over wireless zticopylogs 05/13/2010 4:45:30 PM 0 (0x0000)
    An invalid SLShare value of \\smscentralsrv\ACMData\Logs was specified. zticopylogs 05/13/2010 4:45:30 PM 0 (0x0000)
    zticopylogs processing completed successfully. zticopylogs 05/13/2010 4:45:30 PM 0 (0x0000)

    *smscentral is our server but I would like to use it as completely offline.

    Thanks,

    Yair

     

     

     

    Sunday, May 16, 2010 12:20 PM
  • Hi Brumar,

    I've a same problem by deploying Win2003 on IBM Srv by LTI with MDT 2010 tools .

    Smstslog send same mistakes. Have you found origin ?

    I had open a post : http://social.technet.microsoft.com/Forums/fr-FR/windowsserver2008fr/thread/a4392774-98e7-4ae0-81be-7ac44710db1a .

    If you can, please help me !!!

    Thanks

    François.

    Thursday, September 09, 2010 7:58 AM
  • Consider using a PE environment with better or at least device-specific driver support capabilties and/or error communication/handling of boot-critical devices.

    We have been delighted with http://www.smartdeploy.com. The PE environment with the enterprise product will probably solve the problem. It fits right into MDT...to my knowledge you won't necessarily have to throw out any of your existing processes or work with this. Works with server and client, x86 and x64. Very simple. It's worth a shot.

    Thursday, December 02, 2010 1:20 AM
  • I changed my Dell E6400 laptop from AHCI to ATA mode in its SATA bios settings screen with the same result.

    I also have latest storage driver from Dell in my PE that was created by MDT.

    Tuesday, March 15, 2011 12:35 AM
  • I had the same problem just now when i had to change a dell bios from AHCI back to legacy. The issue is that the machine will not boot if its ahci. Like it does not see the hard drive in the bios, and does not list hard drives as a boot device. The motherboard is a bit messed up.

    Anywhoo.... I did have the drivers, but still got this error. The fix was incredibly simple. I just rebooted the machine after i got the error. The task sequence continued on from where it "failed" and I am now looking at my image booted on this PC.

    it did bitch one time it couldnt find some deployment file, but as far as i can see the image is OK.

    Monday, March 17, 2014 10:56 PM
  • A USB 3 port can cause this behavior.  On a machine with both USB 2 and USB 3 ports I can repro the behavior on a 3 port and have it work fine on the same machine in the 2 port.  We solved the problem by updating the USB driver in the boot WIM.
    Friday, December 12, 2014 8:51 PM