mpepprell Posted October 15, 2014 Report post Posted October 15, 2014 Hi! We have a number of computer models that we image with SCCM 2012 R2, and everything works just fine, apart from one model: Novatech nSpire 15.6 (yeah, the model is not descriptive, but that is the model name!) The laptop has standard Intel Haswell hardware, one fixed disk (Sandisk SSD) and an optical drive. This is much like other computers that we have in the organisation and we have no computers with two or more fixed disks When we image this particular model of computer, the task sequence fails at the "Apply Operating System Image". The partition map from the task sequence is: Volume 1: 350MB fixed size, NTFS Volume 2: 100% remaining space, NTFS The operating system is deployed to the "next available formatted partition" The SSD is partitioned and formatted successfully during the task sequence. If I disable this step and use diskpart for this, the task sequence still fails! Below is the point of failure, from the smsts.log file: User did not specify local data drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume C:\ has 336084992 bytes of free space TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume C:\ is not bootable TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume D:\ has 127548887040 bytes of free space TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume D:\ is not bootable TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume E:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume F:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume X:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) TSM root drive = TSManager 15/10/2014 10:42:51 1292 (0x050C) We do not find an available volume to store the local data path TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a global environment variable _SMSTSNextInstructionPointer=11 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a TS execution environment variable _SMSTSNextInstructionPointer=11 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a global environment variable _SMSTSInstructionStackString=10 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a TS execution environment variable _SMSTSInstructionStackString=10 TSManager 15/10/2014 10:42:51 1292 (0x050C) Save the current environment block TSManager 15/10/2014 10:42:51 1292 (0x050C) pszPath[0] != L'\0', HRESULT=80070057 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,60) TSManager 15/10/2014 10:42:51 1292 (0x050C) Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,676) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to save environment to (80070057) TSManager 15/10/2014 10:42:51 1292 (0x050C) TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,842) TSManager 15/10/2014 10:42:51 1292 (0x050C) 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 15/10/2014 10:42:51 1292 (0x050C) SaveEnvironment(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,420) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to persist execution state. Error 0x(80070057) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to save execution state and environment to local hard disk TSManager 15/10/2014 10:42:51 1292 (0x050C) Any help in this would be greatly appreciated! -- Matt Quote Share this post Link to post Share on other sites More sharing options...
newadmsccm Posted October 20, 2014 Report post Posted October 20, 2014 Mpepprell, Do you have one partition or two? If you have only one partition, pay attention for this fields: System Reserverd: Field: Apply Operation System, insert your variable. Quote Share this post Link to post Share on other sites More sharing options...
mpepprell Posted October 21, 2014 Report post Posted October 21, 2014 Hi I have made the changes as suggested, and the same set of errors occur I'm thinking along the lines that these computers, for whatever reason, are incompatible with the SCCM/WDS image process -- Matt Quote Share this post Link to post Share on other sites More sharing options...
newadmsccm Posted October 23, 2014 Report post Posted October 23, 2014 Post what's log error. Can you ping your server SCCM when you try do deploy? If you don't have success probably you'll need deploy driver NIC in your image boot. Quote Share this post Link to post Share on other sites More sharing options...
mpepprell Posted October 24, 2014 Report post Posted October 24, 2014 Hey I can ping the deployment server, with the following results: Pinging deployment-server.domain.local [10.47.32.19] with 32 bytes of data: Reply from 10.47.32.19: bytes=32 time=1ms TTL=128 Reply from 10.47.32.19: bytes=32 time<1ms TTL=128 Reply from 10.47.32.19: bytes=32 time<1ms TTL=128 Reply from 10.47.32.19: bytes=32 time<1ms TTL=128 Ping statistics for 10.47.32.19: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms I have attached the smsts.log file, for reference -- Matt smsts.log Quote Share this post Link to post Share on other sites More sharing options...
Iroqouiz Posted October 24, 2014 Report post Posted October 24, 2014 You need to tick "Make this the boot partition" Quote Share this post Link to post Share on other sites More sharing options...
mpepprell Posted October 27, 2014 Report post Posted October 27, 2014 Hello! I have made the suggested changes and unfortunately, the same error still occurs. I have attached the smsts.log file for reference I am sorry that I cannot suggest anything to help you help me with this issue, as it has me totally confused -- Matt Quote Share this post Link to post Share on other sites More sharing options...
newadmsccm Posted October 28, 2014 Report post Posted October 28, 2014 I looking for about this error and in another topic was solve check time set if was correctly in the bios, might help you, do this check. Quote Share this post Link to post Share on other sites More sharing options...
mpepprell Posted October 29, 2014 Report post Posted October 29, 2014 Hi In the BIOS, the time and date are correct -- Matt Quote Share this post Link to post Share on other sites More sharing options...
matt1234 Posted April 4, 2016 Report post Posted April 4, 2016 For Win 7 based machines depending how you captured, always make sure you have your image index's set correctly in the "Apply Operating System" and "Apply Data Image" steps. Apply OS Step: 2-2 Apply Data Image: 1-1 Quote Share this post Link to post Share on other sites More sharing options...