Export (0) Print
Expand All

Preparing a Computer for Provisioning (WDK 8.0)

Using Microsoft Visual Studio to configure and set up driver deployment and driver testing is called provisioning a target computer or provisioning a test computer. For information about provisioning, see Configuring a Computer for Driver Deployment, Testing, and Debugging. Here we explain how to prepare a target computer for provisioning if you are using version 8.0 of the Windows Driver Kit (WDK).

The procedure for preparing the target computer depends on whether your computers are joined to a network domain or to a workgroup.

Host and target are joined to a network domain

  1. On the target computer, install the operating system that you want to use to run and test your driver. Join the target computer to the same network domain as the host computer.

    Note  If you cannot join the target computer to the same domain as the host computer, you can still provision the target computer. Enable the Administrator account on the target computer. For more details, see Host and target are joined to a workgroup. Then when you start the provisioning wizard on the host computer, enter the credentials of the target computer's Administrator account.

  2. On the target computer, go to Control Panel > Network and Internet > Network and Sharing Center. Under View your active networks, verify that the active network type is Domain.

    Note  If your target computer has an ARM processor, see Notes for ARM target computers.

  3. On the target computer, go to Control Panel > Network and Internet > Network and Sharing Center > Change advanced sharing settings. You will see a list of network types: Private, Domain, Guest or Public, and the like. Expand Domain. Select Turn on network discovery and Turn on file and printer sharing.

    Note  If the target computer is running Windows Server, see Notes for Windows Server Target Computers.

  4. If BitLocker is enabled on the target computer, disable it. For information about how to enable and disable BitLocker, see Help protect your files using BitLocker Drive Encryption.

  5. If Secure Boot is enabled on an x86 or x64 target computer, disable it. For information about Unified Extensible Firmware Interface (UEFI) and Secure Boot, see UEFI Firmware.

    If the target computer uses an ARM processor, install the Windows Debug Policy. This can be done only by Microsoft or the manufacturer of the target computer. You do not need to disable Secure Boot.

Host and target are joined to a workgroup

  1. On the target computer, install the operating system that you want to use to run and test your driver. Join the target computer to the same workgroup as the host computer.

  2. On the target computer, enable the Administrator account (if it is not already enabled). Go to Control Panel > System and Security > Administrative Tools > Computer Management. Navigate to Local Users and Groups > Users, and double click Administrator. Clear the Account is disabled check box.
  3. On the target computer, sign in as Administrator. If the Administrator password is currently blank, create a password for the Administrator account. Press Ctrl-Alt-Delete, and choose Change a Password.
  4. On the target computer, go to Control Panel > Network and Internet > Network and Sharing Center. Under View your active networks, note the active network type (Private or Public).

    Note  If your target computer has an ARM processor, see Notes for ARM target computers.

  5. On the target computer, go to Control Panel > Network and Internet > Network and Sharing Center > Change advanced sharing settings. You will see a list of network types: Private, Domain, Guest or Public, and the like. Expand the heading that matches your network type (Public or Private). Select Turn on network discovery and Turn on file and printer sharing.

    Note  If the target computer is running Windows Server, see Notes for Windows Server Target Computers.

  6. Verify that you are signed in to the target computer as Administrator.

    Note  It is not enough to sign in as another user that has administrative privileges. You must sign in as Administrator.

  7. If BitLocker is enabled on the target computer, disable it. For information about how to enable and disable BitLocker, see Help protect your files using BitLocker Drive Encryption.

  8. If Secure Boot is enabled on an x86 or x64 target computer, disable it. For information about Unified Extensible Firmware Interface (UEFI) and Secure Boot, see UEFI Firmware.

    If the target computer uses an ARM processor, install the Windows Debug Policy. This can be done only by Microsoft or the manufacturer of that target computer. You do not need to disable Secure Boot.

Verify that the host and target computers can ping each other. Open a Command Prompt window, and enter ping ComputerName.

If the host and target computers are joined to a workgroup and the two computers are on different subnets, you might have to adjust some firewall settings so that the host and target computers can communicate. Follow these steps:

  1. On the target computer, in Control Panel, navigate to Network and Internet > Network Sharing Center. Note your active network. This will be either Public network or Private network.
  2. On the target computer, in Control Panel, navigate to System and Security > Windows Firewall > Advanced settings > Inbound Rules.
  3. In the list of inbound rules, locate all Network Discovery rules for your active network. (Example: Locate all Network Discovery rules that have a Profile of Private.) For each of those rules, double click the rule, and open the Scope tab. Under Remote IP address, select Any IP address.
  4. In the list of inbound rules, locate all File and Printer Sharing rules for your active network. For each of those rules, double click the rule, and open the Scope tab. Under Remote IP address, select Any IP address.

Note  We do not recommend running the Driver Testing feature with BitLocker enabled on the target computer, as it will require you to re-enter the bitlocker key after every reboot.

Notes for Windows Server target computers

If the target computer is running Windows Server, enable these services before you turn on network discovery.

  • Function Discovery Resource Publication
  • SSDP Discovery
  • UPnP Device Host

If your target computer is running Windows Server, provisioning will fail the first time. After the failure, locate the DriverTest folder on the target computer (example c:\DriverTest). Right click the DriverTest folder, and choose Properties. On the Security tab, give Modify permission to the Authenticated Users group. Run the provisioning wizard again.

Notes for ARM target computers

If your target computer has an ARM processor, enable file and printer sharing by opening an elevated Command Prompt window and entering the following commands.

sc.exe config lanmanserver start=auto
sc.exe start lanmanserver
netsh.exe advfirewall firewall set rule group="File and Printer Sharing" new enable=Yes

Related topics

Configuring a Computer for Driver Deployment, Testing, and Debugging

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft