Workstation Credentials after Remote Desktop

Hello,
I am facing an issue with a SSO Captive Portal whenever I log into a server using RDP. While I can login normally using my login username, whenever I log into a server using Administrator credentials, it seems that IE uses the Administrator credentials instead
of the logged user.
Is there a way to identify the reason why IE gets the Admin credentials?
MCSE: Server Infrastructure

If you launched IE using the run as another user option then it is normal that the IE will launched under the administrator session / context. If this is not what you did then I would recommend that you reset IE settings and try again: https://support.microsoft.com/kb/923737?wa=wsignin1.0
More if you ask them in IE forum: https://social.technet.microsoft.com/Forums/ie/en-US/home?category=internetexplorer
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Similar Messages

System create user after remote desktop

hi
after remote desktop system create many user although i have anti virus updated but it not internet security . Can remote system infect local system ?
Thanks

1. Reformulate your question and add more detailes.
2. Use AV program and update it regularly.
3. Remote infection is possible, namely if you use access that is NOT secured.
Regards
Milos

Screen sharing not working after Remote Desktop 3.2 install

OK, I think I screwed it up.
I'm moving to a new iMac running Mountain Lion, and I need to use Remote Desktop. I own Remote Desktop 3.2 on DVD, so I installed from disk and launched the app. My plan was to download the latest update to 3.6.x, but I figured I would launch it to enter my license key and then quit and download the update.
I was given an error that newer components were already installed and clicked the Quit button. Ugh. Next I went to Apple's download site and downloaded the newest update but when I ran that installer it told me it could not install on my drive.
My grand plan has now left me with no Remote Desktop, and the built-in Screen Sharing core service beach balls when I try to connect to a remote client.
Is there a way to save me from myself?
Thanks in advance,
Bill

Hi Bill,
You could try removing all the installed components manually and then try again (install, don't open but update right away).
According to the installer the files are located in:
/Applications/Remote Desktop.app (that one was hard to find )
/Library/Application Support/Apple/Remote Desktop/
/Library/Preferences/com.Apple.ARDAgent.plist
/Library/Preferences/com.Apple.RemoteDesktop.plist
/Library/Receipts/
/Library/Widgets/RemoteDesktop.wdgt
(not sure if the following files tie into other parts of the OS so removing them may cause issues)
/System/Library/CoreServices/RemoteManagement
/usr/bin/share/man/man1
perhaps a permission repair after all parts have been deleted and a restart before trying again.

Remote Desktop Connection Authentication Error from Windows 8.1 Pro to Windows 7 Pro

I keep trying to connect to my server running Windows 7 Pro from my laptop running Windows 8.1 Pro, but I get the following message after providing
my credentials:
"An authentication error has occurred (Code: 0x8007001f)"
I can't find any reference to this error code being associated with using remote desktop.

Hello,
Are you connecting to a server as part of a domain ? if so confirm you are using adequate credentials for remote desktop for example: username: domain\administrator
if not you can try connecting to the localhost using:
username: .\administrator - for example
also you can try running your remote connection in admin mode:
Win + R - bring up run then type:
mstsc /admin
hope that helps.
Cheers,
Harry

Remote Desktop Fail after March 10 Updates!

I updated client servers with MS updates as usual over the weekend remotely. Tried to remotely log into 2 of the servers after they rebooted; Server 2008 R2 and 2008 Standard, and was denied with "Your credentials did not work" message at the top
of the dialog. Administrator, other IDs did not work. Only way to log into either server was to drive into the client (on Sunday) and login from the console. Once logged in from the console I was able to RD into each. If the server is rebooted RD is again
unavailable until logged in from the console. I am now seeing that remote access works for a while but in some cases becomes unavailable after a while. The problem only seems to affect server 2008 and 2012 variants.
Backed out the following updates and the problem remained: KB3002657, KB3033929, KB3046049, KB3035131, KB3034344, KB3032359, KB3039066, KB3035132, KB3035126, KB3033889, KB3032323, KB3030377. Then I restored the System State from the day before the updates but
the problem is still present.
Unfortunately, this particular client has around 30 remote users who need to login every day. The only workaround I've found is to log their IDs in at the console first. Then they can connect remotely. Others have reported this problem and one post leads me
to believe it could be an issue with 2008/2012 RDS boxes on a 2003 Domain Controller. Any help appreciated or, MS: Please Get This Fixed!
More info:
https://social.technet.microsoft.com/Forums/en-US/0a520543-29d4-4466-9967-e39d819d11f1/users-cannot-log-into-remote-desktop-after-3112015-update?forum=smallbusinessserver&prof=required

We are both in the same boat.
While it's nice to know that Microsoft gives us these broken updates so we can charge customers, there is that "loyalty" factor to our customers in which we end up absorbing the many hours of troubleshooting and research time spent.
Failing to find a suitable solution to this problem by end of day I will attempt to remove ALL 27 Security Updates that were installed to see if this resolves the issue.
What scares me is that you probably removed the applicable ones and that we will be in the same situation after removal.
This thread seems a little more active:
https://social.technet.microsoft.com/Forums/en-US/0a520543-29d4-4466-9967-e39d819d11f1/users-cannot-log-into-remote-desktop-after-3112015-update?forum=smallbusinessserver&prof=required

IOS App 8.1.5 Remote Desktop can't connect to Windows 7 Pro after upgrade. Error 0x00000507

Nothing has changed between my network, Windows 7 computer or my iPad besides the upgrade of the ios app software to 8.1.5. Did not used to have any issues connecting but now when I try to connect, I get the above error when logging in.
I have tried reinstalling the ios app with no success and also confirmed I can still remote desktop to the PC from another PC with the credentials I've always been using.
I've also tried explicitly including the domain when entering the username with no luck. Looked through my Windows 7 event logs and can't find any more information on what this error means.
Has anyone seen anything similar or have any ideas what I can do to troubleshoot? Thanks!

Hi,
I have a same problem.
Although RD Client 8.1.4 worked great, now I cannot connect to Windows 7 Professional computer from my iPhone 5 (iOS 6.1.4) since the latest update.
Same as Twiggles, when I try to log in (just after entering username and password), the app gives me error code 0x507 "Disconnected from server".
Note that I connect to my PC over VPN using Cisco AnyConnect app.
After that, I've tried to connect to my PC in two different ways with same network settings as the above situation.
1. Use different remote app
I've tested free version of "PocketCloud" from Dell Wyse, and I CAN connect to my PC.
2. Use different version of iOS
I've tested the latest RD Client 8.1.5 on my another iPhone (5s) with iOS 8.1, and I CAN connect to my PC.
Therefore, I assume our 0x507 is not setting related, but probably some sort of iOS version dependent problem arise from the latest update.
Even though I tried PocketCloud, I believe RD Client is the BEST app for remote desktop for iOS.
I strongly hope this problem will be solved!
Thanks.

Users cannot log into Remote Desktop after 3/11/2015 update!

I have a simple network where users can log into a Windows SBS 2008 server with Remote Desktop to access various applications. This worked quite smoothly until this morning, after the updates of last evening. (3/11/2015)
When users tried to log into the Remote Desktop this morning their credentials were rejected, as if their username and/or password were incorrect. Even I (as the administrator) could not log in remotely. Finally I connected a monitor and keyboard
directly to the server and was able to log in without an issue. After logging in directly I was able to connect through remote desktop.
This method worked for my other users as well - after I logged them in directly they were able to use remote desktop no problem.
The trouble is that I have a couple dozen users, and this is an issue that should not be occurring. What happened in the last update to cause remote desktop to reject users credentials? Why does it only work after the user logs in directly?
And most importantly, how do I fix this?
A few notes:
Simply browsing for files on the server also asks for the user's name and password, and this works as well. This is only a remote desktop issue.
I have already checked to make sure the domain was correct. It was.
I have already checked to make sure the usernames and passwords were correct. They were.
I have already checked to make sure this was not a unique issue for a single (or limited number) of users. This issue effected
all users all the network.
Thank you very much for your help,
Dustin

I'm curious here... If the server is rebooted, does it put the RDS users back into a "credentials failed" situation? If so, could you please have them log in with credentials:
domain.local\username (I suspect they may be currently using domain\username)
and see if that fixes the RDS problem without having to first log into the server directly.
The ".local" may be ".lan" or ".somethingelse" depending on how you initially configured your domain, but the default for SBS 2008 is ".local"
Merv Porter
=========================
That's a good question - the server will auto-reboot this evening and I'll test again in the morning.
You are correct that we've been using domain\username. I tried domain.local\username (which is the way we've set up), and that did not work either.
I'll let you know how things turn out tomorrow morning. I don't want to mess with my users anymore today. :P
Dustin

Black screen after unlocking PC that was previously Remote Desktop-ped to

I'm running Windows Server 2008 R2 Standard, Service Pack 1.
Often I need to work from home, in which case I jump onto a VPN via Citrix client and remote desktop to my work PC. Subsequently, when I come to work in the morning and attempt to unlock my PC, from time to time after entering my login credentials and pressing
'Enter' I get presented with two blank/black screens instead of my desktop. I tried being patient, moving my mouse a bit etc but to no avail. I notice that the keyboard is still functional (CAPS LOCK light goes on/off), and there appears to be some hard drive
activity. However I end up needing to reboot the PC (and lose whatever unsaved work I had).
I've done some googling, attempted most of the suggested solutions (involving changing some registry settings, updating video card drivers etc) but to no avail.
My video card is NVIDIA Quadro NVS 295, driver date 24/01/2014. I do have dual monitors configured (lenovo).
Any tips/suggestions would be much appreciated,
Greg

Hi Greg,
Thank you for posting in Windows Server Forum.
You can try the sfc /scannow command to scans the integrity of all protected system files and repairs files with problems when possible. For more details, please refer to the following article.
Sfc
http://technet.microsoft.com/en-us/library/ff950779.aspx
Also perform the clean boot after restarting system and check the status. You can refer
this KB article.
In addition to this, please check below article and KB for additional details.
1. Windows Server 2008 Repair Steps for No Boot Issues
2. Windows Server 2008 R2 hangs at black screen during boot
Hope it helps!
Thanks.
Dharmesh Solanki

Remote Desktop using Domain Credentials

I have two Domain Controllers (Windows Server 2k8 R2 with IIS and DNS role). Forest and Domain functional level is Windows Server 2008. They are in separate locations joined by a VPN. I also have Dev servers (also Win 2k8 R2 with IIS role).
I want to log into the Dev servers using my domain credentials. Can anyone tell me what I need to check or configure in order to achieve this?
Note:
- I do not have DHCP (yet), -> please confirm if this is an issue.
- I can RDP to the Dev servers using their respective local users.
- but network users (which are members of Domain Admin and Remote Desktop Users) cannot RDP.
- do I need to have Remote Desktop Services (Terminal Services)? -> if so, i need to raise my functional level, right?
- I am accessing them from Windows 7 (which is not a member of the domain)

Hi,
Thanks in advance. I can connect to my dev server (using domain credentials) when I am accessing it from my Domain Controller but when I am using my Windows 7 client, it produces these errors:
*I usually get this error
Remote Desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The Remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.
---- OR ----
*Least frequent error
Configuration information could not be read from the domain controller, either because the machine is unavailable or access has been denied.
---- OR -----
*I get this whenever I entered the IP Address instead of the name (dev1):
Your credentials did not work
The credentials that were used to connect to 10.0.0.20 did not work. Please enter new credentials.
The logon attempt failed
2. There was no Security log when I got that error, but, a while ago, I was able to produce this security log:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 4/13/2012 9:52:47 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: dev1.domain.com
Description:
An account failed to log on.
Subject:
Security ID:
NULL SID
Account Name:
Account Domain:
Logon ID:
0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID:
NULL SID
Account Name:
admindomain
Account Domain:
DOMAIN
Failure Information:
Failure Reason:
Domain sid inconsistent.
Status:
0xc000006d
Sub Status:
0xc000019b
Process Information:
Caller Process ID:
0x0
Caller Process Name:
Network Information:
Workstation Name:
DC-00
Source Network Address:
Source Port:
Detailed Authentication Information:
Logon Process:
NtLmSsp
Authentication Package:
NTLM
Transited Services:
Package Name (NTLM only):
Key Length:
0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2012-04-14T02:52:47.862465000Z" />
<EventRecordID>139204</EventRecordID>
<Correlation />
<Execution ProcessID="808" ThreadID="4648" />
<Channel>Security</Channel>
<Computer>dev1.domain.com</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">admindomain</Data>
<Data Name="TargetDomainName">DOMAIN</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2314</Data>
<Data Name="SubStatus">0xc000019b</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">DC-00</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>
3. No Application Errors

Remote Desktop Connection stop working after upgrade from 10.5.8 to 10.6.1

I too could not connect to a W2K3 server with RDC 2.0.1 after upgrading from Mac OS X, 10.5.8 to 10.6/10.6.1. I have another Mac which is on 10.5.8 and connect fine with the same version of RDC 2.0.1 as well as other PC with Terminal Service Clients.
There is no change on the server side. I have uninstalled and reinstalled RDC 2.0.1 several time and it did not resolve the issue. To rule out firewall/network, I tested with another remote desktop application called CoRD (for Mac) on the same laptop running SL 10.6.1 and it connected to the same W2K3 server fine.
One thing that is worth mentioning (in my case), when it does not connect, RDC totally quit (not running anymore. Not minimize, no cannot connect error message, no little dot on the Dock for RDC, nothing) right after I put in the credential in. When looking at the log entries that are related to RDC in the Console application, I see the following
machine 10.6.1. with RDC 2.0.1 (non-working)
9/22/09 1:17:16 PM [0x0-0x3a03a].com.microsoft.rdc[468] objc[468]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . One of the two will be used. Which one is undefined.
On the 10.5.8 machine with RDC 2.0.1 (working), I see the following entries
9/22/09 1:13:23 PM [0x0-0x24f24f].com.microsoft.rdc[5502] objc[5502]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . Using implementation from /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL .
9/22/09 1:13:39 PM Remote Desktop Connection[5502] * _NSAutoreleaseNoPool(): Object 0x16a25c20 of class NSCFArray autoreleased with no pool in place - just leaking
Stack: (0x9277af4f 0x92687432 0x93062bf5 0x926ce0fb 0x9723dff5 0x9268d52c 0x92fd447a 0x92fd4753 0x92fd4a48 0x930375da 0x530bac 0x4831a2 0x483750 0x483c0b 0x47a811 0x4796ac 0x485dad 0x47d475 0x5099dc 0x574c70 0x4ade03 0x4ae65d 0x4ae6f7 0x4ac8dd 0x53260c 0x534187 0x4ae76a 0x4ae7d0 0x4ae88e 0x493925 0x4ae13d 0x533b1a 0x53da6c 0x94a48057 0x934b3155 0x934b3012)
Any help would be appreciated

Doing some more troubleshooting after my post above as I saw a couple of entries referencing Stop Light keep popping up in the log of the Console. I removed Stoplight and Cocoa Gesture (for good meausre) and RDC 2.0.1 started working. I think it is Stop Light which causes RDC stop working, but I don't have to time right now to put Cocoa Gesture back to confirm that. I might if I have the time or post here if you have Stop Light installed as well and removing it resolved the RDC issue for you.

Remote Desktop Connection to VM does not work after sysprep

Hello altogether.
Often asked, but never answered with an applicable solution!
What shall
we
do if
we
get no access to a Azure VM via Remote Desktop
Connection?
Everything went well: access to the VM via RDC was working perfectly!
Then
the idea came into
our
mind to create an image of the VM by use of the Azure Management Portal.
We
found that
we
had to apply “sysprep”
on the VM.
We
did it.
Then we did not take the image and decided to go on with the VM.
But if we start the VM we get no access via RDC!
We tried to find a solution by reviewing the already published contributions by other Azure
users. But none of the replies marked as answered supply with a qualified solution.
So can one provide a really applicable solution to us on how to arrange the further use of the VM?
Thank you in advance.

There is an issue right now where the VM may start unexpectedly after you have run sysprep and selected the shutdown option (which is normally what you should do).
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/fafb9ee6-1e57-46ba-8440-27467ad986cf/image-capture-issue-vm-unexpectedly-started-after-guestinitiated-shutdown?forum=WAVirtualMachinesforWindows
But regardless of that issue - you can't use that deployed instance of the VM after you've run sysprep on it. It needs to stay shutdown, then you select Capture to create an image from it.
If you start it back up, either intentionally, or it is started unexpectedly because of the issue above, it will be sitting at the first interactive screen of setup. RDP is not working at that point, and since there is no console access to an Azure VM, there
is no way to get past that prompt.
For other scenarios, you might be able to attach the OS disk of that VM as a data disk to another VM, and while you could do that in this case too, there is no supported method for disabling sysprep at that stage of setup.
So while you could attach it to another VM to get data off of it (you would have to remove the VM first), the VHD is no longer in a supported state to use as a VM itself.
Thanks,
Craig

Installed the RDS 2012 Server License per user CAL (5pcs) after not allow over two users remote desktop connection problem

I have successfully to installed the RDS 2012 Server R2 per user CAL (5pcs) Open License after is found not allow over two users to remote desktop connection on this Server problem, I try to uninstall the license and then (internet on-line & telephone
call Microsoft Activate Center get the activate key) to reinstall is still same of the result on below problem.
Select a user disconnect so that you can sign in.
There are too many users signed in
User1 Active
User2 Active
() Force disconnect of the user

Hi,
In addition you can also refer following article for RDL configuration.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
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]

Messages.app no longer connects to Jabber after App Store auto-installed Remote Desktop Update 3.8.2

Messages.app no longer connects to my company's Jabber server after App Store auto-installed Remote Desktop Update 3.8.2 (even though I never purchased that app). The Remote Desktop app can not be found anywhere on my machines.
I suspect the Remote Desktop update because Messages stopped connecting on my office MB Air after the update but still worked on my home iMac. Next day the iMac received the update and Messages stopped connecting on that machine too.
Messages attempts to connect for several minutes (it's been trying for 30 mins as I type this) and just hangs. Occasional I get the following error message:
Error: Messages lost the connection to the Jabber account 'account'. A network error occurred.
I've tried:
- Deleting and recreating the Jabber account in Messages.app
- Toggling on/off SSL (SSL required by our server)
- Toggling on/off auto detect server and port (port 5222 on our server)
- Deleting every plist, cache, etc., I could find in the Library for any IM client I've ever used
- Checked that Keychain trusts the Jabber server SSL certificate (it is a self signed cert)
- Tried connecting from three completely different networks including the company VPN
- Multiple PRAM resets
- Setup a Google Talk account in Messages - works fine
I'm at a loss...
Kurt

I installed and setup Adium. Adium works but Messages.app still does not connect to Jabber.

L7580 net printer driver disappearing in Win 7-62 after connecting with Remote Desktop Connection

I have an Officejet Pro L7580 connected via ethernet. I've been using the driver released from Jan 2010, and whenever I connect to my Windows 7 Ultimate 64 computer via Remote Desktop Connection, the printer drivers for both the printer and the fax disappear. I have to constantly run the "add a device" window to add the printers back again.
Why do they disappear like that?
Fishanderson

OK after updating the Server and clients I am still having this issue :(
and just today after no sound problems for 6 days the sound dropped out on a couple of RDP sessions, yet the sound on the client itself worked fine when tested (minimise the RDP session).
It took the RDP sessions to be restarted to restore the sound within the session.
I have found similar (old) thread regarding this problem:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/958fd891-6f55-432b-8268-a326ac6b2b2e/sound-in-remote-desktop-session-stops-working
but no one has informed about if as solution was ever found.

Remote desktop broken after 10.9.3 update

After the 10.9.3 update, remote desktop is completely broken...
The ard status monitor display : Apple Remote Desktop is disabled. I try a clean install (app + system library coreservice remote management + user library pref ans aap support deleted.
After the Remote Desktop 3.7.2 installed from the Apple Store when i try to launch the application i get this message : The remote desktop client does not mach the administrator software version. Check for update.
And this is the problem : there is no updates available !!!!
I have try to install some 3.7.1 client from some dmg, but all false : ARD agent validate multiple error ( on log) error 6405, fatal error 5, error 100, error 6404, broken pipe, fatal error 0
Now i am back to the clean uninstall and with the new Remote Desktop 3.7.2 with the desktop client not matching and not running...and without any update available.
thanks for help !

Nice idea and helping really !!!!
On safe mode, i could install an old remote desktop client (3.6.x) - and the client works fine as client.
Next i get the last Remote Desktop Admin from the Apple Store and it run also always in safe mode. No error, but all my setting were lost. With the Remote Desktop Admin running i created a new client installer and quit the Admin app for updating the client to the last release (3.7.1). I test all in safe mode (running as admin and as client) and finally reboot the computer to quit the safe mode.. and finally all was running again.
I don't know why during the 10.9.3 update Remote Desktop was corrupted...
Now i need to put back my remote client, but this not really a problem.
Thank a lot th Deadzak for his genius intuition.

Workstation Credentials after Remote Desktop

Similar Messages

Maybe you are looking for