Windows 2008 R2 Remote Desktop install Error on AD auth.

Hi ALL, I just did a clean install of Windows 2008 R2 and a refresh install of Business Object XI R3 sp3. When I try and have a user authenticate I get an error :
[repo_proxy 13] SessionFacade::openSession -
(com.crystaldecisions.sdk.exception.SDKException$SecurityError: The secWinAD
security plugin is not enabled. Contact your system administrator for
details. (FWB 00002)) [repo_bridge - BridgeSessionFacade::openSession]
On are other TS server that is just 2008 we don't get the error.
Could anyone point me in the right direction to troubleshoot this one.
-i

this error means that on this "refresh install of Business Object XI R3 sp3" AD authentication is not enabled.
you need to enable and configure AD in CMC, only then login with seWinAD autentication from client tools.

Similar Messages

Windows 2008 R2 + Remote Desktop Web Access + Single Sign-On + 2 servers

Hi
First sorry for my English. I have got problem with run SSO with RDWeb. I configured everything follow this instructions: http://blogs.msdn.com/b/rds/archive/2009/08/11/introducing-web-single-sign-on-for-remoteapp-and-desktop-connections.aspx
and http://blogs.technet.com/b/mrsnrub/archive/2010/03/22/remote-desktop-services-websso.aspx. After logon to RDWeb web page I click application icon. Then I see dialog box for credentials - SSO not working.
I have got 2 servers with Windows Server 2008 R2 Standard:
Server OL-AP1 with role Remote Desktop Session Host (RDSH) and certificate for digital sign RemoteApps
Server OL-AP04 with ONLY Remote Desktop Web Access (RD Web) with certificate for https
Client PC: Windows 7 SP1 with installing certificate for OL-AP01 witch I used for digital sign RemoteApps
All certificates created by enterprise domain CA - Active Directory Certificate Services (AD CS)

Hi,
Thank you for posting in Windows Server Forum.
Do you have RD Gateway setup in your environment?
Have you configure RD Connection Broker and set the Fully Qualified Domain Name (FQDN) of the RD Connection Broker server in case of RD Connection Broker mode. In RD Session mode, it is set to the FQDN of the RD Web Access server.
Client operating systems must trust the certificate with which the RemoteApp programs are signed. Suggest to install RDP 8.1 for client OS.
Do you have a trusted certificate with a matching name configured on your RDSH server in RD Session Host Configuration? (Means cert must match the name that clients use to connect to it for running the RemoteApp).
Hope it helps!
Thanks.
Dharmesh Solanki

Windows 2008 R2 Remote Desktop Services - user profile path not working

Trying to setup remote desktop profiles. We have 1 farm with 2 Windows 2008R2 RD session hosts and a broker server and want the all of the remote user profiles to reside on a dedicated profile server. We've created the user shares but when a remote
user logs in their user profiles is automatically created on the session hosts. Each remote users profile path is specified in AD under the user's Remote Desktop Profile tab.
I've seen posts about creating a GPO to handle roaming profiles but I'm not sure as to where this needs to be created...should it be done on each of the session hosts? Are their any step by step instructions out there on how to achieve this that I just haven't
found yet?
bl

Hi,
Thank you for posting in Windows Server Forum.
Do you have RD Gateway setup in your environment?
Have you configure RD Connection Broker and set the Fully Qualified Domain Name (FQDN) of the RD Connection Broker server in case of RD Connection Broker mode. In RD Session mode, it is set to the FQDN of the RD Web Access server.
Client operating systems must trust the certificate with which the RemoteApp programs are signed. Suggest to install RDP 8.1 for client OS.
Do you have a trusted certificate with a matching name configured on your RDSH server in RD Session Host Configuration? (Means cert must match the name that clients use to connect to it for running the RemoteApp).
Hope it helps!
Thanks.
Dharmesh Solanki

Windows 2008 R2 Remote Desktop Service Role pickup 2012 RDS License Server.

I am installing Citrix onto a Windows 2008 R2 server as part of this I need to setup the RDS Role on the same box and then point it to the Windows RDS License server.
Our plan is to have a Windows 2012 License server for RDS Licenses i.e. install 2012 RDS Licenses.
I was wondering if it was possible for a 2008 R2 RDS role to pick up 2012 RDS Licneses from a Windows 2012 RDS Server?
Many thanks,
Steve

Hi Steve,
Thank you for posting in Windows Server Forum.
Yes, agree with TP’s comment. You can also check below interoperability matrix link for details.
RDS and TS CAL Interoperability Matrix
http://social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Intermittent Disconnects for clients of 2008 R2 Remote Desktop Services

Hello, I have an issue that I am trying to work on for a client who is experiencing intermittent disconnected sessions when logged into a Windows 2008 R2 Remote Desktop Services (RDS) server.
As I mentioned, the disconnect is intermittent in nature and almost appears to be network related, although I cannot find any data in the Application, System, or application specific logs to support that.
The RDS server overall does not exhibit any error, but the user's session is briefly interrupted and then restored. I would like to be able to gain some additional information about what is going on under the hood, but I am having trouble finding any
details on how to turn on debug logging for Terminal Services (er, RDS) on 2008 R2.
Can someone provide some additional details on what kind of logging or other means that I can take on this server in order to gain some additional insight?
Thanks in advance for any advice.

Hi,
There are certain reason for which the client get disconnect from the server. The following are some of the commonly seen symptoms:
• You may be limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session.
• You may have a port assignment conflict.
• You may have an incorrectly-configured Authentication and Encryption setting.
• You may have a certificate corruption.
More information.
http://support.microsoft.com/kb/2477176
If you want to have log for login\logoff for the client on server end then you can get the information from below log.
Event Viewer>Application and Service Logs>Microsoft>Windows>TerminalServices-LocalSessionManager>Operational
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Remote Desktop Certificate Error - Server 2012 Essentials

My remote desktop connection was working fine until the operating system installed some recent updates automatically. I had everything set up, and the certificate was installed and working fine and had no issues getting to my remote computer. Recently when
I log into my remote web access and try to connect to any of the computers on the list I get an "Remote Desktop Connection" error. "Your computer can't connect to the remote computer because no certificate was configured to us the Remote
Desktop Gateway server." Like I said the certificate was installed and working fine the other day. Any insight is appreciate. Thanks

Hi ChrisCJK,
Based on the error message, please refer to the following operations and then check if can help you to solve
this issue.
Locate to Remote Desktop Services folder in Administrative Tools, then please open the
Remote Desktop Gateway Manager.
Right click server name and select
properties.
Select the SSL Certificate tab.
Then please click the “Import Certificate…” button.
Select the trusted certificate and click Import again. And then click Apply and OK.
If this issue still persists, please type the following command at the command prompt, then press ENTER:
netsh http show sslcert
Please check the value for
Certificate Store Name.
Meanwhile, please follow the path in Event Viewer:
Applications and Services Logs-> Microsoft-> Windows-> TerminalServices-Gateway folder. Please check if you can find any error message. Please also check other related TerminalServices folder if you can find some other clues. It will help us to go
further analysis.
Hope this helps.
Best regards,
Justin Gu

How to enable users to access windows 2012 through remote desktop client on windows XP SP3

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.

Hi I have just installed Windows Server 2012 and trying to give access to the users. The users are on windows XP Pro SP3 remote desktop client (Shell and control version 6.1.7600 with Remote Desktop Protocol 7.0 support).
I have enabled the windows server 2012 remote desktop users through "control panel -> systems and security -> Remote access" for the users. When I try to connect to the windows server as administrator, it is getting connected.
But when I try to connect as other users I get the following message.
"To sign in remotely, you need the right to sign in through Remote Desktop Services. By default members of the Administrators group have this right. If the group you're in does not have the right, or if the right has been removed from the Administrators
group, you need to be granted the right manually."
Is there any other setting to be done to eanble the Remote Desktop for the users.
Have you tried adding those users to the "Remote Desktop Users" group? It's in Active Directory Users and Computers and it's a Built-In group. Might want to give that a try ...
- JJ

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.

Windows Server 2008 R2 Remote Desktop - The requested session access is denied

Hi, I have been using Windows Server 2008 R2 since it was released, and have 100 servers up and running. I configured Allow Remote Desktop on all of them and have been able to connect to them and manage them via RDP since then. I also have two servers configured as Remote Desktop Services.
That was up until yesterday. Yesterday afternoon I started getting the The requested session access is denied. I managed all Terminal services via Group Policy and have three users entered.
I am connecting to the servers via Windows XP SP3 and Windows 7. Both clients have been updated to the latest Remote Desktop Services client.
I have been searching for the answer, and I am not finding it.
I have also tried KB954369 without any success.
Thanks,
Brian

Ok, from my trials and tribulations and discussions with Microsoft I have identified the following;
Assumptions;
A. My terminal server is in domain widget
B. All the users are in domain contoso
1. I had the Terminal Server configurured with a specific Login, which would launch a specific application only and not give them any desktop functions. Wiht this configured this way, I get the error I wrote about.
2. If I turn the specific login off, then I can login normally and perform the functions as Administrator that I need/want to do.
3. Microsoft said to configure the Terminal Server with Single Sign-on. I did as instructed and went thru all the steps, however because my terminal server is in domain widget, the users get prompted twice each time for login. Once on the website, and then again as the application launches. Microsoft said that the users needed to Remote Desktop Client 7.x or the self-signed certificate that I have has to be included in the domain contoso certificate authority so that they will not be prompted for the second sign-on.
4. Conclusions - I need to have a chat with our enterprise security team about including the self-signed certificate in the contoso certificate authority. I need to also work on my RDWeb website so that it meets our company standard look.
Here are the links that Microsoft provided;
http://technet.microsoft.com/en-us/library/cc772108(WS.10).aspx
Enable RDC Client Single Sign-On for Remote Desktop Services
http://technet.microsoft.com/en-us/library/cc742808.aspx
Blogs -
http://blogs.msdn.com/rds/archive/2007/04/19/how-to-enable-single-sign-on-for-my-terminal-server-connections.aspx
http://blogs.msdn.com/rds/archive/2009/08/11/introducing-web-single-sign-on-for-remoteapp-and-desktop-connections.aspx
http://blogs.msdn.com/rds/archive/2009/06/05/publishing-in-windows-server-2008-r2.aspx
http://blogs.technet.com/pfe-ireland/archive/2008/09/05/windows-server-2008-terminal-services-presentation-virtualisation-and-windows-xp-clients.aspx
I hope this help you in your troubleshooting.
Brian

After MS13-098 and SecurityAdvisory(2915720), Windows Server 2003 Remote Desktop(TermService) cannot start service

I have trouble with Windows Server 2003 R2 Standard. I installed the KB2893294(MS13-098) patch, and I changed the registry that is suggested actions of Security Advisory(2915720) http://technet.microsoft.com/en-us/security/advisory/2915720
Suggested Actions:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config]
"EnableCertPaddingCheck"="1"
After rebooting the event viewer(system) says:
Event Type: Error
Event Source: TermService
Event Category: None
Event ID: 1014
User: N/A
Description:
Cannot load illegal module: C:\Windows\system32\rdpwsx.DLL
After I cannot use Remote Desktop Connection from other client.
So I check the all security patches and other hotfixies. I checked the KB2653956 and KB958476.
But TermService do not recover the error.
And then, I delete the "EnableCertPaddingCheck" registry and reboot systems.
TermService have no error. I can use Remote Desktop Connection from other client.
After KB2893294 installed, Remote Desktop Connection cannot use from other client that "EnableCertPaddingCheck" registry set to "1".
Other Windows Server 2008 systems do not effect the KB2893294 patch. But All Windows Server 2003 systems cannot use the Remote Desktop Connections after the KB2893294 patch.

Update on this issue:
The debug team has accepted the issue and has identified it as a regression. Right now they're targeting *June* as the release date for a fix. I'm attempting to educate them that customers don't just install patches the day (or even month) they're
released and that the fix needs to be moved up in priority to give a minimum of 60 days to install the patch before the time-bomb explodes.
In the meantime, a workaround has been provided that will turn off the new functionality. Note that I have not yet had a chance to test this. It entails creating a new DWORD registry entry--UseLegacyPE--and setting it to 1.
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ImageHlp\UseLegacyPE
I will update this thread when I have further information.

NULL SID Security Log Event ID 4625 when attempting logon to 2008 R2 Remote Desktop Session Host

This is a new deployment of Server 2008 R2 in a newly created 08 R2 active directory on a newlyt installed 08 R2 RDSH server.
A new generic user is created in AD. That user can log on to the terminal server on the console just fine. But that user cannot logon via RDP. Furthermore, the domain admin credentials also cannot logon via RDP.
When either set of credentials is used, the logon attempt registered in the Windows Security Even Log as a denied attempt with Event ID 4625 reporting a NULL SID.
Troubleshooting: The RDSH has already been disjoined and rejoined to the domain. Also, curious note, there are three ways to save the user account on the RDSH server as a valid user account which has permissions to logon. The one Microsoft recommends is to open computer management and edit the remote desktop users group. When I the accounts here and click apply, they immediately dissapear. Secondly, I can open the computer properties and go to the remote tab. There I find the user accounts added using the previous method are enumerated but not displaying correctly. They show up with the RDSH server name and a question mark. The last way, is to open the Remote Desktop Session Configuration tool and edit the properties of the rdp connection and go to the security tab. This was the only place I could get a user to ‘stick’ but the logon attempts still show a NULL SID and access is denied.
I have scoured every bit of RDS documenation I can find with no luck.
Thanks,
Chris

I am also experiencing this issue.
2008 servers, 2007 exchange on server 2008.
These are fresh servers, fresh AD. Users can log onto domain normally, RDP not working for admin accounts, generating same errors as posted above.
The bigger issue, is that we have a cisco messaging service account that is generating this error on the DC's and the Exchange server as well. The service basically emails users voicemails to their inbox. The user we've created for the cisco service is unable
to authenticate to the exchange server, in turn generating the same errors posted above as well. We can log on to the domain with this account just fine.
Any ideas on this? We have not tried re-adding the servers to the domain.
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 5/5/2010 9:01:13 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: xx.corp
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:
xxxx
   Account Domain:
xxxx
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: laptop
   Source Network Address: -
   Source Port: -
Detailed Authentication Information:
   Logon Process: NtLmSsp
   Authentication Package: NTLM
   Transited Services: -
   Package Name (NTLM only): -
   Key Length: 0

Windows 2012 R2 - Remote Desktop Sessions, RemoteFX, GPU, Blue Screen RemoteFX adaptor

Nvidia GPU GRID K1
Host Server - Dell Power edge R720 128 gig RAM 2 Xeon E5-2640v2 2.0GHz, 20M cache 8c
Windows 2012 R2 full installation – Bios and all hardware with latest updates.
Roles - Hyper V and Remote Desktop Virtualization Host
EPT, GPU, WDDM (latest drivers) compatible for RemoteFX and fully up to date.
I have disabled the video adaptor on the motherboard.
I cannot complete with administrative permissions;
dism /online /enable-feature /featurename:Microsoft-Windows-RemoteFX-EmbeddedVideoCap-Setup-Package
Error: 0x800f080c
Feature name Microsoft-Windows-RemoteFX-EmbeddedVidoCap-Setup-Package is unknown
Question 1 - because video card on motherboard disabled, do I still need to complete this command?
VM’s
**I’m not interested in VDI but more Remote Desktop Sessions and the option to ‘pinch and zoom with Windows 8.1 tablets**
VM1 - Windows 2012 R2 configured as generation 1 that is fully patched.
This VM is able to start up and run until I add the new hardware for the RemoteFX Video adaptor from within the Hyper V settings. When I start the VM the server blue screens. I have tried multiple VM’s with 2012 but same thing
If I created the VM as Generation 2 I am able to start the VM but the RemoteFX adaptor doesn’t appear in the device manager. I have read generation 2 isn’t compatible with RemoteFX.
VM2 – *Testing purposes* - Windows 8.1 Enterprise configured as generation 1 that is fully patched.
This VM I am able to start up and run the VDI after the RemoteFX video adaptor is installed, also the correct adaptor appears in the device manager. This seems to at least work correctly but I cannot pinch and zoom and the experience is poor.
GPU summary within the Hyper V settings state there are 4 physical GPU’s all of which can be used with RemoteFX and that 1 virtual machine are using the GPU (Windows 8.1 enterprise VM)
Firewalls off, latest RDP clients
I have read you should be able to use Windows 2012 R2 and we should be able to use the sessions with pinch and zoom but now and then you come across something that tells me different.
Question 2 – I need this to work with Windows 2012 R2 so we can use Remote Desktop Sessions
and the tablets can use pinch and zoom, anyone tell me what I may be doing wrong?

Hi,
Thank you for posting in Windows Server Forum.
As per my research, you need to run the command although video adapter is disabled on motherboard. If you install the RemoteFX cap driver, the integrated video adapter is disabled while the operating system is running.
For more information you can refer beneath article.
1. RemoteFX (with Hyper-V) is a serious business tool. For games.
2. Configure RemoteFX in Hyper-V running Windows Server 2012 with low end GPU
Hope it helps!
Thanks.
Dharmesh Solanki

Oracle 11g ODAC 11.1.0.6.21 on Windows 2008 Standard server gives TNS error

Hi,
I have Oracle 11g ODAC 11.1.0.6.21 installed on my Application server that has 32 bit Windows 2008 Standard. The Oracle database 10g is installed on another 2008 server. On database server I can connect using SQLPlus. But on application server I cannot connect using ODAC SQLPlus. I have given correct service name in tnsnames.ora file.
Error is ORA-12154 TNS: Listener cannot resolve service name
What's wrong? Is 11.1.0.6.21 not meant for Windows 2008? I did not get any errors while installing.
This 11.1.0.6.21 works perfectly for me on XP machine.
I have browsed this forum but not getting clear steps to peform.
Can someone guide me what is needed?
Thanks
Shrini

Hi,
The request to connect from the client is reaching the server but it seems the parsing of the service name is either wrong or the information is correct. Here are a couple of suggestions.
If you have a good known set of sqlnet.ora and tnsnames.ora files on another client where the same connection descriptor works, then backup the curreny client network config files and copy the good known files to the Windows 2008 web server where you see the error. Make sure you recycle the worker processes once the files have been copied.
Try to connect via Ezconnect and by pass the config files to see if you get the same error.
//hostname:port/servicenameofdb
where hostname is the machine where the target database is running
port is the port on the DB machine where the tns listener is running and listening
service name is the service name of the target DB
Use this syntax in the connect string box when attempting to connect from SQL PLUS out of the ODAC home.
You can also run lsnrctl utility on the server and vertify there is a handler for the service name or instance that is the target,
HTH
Jenny B.

Remote Desktop Services Error when trying to send a message to a user in the collections

We are implementing RD for thin clients and when I try to send a message to a user I get an error that states,: Unable to send a message to session X on (SERVER NAME.COM). WTS API Failed
Is there a service that needs to be turned on?
Thanks EPK

Hi,
Thank you for posting in Windows Server Forum.
Before sending message please check following considerations.
- You must have Message special access permission to send a message to a user.
- You can send messages only to users whose sessions are in the active or connected state.
- You can send a message to a user session in Remote Desktop Services Manager by using the Send Message action.
Send a Message to a User
http://technet.microsoft.com/en-us/library/cc754124.aspx
Else you can also try below script and check the result.
Send-NetMessage - Net Send / Msg.exe
http://gallery.technet.microsoft.com/scriptcenter/Send-NetMessage-Net-Send-0459d235
Hope it helps!
Thanks.
Dharmesh Solanki

2008 R2 Remote Desktop Services Problems With Older RDP Clients

I recently deployed a new 2008 R2 server to serve as a Terminal Server (Remote Desktop Services) for about 30 people. The new server is replacing a 2003 server. I expected the new machine to be a considerable upgrade and was looking forward to happy people
and less problems. Reality is I am finding several unexpected headaches - discouraging considering the amount of money we have spent on the new machine.
Most of the users connect via HP thin clients, they are the T5510, T5520 and T5530 thin clients. What I have found is performance issues when connecting via these thin clients. I believe the RDP client on these thin clients is RDP 5.5 or earlier. And I do
not believe it is possible to upgrade the RDP client version on the thin clients - I guess they are to be seen as "disposable".
The performance issues are: black blocks appearing when connected - and I have deselected bitmap caching - makes no difference. When typing in certain places the display of the typed characters could not keep up with the user. And lastly I have a weird thing
that just popped up today; where if the user goes to Google it freezes up their entire environment - I cannot even remote control the user/session - why this came up today and was not a problem before I am not sure.
With all of the above issues I have found that the problem goes away or does not exist if I connect to the server using an RDP client on an XP or 7 computer. So I have to conclude the RDP client is the problem.
Does anyone have information on this? Is there anything I can do as far as configuration on the server to allow me to use these older RDP clients? Do I have any alternative other than buying new thin clients?
thanks!

From your description, I also agree that the problem may be in the top RDP client.
1.
HP Compaq t5510 Thin Client:
Operating System: Microsoft Windows CE.NET
RDP Client: Remote Desktop 5.1 Add-On
2.
HP Compaq t5520 Thin Client:
Operating System: Microsoft Windows CE 5.0
RDP Client: Remote Desktop 5.5 Add-On
3.
HP Compaq t5530 Thin Client
Operating System: Microsoft Windows CE 5.0\6.0
RDP Client: Remote Desktop 5.5 Add-On
We can try to optimize two ways.
1.
Upgrading Driver – Network for Thin Client
(1) HP Compaq t5510 Thin Client:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=420576&prodTypeId=12454&prodSeriesId=420575&swLang=13&taskId=135&swEnvOID=1054
(2) HP Compaq t5520 Thin Client:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=500833&prodTypeId=12454&prodSeriesId=500832&swLang=13&taskId=135&swEnvOID=2051
(3) HP Compaq t5530 Thin Client
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01087297&prodTypeId=12454&prodSeriesId=3341951
Upgrading RDP to the latest version of HP Web site.
Let thin clients use to connect to the Remote desktop server with low load.
(1) Open the Remote desktop client in customer’s Thin Client
(2) Click Advanced option. In choose your connection speed to optimize performance area, you can select the low load option. For example, modem(56kbps).
I noticed that you have deselected bitmap caching in Remote Desktop Client options, but makes no difference. You can try again. Then please remember disconnect idle sessions and rational allocation of resources in Terminal Server.
Technology changes life……

Windows 2008 R2 Remote Desktop install Error on AD auth.

Similar Messages

Maybe you are looking for