Atradius

I have a asus laptop which was experiencing issues when signing into the admin account. It would just sign me into a temporary account and a error would pop up saying "We cant sign into your account".

But after a few restarts I managed to sign into the admin account but it was all wrong, my usual desktop icons were gone all my local files are now in the wrong place. All my documents are still accessible but I have to navigate through the c drive to the user. I also noticed in registry editor that the Profileimagepath for the account was a temporary path but I'm sure that's wrong and it should be the profile user name. Im not sure whats gone wrong here but any solution to this problem would be very helpful!

Hello,

I have a problem with my setup. If I connect via RDP to a termianlserver through a RDGW I must type the AD-Credentials two times.

One time for the RDGW and one time for the terminalserver.

I have configured the deployment setting  of the RDGW to "Use RD Gateway credentials for remote computers" but it´s not working.

Both systems are Windows 2016 Server.

Have anyone an idea and can help me please?

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.

I'm getting an "Object reference not set to an instance of an object" error when doing any

I have three RDS servers in my farm. I can change the groups in the other collections in the farm without errors, just not this one.

After installing 2018-11 Cumulative Update for Windows Server 2016 (1709) for x64-based Systems (KB4467681) on our RDS servers the outlook 2013 search bar does not work, clicking on the magnifying glass does nothing.

Going to advanced find and searching there works.

Search works again after uninstalling update.

Hi,

I would want to install RDS Licences User CALs for a windows server 2012 r2. 

Is it a must to have Active Directory to effect this or I can  install without the need for the AD?

Much appreciate the assistance/advise.

Hello and thanks for the help.

I'm trying to find a solution for allowing external users on a different domain to securely access TFS from their copy of Visual Studio to check-in/check-out code. 

I'm using a Privileged Access appliance that has a technology that allows folks to start applications remotely like this, but the rep told me they do not think I could use Visual Studio in this kind of manner because it is not on the "approved list" of RemoteApps.

I've been looking for a little while and can't find any sort of list of approved Microsoft RemoteApps.

It's difficult to search for this because it always brings back error-related threads.

Does an approved list of software for RemoteApps exist and if so, where can I find it?

Hi All,

So I've got an RDS farm as follows:

2 RCB + RCWA combined servers
4 Session Hosts

no web gateways.

I'm using NLB to balance the RCB/RCWA connections.

I have Win7 GPO's configure for SSO and configuring the "RemoteApp and Desktop Connections" client.

Now, it all works, the client configures correctly, apps can be launched, there are no errors, no logon prompts, nothing.

BUT, if i fail-over the WA servers, the client stops being able to update. RemoteApps can still be launched, but the scheduled tasks fail and manual update attempts immediately bring back a logon prompt.

so to reproduce the issue:

1. Win7 machine gets the GPO and connects to rds.mydomain.com, NLB routes this to RCB01 and gets its config ok.
2. RCB01 goes down for maintenance, NLB routes traffic to RCB02
3. Client update attempts fail

At first i thought maybe NLB was messing things up so i removed it and used RRDNS instead, the issues is still the same.

Then I thought maybe I've just fudged something else, so i tried creating a whole new fresh deployment, very vanilla but with the same setup, 2 servers to host Connection Broker and Web Access roles, a SQL box for the Broker HA DB, and 2 Session Hosts.

Correct valid certs applied.

I published 2 remoteapps (paint, calc) and had a brand new Win7 machine get the GPO and hacked the host file to point "rds.mydomain.com" to the IP of my new TESTRCB01.

Everything works like it should, re-wrote host file to point to TESTRCB02, same issue.

So the problem isn't unique to my live deployment...

I checked the IIS logs and I see this on the server it first does its config on:

2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/Feed/webfeed.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 302 0 0 7
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/FeedLogin/WebFeedLogin.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 401 2 5 4
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/FeedLogin/WebFeedLogin.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 401 2 5 3
2019-03-11 11:32:52 "My RCB01 IP" GET /rdweb/feed/webfeed.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 302 0 0 5
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/FeedLogin/WebFeedLogin.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 401 2 5 4
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/FeedLogin/WebFeedLogin.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 401 2 5 3
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/FeedLogin/WebFeedLogin.aspx - 443 "mydomain\myusername" "My Win7 IP" TSWorkspace/1.1 - 200 0 0 145
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/Feed/webfeed.aspx - 443 S-1-5-21-842925246-1757981266-682003330-9437 "My Win7 IP" TSWorkspace/1.1 - 200 0 0 686
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/Feed/rdp/myapp1.ico - 443 S-1-5-21-842925246-1757981266-682003330-9437 "My Win7 IP" TSWorkspace/1.1 - 200 0 0 11
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/Feed/rdp/myapp2.ico - 443 S-1-5-21-842925246-1757981266-682003330-9437 "My Win7 IP" TSWorkspace/1.1 - 200 0 0 4
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/Feed/rdp/myapp1.rdp - 443 S-1-5-21-842925246-1757981266-682003330-9437 "My Win7 IP" TSWorkspace/1.1 - 200 0 0 4
2019-03-11 11:32:52 "My RCB01 IP" GET /RDWeb/Feed/rdp/myapp2.rdp - 443 S-1-5-21-842925246-1757981266-682003330-9437 "My Win7 IP" TSWorkspace/1.1 - 200 0 0 5

So all looking good, but then when i failover this is what i see on the other RCB:

2019-03-11 12:48:44 "My RCB02 IP" GET /RDWeb/Feed/webfeed.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 302 0 0 7
2019-03-11 12:48:44 "My RCB02 IP" GET /RDWeb/FeedLogin/WebFeedLogin.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 401 2 5 4
2019-03-11 12:48:44 "My RCB02 IP" GET /RDWeb/FeedLogin/WebFeedLogin.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 401 2 5 4
2019-03-11 12:48:44 "My RCB02 IP" GET /RDWeb/FeedLogin/WebFeedLogin.aspx - 443 - "My Win7 IP" TSWorkspace/1.1 - 401 2 5 4

You see I'm getting 401's? But then if i delete the connection and re-create it against the same server, it succeeds?

For some reason changing between the Web Access Servers breaks my SSO? but only the actual changeover??

I suspect its not an issue on the RD servers but Windows 7 is sending the wrong info to the server or something?

Please if anyone could help, I'm lost and this is causing issues as half my clients at a time can't update their app lists.

I have probably created a huge mess. I originally had three servers in my farm. I made changes in collections to control who can log onto which rds host using domain group membership.

That works fine when directly connecting to the rds host via our vpn, using the ip of the rds host.

Now I'm trying to get the web access corrected. I have expired certificates. Figure correcting this will help.

I'll start with this screenshot. Can anyone help resolve the error?

Happy share more info if needed.

I  have Windows 2008 R2 server with Network level authentication enabled. I can use remote desktop it by administrator account normally. I created a user account and assigned to administrator group. However, I can use remote desktop to connect it by the user account, the error message is 

We couldn't connect to the remote PC. This might be due to an expired password. If this keeps happening, contact your network administrator for assistance.

Error code: 0x207"

However, once I disable Network level authentication, the user account can be used to remote it. Is there any way to fix it?

I have a problem with mstsc. 

I run the mstsc in the HP thin clint to login the server remotely,but it doesn't work. The detail problem is shown as follows.

Problem name:APPCRACH

APP name:mstsc.exe

                  6.3.9600.16415

                  524b4de4

                  mstscax.dll

                 6.3.9600.16415

                52901 d9b

                c0000005

T he os is wes 7 in thin clint and server 2012 in server.

Hay,

i'm trying to move my application to work as RA.

When a user is login to the RA he go to the Broker, from the Broker he go to the Remote Application server.

I can see the user login to the Application Server and the application open on his PC.

When he try to run the same application again I can see that in the Remote Application server open one more session(The same user is login twice... and the application process runs one time in each session)

How can I make the RA "understand" that the user is already login and just to start the process in the same session?

Good day Everyone,

So, the agreement between my company and another was to use terminal services for their users to connect and use the published apps, which was fine to test out during the 60day trail period. Complications occurred when the white-listing of specific sites stopped working and we had to find ways around this, which meant that by the time things got sorted, the 60 day trail period you get when installing RDS role, expired. 

The company doesn't want to purchase any CAL's for their 2/3 users (users is expecting to grow, hence terminal services) and requested that terminal services be removed for the time being. This is fine, because I can just uninstall the RDS role form server manager. 

The problem is, even after uninstalling, RDS still appears in the quick access on the left in server manager. I am not an expert on RDS or terminal services, but i would expect it to be removed. But this isn't the real problem, the problem is, even after removing the role, windows still complains about there not being a license configured in the license manager, which means that users can't RDP to the computer. I've been searching the internet and cannot find a solution. 

I already tried going to regedit HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp and selecting decimal and setting it to 3389. 

My understanding is that server is for some reason still sending incoming rdp requests to the session host? And that it's checking for a license on the license manager since the temp license expired.. Not sure what the process is that it's following. 

I just want to reinstate that default RDP, so that users can atleast connect to the machine again. 

I saw a fix where a user said you must go to the session host config and create a new RDP-Tcp listener, but i have no session host server added, and cannot add one. 

Any help would be appreciated please. 

Thanks

We have some problems with redirected printers in Server 2016 datacenter.

When the client redirect his printer into the remote desktop Service. The server uses the default remote easyprint driver.  The problem we come across is that the client settings will not be redirected so the client can't use all the trays or uses both side printing. it isn't possible to change settings on the printer because it's a redirected printer.

The steps we take.

- Tried another printer (same problem)

- Tried original drivers on the server (same problem)

- Clean Windows server 2016 standard installation (same problem)

- Tried on server 2012 with both printer. remote easyprint (no problem)

- Install the printer directly on the server with original drivers (no problem)

All the above steps are performed with an administrator account.

So we can conclude there are some issues with redirected printers in server 2016.

Is this a well know issue in server 2016 or is there a solution for this problem. 

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.

I am trying to apply a third-party wildcard cert to a RDS server farm.  The .pfx is imported successfully for the RD Connection Broker roles, but gives an error "Could not configure the certificate on one or more servers..." when I apply it to RD Web Access.  In the Event log, this generates event ID 20480 "Property page: Manage certificates update failed: due to Exception Failed to enumerate server SSL certificate information."

This is an internal farm, with no RD Gateway server, 1 Connection broker/Licensing/Web Access server, and three additional session hosts.

Hello,

Users from a single location are experiencing major issues connecting to our RDS server. There are 3 locations, one main site where the server is location on the same subnet, another site south, and another site to the east. The south and east sites are connected with a VPN connection. Only users at the east site are not able to connect well to the server. I can check event viewer logs and I once saw something with winlogon stopping but I always see the error "session 14 has been disconnected, reason code 0" and "session 14 has been disconnected, reason code 5" from the east site subnet. I did a netstat to see that users are connecting with TCP 3389. An RD Gateway is not configured. I can connect to the RDS server for hours and have no problems. Error code 0 means No additional info is available and 5 means client's connection was replaced by another connection. I am not sure what would be doing this.

I was thinking like some kind of time but I sent all of the timeout settings on the server to never. I thought maybe it was a UDP socket timeout that was acting weird over that single connection but with netstat -a | findstr ":3389" I only see TCP ESTABLISHED sessions and only listening on UDP 3389. 

Update KB3000850 is installed which replaced KB2984006 update for windows server 2012 R2 that fixes RDS issues like this. Clients are Windows 10.

Any help would be appreciated. 

Hello Expertiz,

I am experiencing a weird problem on my windows 2016 server.

I have only one server ( win 2016 datacenter) deployed on azure where in I have configured RDSH, RDCB, license and webaccess role. Till now I was running on 120 days trial period of license. Now I have purchased 15  win server 2019 CALS and installed the same. The problem here is, even though I have installed the CALS the server is not allowing me to connect more than 2 users and it throws an error " there are too many users signed in. Select a user to disconnect".

Licensing diagnoser displays no error. I can see green tick mark which says " RD Licensing diagnoser did not identify anylicensing problem for Remote desktop session host server".

RD licensing manager says "Total licenses =15 ", " Available licenses =15". " Issued = 0" . Here no licenses are not getting issued even though it has enough to distribute to the users. 

I have tried all possible ways to fix this but no luck. Below are the few troubleshooting steps performed.

• Applied group policy settings - Computer configuration - Administrative templates - windows components - remotes desktop services - remote desktop session host - licensing - use specified licensing server ( updated the FQDN name of the licensing server )
•  Computer configuration - Administrative templates - windows components - remotes desktop services - remote desktop session host - licensing - set the remote desktop licensing mode ( set per user license)
• Computer configuration - Administrative templates - windows components - remotes desktop services - remote desktop session host - connections - Limit number of connections ( set to 99999)
• Gpupdate /force
• But no luck. Hence I uninstalled the licensing role and re-configured from the scratch. But still the same issue.

Any suggestions to resolve my issue would be much appreciated.

Thanks,

Mulge