Upgraded from 2008 R2 Standard to Enterprise with DISM on remote desktop serer and now users can't print.

Hey,

Here's a little background: I added a second CPU to a vSphere hypervisor for a virtual 2008 R2 standard remote desktop server, upgraded from Standard to Enterprise to take advantage of the additional cores using DISM, everything goes smoothly but when users log in after the upgrade no one can print. The printer is a HP Color LaserJet 4525N.

I've uninstalled/re-installed with the most recent drivers, restarted the print spooler multiple times, installed the printer on two other 2008 R2 Standard servers and shared the printer (prints fine from the Standard servers) and created a local LPT2 port and mapped it to the shared printer on one of the other servers all to no avail. There is nothing in the event viewer regarding printing services. I am getting two errors:

1. Printing to a shared printer: "Test paged failed to print. Would you like to view the print troubleshooter for assistance? Operation could not be completed (0x0000000d)."

2. Printing directly to the printer via TCP/IP: "Test page failed to print. Would you like to view the print troubleshooter for assistance? Unable to create a print job."

I've researched the 0x0000000d error, but I haven't found anything that has worked.

Thanks
fishertechAsked:
Who is Participating?
 
David Johnson, CD, MVPConnect With a Mentor OwnerCommented:
VMWare Tools is saying its Out-of-date in the vSphere cleint. Which also reminds me of a piece of background info I for got to mention: in addition to upgrading from Standard to Enterprise, I also upgraded ESXi from 4.1 to 5.0 last week.

You didn't think this was pertinent? Upgrade your vmware tools and your problems will probably go away.
0
 
RichfieldTechCommented:
I've been told to only run print servers on "standard" servers.
0
 
fishertechAuthor Commented:
This isn't a print server. I'm simply trying to print from this 2008 R2 Enterprise server.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
fishertechAuthor Commented:
Just installed a second, different model printer and getting the same errors.
0
 
xmlmagicianCommented:
can you ping the printers?
and i assume that you are 100% that you have the correct drivers
0
 
fishertechAuthor Commented:
I can ping the printer, in fact I can log into it's web based interface from that server.

I've tried drivers freshly downloaded today, Windows drivers for this printer and drivers from older model HP CLJs. I also installed a Brother MFD we have and I get the same errors so I'm pretty confident it's not a driver issue.
0
 
xmlmagicianCommented:
do you get any other errors in the event viewer except the one you mentioned above?
0
 
fishertechAuthor Commented:
Nothing in event viewer.
0
 
fishertechAuthor Commented:
Update: I just enable printer redirection on the RDS so that I could see my local usb connected printer and I got the same error. Definitely something with the print spooler or the OS.
0
 
xmlmagicianCommented:
Have you done all the updates in case it is a known issue
0
 
fishertechAuthor Commented:
Yes, I checked this morning - it's completely up to date.

I came across something else today, the sound isn't working either on that server and my theory for that is VMWare Tools is saying its Out-of-date in the vSphere cleint. Which also reminds me of a piece of background info I for got to mention: in addition to upgrading from Standard to Enterprise, I also upgraded ESXi from 4.1 to 5.0 last week.
0
 
xmlmagicianCommented:
Try to update them see if it makes any difference
0
 
fishertechAuthor Commented:
You are correct  - I upgraded vmware tools last night on that vm and it did resolve the printer issue.
0
 
xmlmagicianCommented:
With all due respect isn't it what I said in my comment?
0
All Courses

From novice to tech pro — start learning today.