Windows 10: Provisioning Packages Not Naming Devices?

Hello there all. I come to you with a simple question that hopefully has an equally simple solution. For a while now I've been enrolling devices into AAD with provisioning packages, and I rely heavily on the naming convention to apply via the package so the device pulls the correct profile from Intune. Starting today for some reason, the provisioning process doesn't apply the device name anymore, which really slows me down by causing me to have to manually rename the device, reboot it, and then sign into the DEM account on Intune to have it begin pulling the correct profile.



Is there any reason that my .ppkgs would suddenly just... not apply names anymore? My target devices are on RS4... and so I'm not quite sure what the issue may be to be honest.

:)

 

Provision Package to control Start Menu tiles

Hello Stephen,



Thank you for writing to Microsoft Community Forums.



I suggest you to refer the article on
Building Windows 10 Provisioning packages.



However, the issue you posted is related to Provisioning packages with Windows 10 and would be better suited in the TechNet community. Please post your question in the
TechNet forum.



Hope it helps.

Let us know if you got the help you needed by clicking ‘Yes’ or ‘No’.



Regards,

Prakhar Khare

Microsoft Community – Moderator

 

Provisioning Packages and Scanstate


I've been experimenting with the new Provisioning Packages in Windows 10. They seem to be the new way to deploy and save customisations.

For instance you can now use the scanstate command (in the Assessment and Deployment Kit or ADK) to save customised software into a provisioning package for use when you create a Recovery Drive, and also for use when you Reset the computer.

Video is here:
WV9FR-cxFBg

A tutorial similar to the video, showing the detailed steps to create your own provisioning package, is here:
Create Custom Provisioning Package used to Reset Windows 10 or Create Recovery Drive

There is further discussion of scanstate here:
https://www.tenforums.com/installatio...-designer.html

 

Provisioning Package - Only for desktop app

Hi SpikeTJ2,

Provisional packages were designed to apply configuration settings to Windows 10 devices. It focuses only for the development of the personal or IT admin pre-planned settings for selected devices that they need to control. Are you an IT administrator handling
a small to medium size business?

Developing apps or its settings is a separate branch here. Every application have a different person that develops, they are the only ones that can be asked for a configuration.

For more information how this concept works, you can read more here:

• How provisioning works in Windows 10
• Provisioning packages for Windows 10

However, Provisioning packages for Windows 10 related concerns are best handled by our team in
TechNet forums. We recommend that you visit the site and click
Ask a question. If you don’t have a profile yet, create one and accept the legal terms by checking “I agree”. Once you’re done, click
Continue. After that, you can now start composing your queries and question about your concerns.

Let us know if you have more questions.