I have just recently setup a new Microsoft 2008 R2 server on a ESX system. Everything works great with the server it has 4 gigs of ram and only utilizes a small portion of that. I setup this server to be a print server and currently I have the print manger with the internet services role installed. I also have the IIS role installed which allows me to browse my printers via the use of a URL. The problem I'm seeing is when users go to the site I have setup and select the printer they want to install and then actually install the printer using the site, they then see a very slow response from the printer when trying to print from within programs. An example would be if a users would working in Word and needed to print, they then would select print and it takes a good minute to actually pull the listing of available printers. I have tested this on multiple computers with the same result. However, If I just install the same printer locally then It reacts as you would expect, very quickly. I also notice that when the printer is installed using the URL or Internet Printing Protocol, it installs it on a HTTP port on the local machine. Is there a way to use the URL to install a printer on a local port so It doesn't have to communicate with the website for everything? Of if you know of any other options that I have yet to configure would be nice. I also have print spooling turning on and the printers are always available so all settings on the printer side match with what the settings would be if I installed the printer locally on the machine without the use of the URL. So the bottleneck here seems to be the way the printer installs from the URL?