topic existing devices JSON issue For Autopilot in Integration and Testing

existing devices JSON issue For Autopilot

usoartit — Fri, 28 Aug 2020 10:33:11 GMT

I made an errand succession utilizing the "Autopilot for Existing Devices" wizard utilizing the orders here:

I have numerous autopilot provisioning profiles and have traded the JSON straightforwardly to my MECM organization share utilizing this order:

Get-AutopilotProfile - id {profile id} | ConvertTo-AutopilotConfigurationJSON | Out-File \\server\share\Autopilot\AutopilotConfigurationFile.json - Encoding ASCII

The TS seems to work and I can affirm that the JSON is being replicated to \windows\provisioning\autopilot\AutopilotConfigurationFile.json. Yet, when I open this record in Notepad or Notepad++, it shows that the encoding is UTF-8, not ASCII.

I have promoted my cross breed join setup profile to all gadgets and the JSON is for the half breed autopilot arrangement profile.

Re: existing devices JSON issue For Autopilot

usoartit — Thu, 17 Sep 2020 05:49:04 GMT

As per the article that ishboo3002 linked to, removing the "prepare for capture" step, which syprep /generalizes the machine and removes the JSON file in doing that, and replacing with with a command step "sysprep /oobe /reboot, took care of my issue. gbwhatsapp

Re: existing devices JSON issue For Autopilot

PeacefulMonk — Mon, 21 Sep 2020 08:37:39 GMT

@usoartit wrote:
As per the article that ishboo3002 linked to, removing the "prepare for capture" step, which syprep /generalizes the machine and removes the JSON file in doing that, and replacing with with a command step "sysprep /oobe /reboot, took care of my issue. Tell Dunkin

Your article is so useful for us,thanks for sharing. Good stuff!