Printers print garbage in remote desktop section

When conected in a remote desktop section with the Windows Server 2008, all the printing work from oulook, words, and explorer are send to the printer very slow and all it prints is garbage.

Hi,
Thanks for the post.
At this time, I need to confirm the following points with you.
1. Is TS Easy Print function used on Windows Server 2008?
2. If we just print a text file from Notepad, what will happen?
3. Is the problematic printer hosted on the client?
4. Is there any error message in the Event Log?
If TS easy print function is used on Windows Server 2008, please try to install the appropriate printer driver on TS server and disable the following policy setting, then verify if this issue will occur.
Use Terminal Services Easy Print printer driver first
Thanks,
Miles
This policy setting is located in the following node of the Local Group Policy Editor:
Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer RedirectionPlease remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

I want to be able to print using windows remote desktop services what printers can i use?

Hi I want to use Windows Remote Desktop Services on my iMAC.
I understand some printers work but some dont when printing from the VDI client.
Can anyone give me a list of printers that will work with the VDI client or some work arounds so that I can print using my iMAC and that print jobs can be parsed through the VDI clien to my iMAC and then printed through the iMACs connection to the printer
Thankyou

ARD won't be as smooth as you think over the Internet and be a security risk for your daughter.
Your best bet would be to install nannyware, then when she's asleep you can review the logs.
This is the best and Mac friendly
http://www.internetsafety.com/

HP LaserJet M1132 MFP does not print from a remote desktop

Hi,
I have a HP LaserJet M1132 MFP (product number CE847A) connected to a PC (MS Windows XP Home Edition + SP3) via USB. There is no problem with the printer. However, when the connection using Remote Desktop (it's set to use local facilities and resources, or in my case, printers, and serial ports) to the server (MS Windows Server 2008 R2), I can not even print a test page from a remote desktop.
Error message: "Print a test page failed. Do you want to display a tool to solve problems with printing to get help?"
But it does not lead to nowhere, as expected is access to the internet, and I have not it from a MS Windows Server 2008 R2.
The same error is for the HP LaserJet M1120n MFP.
I have installed on my PC other printer - old OKI ML321 (needle) connected to a PC using LPT cable and network printer Konica Minolta 1690MF (in another room). In both of these printers can easily print a test page from a remote desktop.
Please help me.
This question was solved.
View Solution.

Thank you for your interest.
The situation is a bit different than the picture. Windows Server 2008 R2 is available through the WAN. LAN is plugged into the PC-1, PC-2 and Konica Minolta printer. HP LaserJet M1120n MFP is connected via USB to the PC-1. OKI ML 3320 printer is connected via LPT also to the PC-1. PC-1 has access to Konica Minolta printer via the LAN. PC-2 also has access to Konica Minolta printer via the LAN. PC-2 is also available for PC-1 HP and OKI.
It seems to me that I found the explanation for the printing problems - some of "my" printers are simply not compatible with Windows Server 2008 R2. I found on the net the following information:
http://www.windowsservercatalog.com/item.aspx?idItem=cdde267a-800d-2d9f-1f0c-225cabd6838e&bCatID=128...
http://www.windowsservercatalog.com/item.aspx?idItem=31df9819-ca52-4684-dc3b-8e31b70c77d7&bCatID=128...
http://www.windowsservercatalog.com/item.aspx?idItem=6475235d-8dbb-9e95-11dc-3575d569acc2&bCatID=128...
http://www.windowsservercatalog.com/item.aspx?idItem=59731747-9976-8d51-dcbb-7664cbc17a89&bCatID=128...
I think I can close the topic.
(translated from Polish into English using Google translator)

Printer Redirection to Remote Desktop Server

Hello everyone, thanks for any help on this issue. We are running Server 2008 R2 with remote desktop. Our OS X users, a mixture of 10.5 and 10.6, connect with the remote desktop connection client for mac. They are using version 2.0.1 (090714).
We find that not all printers redirect once connected however some do. Currently we haven't found any differences, apart from the printer model that might cause this. Windows clients will redirect the same printers that do not redirect from OS X. Are there any guidelines around that show requirements for a printer to redirect from OS X to RDS 2008 R2?
Thanks again for any help
Mike

Hi we're seeing similar issues here but in our case none of our printers show up on the 2008 R2 Server when we connect from a Mac but they all show up when connecting from a Windows Box. Furthermore, the same Mac has its Printers show up fine when connecting to a Win 2003 R2 Server. Have you made any progress at your end?

Sharing a Printer With Microsoft Remote Desktop

How do you set it up?
The printer (Epson Stylus Photo 820) is connected through USB to an Intel iMac.
I control a Windows XP Pro PC from the iMac through firewire with Microsoft Remote Desktop and it works fine (although I can't get it to share the internet connection.) I have turned printer-sharing "On" in the iMac Preferences. I have also checked "Printers" in the "Connect automatically to these local devices when logged on to the remote computer" dialog box of MS RDC.
When I go to Add Printer in Windows, I search for a printer and get a tree view with "Microsoft Windows Network" on top and "WORKGROUP" under it. I try to input the printer name, but it tells me it can't find such a printer.
If I go to the Epson control panel under Windows, and click on ports, it shows the name of the iMac on four separate ports, and if I activate one of them it shows the Stylus 820.
But then it doesn't print.
Any ideas?

same problem here. cannot print a document from the remote desktop computer (microsoft) to my local printer connected to an intel mac .please can anybody help I have a offcejet HP g55

Printing locally from remote desktop not working

i have a client who recently upgraded his computers from xp to win7. he has a multi store quickbooks pos setup where he has to log in to a remote desktop connection onto a server in another store. he used to just login and run his reports and
then print them locally. since the upgrade, he has not been able to do this. the work around i found was to keep the xp laptop just for printing reports. well, now he is separating from the other store and going out on his own. he needs
to run some reports and save them to the local machine in order to bring the databases to his store. first, i need to know how to make the win 7 computer print the reports locally, so that he can run them (the xp laptop crashed). second, i need
to know how to copy the files onto his local computer (in server 2008 i can drag and drop them, not in 2003).
the win 7 is 64 bit, the server 2003 is 32. i tried installing the print drivers locally onto the server, but it's the wrong architecture. i also tried installing the 32 bit drivers onto the win 7 machine, same thing. i found several things
to try, but really need to get this fixed asap. when i try to install the printer, it shows up, and adds just fine. i am really having a fit here.
the copying thing is an absolute must also. i may be able to get by without the print issue fixed, but would like to know what happened just for my own information. thanx in advance.

Hi,
Firstly you can check whether print spooler service is not stopped. Also ensure that printer driver is compatible\supported by Windows 7 and by server. If you are using printer redirection then might happen that it’s not configure properly. The client must
have enough permission and also check client requirement for printer redirection (RDP 6.1 or above, .Net 3.5or above).
More information:
Terminal Server and Printer Redirection
Five reasons printer redirection causes Windows printing problems in RDS
For this can you describe little more”second, i need to know how to copy the files onto his local computer (in server 2008 i can drag and drop them, not in 2003).” Do you want to copy from remote session to local computer?
Hope it helps!
Thanks,
Dharmesh

Printing quality with Remote desktop technologies

Hello,
I manage several servers using Remote Desktop Technologies : 2003 R2 Terminal services, 2008 R2 RDS, 32/64 bits...
I upgraded recently to Adobe Reader X and I observe a strange behaviour : when I connect to theses servers with my RDP client, fonts are not the same as displayed, letters are glued without any spaces between them BUT if I connect to the console (HP ILO or vmware console), print quality is fine !!!!
I'm still making comparative tests but I'm stuck.
Any ideas ? I didn't find any thread related to this problem in the forums.
Kind regards,
Sebastien

Hi!
I have the same problem as you!
Other applications works fine with printredirects, but not Adobe Reader X. I have tried to modify the GPO to disable Remote Desktop Easy Print as i seen on Microsoft forums to try on printing errors, but no luck.
I have checked that the printerdriver seems to be the correct one for the local printer, but it does not matter.
Have you found out anything please let me know.
Best regards

Crystal Report unable to print out throught Remote Desktop from server

Dear All Expert,
I am facing problem when print a crystal report layout from SAP B1 8.8 through Remote to Server, print to Client machine. It will promt out Error Message "thunking spooler apis from 32 to 64 process has stopped working fix", but if print PLD, then it is work. Any Idea? Client machine using Windows 7 facing this problems, earlier using windows XP is fine. Thanks a lot.

Hi Gordon,
fyi, I have Turn Off UAC for the client machine (Win 7 32 bit), do the checking from command prompt (srf/scannow), uninstall the printer driver and reinstall the correct printer driver for server (windows server 64 bit), client machine (win7 32 bit), reboot the machine. Do the setting from internet option > Advance>
1. Allow active content fro CDs to run on My Computer*
2. Allow active content to run files on My Computer*
3. Allow software to run or install even if the signature is invalid.
But all of the above could not resolve the problem happen. It happen only print SAP B1 8.8 crystal report layout. Others PLD layout is able to print. Please Advice.

Remote Desktop doesn't work with local printer

I am having trouble using a locally networked printer when I use Remote Desktop to connect to a Vista machine. Under the local resources tab for RD, I have checked printers. The only thing I can figure is that my printer is networked locally, not connected directly to my machine. Every time I try to print during my remote desktop session, I can't access my locally networked printer.
I installed the printer drivers on the remote computer and when I try to locate the printer, I get the following error: "Windows cannot connect to the printer. Server print spooler service is not running..." but the spooler service IS runing.
I also found a post elsewhere that discussed setting 'share permissions' and 'network permissons' to resovle the spooler error. Still no go.
I tried to plug in my printer to a local USB port this morning. Still would not work. I keep getting the same spooling error. The drivers are not corrupt, as others have indicated may be the cause. They work fine on my system locally with 7.
Any advice would be greatly appreciated. I've spent a few hours on this one and am at a loss at this point.
Please help. I really need to print locally.

My problem was that the Vista remote system never saw local port that my printer was using for some reason and it never accepted the path noted above (\\servername\printer)...always came back with an error that it was an invalid path. This was with it both networked and plugged in via USB port.
I finally figued it out after four days and many hours on the phone with Microsoft. Microsoft support claimed that it was related to my router settings, but I didn't believe it since the remote computer saw my iPhone just fine when it was connected locally. After simply playing around, here's what I found...it was actually quite basic!
On the remote system, when you try to add a 'local' printer, there's a drop down menu with a list of local ports that your remote system sees. Some of those will be on the remote system, but others will be on your local system. Make a note of the ones that are seen on your local system. In my case, LPT1 was not visible, but COM3 was.
Next, on your local system, in the settings for your functioning printer (Printer Properties, Ports Tab), there's a tick box that says "Enable Printer Pooling." Once you check that box, you can select multiple ports on your local machine. Here, you need to tick the box that your remote system is seeing (in my case, it's COM3), but make sure that your exisitng port remains checked as well (in my case, an IP port for my wireless router). Basically what you're doing is on your local system, you are pooling your exising printer setup with a port that can be seen by your remote system.
Then, on the remote system, install the printer drivers but don't select a port. Then go into Printers and add a printer. Select 'local' setup for that and when asked for the port, use the port you checked in the previous step on your local system (in my case, I selected COM3 on my local system). Select your printer from the list. It will ask if you want to use the exisiting drivers...say yes. Then print a test page to be sure that it works. Worked fine for me.
I simply can't believe how obvsious that solution was! If the remote system can't see the port you currently use, pool your printer setup with a port that it can see!

Printing to a Printer Connected to TIme Machine when using Remote Desktop

Hi,
I am having trouble printing to a printer connected to our wireless network via Time Capsule when I am on my remote desktop connection. Printing from all other programs work. I downloaded Bonjour on our Windows based server, and it did not detect any printers. When I am connected directly to the printer, I can print when using remote desktop. Any suggestions are much appreciated.
Thanks!
Mac OS X (10.5.4)

Airport Extreme/Express do emulate Jetdirect/port 9100 printing, but that isn't what they use for printing from OS X. OS X and the Bonjour/airport software use USB port redirection, a unique and separate method.
If the HP driver supports any protocol over ethernet, it would be appletalk. Does that router server use appletalk?

Local printers won't show up in Remote Desktop Connection Manager 2.7

Hi everybody
I really need help. I connect to a server through RDC Man 2.7 on my Surface Pro 3 to use the installed accounting software. Now I want to print stuf such as journals but when I print, I cannot choose my locally installed wirless Printer. I used to be able
to do it using RDC Man on my iMac in OSX.
I have ticked printers on the local resources tab in settings to no avail. I hope somebody can help me with this issue as I really need to be able to print.
Thanks a million.
Best regards
Ben

Hello Ben,
Do you mean that the Surface Pro 3 can’t find the local wireless printer when you remote desktop to a server? And when you remote from a iMac at the same time, the Surface Pro 3 can find the printer?
Can the surface pro 3 printer when it is not connected with the remote server?
Please take the following steps for troubleshooting:
1. Check if you can normally ping the IP address of the printer when you can’t printer.
About the command ping, please take a look at the following article.
https://technet.microsoft.com/en-us/library/bb490968.aspx?f=255&MSPPError=-2147217396
2. Go to Control Panel\All Control Panel Items\Troubleshooting\All Categories
and run printer troubleshooter
3. Please try to update the driver from the manufacturer website and check if the issue still exists
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Hp laser jet 1102 printer dosen't work on remote desktop

i have a problem on printer HP laserjet 1102 on printing on remote desktop .
my printer connected to my computer and work ok but when i open anther computer remote it appear on it but not printing
if this printer dosen't support this option what is the model you advice me
many thanks for you

Try to run the print and scan doctor and check the results.
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03275041
Does it gives you an error message when you try to print from the remote desktop?
**Click the KUDOS star on the left to say 'Thanks'**
Please mark a reply "ACCEPTED AS SOLUTION" if it solved your problem, so others can find it.

Windows 8.1 Update - Remote Desktop missing from Remote Tab

I recently purchased a new Lenovo G780 with Windows 8. I updated to Windows 8.1 this past weekend.
I was surprised to find the "Remote Desktop" section (on Remote tab in System Properties) was missing. I can see "Remote Access Assistance" but not "Remote Desktop". Note that I can run Remote Desktop to connect to another computer, but w/out this setting I am UNABLE to accept incoming remote desktop requests.
I did find a link related to my very same issue, though for an earlier windows version.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/e51a7001-85f7-4578-af65-6dee5a35c261/...
I have same symptom, just newer OS I can only surmise that my Windows 8.1 update messed something up. It may be possible this was the situation before I updated to Windows 8.1, as I don't think I messed with that setting.
Does anyone know of a fix? Apparently re-inputting the Product Key (and reactivating Windows) might help solve but I don't have a Product Key for Windows 8...will Lenovo supply that?
Solved!
Go to Solution.

Hi dsmall2112,
I think you answered your own question again. The upgrade from Win 8 basic will only go to 8.1 basic. The key you have will only work on the Win. 8 basic and the upgrade to 8.1 will still only give you 8.1 basic, with that key.
In order to get Win 8.1 Pro features, you will have to buy a Win 8.1 Pro key.
Regards,
Dave
T430u, x301, x200T, x61T, x61, x32, x41T, x40, U160, ThinkPad Tablet 1838-22R, Z500 touch, Yoga Tab 2 Windows 8.1, Yoga Tablet 3 Pro
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
If someone helped you today, pay it forward. Help Someone Else!
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество

"Remote Desktop connection has stopped working." problem in Windows 8

here is the event log. Only happens on a few of our servers
Faulting application name: mstsc.exe, version: 6.2.9200.16384, time stamp: 0x50108ae1
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505ab405
Exception code: 0xc0000005
Fault offset: 0x0000000000002acd
Faulting process id: 0x13c4
Faulting application start time: 0x01cdbd0d09091fcd
Faulting application path: C:\Windows\System32\mstsc.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 4d923a55-2900-11e2-be73-cc52af4d02a3
Faulting package full name:

Your Ricoh printer drivers cause the crashes:
* Exception Analysis *
*** ERROR: Symbol file could not be found. Defaulted to export symbols for RC5BE130.DLL -
FAULTING_IP:
ntdll!memcpy+21a
000007f8`1fed2acd f30f6f4402f0 movdqu xmm0,xmmword ptr [rdx+rax-10h]
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 000007f81fed2acd (ntdll!memcpy+0x000000000000021a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000bd9e440c
Attempt to read from address 00000000bd9e440c
DEFAULT_BUCKET_ID: INVALID_POINTER_READ
PROCESS_NAME: mstsc.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000bd9e440c
READ_ADDRESS: 00000000bd9e440c
FOLLOWUP_IP:
RC5BE130!PrinterProperties+2a1ea
00000000`71c4c46a 8b442430 mov eax,dword ptr [rsp+30h]
DETOURED_IMAGE: 1
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
APP: mstsc.exe
FAULTING_THREAD: 0000000000001198
PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ
BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ
LAST_CONTROL_TRANSFER: from 0000000071c4c46a to 000007f81fed2acd
STACK_TEXT:
000000bb`ba9cf248 00000000`71c4c46a : 000000bb`00000040 000000bb`ba9cf618 000000bb`bd7a1458 00000000`00000000 : ntdll!memcpy+0x21a
000000bb`ba9cf250 00000000`71c4bf68 : 000000bb`b45ccc40 000000bb`bae6e7c8 000000bb`bd7a1458 00000000`00000000 : RC5BE130!PrinterProperties+0x2a1ea
000000bb`ba9cf2a0 00000000`71c4b2f9 : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`71c10000 : RC5BE130!PrinterProperties+0x29ce8
000000bb`ba9cf380 00000000`71c2a08a : 000000bb`bd7a1458 000000bb`bd7a1458 00000000`00000000 00000000`02000000 : RC5BE130!PrinterProperties+0x29079
000000bb`ba9cf3d0 00000000`71c283de : 000000bb`ba9cf618 000000bb`badfb050 000000bb`00000000 00650074`00730079 : RC5BE130!PrinterProperties+0x7e0a
000000bb`ba9cf440 00000000`71c2209d : 00000000`00000000 000000bb`ba9cf618 00007989`001a0019 000007f8`169fafa0 : RC5BE130!PrinterProperties+0x615e
000000bb`ba9cf550 000007f8`169e5ea0 : 00000000`00000000 000000bb`ba9cf618 000000bb`bd7a1458 000000bb`bd7a1458 : RC5BE130!DrvDocumentPropertySheets+0x1d
000000bb`ba9cf580 000007f8`169e6b9f : 000000bb`00000000 000000bb`ba9cf670 00000000`00000000 00000000`00000004 : winspool!DocumentPropertySheets+0xb0
000000bb`ba9cf5f0 000007f8`169e6aa5 : 00000000`00000002 000007f8`ffffffff 00000000`00000000 00000000`00000000 : winspool!DocumentPropertiesWNative+0xcf
000000bb`ba9cf680 000007ff`f4f3dc32 : 00000000`00000000 000000bb`b93f3990 00000000`000004d4 000000bb`ba9cf790 : winspool!DocumentPropertiesW+0x7d
000000bb`ba9cf6e0 000007ff`f4f9a09b : 00000000`00000000 000000bb`ba9cf7b0 00000000`00000000 000000bb`b93c7530 : mstscax!CTSClientPrintDriver::DocumentPropertiesW+0x37e
000000bb`ba9cf730 000007ff`f4f994d4 : 000000bb`b93c7530 000007f8`00000000 00000000`00000000 000000bb`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Invoke_DocumentPropertiesW+0x12b
000000bb`ba9cf7e0 000007ff`f4f8ff0c : 000000bb`b93c7530 000000bb`b93f29e0 000000bb`b94060d0 00000000`00000000 : mstscax!CStubITS_PrintDriver<ITS_PrintDriver>::Dispatch_Invoke+0x68
000000bb`ba9cf840 000007ff`f4f95a84 : 000000bb`b93c7530 00000000`00000000 000000bb`b93c7530 000000bb`b93cccc0 : mstscax!CStub<IMMClientNotifications>::Invoke+0x64
000000bb`ba9cf8b0 000007ff`f4f94310 : 000000bb`b93cccc0 000000bb`b93c7530 000000bb`ba9cf930 000000bb`b693b3c0 : mstscax!CRIMStreamStub::OnDataReceived+0x98
000000bb`ba9cf8e0 000007ff`f4f18c5a : 000000bb`b93cccc0 000000bb`b93f4cd8 000000bb`b93f4b10 000000bb`b93f4cd8 : mstscax!CRIMObjManager::OnDataReceived+0x150
000000bb`ba9cf960 000007ff`f4f20132 : 000000bb`b93c6908 00000000`00000000 000000bb`b93c6908 00000000`00000e28 : mstscax!CDynVCChannel::HandleAsyncCall+0x12e
000000bb`ba9cf9b0 000007ff`f4ed94e7 : 000000bb`b93f36a0 000000bb`b93c68c0 00000000`00000000 000000bb`b93f40d0 : mstscax!CDynVCThreadPoolThread::ThreadPoolEntry+0x102
000000bb`ba9cfa00 000007ff`f4c5aba9 : 000000bb`b7ddeb58 00000000`00000000 000007ff`f4b50000 00000000`00000000 : mstscax!CTSThread::TSStaticThreadEntry+0x33b
000000bb`ba9cfa90 000007f8`1e41167e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : mstscax!PAL_System_Win32_ThreadProcWrapper+0x25
000000bb`ba9cfac0 000007f8`1fef3501 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
000000bb`ba9cfaf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: rc5be130!PrinterProperties+2a1ea
FOLLOWUP_NAME: wintriag
MODULE_NAME: RC5BE130
IMAGE_NAME: RC5BE130.DLL
DEBUG_FLR_IMAGE_TIMESTAMP: 4bd67428
STACK_COMMAND: ~18s; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_RC5BE130.DLL!PrinterProperties
BUCKET_ID: APPLICATION_FAULT_INVALID_POINTER_READ_DETOURED_rc5be130!PrinterProperties+2a1ea
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/mstsc_exe/6_2_9200_16384/50108ae1/ntdll_dll/6_2_9200_16420/505ab405/c0000005/00002acd.htm?Retriage=1
Followup: wintriag
0:018> lmvm RC5BE130
start end module name
00000000`71b00000 00000000`71cdd000 RC5BE130 (export symbols) RC5BE130.DLL
Loaded symbol image file: RC5BE130.DLL
Image path: C:\Windows\System32\spool\drivers\x64\3\RC5BE130.DLL
Image name: RC5BE130.DLL
Timestamp: Tue Apr 27 07:20:40 2010 (4BD67428)
CheckSum: 001E2D52
ImageSize: 001DD000
File version: 0.3.0.0
Product version: 1.0.0.0
File flags: 1 (Mask 3F) Debug
File OS: 40004 NT Win32
File type: 2.1 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: RICOH CO., LTD.
ProductName: RICOH RPCS Printer Driver
InternalName: RC5BE130.DLL
OriginalFilename: RC5BE130.DLL
ProductVersion: 1.0.0
FileVersion: 7.6.9
FileDescription: RICOH RPCS Printer Driver
LegalCopyright: Copyright(C) 1999-2010 RICOH CO., LTD.
so check for a printer driver update and what you can also do is to avoid mapping your printer to the Remote Desktop. Maybe this also fixes the issue.
"A programmer is just a tool which converts caffeine into code"

Windows7 x64 Enterprise - SP1 disables Remote Desktop - missing RDP functionality

Windows 7 Enterprise x64 SP1
Installing SP1 (update KB976932) disables Remote Desktop functionality (System Properties/Remote tab will not show the "Remote Desktop" Section under the "Remote Assistance" section). The issue is known to MS.
Manually changing the registry keys
[HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server]
"AllowRemoteRPC"=dword:00000001
"fDenyTSConnections"=dword:00000000
will not help.
Removing SP1 (update KB976932) brings things back to work.
Does anyone know a way to keep using RDP with Windows7 Enterprise x64 after installing SP1? Is it a strategy from MS to prevent people to use it correctly? According to my experiments this happens only on the Enterprise edition.

Intresting issue.
I see that some other people are having problem with that as well.
http://www.sevenforums.com/network-sharing/149496-remote-desktop-doesnt-work-after-upgrade-sp1.html
However i have windows 7 enterprise 64 bit running on my laptop and i am fine. (and everyone else in my organization). Is it possible that your download for sp1 was corrupted/incomplete and as a result you are seeing issues now with it.
I would find it very strange, because I had the same behavior on 3 machines that are absolutely independent from each other, and download updates separately. Furthermore, when I investigated the problem, I even found somewhere an official document from MS,
saying that on this version RDP will be disabled by SP1, but maybe I am just not remembering it correctly. Are you sure that your systems are "Enterprise" and not "Professional"? On the Pro version everything is running fine.
I would try following:
Uninstall sp1
Stop windows update service
delete "C:\Windows\SoftwareDistribution" folder
Start windows update service
Run windows updates to scan for new updates (wuauclt /detectnow)
Install SP1
This is an interesting try. On one of these three machines I actually don't need RDP, so next weekend I will perform your suggestion, then I'll let you know what happens.

Printers print garbage in remote desktop section

Similar Messages

Maybe you are looking for