Deployment Solution

I'm trying to capture a Windows 10 x64 1607 image. The "Prepare for Image Capture" task fails after 8 seconds (return code 1); following are the logfile entries that may be helpful. Thoughts?

[2017/11/08 09:06:44.481 2832:3632 0] File:ExecuteCommand.cpp,Line:4370 ERROR: Exception has occured in function ExecuteCommand.cpp() at Line No 2420. Type of exception is ExecuteClassException. Error is Default Message: Exception in ExecuteClassException. Error Description is  "Unable to create new process as user". Value of Windows error code = 740 and message is " The requested operation requires elevation.
"

[2017/11/08 09:06:44.513 2832:3632 2] DisableWow64
[2017/11/08 09:06:44.513 2832:3632 2] OS is Vista and Above using Wow64 Redirection

[2017/11/08 09:06:44.529 2832:3632 2] ExecuteCommand.cpp@4422 ExecuteClass::SetResult() - StopTaskCmdReceived = 0

[2017/11/08 09:06:44.529 2832:3632 2] ExecuteCommand.cpp:util::ExecuteClass::SetResult():4440. Value of nResult(@ReturnValue) = 1, Value of bResult(@Success) = 0

[2017/11/08 09:06:44.544 2832:3632 2] ExecuteCommand.cpp@4459 Output @errorMessage=Exception has occured in function ExecuteCommand.cpp() at Line No 2420. Type of exception is ExecuteClassException. Error is Default Message: Exception in ExecuteClassException. Error Description is  "Unable to create new process as user". Value of Windows error code = 740 and message is " The requested operation requires elevation.
"
[2017/11/08 09:06:44.559 2832:3632 2] ExecuteCommand.cpp@4468  Task have completed. Failure return!!

Hi,

Have you made sure your version of Deployment Server supports 1607?

https://support.symantec.com/en_US/article.HOWTO125345.html

Thanks!

Hi,

Is it a clean install of 1607 or one that's been upgrade from an older version (1511 or earlier?)?  Some versions of Deployment Solution would not run Prepare For Image Capture tasks on images that had been upgraded...

I'm running 8.1 RU3, so it deifnitely supports Windows 10 1607--on a side note, it's Windows 10 Education.

The install of Windows 10 1607 is a clean, scripted install, straight off the ISO, then joined to the domain. Upon joining the domain, a group policy deploys the university's SCCM client, but this had not been a problem in the past.

Update: I succeeded by having sysprep run with local administrator credentials (.\administrator); in the past, it worked successfully with domain\adminuser.

Odd.