Unable to take remote access from windows 10 machine in workgroup environment to windows server 2016 joined to Domain using MSTC by using  Domain user credentials.

Got stuck in a login loop, login credentials window popping again and again.

Tried multiple Domain Users credential but still same issue.

From Other workgroup computer in same location having windows 10 OS, remote access to windows server 2016 is working fine by using same domain credentials.

Please let me know if there is any solution.

Remote App and Desktop Connection has been working fine for a long time, today we tried to add this Remote App to a new users computer and are getting the message "An error occurred, contact your system administrator"

Each time we try and connect, an event ID 1309 is logged in theApplication Event Log and the output is as follows:

Server is Windows Server 2012.

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 29/07/2019 13:20:55

Event time (UTC): 29/07/2019 12:20:55

Event ID: f9fa47823cd6482d970739de8f39ec5e

Event sequence: 14

Event occurrence: 5

Event detail code: 0

Application information:

    Application domain: /LM/W3SVC/1/ROOT/RDWeb/FeedLogin-2-132088762149519861

    Trust level: Full

    Application Virtual Path: /RDWeb/FeedLogin

    Application Path: C:\Windows\Web\RDWeb\FeedLogin\

    Machine name: SERVER

Process information:

    Process ID: 2796

    Process name: w3wp.exe

    Account name: IIS APPPOOL\RDWebAccess

Exception information:

    Exception type: NullReferenceException

    Exception message: Object reference not set to an instance of an object.

   at ASP.webfeedlogin_aspx.Page_Load(Object sender, EventArgs e) in c:\Windows\Web\RDWeb\FeedLogin\WebFeedLogin.aspx:line 17

   at System.Web.UI.Control.OnLoad(EventArgs e)

   at System.Web.UI.Control.LoadRecursive()

   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Request information:

    Request URL: https://MYDOMAIN.COM:443/RDWeb/FeedLogin/WebFeedlogin.aspx?ReturnUrl=/rdweb/feed/webfeed.aspx

    Request path: /RDWeb/FeedLogin/WebFeedlogin.aspx

    User host address: 217.x.x.x

    User: 

    Is authenticated: False

    Authentication Type: 

    Thread account name: IIS APPPOOL\RDWebAccess

Thread information:

    Thread ID: 12

    Thread account name: IIS APPPOOL\RDWebAccess

    Is impersonating: False

    Stack trace:    at ASP.webfeedlogin_aspx.Page_Load(Object sender, EventArgs e) in c:\Windows\Web\RDWeb\FeedLogin\WebFeedLogin.aspx:line 17

   at System.Web.UI.Control.OnLoad(EventArgs e)

   at System.Web.UI.Control.LoadRecursive()

   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Any help would be greatly appreciated.

HI,

We are trying to install RDS on one of the server OS 2016. But facing below error

Unable to connect to the server by using Windows Powershell Remoting

-- We are installing all RDS Role on the same server, there is no remote server involve in it.

Did below troubleshooting but still issue persist .

-- We ran below command but no luck.

Enable-PSRemoting -force
Set-Item WSMan:localhostShellMaxMemoryPerShellMB 1000

Refer : https://community.spiceworks.com/topic/1463758-unable-to-connect-to-the-server-by-using-windows-powershell-remoting-rds

-- Disable windows firewall

refer : https://rlevchenko.com/2015/05/22/rds-unable-to-connect-to-the-server-by-using-windows-powershell-remoting/

Ran "Set-ExecutionPolicy -ExecutionPolicy RemoteSigned"

Ran "Set-ExecutionPolicy -ExecutionPolicy UnRestricted"

Refer : https://social.technet.microsoft.com/Forums/sharepoint/en-US/68af42d6-7a12-49eb-941c-72ba0cc6d316/setexecutionpolicy-unrestricted-force?forum=winserverpowershell

-- Further we tried to install the RDS from DC but when we tried to add the server **3 in server manager group it shows below error.

Error **3 : Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".  7/19/2017 5:03:36 AM

-- We provide local admin rights to user "helpdesk" but no result.

-- Disabled IP v6 but still no result.

Refer : https://rlevchenko.com/2015/05/22/rds-unable-to-connect-to-the-server-by-using-windows-powershell-remoting/

---------------------------------------------------------------------------------------------------------------------------------------

Thanks, Sajjan T

Hi,

All our win 10 1903 clients, immediately after been updated from 1803 to 1903 start repeating keystrokes in remote apps. Servers are 2012 R2. RemoteFX cannot be disabled on session hosts servers since that solution causes problems to some of the apps running. Any one facing the same problem ? Any solution?

Hi,

our workstations with Windows 10 pro are in this weekend updated to version 1803. For main system we use RemoteAPP aplications on Windows server 2012R2 (Windows server 2012R2 is full updated). After update on client station are RemoteAPP slower, and  right mouse button is unresponsive, or react verly long time... 

It is a big problem for us.

PS: after replace mstsc.exe and mstscax.dll from older version Windows 10 is all OK. but this is not a solution.

Thanks.

Hi,

We've recently moved a client's cloud server to a new data center. The process involved making a backup of the VM in the old environment, and restoring the VM in the new data center environment. This server runs the Remote Desktop Services role on Windows Server 2012 R2.

The migration seemed to go smooth, and the end-users can access their applications using RemoteApp, from any remote location. This particular client has a technical contact, who uses Server Manager on her Windows 10 PC to disconnect users from RDS as and when she needs to.

For some reason, since the migration, if we open Server Manager on the server itself, or on the technical contacts PC, we receive the infamous message:

The following servers in this deployment are not part of the server pool: 
1. [server_name] 
The servers must be added to the server pool.

The thing is, the server IS in fact visible in the list of Servers in Server Manager. I've tried re-adding it using the AD search, using the IP address in the DNS search, and even using the FQDN in the DNS search. All it seems to do is add another instance of the same server to the list of servers, but the above message is persistent and RDS can't be managed from Server Manager.

Has anyone seen this type of odd behavior before?

So to get the flavours right. Correct me if am mistaken or left some feature out.
Cause up until recently all of the following 4 items were spaghetti in my head.

A user starts an RDS (terminal services session into a server to run an app) . TYPE 1 RDS

An administrator can monitor that session via the ADUC user properties tab "Remote control tab" enabled. TYPE 2 Shadowing?

An administrator can also remote control the desktop that the user is running while he is connecting to an RDS. TYPE 3 Computer enabled remote control (In system properties)

A help desk analyst can do Remote Assistance on that same desktop in Type 3 sharing the same desktop. TYPE 4 Remote assistance.

Does this make sense?

Hi guys,

On a random base (daily, weekly) we're experiencing major log-in problems on our Windows Server 2012 R2 Remote Desktop Services farm. The VM's are hosted on Hyper-V 2008 hosts and we're not using Citrix techniques etc.

Users are reporting that they cannot log-in, the log-in sessions hangs with a blank screen when loading their user profile (e.g. Please Wait For The User Profile Service).

In the System event log of the server on which the user is logging on the following errors are shown:

Source:        Service Control Manager 
Date:          23-12-2014 7:28:01
Event ID:      7011 
Task Category: None 
Level:         Error
Keywords:      Classic
User:          N/A 
Description: 

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

…and after 30 (or sometimes 60) seconds, the same error only another service (in random order):

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

…and after exactly 30 seconds, the same error only another service:

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UxmSms service.

etcetera, with the following errors:

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Netman service.

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndPointBuilder service.

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WPDBusEnum service.

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.

The Portable Device Enumerator Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TrkWks service.

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.

These errors are logged continuously.

An administrator cannot solve this since he isn't able to login in as well (console or remotely), only a hard reset of the VM is possible to use the affected server again.

I took different steps to solve this problem without any success, like:

- Installing the latest Windows updates
- Removed unnecessary printer drivers, print monitors and print processors (no local printers/drivers are installed, only Remote Desktop Easy Printer driver is used)
- Searched different forum posts, but found only hotfixes for Windows Server 2008 R2.

Can someone please help me with this annoying problem?

Many thanks!!

EDIT:
Of course is increasing the time-out not really an option here... http://social.technet.microsoft.com/wiki/contents/articles/13765.event-id-7011-service-timeout.aspx

I have set up a test Server 2012 RDS collection (Single Server for now) and implemented User Profile disks.

I have two problems.

First: My generic test user can connect and does successfully use the user profile disk as expected. However, atlogoff, the system event log contains these errors:

The error (NTFS 137) is: The default transaction resource manager on volume C:\Users\ts3.test encountered a non-retryable error and could not start.  The data contains the error code.

The warning (NTFS 50) that concerns me is:

It appears that the user profile disk is being "disabled" or "disconnected" before the profile data is completely written at logoff. What can I do to troubleshoot this?

Second:

Update: A post from Mike Connor on the following page: -LINK- solved the problem described below. 

My administrative user always logs on now with a temporary profile. At the beginning, the UPD was working and mounting. That stopped working. In attempting to troubleshoot, I logged the admin user off and deleted the UPD disk file from the share. I remember it working again after generating a new UPD disk file in the share. Soon, it quit working again. I deleted the UPD disk file again from the share and ever since, it has never regenerated a new UPD andalways logs on with a temporary profile.

The Remote Desktop Management service failed to start. Error code: 0x88250003

1) is there a way we can see what certificates are assigned to RDS roles.

2) how to assign the renewed certificate to the roles, if deployment page is not openeing.

this is one more event error reported. need help to fix this.

Ekachakra

Redirected profile including AppData and since doing updates on some machines, they are getting an error stating windows cannot access the specific device, path or file.

Our organization uses redirected profiles AppData and since doing updates on some machine, they are getting an error stating windows cannot access the specific device, path or file. You may not have the appropriate permissions to access the item. The path listed is C:\Program files\windowsApps\%AppName%. Common occurances are Microsoft.office.Desktop.PowerPoint or Microsoft.MicrosoftOfficeHub .

This is happening on multiple machines ranging from version 1709, 1803 and 1809.

Please let me know if any one have solution.

Hello, I currently have a Remote Desktop Server "Windows Server 2012 R2" running in a small but busy Accounting Office and it's working great but during last tax season it bogged down from time to time so we are considering implementing a 2nd Remote Desktop Server to help service the load..

Here's some details:

1 - Approx 30 Users running MSOffice and Accounting Apps connecting via RDWeb to run Apps..

2 - The current RDS is a Physical installation with no Gateway as there's no external access at this time to limit security issues.

Question: My plan is to install a New Host "Windows Server 2016" and implement the new RDS as a Virtual Server and I'm not sure if I should tie it back to the current Physical so it can manage the load balancing or if I should just set this up as a separate standalone and just instruct the users how to access each server.. 

My concern is if I tie it to the Physical RDS and there's a problem with the physical server then will it prevent users from accessing the new Virtual RDS.. 

Thanks for you help...Scott

Hi

We are having a strange error with a windows 10 (1903) trying to RDP to a windows 2016 server. We receiving an error An internal error has occurred. We can however, rdp to other servers. We tried different profiles also and same error message. If we reboot the RDS server it is okay for a few days... There are no other error messages. It was working previously then just broke. Also the firewalls are disabled on both sides. 

Hi

Please give us solution to 

Disable / Block / Hide / Prevent Connection settings in remote desktop connection

or/and hide / block / disable totaly Show Options

See attached screen

https://ibb.co/RTVPTdw

Hi, I have set up RDS 2016 farm in forest A (2 WA, 2 CB and 2 SH servers). Having done that, session host sitting in other forest B was added to the RDS farm. There are two collections, one with apps published on 2 SH servers in forest A and the other one with apps published on SH in forest B. Adding SH from forest B and collection creation/app publishing on it were done with TWO-WAY trust between forest A and forest B.

Having removed trust (forest A trusts forest B) leaving me with ONE-WAY trust I can access applications published on SH in forest B by using PAM request and proper rights were passed through. Problem is that now, with one-way trust in place, I can not publish new apps on SH in forest B neither with GUI or PowerShell.



Since this RDS farm is part of Active Directory Red Forest design (ESAE) having two-way trust between forest(s) defies purpose of whole project. Is there any solution for this or only way to publish new apps on SH in forest B is to temporarily recreate other trust direction (forest A trusts forest B) which would certainly be turned down?

Thanks in advance!

We upgraded a system to 1903 and immediately we are unable to remote powershell to that box.

Already done:

No available updates to install.

rebooted several times more.

Firewall is disabled.

disable-pssession and re-enable pssession, no errors.

This is the error we get when trying to connect:

Enter-PSSession : Connecting to remote server testdesktop failed with the following error message : WinRM cannot process the
request. The following error with errorcode 0x80090322 occurred while using Kerberos authentication: An unknown security error
occurred.
 Possible causes are:
  -The user name or password specified are invalid.
  -Kerberos is used when no authentication method and no user name are specified.
  -Kerberos accepts domain user names, but not local user names.
  -The Service Principal Name (SPN) for the remote computer name and port does not exist.
  -The client and remote computers are in different domains and there is no trust between the two domains.
 After checking for the above issues, try the following:
  -Check the Event Viewer for events related to authentication.
  -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS
transport.
 Note that computers in the TrustedHosts list might not be authenticated.
   -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ Enter-PSSession testdesktop
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (testdesktop:String) [Enter-PSSession], PSRemotingTransportException
    + FullyQualifiedErrorId : CreateRemoteRunspaceFailed

The internet has a lot of stuff about broken SPN's on web servers and deleting or recreating:

http/host.domain.com  

but this isn't a web server, it's just a Windows 10 desktop. there are no existing HTTP SPN's on this box.

Domain trust is fine, computer account is fine.

Any ideas are appreciated.

Hi Team,

Im trying to determine if  the number of RDS admin's be increased from 2 Admins per server  or is this a hard limit ?

Cheers

Dean

The MS post below i not understanding, i added the powershell on management VDI, to download the virus update and unpack it, but how the VDI vms can get these unpack virus file?

https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/deployment-vdi-windows-defender-antivirus

Hello Team,

Currently our server is configured with a license server type "TS or RDS Per Device". The server mode is configured for "Per User", but diagnostic is presenting the following problem: 

The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server servername01.local does not have any installed licenses with the following attributes:
Product version: Windows Server 2008 or Windows Server 2008 R2
Licensing mode: Per User
License type: RDS CALs

The suggested solution is: 

Use RD Licensing Manager to install the appropriate licenses on the license server or change the licensing mode for the Remote Desktop Session Host server.

How I can resolve this issue? The intent is to have the server license running in "Per User" mode. 

Regards!