Error applying Provisioning Package during OOBE - "Something unexpected happened. Please try again."

Question

I'm trying to apply a provisioning package to join the hub to AAD, auto-enroll into Intune, and use the SurfaceHubConfiguration.csv file to let the local user that's setting it up choose from a list of device accounts to sign into and speed up the configuration of the Hub.

I have the configuration file set up properly. When I get to the point during OOBE, I see the list of device accounts I added into my file. However, I do notice that there is a character limit as the friendly name (the third column of the configuration file - e.g. [City Name, Conf Room 3 Hub]) will have a character or two truncated depending on the length of the UPN and Friendly Name (and possibly the included password?). Does anyone have any information on these character limits?

Now to the issue: When I choose the device account to add, it spins for a few seconds and then I get a "Something unexpected happened. Please try again." without being able to continue. When I choose to the configure device account manually, I can add the account and sign in, and it autodiscovers all of the EXO and sip info properly. The next screen is the friendly name and device account name. The friendly name defaults to the display name in AD of the account (which is much much longer than what is defined in my csv - e.g. [City Name, Conference Room 3 (seats 6) (Surface Hub)]) and the username portion of the UPN, but then won't let me continue because it says it is too long (e.g. cityname.conference3). Once I shorten the device name to something sort of random, it works and allows me to continue.

Anyone have information again on character limits and what could be causing the device account from being added via the configuration csv? My only guess is that it tries to take the username portion of the UPN and change the objects device name, but won't allow because of the aforementioned naming length issue when configuring the account manually. Any insight would be appreciated.

greg_a · Answer

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.

greg_a · Answer

SimonSkotheimsvik&nbsp;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

greg_a · Answer

cezarcretu&nbsp;Maybe you can answer this question as well? You were able to answer my TeamsMode provisioning package thread. Thanks.

cezarcretu · Answer

Hello&nbsp;Greg_A,
&nbsp;
The device name character limit should be set by AAD but I'm not sure what the limit is. Please open a service request with the support team and we can look into this
&nbsp;
Thank you,
Cezar
&nbsp;

simonskotheimsvik · Answer

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.&nbsp;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

Forum Discussion

Error applying Provisioning Package during OOBE - "Something unexpected happened. Please try again."

6 Replies

Resources