Applying an ICD provisioning package (Part 3)

1. part – I installed Windows Imaging and Configuration Designer (ICD) tool

2. part – I created a provisioning package

In this final part I’ll apply the created provisioning package to a Windows 10 Pro client system.


Here I got the non domain joined machine with a non standard computer name.

The computer is running Windows 10 Pro.



Copy the newly created provisioning package to the computer or a USB.




Run the Provisioning package? Yes, sure



Du you trust the creator? Yes, add it



NOTE: I removed the password in my test setup. In production you will be prompted for a password to apply the package.


The provisioning package is applied……





After the provisioning package is applied you’ll be signed out and the computer will restart a couple of times.



We sure did change something Smiley, der blinker



Verify that you now can login with your domain account.



After login. Cool…



The computer is now domain joined, have a standard computer name and the Windows version is now Enterprise.



Verify that the computer is in the right OU in Active Directory too and the mission is accomplished.



  1. 09/12/2015 at 16:43

    Are there any client side logs left after this process? I’m trying to troubleshoot why everything but Join Domain is working.

    • 11/12/2015 at 09:43

      Hi, you should look into the c:\windows\debug\netsetup.log for domain join issues, not ICD specific.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: