Client Management Suite

 View Only
  • 1.  Unable to prepare image win 10 x64 1709

    Posted Jan 08, 2018 04:10 PM

    Running 8.1 ru4, I have a fresh loaded vm running windows 10 1709, update service is turned off and is not a upgrade, when I try to run the prepare for caputure I get the error below:

    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.

     

    I'm using the win 10 white paper and had no issue when I did this with the 1703 with no issues, I have tried the devicename\administrator or devicename\admin(account I created with admin rights like the white paper says). This is not domain joined at this point either.

     

     



  • 2.  RE: Unable to prepare image win 10 x64 1709

    Posted Jan 10, 2018 08:36 AM

    answer my own question but this is known issue with 1709, hopefully resolved soon:

     

    https://support.symantec.com/en_US/article.HOWTO127058.embed.html



  • 3.  RE: Unable to prepare image win 10 x64 1709

    Posted Jan 12, 2018 03:26 PM

    So I had been using the whitepaper but looks like with 1709 there is a extra step:

    3.     On Windows 10 systems disable UAC by modifying the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.  Set EnableLUA to '0'

    This is posted under:

    https://support.symantec.com/en_US/article.TECH223595.html?

    I do notice this above link they don't talk about turning off the update service which I still did and then have it turning back on in my deploy job



  • 4.  RE: Unable to prepare image win 10 x64 1709

    Trusted Advisor
    Posted Jan 18, 2018 07:42 AM

    @cody - I have been using my below linked workflow to create win10 images with VMWare and haven't had issues.  I have never needed to follow the registry suggestions nor disable win update as Symantec has suggested.  When I've talked to support they're surprised it works for me, but it does.  I've tested imaging various Dell latitude and optiplex systems in either legacy or UEFI boot options (UEFI is preferred here to take advantage of secure boot, etc).

    I also don't think removing stuff via powershell scripts makes much sense, instead I use GPO to block the items I don't want to run via applocker (I understand that requires win10 enterprise or edu, though).  Using the powershell method seems to beg for issues later when you have to push out feature updates and those items often come back.

    Maybe my workflow will be of some help for you.  Let me know if I can answer any questions.

    https://www.symantec.com/connect/articles/creating-win10-image-vmware-workstation