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

Similar Messages

  • How to use Remote Desktop Service in Windows Azure

    Good day
    Hi! im kinda newbie when it comes to windows azure, I would like to ask if how can we use the RDS CAL in windows azure?

    Hi,
    Please visit the URL below for detailed instructions on using/configuring RDS CAL.
    http://blogs.technet.com/b/keithmayer/archive/2013/09/04/step-by-step-remote-desktop-services-on-windows-azure-a-cost-effective-alternative-to-desktop-as-a-service-part-2.aspx
    Regards

  • Can I use Remote Desktop to run Windows software from my Mac

    Here's what I want to do:
    1) Set up a small office LAN with an Apple Xserve as the file server; clients are mostly iMacs but a few PCs.
    2) There are one or two software apps I need that exist only in the Windows world (such as a good document comparison software like DeltaView).
    3) I want to have one dedicated PC for my one or two essential Windows apps and then run Remote Desktop Connection on my Mac client to launch the Windows app on the PC client and use it to edit or otherwise manipulate a data file stored on the server.
    Is this possible?

    Thanks for your prompt reply.
    OK, maybe I'm missing something basic but then why would I ever want to run Windows network in my office? The bugbear about Macs is that there is certain Windows software for which there is no good Mac equivalent. But you are telling me that as long as I have a couple of Windows boxes, I can run my Windows software on them through my Mac, even though the data files are stored on an separate box (an Xserve).
    Now, for the $64 question -- is it possible to set up a network in such a way that I could use RDC on my PowerBook in, say, Chicago to run the software installed on the Windows box and in turn to open and manipulate the files stored on the Xserve in my office, halfway across the world in Abu Dhabi? Would this be a particularly difficult configuration?
    Thanks,
    DXB Law

  • Cannot get Remote Desktop to work on Windows 7

    Ok. I am having issues trying to connect remotely using RDP. From what I know, the network was pre-configured from another IT group and was able to get it up and running. My company was commissioned to migrate his old PC (WINXP) to Windows 7. I have gone
    through the steps of allowing remote desktop and following instructions:
    To configure remote access, follow these steps:
    1. In Control Panel, click System And Security, and then click System.
    2. On the System page, click Remote Settings in the left pane. This opens the System Properties dialog box to the Remote tab.
    3. To disable Remote Desktop, select Don’t Allow Connections To This Com¬puter, and then click OK.Skip the remaining steps.
    4. To enable Remote Desktop, you have two options. You can:
    Select Allow Connections From Computers Running Any Version Of Remote Desktop to allow connections from any version of Windows.
    Select Allow Connections Only From Computers Running Remote Desktop With Network Level Authentication to allow connections only from Windows 7 or later computers (and computers with secure network authentication).
    5. Click Select Users. This displays the Remote Desktop Users dialog box.
    6. To grant Remote Desktop access to a user, click Add. This opens the Select Users dialog box. In the Select Users dialog box, click Locations to select the computer or domain in which the users you want to work with are located. Type the
    name of a user you want to work with in the Enter The Object Names To Select field, and then click Check Names. If matches are found, select the account you want to use and then click OK. If no matches are found, update the name you entered and try searching
    again. Repeat this step as necessary, and then click OK.
    7. To revoke remote access permissions for a user account, select the account and then click Remove.
    8. Click OK twice when you have finished.
    One thing that I found odd when he launched Remote Desktop from his home laptop is the IP entry:
    Computer> [Public Router IP]:49250
    Login> Domain\Admin
    Password> *****
    From the odd port number I would assume that was for port forwarding so I logged into his router and found exactly that. In port forwarding, he had the in/out as 49250 TCP to 192.168.30. I went into the firewall and enabled Remote Desktop in the inbound
    rules. 
    As of right now, I can use Remote Desktop to remote into the server, and withing their server, I cam use Remote Desktop to remote into the workstation. I just can't remote into the workstation directly using the port 49250. Any suggestions on this, something
    I have missing?
    He has Norton Security installed on this computer and I tried adding Inbound/Outbound rules to its 'Smart Firewall' to allow remote desktop and the port.

    Thanks for the reply.
    When I use Remote Desktop and use the Public IP of the router without the port number (49250), I am able to get into the server. However, when I try to use RDP with the [Public IP]:49250, it will not connect to the 192.168.0.30 workstation.
    Right now the router is program to forward port 49250 requests to the 0.30 workstation.
    I am going to work on the Inbound/Outbound Firewall settings today and see if this will resolve the issue.

  • 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.

  • Using Remote Desktop - Windows RT 8.1

    Hello,
    I was directed here from the Microsoft Answers community site about my issue regarding Remote Desktop on my Surface 2 RT.
    I am trying to connect my Surface 2 to my Windows 8.1 Pro desktop (it has Media Center on it as well).
    The problem that keeps surfacing on the Surface 2 is the credentials. I have checked time and time again to make sure my credentials were correct every time I try to get Remote Desktop on the Surface 2 to connect to the Windows 8.1 Pro desktop - it says
    my credentials did not work. Both machines are connected to my Microsoft account, and both machines use my Microsoft credentials to log in as well as sync.
    I have used the Incoming Connections troubleshooter on the Windows 8.1 Pro desktop, it didn't raise any issues regarding my network connection (both the Win8.1 machine and the Surface 2 are on the same network).
    If I understood the FAQ correctly, I can connect my Surface 2 RT 8.1 to a computer running Windows 8.1 Pro (but not vice versa) using Remote Desktop.
    So what underlying issue could there be?

    Are you able to RDP into the desktop with another machine? Is it only the Surface RT that doesn't work?

  • 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.

  • Remote Desktop Connection freezes Windows 7 64-bit

    At home, I just upgraded from a Windows 7 Ultimate 32-bit desktop to a new Dell with Windows 7 Ultimate 64-bit OS.  Remote Desktop Connection from my old home PC to my work PC worked great for years even after upgrading both to Windows 7 Ultimate.  Now everytime I try to use Remote Desktop Connection (RDC) to connect into my work PC (with Windows Ultimate 7 32-bit) the RDC window will freeze after a new seconds of use.  If I wait approx 3 minutes the RDC window will unfreeze for a few seconds before freezing again.  If I minimize the RDC window on my home PC, I can continue to work because it's only the RDC window that is frozen.  Here is everything I've tried already that has not helped:
    1. Trying reducing the home PC screen resolution
    2. Downloaded the latest 64-bit driver from NVIDIA for the GTX 260 graphics card
    3. Taken my home PC to work to test behind the company's firewall--doesn't help
    4. Disabled Window Auto Tuning (suggestion from this website)
    5. Called Dell support--they tried for about an hour to help but couldn't; thier suggestion was to order Windows 7 32-bit version OS and install it
    6. Tried running the 32-bit version of mstsc.exe - no help
    7. Using MSCOMFIG, disabled all Startup items - no help
    I have another home PC running Windows XP, it works perfectly using RDC to connect to my work PC.  Also, I have no problem at all using RDC from my work PC back into my home PC (the other direction).
    Here may be a clue:  if I start up my new Dell Windows 64-bit OS in Safe Mode, the RDC session does not freeze.
    Any suggestions would be appreciated!

    Hi,
    Since it works in Safe Mode, I suspect this should be related to some conflicts, please try the methods in the following Knowledge Base article to have a check:
    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
    In addition, please also ensure the NIC drivers on all of the computers are up-to-date.
    Hope this helps. Thanks.
    Nicholas Li - MSFT

  • Remote desktop connection in windows 7 pro

    I have a problem accessing remote desktop connection using windows 7 64 bit.
    My remote desktop connection shell version 6.3.9600 shows the Network Level Authentication is not supported.
    My other computer also win 7 pro 64 bit has a different shell version 6.2.9200 that supports Network Level Authentication.
    How do I go backwards to shell 6.2.9200?
    I have been trying use remote desktop using the more robust security and could not figure out why I could not log.
    I have screen shots of the two shells and my system screens

    Hi,
    Configure Network Level Authentication
    Click Start, click Run, type regedit, and then press ENTER.
    In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    In the details pane, right-click Security Packages, and then click Modify.
    In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
    In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
    In the details pane, right-click SecurityProviders, and then click Modify.
    In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
    Exit Registry Editor.
    Restart the computer.
    Hope this helps!
    Andy Altmann
    TechNet 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?

  • 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

  • Guideline of installing remote desktop services in window server 2012 r2

    Hi,
    I tried to install remote desktop services in window server 2012, I joined my current domain ( in window server 2003).
    During installation, it require me to promote my server to domain controller? This is one of the requirement for remote desktop services?
    If I didnt join any domain, it prompt me I must join a domain.
    Anyone can advise me? provide me a steps by steps guide will be perfect!
    Thanks 

    Hi GP_IT001,
    In your current network do you currently have a domain controller? You mentioned that you "had" a Domain Controller running Windows Server 2003.
    Am I correct in thinking that you no longer have this server?
    As this article mentions:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/f3d0543a-edab-4eb2-8360-3658a3351bb0/licensing-issue?forum=winserverTS
    You will need a domain environment which means you'll need a server that is a domain controller, and I believe that it will also need to operate Windows Server 2012 or above. You could, if you wanted, setup a new server (virtual or physical) as a domain
    controller and use that if you wish.
    Best regards,
    Please remember to mark the replies as helpful if they help, or as answers if they answer your question. Please also unmark the answers if they provide no help.
    Zach Roberts
    Independent Microsoft Community Support Advisor
    Disclaimer: I don't work for Microsoft. Any advice given is my own and does not represent Microsoft.
    Follow me on Twitter:
    @WindowsZach

  • 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

  • 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 

  • High availability SQL Server requirements for Remote Desktop Services in Windows Server 2012

    Good night,
    Thanks for reading this question, I do not write much English.
    I am implementing Remote Desktop Services in Windows Server 2012, I need to know the size of the database to create and feature on the .mdf and .ldf, I searched in different microsoft link but I have not received a response.
    Kindly appreciate your cooperation and attention.

    Hi Alejandro,
    I am implementing Remote Desktop Services in Windows Server 2012, I need to know the size of the database to create and feature on the .mdf and .ldf
    If you want to know the size requirements of .mdf abd .ldf files, since they are parts of SQL database, I suggest you refer to SQL forums below to get more professional support:
    https://social.technet.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlgetstarted
    https://social.technet.microsoft.com/Forums/sqlserver/en-US/home
    In addition, here are some articles regarding RDS deployment for you:
    Remote Desktop Services Deployment Guide
    https://technet.microsoft.com/en-us/library/ff710446(v=ws.10).aspx
    Remote Desktop Services (RDS) Quick Start Deployment for RemoteApp, Windows Server 2012 Style
    http://blogs.technet.com/b/yungchou/archive/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style.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]

Maybe you are looking for