Beeing kicked out from remote desktop to a Windows 2008 R2 server

My server have 2 users, the Administrator and a user "sigma".
When I use the user "sigma" with remote desktop I always get kicked out from the server after a couple of minutes. This does not happend with the user Administrator. I tried to set the RDP-Tcp Properties, but it did not help.
Greetings from the cold norths

Hi,
Thank you for posting in Windows Server Forum.
Have you applied any GPO setting related to session time out?
Please check the setting under below path.
•Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits 
•User Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits 
In addition, also check the setting related to “keep-alive connection interval” under GPO setting.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections
Configure keep-alive connection interval:         Enabled and Specify the Value
More information.
[Forum FAQ] Restrict number of Active Sessions in RDS 2012 and 2012 R2
http://social.technet.microsoft.com/Forums/en-US/00c2252b-8ec0-489f-8da2-07a434a9b5a2/forum-faq-restrict-number-of-active-sessions-in-rds-2012-and-2012-r2?forum=winserverTS
Hope it helps!
Thanks.
Dharmesh Solanki

Similar Messages

  • Remote Access to Windows 2008 R2 Server configured with local IP

    Hello,
    I have a Windows 2008 R2 Server configured with local IP (e.g. 192.168.1.115).
    Please how can I access it remotely outside its local domain through (remote desktop connection).
    Thank you.
    Tony.

    Hi Tony,
    Based on your description, you would like to connect to the Windows 2008 R2 server via remote desktop connection.
    So you need to enable remote desktop on the Windows 2008 R2 server if it is not already.
    1.Install and configure the Remote Desktop Session Host role service in the Windows 2008 R2 server.
    2.Add related user to the Remote Desktop Users group in the Windows 2008 R2 server.
    3.Configure remote desktop connection in the Client.                   
    Also, due to you would like to access it remotely outside the domain, so you will need a VPN connection or a port forward to connect through.
    For more details, please refer to the guide below,
    Installing and Configuring Remote Desktop Session Host
    http://technet.microsoft.com/en-us/library/dd883253.aspx
    Allow Remote Desktop connections from outside your home network
    http://windows.microsoft.com/en-IN/windows7/allow-remote-desktop-connections-from-outside-your-home-network
    Best Regards,
    Tina

  • Printing from Remote Desktop

    Cannot print on Fanfold 210 x 305mm on Epson LQ680 from remote desktop on windows server 2008 r2.
    Printer installed in the local system is listed under printers in remote session and able to print on other paper size fanfold
    210mm x 11.5 inch
    When selecting the paper size fanfold 210 x 305mm, it is not printing. 

    Tried disabling :"Use Terminal
    Services Easy Print printer driver first" 
    Still not able to print on  paper size fan fold. 210 x 305mm.
    I tried using another printer OKI Ml5790 which supports windows server 2008.
    Same was the result.

  • Been watching HD TV shows on Apple TV for a month with my 1080i TV. Tonight getting error on TV, "This content requires HDCP for playback". All other media from remote desktop working OK, including 720p movie.  WI-FI network running normal. Help?

    Been watching HD TV shows over home WI-FI from remote desktop using Apple TV for a month with my 1080i TV. Tonight getting error on TV, even on recently watched shows, "This content requires HDCP for playback. Either your HDMI cable isn't properly connected, or your HDMI connection doesn't support HDCP.  Please reconnect the HDMI cable from your Apple TV to your HDTV and try again". All other media from remote desktop working OK, including 720p movie.  WI-FI network running normal at about 4.7 mB/sec.  Any ideas?  Thanks.

    Been watching HD TV shows over home WI-FI from remote desktop using Apple TV for a month with my 1080i TV. Tonight getting error on TV, even on recently watched shows, "This content requires HDCP for playback. Either your HDMI cable isn't properly connected, or your HDMI connection doesn't support HDCP.  Please reconnect the HDMI cable from your Apple TV to your HDTV and try again". All other media from remote desktop working OK, including 720p movie.  WI-FI network running normal at about 4.7 mB/sec.  Any ideas?  Thanks.

  • Extract data from remote desktop(presentation server)

    Hi friends,
       How to import and export  data from remote desktop (presentation server) to my sap server.
    I have user name password of the remote desktop(presentation server)
    Please guide me.
    By
    Raju

    Hello
    Question is not clear to me...
    Thank u,
    santhosh

  • 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

  • Windows 2012 R2 Active Directory Domain Services and Remote Desktop services Role on the same server.

    Findings: 
    Currently, Windows 2012 R2   AD DS role and RDS With Broker services can only seem to coexist properly in a new domain not an existing domain. Any attempt to add to an existing domain causes internal database user access denied issues and any attempt to
    adjust rights and circumvent is dubious at best.
    The escalation technician said it best. Out of 50 clients that want to do this, they end up not being able to help 5 right off the bat for whatever reason. As for the other 40 they might be able to help by running reports, adjusting rights and trying to add
    the roles until it works.  This can end up being a 20 day process. Basically they are playing whack-a-mole with user rights and permissions until something sticks.
    We tried creating an OU where any other domain policies would not be inherited to see if that was the issue, a fresh install with different sequence of adding the Roles, no effect.
    Given the errors I witnessed when running procmon and then trying to add the roles, the NT System and the Windows Internal database user had access denied issues on 100+ registry keys when trying to add the roles. After that the system is not behaving normally.
    The errors displayed almost mirror the errors that would occur on Windows 2012 when those two roles would be added which of course is officially NOT supported on that system.
    This blog needs serious revision:
    http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
    This is the excerpt from that blog: Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller.  In addition, we published
    guidelines for how RD Session Host could be used without the RD Connection Broker.
    Microsoft Support was curteous and helpful and they were the ones who advised cutting our losses, which mirrored my hunch after seeing what was transpiring in the system.  They refunded my money for the support call. 
    For me, it was an opportunity to find out if there was any way to configure Windows 2012 R2 in the Same manner that it was setup as Windows 2008 R2 and lay that to rest. The coexistence is poorly implemented. It is as if there was a reaction from all the deprecation
    of bread and butter features such as shadowing in TS and the coexistence of AD DS and RDS to where those features were re-added haphazardly. (I have no complaints on shadowing on Windows 2012 R2 it works, just do not like having to go to server manager to
    use it).
    I opted for virtualizing the Domain controller to eliminate the incompatibility issues and that is what I will be doing from now on. I found free solutions for backing up and reporting for virtual machines as well as the suggested procedures for configruing
    a Domain controller as a virtual machine on a Hyper-V environment and I will be sticking to those. Thus far the setup has been operational.
    I am not allergic to virtualization, but for really small setups it adds additional time and considerations but if that is how it has to be done, so be it. Windows 2008 R2 days are numbered and since we can usually squeeze 5-7 years on quality server equipment,
    buying a Windows 2008 R2 setup now is a borderline disservice in my opinion.
    Hopefully someone finds this useful and saves some time.

    Hi,
    Thank you for posting in Windows Server Forum.
    Do you need any other assistance?
    Based on your description, you are describing your story of successfully implementing RDS server with AD role and more regarding all RDS related scenario. For shadowing feature, you can use with command also. Below is the syntax to shadow a session.
    mstsc /v:<ServerName> /shadow:<SessionID>
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • 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

  • Remote Desktop Connection certification issue with Win Server 2008 R2

    When connecting to Windows 2008 server R2, from Windows 7, Vista and Mac OS 10.6.7 via Remote Desktop Connection, i am getting a 'Server Name on the Certificate is Incorrect' error. 
    if i click connect, i can still connect to the machine, due to a 3rd party managing the server, this doesn't look very professional on my part...
    The server is a standalone machine and is not currently on a domain. RDC is only used for management purposes.

    Hi,
    This certificate error is normal, because your client do not trust the certificate which is installed on the terminal server. To avoid this issue,
    you can export the certificate and import this certificate into the client side (computer account).
    Thanks.

  • Remote Desktop (Terminal Services) Configuration on a Server Standard 2012, standalone installation

    I'm new to this, so bear with me..
    I need help locating documentation on how to configure a Server Standard 2012, standalone server, to act as a terminal server. In server 2008, you could have the server as a domain controller, and also host remote desktop sessions for thin clients. Apparently
    a lot has changed with 2012, and I don't think I'm even using the right search terms because I having a time finding proper information.
    I'll be glad to provide whatever further information is needed for someone to help me..
    Thanks in advance, and looking forward to gaining a better understanding of how this works. Don't mind doing the work, like I said, i just need some good documentation I can follow.

    Hi,
    Also here, the below articles should be helpful:
    Windows 8 / Windows Server 2012: Remote Desktop Management Server
    http://blogs.technet.com/b/askperf/archive/2012/10/30/windows-8-windows-server-2012-remote-desktop-management-server.aspx
    Windows Server 2012 Remote Desktop Services (RDS)
    http://blogs.technet.com/b/windowsserver/archive/2012/05/09/windows-server-2012-remote-desktop-services-rds.aspx
    Follow me and learn Windows Server 2012 – Remote Desktop Services
    http://blogs.technet.com/b/bruce_adamczak/archive/2012/10/27/follow-me-and-learn-windows-server-2012-remote-desktop-services.aspx
    Remote Desktop Services in Windows Server 2012 Test Lab
    http://social.technet.microsoft.com/wiki/contents/articles/12934.remote-desktop-services-in-windows-server-2012-test-lab.aspx
    Regards,
    Yan Li
    Cataleya Li
    TechNet Community Support

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

  • 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

  • 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

  • Unable to list SFTP Directory on windows 2008 r2 server from internet

    Hi experts,
    I have configured a SFTP on windows 2008 r2 server. And i am using the Filezilla on client machine to connect to SFTP server.
    The connection works properly on internal network but it displays error when i connect from internet.
    Error: GnuTLS error -53: Error in the push function.
    Response: 550 Data channel timed out.
    Error: Failed to retrieve directory listing
    This machine is publish with public IP and port22. The connection and authorization process gets complete but stops are Directory Listing.
    PLease suggest the troublshooting steps..
    Let me know if any more info is rquired.

    Hi,
    Do you also use the Filezilla to configure SFTP server? Since you use Filezilla on client machine to connect to SFTP server, I would suggest you ask for help from Filezilla forums for better and accurate answer.
    https://forum.filezilla-project.org/
    Best Regards,
    Mandy 
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Remote Desktop Connection to Windows 8 PC from other computers crashing

    Hi all.
    Was hoping someone would be able to help me with an issue I'm having.
    I'm trying to get a LAN remote desktop connection established to my Windows 8 laptop. It's an HP ENVY 17t-2100 CTO 3D Edition Notebook PC. Note that I'm running Windows 8 Pro only - not 8.1 as HP haven't released 8.1 graphics drivers for this laptop and probably
    never will. The computer has a single user profile that has full administrator rights.
    I have followed numerous web tutorials on how to turn on Remote Desktop. I've gone into Advanced System Settings > System Properties > Remote > checked "Allow Remote connections to this computer". All seems ok to me. 
    The problem comes when I try to establish a connection. When the connection is made, it almost instantaneously crashes the session on the computer or device trying to connect. The RDP client on my Windows 7 laptop, Mac OSX or Mac running Windows 8.1 Pro just
    crashes, while the RDP iPhone or iPad app simply flickers for a few seconds then goes back to the main screen. Meanwhile, the HP ENVY loads the lock screen and displays a message saying XXX device is connected remotely and it won't let me log back in to kill
    the connection or do anything. I have to restart the computer from then to be able to use it again.
    I'm convinced there's not a problem with my local network as the HP ENVY can RDP into the Windows 7 laptop or Mac running Windows 8.1 without any problems. All computers are connected via Ethernet to a Linksys/Cisco wireless ADSL modem router which supports
    Gigabit. The iPhone and iPad of course connect to the wifi network from the Cisco/Linksys modem router
    I've also had a brief look at the RDP local connection logs. From what I can make out, they confirm that a user has successfully logged in, but they don't provide a crash log or a log of the user ever disconnecting, probably because I have to restart the computer
    to continue using it. Dead end there, it seems.
    The HP ENVY is connected to 3 external HP LED monitors. I've disconnected them and tried all devices with no luck. I've also played round with the RDP client settings to not mount drives or printers and the HP ENVY has no printers connected anyway, though I've
    done all I can to remove any printer drivers as I've read elsewhere that they are what could cause the problem, but I've had no luck. 
    If anyone can suggest anything more that I can try, I would be unbelievably grateful! I'm more than happy to provide screenshots or videos of what happens when I try connecting. I'm not sure what you experts would find immediately helpful so just ask away if
    you think I can provide anything.
    Thanks in advance!
    rugbyreff

    The first thing that I would try is to uncheck all of the boxes for local resources on computer running the RDP client. It is possible that a device, such as a printer or other redirected device, is causing the crash. You can also look under Event Viewer
    in the event logs of both systems and see if anything unusual appears when you attempt the remote connection.
    Brandon
    Windows Outreach Team- IT Pro
    The Springboard Series on TechNet
    Hi Brandon
    Many thanks for your suggestions. There's nothing in the logs that I could find, like I said in the original post. I've also tried connecting with bare minimum settings on all devices (FYI the iPad and iPhone version don't support the use of printers) and
    this still hasn't helped.
    If you have any other ideas I'd be very glad to hear them!
    rrugbyreff
    "If it's worth doing, it's worth overdoing" -- MythBusters

Maybe you are looking for