Have you had Virtual Servers running on a 2008 HyperV Server and needed to add a LPT port to the Virtual Server? If you was like me you searched the web and MS high and low and you found that it is a non supported deal and no one had a way to make it work. Well we had created a couple of Terminal Servers running on our HyperV Servers and some of the software needed the LPT1 port to be there. Well when HyperV was in Beta I monkeyed around and got LPT1 defined and working. Well you know what they tell you about documentation I ignored it and did not write down anything I had done to make it work. No problem here that settling will come over when I move them to new hardware. Wrong answer the settings did not.
Okay now what do I do well I messed with it some but run out of time so Randy our network admin took this and figured out what I did and this is the steps to create a LPT1 Port on your Virtual Server running on a 2008 HyperV Server. I am going to add to this that this is not a supported MS deal this is just what we came up with the make this work for us.
So I looked at the registry keys on the old machines and on the Registry Key on the new ones
I changed the DWORD Value of Start from 4 to 3
I did the same on CurrentControSet001 and CurrentControSet002 as well
On the registry Key
I added the missing key PARALLEL PORTS
Then I added a string \Device\Parallel0 with a value of \DosDevices\LPT1
Next I went into the services and disabled the services HP Port Resolver and HP Status Server
I’m not real sure if this actually had an impact but it seemed like a good idea when I ran across certain problems associated with these two services
Lastly if the LPT1 did not exist in the Device Manager I went to add Hardware and manually added a Printer Port.
Under the Printer port settings I changed it from LPT3 to LPT1
Checked the Option “Never Use an Interrupt” and checked “Enable Legacy Plus and Play Detection”
After I completed these steps on one of the terminal servers the error flag cleared immediately on the port in device manager. On the other I had to restart the server but when it came back up the error was cleared and it is working fine.
Til Later just Roger