Redirected printers using Remote Desktop Easy Print driver work only once during session

Hello all
We are running Windows Server 2012 R2 Remote Desktop Services Sessions hosts with printer redirection allowed using only the Easy Print Driver, we have no other drivers installed on the servers. All client printers are redirected and can print fine, but
only once per session! We have tested with several different client printers and they all work a single time in each session. After that the user needs to log off and then back on again to be able to print once again, but only once. Needless to say, our users
are annoyed. If I look at the c:\windows\system32\spool\printers folder while jobs are printing, but failing, I can see the spool files appearing and disappearing as jobs are spooled. No errors in the event logs accompany the behaviour. Our clients are running
Windows 7, 8 and 8.1. All exhibit the same problem. The error looks a little like what is described here:
http://support.microsoft.com/kb/2925429
While similar, this problem describes a scenario where Easy Print is not used, but XPS is, and since Easy Print is based on XPS and the behaviour is very similar, I am tempted to make a connection.
I have checked all the usual stuff with permissions etc, and no manufacturer provided drivers are present. The problem appears on newly installed systems as well as one that have been running for some time. Restarting the spooler services does not resolve
the problem. Actually I do not think it is related to the spooler service or driver framework at all, but rather is an Easy Print driver issue that is occurring much later in the process, if not I would see some errors in the logs and no jobs would print at
all.
Anyone ever heard of something like this?
Thanks
Morgan

Hi Morgan,
Based from your description, users can only print once during single RDP session, I suggest you check if this issue also happens locally.
In addition, after the first print attempt, does any other issue exist on the RDP session?
Is the server fully patched? If there are any available driver updates, please also apply them. If there are any third party software installed, try disable/uninstall them to see if the issue persists.
You can also enable print auditing to get more detailed information about this issue.
More information for you:
Auditing Printing Events
https://technet.microsoft.com/en-us/library/cc976774.aspx
Logging Spooler Events
https://technet.microsoft.com/en-us/library/cc976746.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Similar Messages

Remote Desktop Easy Print with Windows 7 Professional host

Is it possible to utilize Easy Print with a Windows 7 Pro client hooking up to a Windows 7 Pro RDP Host? Easy print doesn't seem to be present in that scenario... but with Ultimate it seems to work...
Trying to print to a Dell 5110cn from my home computer with Win7-Pro to a printer here at work. Again, this works with a different machine with Win-7-Ultimate but doesn't with Win-7-Professional
Dell 5110cn <-[network]-> Windows7Pro client(@work) <-[RDP]-> Windows7Pro host(@home)

Hi,
No, the destination host needs to be Ultimate or Enterprise edition (or Windows Server 2008/2012 with RDSH installed). What you can do instead is install the exact same printer driver that you have on the client PC onto the host PC. That way
when you connect it will create a redirected printer using the manufacturer's driver instead of RD Easy Print driver.
-TP

Remote Desktop Farm Printing

Hello,
I am setting up a new 2008 R2 RDS load balancing Farm. I have seen other 2008 R2 Farms with identical print servers setup on each RDSH server. Each user gets an identical list of printers no matter which server they log into.
They use rdp profiles to follow them to each server.
Is it best to setup print server on each server or is there a different way to do this? It worked pretty well at other site. I just want to do it the best way. If there is any documentation thats good too.
Thanks!

Hi,
The best practice for setting printer in office environment depends on company’s requirement and many other factors. You can install printer or each server and then assign to use by users or make printer redirection setting for client to use as specified printer
is allocate to the users session. If you want then also try to RD Easy print service for your case. For more information you can go through beneath link.
1. The Ultimate Guide to Terminal Server Printing - Design and Configuration
2. Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
3. How to configure Microsoft RDS Universal Printing
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Remote Desktop Services Printer Redirection with easy print not working as Desired

Hi,
I have a Terminal Server Farm with a number of Windows Server 2008 R2 Remote Desktop Session Host Servers in the Environment. There is also a RD Gateway server which is used to connect to the RD Session host servers in the environment. We
had configure the policy "Use Terminal Services easy Print Driver First" for all the RD Session Host servers. Everything was working well untill a couple of users Complaint about slow printing on Easy Print. While trying to troubleshoot the issue we came
to know that when we by-pass the RD Gatewat and make a Direct connection to the RD Session Host Servers we are able to Print Really fast using Easy Print. Only When we use the RD gateway server we get the problem with the Printing.
As we could not get through this problem and we are not in a condition to by-pass RD Gateway for connections we decided to put the TS Easy print Driver as a Second option. We went ahead and identified the 3 printers for which printing was slow. we
Installed the Drivers for the same printers on all the Terminal Server and Disabled the policy "Use Termianl Server Easy print Driver First". After this we were able to print fast on the 3 printers having Slow printing issues. All the other Printers were using
Easy print.
After a day we realised that there were more than 20 drivers for Different printers installed in the Print Server Properties. We started getting viered problems with the Printing on all the Terminal servers like, Print Spooler Service Crashing, Hanging,
Users not able to redirect printers at all. To avoid this we Removed the Driver Packages but they came back the very next day.
I am not sure what could be causing this kind of behavior. I would really appriciate if someone can help he with these two problems
1) Easy print Working Slow only when using RD Gateway Server
2) Printer Drivers Getting installed on Terminal Servers when Easy Print Policy is disabled.

1) Easy print Working Slow only when using RD Gateway Server
> Difficult to track down especially through forum. Looking for some known issues/hotfixes
954743 FIX: After you apply hotfix 954744, printing performance may be significantly slower when you print documents by using Terminal Services Easy Print
http://support.microsoft.com/?id=954743
The Remote Desktop Easy Print (RD Easy Print or TS Easy Print) uses the XPS print driver that ships with .NET Framework.
2) Printer Drivers Getting installed on Terminal Servers when Easy Print Policy is disabled.
> If Easy print is not the first driver then it installs the driver if they are InBox drivers
> If these are non-inbox drivers - This is because administrators are RDPing to the server from another PC with several printer/drivers installed.
When they RDP with printer redirection enabled, the drivers get automatically installed.
To avoid this, either turn off printer redirection at server level from RDP-TCP properties - might not be feasible if users need redirected printers
Else make sure that when admins RDP, printer redirection is turned off so that drivers are not automatically installed
This was a major issue in 2k3, i havent tested it in 2k8 though
This behavior is related to the change you made in Easy print driver behavior
Sumesh P - Microsoft Online Community Support

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?

Easy print not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1

Easy print is not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1 . Printers dont get redirected when you connect to the terminal server. The server we are connecting to has Windows 2008 server. On 32 bit Windows
7 and windows XP clients Easy print is working fine and printers get redirected in terminal server.

I am having the exact same problem. Windows 7 works fine, but 8.1 will not redirect printers. Others said to check local policy terminal services settings and my setting are all set as they should.
I think Windows 8.1 is not telling the terminal server what printers it has.

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

I am accessing a windows server using remote desktop and I am wondering if I can transfer files by sharing drives?

Probably. You may be able to use Finder > Go > Connect to server to access the server. You may be able to share folders using Remote Desktop too. Whichever one you like the best.

Print with Easy Print Driver

Helo!
We need print from redirected printers on Windows Terminal Server based on Win 2008 Server.
Driver which used for that print task is Easy Print driver. WTS administrators say that we can't use any other drivers for that print task.
But when I printin this way from sap spool request created in WTS spool, but not redirected to client PC spool and not printed on it.
Please explain which Device Type I can use in SPAD SAP for print via Easy Print driver?

Dear Evgenij Sorokin ,
1) There is no need to install any drivers in WTS .
2) It is the access method which is important not the device type.
3)Use access method 'G' while creating output device.'SAPWIN' device type is enough.
4).visit this page http://mywts.sap.com/faq/WTSPrintingInformation.pdf
Your local printers are seen in the WTS if they are shared while connecting to the terminal server.

"remote desktop connection has stopped working" When printing from remote desktop connection

I have been having a issue when using a windows 7 machine. I have Remote Desktop to a session on Windows2008 R2, I am using the local printer resources to redirect the printing. However everytime i try to print it crashes the remote desktop application.
Gives me "remote desktop connection has stopped working." I have 4 other computers connected and printing with no issues what so ever. This only happens when i print. It does print by the way just the application crashes.
-I have also updated the printer drivers to newest possible thru the manufactorer website. The printer is a Brother MFC-8890DW. Windows 2008 R2 is up to date for the RDS server. 3 other machines are able to Remote in and print. The user is able to print using
diffrent machines just not the Windows 7 machine.

Hi,
Happy to hear that you resolved your issue. For another issue which you are facing here trying to provide some suggestion.
As you have commented that you are facing issue with second screen resolution on wide screen. The setting which I am suggesting can only applies when you are using multi-monitor Remote Desktop connections. If you are making Connections using a single
monitor do not use this setting.
So for this you can try to apply “Limit maximum display resolution” setting in group policy, where you can mention the width & height for the screen to display. The setting can be applied on below mentioned
path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment
Meanwhile sharing article with you for more information.
Remote Session Environment
http://technet.microsoft.com/en-us/library/ee791847(v=ws.10).aspx
Hope it helps!
Thanks.

Report hangs when using Remote Desktop

I am having trouble with Crystal Reports 11. I was wondering if there is a known issue when using it in conjuction with Remote Desktop.
Here is the scenario.
I am using Remote Desktop to connect to a server.
I am running a report using Crystal Reports 11.
The records have already been retrieved (approx. 800,000 records) and is printing - slowly.
It takes around 75 minutes for the report to print 12 pages.
If the Remote Desktop connection is closed, then re-established, the Crystal Reports pops up a message box stating "Not Supported". The pages of data the were previously printed are now blank. (For example: if it was on page 1 of 9+ it will go back to 1 of 1+ and the page will be blank.)
If I use a VPN to connect to the network, then use the Remote Desktop Connection to connect to the server, the connection will periodically disconnect and the re-establish. This does not occur when not using Crystal Reports.
Is there a problem with using Crystal Reports with Remote Desktop? Is there a better way to run my reports remotely?
Thanks for any input.
Ryan

You may be better off posting this in the Crystal Reports Design forum as that team supports issues regarding working with the CR designer:
SAP Crystal Reports
Ludek

Cannot use Remote Desktop host on Windows 8.1 Pro, termsrv corrupted?

Hello,
Few days ago I upgraded my home desktop machine from Windows 8.1 to Windows 8.1 Professional so I can use the Remote Desktop feature.
I enabled everything needed, checked "Allow computers to connect to this computer" from the Remote Settings, forwarded the port 3389 in my rounter and allowed it in my firewall etc...
But I still can't connect to this computer from outside my home network or inside it. The error I get trying to connect is this:
(For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
I'm trying to connect using a laptop running Windows 7 Home Premium.
After searching around I found out that the service responsible for the RDP is called "TermService", I found it on my services but was unable to start it:
(For some reason i still can't post images in this forum...) So I posted a link below to my original thread with the images
Also, notice the description of the service. So I tried to run a System File Checker on the service's DLL (sfc /scanfile=c:\windows\system32\termsrv.dll) and got this log:
2014-10-05 14:20:41, Info CBS TI: --- Initializing Trusted Installer ---
2014-10-05 14:20:41, Info CBS TI: Last boot time: 2014-10-05 13:56:05.492
2014-10-05 14:20:41, Info CBS Starting TrustedInstaller initialization.
2014-10-05 14:20:41, Info CBS Ending TrustedInstaller initialization.
2014-10-05 14:20:41, Info CBS Starting the TrustedInstaller main loop.
2014-10-05 14:20:41, Info CBS TrustedInstaller service starts successfully.
2014-10-05 14:20:41, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2014-10-05 14:20:41, Info CBS Startup processing thread terminated normally
2014-10-05 14:20:41, Info CBS Starting TiWorker initialization.
2014-10-05 14:20:41, Info CBS Ending TiWorker initialization.
2014-10-05 14:20:41, Info CBS Starting the TiWorker main loop.
2014-10-05 14:20:41, Info CBS TiWorker starts successfully.
2014-10-05 14:20:41, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:41, Info CBS Universal Time is: 2014-10-05 11:20:41.783
2014-10-05 14:20:41, Info CBS Loaded Servicing Stack v6.3.9600.17246 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.17246_none_fa4ae8e99b1f603c\cbscore.dll
2014-10-05 14:20:41, Info CSI 00000001@2014/10/5:11:20:41.786 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffeeace2e53 @0x7ffeeace24ac @0x7ff69a94d2df @0x7ff69a94dc97
@0x7fff02912225)
2014-10-05 14:20:41, Info CBS SQM: Initializing online with Windows opt-in: True
2014-10-05 14:20:41, Info CBS SQM: Cleaning up report files older than 10 days.
2014-10-05 14:20:41, Info CBS SQM: Requesting upload of all unsent reports.
2014-10-05 14:20:41, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2
2014-10-05 14:20:41, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2014-10-05 14:20:41, Info CBS NonStart: Set pending store consistency check.
2014-10-05 14:20:41, Info CSI 00000002@2014/10/5:11:20:41.801 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffee15c60e5 @0x7ffef3637fc0 @0x7ffef36380f2 @0x7ff69a94ca25 @0x7ff69a94dcae
@0x7fff02912225)
2014-10-05 14:20:41, Info CSI 00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x559943db20
2014-10-05 14:20:41, Info CSI 00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
2014-10-05 14:20:41, Info CSI 00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x26c
2014-10-05 14:20:41, Info CSI 00000006 Poqexec successfully registered in [ml:26{13},l:24{12}]"SetupExecute"
2014-10-05 14:20:41, Info CSI 00000007@2014/10/5:11:20:41.999 Beginning NT transaction commit...
2014-10-05 14:20:41, Info CSI 00000008@2014/10/5:11:20:41.999 CSI perf trace:
CSIPERF:TXCOMMIT;143
2014-10-05 14:20:42, Info CSI 00000009 CSI Store 367642371808 (0x00000055993166e0) initialized
2014-10-05 14:20:42, Info CSI 0000000a [SR] Verifying 1 components
2014-10-05 14:20:42, Info CSI 0000000b [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:42, Info CSI 0000000c [SR] Verify complete
2014-10-05 14:20:52, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:55, Info CBS TiWorker: Client requests SFP repair object.
2014-10-05 14:20:55, Info CSI 0000000d [SR] Verifying 1 components
2014-10-05 14:20:55, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:55, Info CSI 0000000f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000010 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 00000011 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000012 [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 00000013 [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
2014-10-05 14:20:55, Info CSI 00000014 Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000015 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000016 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
in store is also corrupted
2014-10-05 14:20:55, Info CSI 00000017 [SR] Verify complete
2014-10-05 14:20:55, Info CSI 00000018 [SR] Repairing 1 components
2014-10-05 14:20:55, Info CSI 00000019 [SR] Beginning Verify and Repair transaction
2014-10-05 14:20:55, Info CSI 0000001a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 0000001b [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 0000001c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 0000001d [SR] Cannot repair member file [l:22{11}]"termsrv.dll" of Microsoft-Windows-TerminalServices-RemoteConnectionManager, Version = 6.3.9600.17095,
pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-10-05 14:20:55, Info CSI 0000001e [SR] This component was referenced by [l:154{77}]"Package_3_for_KB2959626~31bf3856ad364e35~amd64~~6.3.2.0.2959626-3_neutral_GDR"
2014-10-05 14:20:55, Info CSI 0000001f Hashes for file member \??\C:\Windows\System32\termsrv.dll do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000020 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..teconnectionmanager_31bf3856ad364e35_6.3.9600.17095_none_7f53b5b72842754a\termsrv.dll
do not match actual file [l:22{11}]"termsrv.dll" :
Found: {l:32 b:wutByJu/YxhxLZan2VmIk9CNy/65VNpYphCkpd5tWqQ=} Expected: {l:32 b:cLIGmreRLrSas6vRjUtCy5Ssmcpt4/Y/SIi46qx4qqI=}
2014-10-05 14:20:55, Info CSI 00000021 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"termsrv.dll"; source file
in store is also corrupted
2014-10-05 14:20:55, Info CSI 00000022 [SR] Repair complete
Since it's the first time I use this tool I'm not familiar with this log file, but what I managed to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
My question is:
How can I repair this file? Is this even the problem preventing me from connecting to this computer via Remote Desktop?
Here's a link to my original question which contatining the images.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-system/cannot-use-remote-desktop-host-on-windows-81-pro/e4776239-4d9e-4934-ae2d-b87cc09f7ade

managed to figure out from it is that termsrv.dll is corrupted and windows cannot repair it for some reason.
So, the next step supposedly is
using DISM.
Coincidentally I reached that page last night from
this one, which I thought gave me a better awareness of how much manual repair might be possible. E.g. maybe the WinSxS isn't quite as fragile as we are being led to believe? (It's making me feel sort of like how I used to feel about the
registry when seeing all the caveats about using RegEdit before I got used to that tool.)
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779(v=WS.10).aspx
Something else that I became aware of yesterday serendipitously is SxStrace.exe. I have never seen it used but it sounds useful. E.g. perhaps easier to interpret for supplemental clues than the ProcMon trace that I usually advocate.
Or perhaps use both and see in ProcMon when the SxStrace is writing. E.g. filter with Operation Is WriteFile.
However, what I would do first is find out what the state of your system is regarding that module. E.g. try this Powershell pipeline to list what you have.
PS C:\windows> dir -R -Fil "termsrv.dll" | sort-object FullName | ft Length, FullName -AutoSize
Note that I am giving you the whole command line, including prompt to show where the command should be started from.
C.f. another thread where doing the same diagnostic procedure seems to be finding more a problem with the Windows Update software than with the user's WinSxS cache.
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_store/windows-81-store-error-0x80070002-comprehensive/2b0ed3e1-1835-4517-97dd-0a7abb6ef74c?page=3#LastReply
HTH
Robert Aldwinckle

Agent install hang When Install by using remote desktop

Hi All
My Customer has some workstation,that were placed on branch office,occur some problem and he want to re-install.
When he using remote desktop to login/install, ZCM Agent install service will hang on "novell-rm-md-core". he test some times and get the same result.
But he call another admin install agent locally. agent install successfully.
Who have the same experience about remote install by using remote desktop(mstsc) ??
thanks
wyldkao

Originally Posted by wyldkao
Hi All
My Customer has some workstation,that were placed on branch office,occur some problem and he want to re-install.
When he using remote desktop to login/install, ZCM Agent install service will hang on "novell-rm-md-core". he test some times and get the same result.
But he call another admin install agent locally. agent install successfully.
Who have the same experience about remote install by using remote desktop(mstsc) ??
thanks
wyldkao
Windows XP right?
Then you need to install this patch before installing ZCM agent: An application that installs a mirror driver over a Terminal Services session may stop responding on a Windows XP-based computer
Thomas

I don't have a wireless keyboard or mouse for my 2007 iMac, is there any way that can use remote desktop and access it from my 2010mbp.

i don't have a wireless keyboard or mouse for my 2007 iMac, is there any way that can use remote desktop and access it from my 2010mbp

Hi champrider,
You can use an application such as Apple Remote Desktop to control your iMac remotely. See this article -
OS X Mavericks: Allow access using Apple Remote Desktop
This help page will provide you with some other useful resources for Apple Remote Desktop -
Remote Desktop Help
Thanks for using Apple Support Communities.
Best,
Brett L

Not able to use remote desktop externally on a WRV200

Hello all,
Untill 5 minutes ago I wasn't able to get remote desktop to work from an extern computer to my computer which is wireless connected in our network. It worked from a network computer from the beginning.
I have port 3389 correctly forwarded to my static intern ip address (same way as i did with my ftp server which works properly, so I guess I did it wright)
Just 5 minutes ago I found out that it does work when I enable DMZ (see bottom for DMZ details).. What am I doing wrong? I prefer not to use DMZ since it will automatically forward all internet port requests which arent forwarded to any of the other computers, which makes my computer quite vulnerable, wright? (I am using the win xp firewall, but still)
Thanks in advance!
Edit 1: I have UPNP enabled
Edit 2: I have remote desktop excluded in the windows firewall, but thats logic since remote desktop does work from another network computer and with DMZ enabled
Edit 3: I'm the only one in our network who is using remote desktop
Edit 4: I also tried to forward all these ports to my pc: 22, 65301, 5631-5632
The DMZ screen allows one local PC to be exposed to the Internet for use of a special-purpose service such as
Internet gaming and videoconferencing through Software DMZ. Whereas Port Range Forwarding can only forward
a maximum of 10 ranges of ports, DMZ hosting forwards all the ports for one PC at the same time.
Message Edited by PulpVictim on 07-06-2007 02:30 AM
Message Edited by PulpVictim on 07-06-2007 02:34 AM
Message Edited by PulpVictim on 07-06-2007 02:35 AM
Message Edited by PulpVictim on 07-06-2007 02:39 AM

Enable the logs on your router. Then try to do remote desktop. It will fail of course. After it does, view the logs, there might be ports listed in the incoming logs that you failed to forward.

How to use remote desktop client in mountain lion

How to use remote desktop client in mountain lion.
I want to connect my other system(ubuntu) using mac remote desktop client, But i could not locate remote desktop client in moutain lion.

In Ubuntu 12.xx use Dash to find "Desktop Sharing" and set the preferences, including requiring a password.
Then in Ubu use System Settings > Network to determine your Ubu machine's IP address, such as 192.168.1.13.
On the Mountain Lion Mac do Finder > Go > Connect to Server and enter: vnc://192.168.1.13 or whatever your IP is. Enter the password that you used in the Ubu Desktop Sharing setup, when asked.
On the Ubu machine answer the question that pops up asking for permission to connect. Your Ubu screen will now show up on the Mac, and you can remote control it. Here I am running "Octave" (a math program) on the Ubu machine, remotely.
Works great! BTW, you can do this from an iPad too, using a VNC client such as Mocha VNC Lite. You can even run both remotes simultaneously.
Good luck.

Redirected printers using Remote Desktop Easy Print driver work only once during session

Similar Messages

Maybe you are looking for