CCMEXEC.COM – System Center blog

CCMEXEC.COM – by Jörgen Nilsson

Browsing Posts tagged Configuration Manager vNext

Provisioning packages in Windows 10 is a really cool new feature which has great potential both for configuring Windows 10 and to assist in the deployment. Configuration Manager vNext has a great new feature as well which is Bulk enrollment of Windows 10 devices, Technical Preview 3 support Windows 10 Desktop edition, but let us all hope it will support Windows 10 Mobile as well when it is released. It is great news that we will get Bulk enrollment of Windows 10 devices!

It can be used to import a Trusted Root certificate, Wi-Fi Profile and enroll the device either in the cloud or On-Prem MDM which is new as well in Configuration Manager vNext. Panu and Kent has written a great blog post on how to get started with On-Prem MDM in Configuration Manager vNext Technical Preview, I had the same issue as they are explaining as well that my CRL lists where not accessible to non-domain clients and then you cannot enroll a Windows 10 using the MDM agent in Windows 10.

What I will focus on here is the new Bulk Enrollment feature. It is configured in the Configuration Manager vNext Admin Console, before we start note the following:

  • Configuration Manager vNext Technical preview must be installed and configured to support On-Prem MDM
  • You MUST start the Console with right-click and “Run as Administrator” otherwise creation of the Provisioning Package will fail.
  • A Trusted Root Certificate must be imported before starting the wizard under Compliance Settings, Company Resource Acess, Certificate Profiles.

Under All Corporate-owned Devices we have a new option under Windows, Enrollment profile.


We select Create Enrollment Profile in the menu. In the next dialog we can choose either On-Premise or Cloud.


We select which proxy enrollment point the Windows 10 client we run the provisioning package on should use.


We select the Root Certificate that should be imported as part of the enrollment process so that the Windows 10 client trust the certificate that is used for the roles in the Configuration Manager site that uses HTTPS.





Now we have a enrollment profile that we want to export to a provisioning package, that is achieved by selecting the enrollment profile and select export.


Then we have two files in that folder which makes up the provisioning package.


We then copy the files to a USB drive or locally on the Windows 10 computer and launch the provisioning package and we are presented with a dialog with what the package will do to the client.


After launching it we wait a minute before we open Work Access under Settings, Account in the Windows 10 client. There we now can see that the enrollment process is successful. Note that as it is enrolled as a Corporate owned device it has no username associated with it.


The provisioning package created can be opened using the Windows Imaging and Configuration Designer, you will get a warning that not all settings can be read.
bulkwicd After opening it we can see which feature in WICD that is used to do the Bulk enrollment which is shown below.

bulkwicd1I am really looking forward to when we can start using this live to enroll Windows 10 devices in Intune and Configuration Manager vNext ON-Prem MDM will be really cool. Then we can have a single provisioning package that can configure the device and enroll it in Intune. :D

Just a quick post to announce that our recordings from System Center User Group online meetings in June on “Enterprise Mobility Suite” and in September on “ConfigMgr vNext TP3 + Windows 10″ are now available on our YouTube channel, they are both in Swedish…

SCUG.SE – Sept 2015 – ConfigMgr vNext TP3 + Windows 10

SCUG.SE – June – Enterprise Mobilty Suite


One new feature in Configuration Manager vNext is a new Task Sequence step called: “Download Package Content”. It does what the name implies and could be one of my new small favorite features in Configuration Manager vNext. It will be useful to download content in a controlled way that later on can be used by scripts, applications installations.

There are a few options for the step on where you want the content located, the following are the options:

  • Task Sequence Working Directory
  • Configuration Manager Client Cache
  • Custom Path

To be able to choose the location is a really cool feature as we don’t want to fill up the Client Cache for instance.

It is also possible to set a task sequence variable containing the location of the downloaded package as show below.


So where does the files end up on the client in the example above? In the C:\Windows\temp directory?
Yes, in the C:\Windows\Temp folder and a folder with the PackageID as shown below.


The variable we created is available in the Task Sequence just as expected as shown in the variable dump below.

DownloadContent2This will be a very useful new Task Sequence step in the upcoming version of Configuration Manager which will at least get rid of some of the Xcopy and Robocopy steps out there. It would have been even better if it was possible to tick a box that it should copy the package content to in this case C:\Windows\temp and not a sub-folder with the packageID as name.