–
Kernel Drivers
Windows File System and Device Driver Consulting www.KernelDrivers.com
866.263.9295
------ Original Message ------
From: “xxxxx@gmail.com” To: “Windows File Systems Devs Interest List” Sent: 9/25/2017 4:43:52 AM Subject: RE:[ntfsd] Remote debugging in Microsoft Visual Studio
>I basically followed the instructions from Microsoft on how to >provision and debug on a remote system. Right now in Visual Studio if >I right click a project and deploy or debug it appears to go through >the steps to connect, drops files on the remote pc and attempts to >install etc. I have done a lot of googling and is it a case that this >automatic remote provisioning and setup only works with windows drivers >and not microfilters? For example I dont see fltmc being run >remotly… > >— >NTFSD is sponsored by OSR > > >MONTHLY seminars on crash dump analysis, WDF, Windows internals and >software drivers! >Details at http: > >To unsubscribe, visit the List Server section of OSR Online at >http:</http:></http:>
This was a small write up I was given when I started to write drivers. Hopefully this helps else just configure Windbg using pipes
Create virtual machine:
Network: Bridge Adaptor
Turn off firewall using control panel
Make remote access possible.
Know ips of both machines using ipconfigure. Try to ping from both machines to each other.
Deploy and install the driver
Copy C:\Program Files (x86)\Windows Kits\10\Remote\x64(x86)\ of host into target pc.
Run C:\Program Files (x86)\Windows Kits\10\Remote\x64(x86)\WDK Test Target Setup x64-x64_en-us.msi file on target.
On the host computer, in Visual Studio, on the Driver menu, choose Test > Configure Devices.
Click Add new device.
Display Name: name for target pc
Network host name: target pc?s ip address
Select Provision device and choose debugger settings.
Connection Type:Network
Port No: 52121(between 50000-65535)
Host ip : Ip of host machine.
on target machine use bcdedit /dbgsettings command in cmd(always run as administrator).
It should show configurations done above and key which we obtain.
Target computer should be log in as WDKRemoteUser.