Forum Discussion
Error applying Provisioning Package during OOBE - "Something unexpected happened. Please try again."
Hi Greg_A,
I have a situation looking like yours when trying to onboard Surface Hubs by use of a provisioning package and the CSV file.
At the stage where the device has been enrolled in AAD, rebooted and started into the OOBE we finally get the "Configure your Surface Hub" screen with the account from CSV listed. I have no shortage in the naming etc, but when selecting the account, we receive the same message as you which is telling "Something unexpected happened. Please try again."
Did you figure a way of getting past this problem?
Thanks,
Simon
- I had a ticket open with Microsoft which got escalated and he said everything looked right it and he submitted a bug with development. Workaround is to simply not use the configuration csv with device accounts and just manually add it. Which is fine for my case. I was just wanting to have as few possible points of failure for a local user in an office that may be setting these up. It's unfortunate, but it is what it is.
- Thanks for sharing your experience on this. Did you manage to get Intune policies to apply to the device when doing a manual enrollment?
SimonSkotheimsvik yes. I still used a provisioning package to get it AAD joined and we have auto enrollment on for intune. I only didn’t use the SurfaceHubConfiguration.csv file to automate adding a device account. I manually add the device account during OOBE, and then I have a dynamic AAD group to pick up all Hubs to which my intune policies are applied
