Windows 10: MS Autopilot and Computer rename

Hi there,


We have a serial number naming convention on our estate - We are moving to AAD with giving users the OOBE using InTune and Autopilot. One issue we came across was the %SERIAL% needs to have a parameter before it eg DESK-%SERIAL% - Is there anyway around this or do I have to use this, join the AAD and run a script to rename after?


Thanks

Paul

:)

 

Renaming the Computer...

Hi John,

Welcome to Microsoft Community and thank you for your interest in Windows 10.

I suggest you to rename the computer name as below and check if the issue persists.

Here’s how to rename the computer on Windows 10:

• Click on the Search icon in the taskbar Search icon;
• Search Rename this computer and click on the result;
• Click Change;
• Rename the computer and then click OK to save.

Hope this information was helpful and do let us know if you need further assistance. We will be glad to assist.

 

Windows Autopilot with Symantec Endpoint encryption

Hi,



Thank you for writing to Microsoft Community Forums.



We understand that you want to use Autopilot to upgrade Windows 7 to Windows 10, without decrypting Symantec Endpoint encryption drive.



We would suggest you to refer the Symantec article on
How to upgrade computers encrypted with Symantec Endpoint Encryption to a Windows 10 release and see if that helps.



You may also want to refer the article on
Windows Autopilot for existing devices to know more about using Windows Autopilot.



However, as you are working on Windows Autopilot, let me point you in the right direction towards the appropriate forum better suited for Windows Autopilot. I would suggest you to post your query in
TechNet forums, where we have support
professionals to assist you with your query. I hope that you will find the resolution at the earliest.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Autopilot Profiles: Azure /Intune.

In the Microsoft Partner Center Dashboard I am able to both create and configure Autopilot profiles and (once it’s working) register devices to apply those Autopilot profiles to.



In the Azure Intune Dashboard I am able to do the exact same functions as mentioned above in the Microsoft Partner Center by navigating:

• Open Azure
• Open InTune
• Click Device Enrollment
• Click Windows Enrollment
• In this GUI there are options for Windows Autopilot

The odd thing is that for the same customer I can configure Autopilot in two different places. Additionally, if I create a profile in one location, it does not propagate to the other. I can have two completely different profiles in each place.



How is it determined which is the profile that will be used for Autopilot if I have one in each place? Is one being phased out? Thanks for any information that you can provide.

Also, what would happen if we had a device from a completely different source than Ingram? Like we inherited a client that already had PC’s, and we wanted to onboard them with the Azure/InTune stack? Would we not be able to register
those devices? I don’t think Ingram would interested in taking requests for devices that they didn’t even sell.

Thank you.