Scenario: You are writing a kernel driver project in Visual Studio 2013 and you want to provision a computer as a target. Unfortunately, you end up with a WDKRemoteUser user name or password not found. And the provisioning fails with a message similar to this:
Provisioning log
Installing necessary components...
Connecting to computer "192.168.68.28"
Connecting to driver test automation service
Getting computer system information
Copying driver test automation files
Copying driver test automation files succeeded
Configuring WDK Remote User Account
WDK Remote User Account successfully created
Installing .NET Framework (possible reboot)
Installing .NET Framework (possible reboot) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing VC Redist (x64)
Installing VC Redist (x64) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing test automation (x86)
Installing test automation (x86) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing test automation (x64)
Installing test automation (x64) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing debuggers (x86)
Installing debuggers (x86) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing debuggers (x64)
Installing debuggers (x64) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing driver test framework
Installing driver test framework failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Registering logging components
Registering logging components failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Configure debugger settings (x64) (possible reboot)
Configure debugger settings (x64) (possible reboot) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Configure computer settings (x64) (possible reboot)
Configure computer settings (x64) (possible reboot) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Creating system restore point
Creating system restore point failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
What do?
Solution: Log in to the target computer with an admin account. Go to 'Edit Local Users and Groups'. You should see the 'WDKRemoteUser' in the list. Right-click the user and 'Set Password...'. Put in a password that will work with your group password policy. Sign out and login as ".\WDKRemoteUser" with your current password. Retry the provisioning with the corresponding debug settings. It will run through the provisioning correctly this time.
Please leave a comment if you have any issues. I'll take a look and try to replicate it.
Provisioning log
Installing necessary components...
Connecting to computer "192.168.68.28"
Connecting to driver test automation service
Getting computer system information
Copying driver test automation files
Copying driver test automation files succeeded
Configuring WDK Remote User Account
WDK Remote User Account successfully created
Installing .NET Framework (possible reboot)
Installing .NET Framework (possible reboot) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing VC Redist (x64)
Installing VC Redist (x64) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing test automation (x86)
Installing test automation (x86) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing test automation (x64)
Installing test automation (x64) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing debuggers (x86)
Installing debuggers (x86) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing debuggers (x64)
Installing debuggers (x64) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Installing driver test framework
Installing driver test framework failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Registering logging components
Registering logging components failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Configure debugger settings (x64) (possible reboot)
Configure debugger settings (x64) (possible reboot) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Configure computer settings (x64) (possible reboot)
Configure computer settings (x64) (possible reboot) failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
Creating system restore point
Creating system restore point failed. Please ensure connectivity with the remote machine, and then restart the provisioning process.
What do?
Solution: Log in to the target computer with an admin account. Go to 'Edit Local Users and Groups'. You should see the 'WDKRemoteUser' in the list. Right-click the user and 'Set Password...'. Put in a password that will work with your group password policy. Sign out and login as ".\WDKRemoteUser" with your current password. Retry the provisioning with the corresponding debug settings. It will run through the provisioning correctly this time.
Please leave a comment if you have any issues. I'll take a look and try to replicate it.
I have tried this, and cannot get logged in via WDKRemoteUser. Initially I set the account to have no password and that didn't work. I changed it to accept a password, and still cannot login to it. In either case, the login seems to begin (as in it seems to accept the password, or not care when configured to not need a password) but then reports that the user profile cannot be loaded.
ReplyDeleteI am using Visual Studio 2015 Community and WDK for Windows 10, and the PC is running Windows 10. thanks,
One of the conditions to set up a profiling is that you have to be able to connect to the test machine by name. I found that once I was able to do that, I didn't have any issues with the login/password. Both computers were on a domain, if it helps.
ReplyDeleteThank you! this was the last missing piece of the puzzle in my config.
ReplyDeleteW7-64 host.
W7-64 target on a vmware guest in the host. Connected to debug through Named Pipe.
Additionally for good measure after setting the password for WDKRemote user, I also added the user as a "AutoLogon" user.
The install/deploy step then went through without a problem.
Curiously the password for the user was then changed again by Visual Studio 2013.