Hi,
Trust you are well.
We currently have 5000 client access license (CAL’s) which is registered to domain AUTOMATE-FAC.AUTOMATE.CO.ZA
I would like to split the CAL’s into the following domains.
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?
We are using a hosted solution and we have a link in RemoteApps to a shared folder on the server. We can access it via the remote desktop Web portal; however, I need to be able to map this drive to our desktop. I can then scan documents to it and it will upload to the server, since it is a shared folder on the server. However, it is not allowing me to map this tsclient folder through RDWeb. I was thinking we could run a powershell script to login to RDWeb App but I am failing figuring out how to map that location to a drive letter on my local system. The saas provider won't allow for Webdav. I am also thinking about trying to setup a VPN connectionl; however, I would like to without it.
Any suggestions would greatly help!
We have a RDP farm with 100+ users who are using Windows 10. Sometimes we have network problems like short network outages and packet losses. When network problems occur users are disconnected from RDP session with error: Your Remote Desktop Services session has ended.
However when I am logged on random server (not member of RDP farm) and network problems occur - I have window that says: The connection has been lost. Attempting to reconnect to your session...
In connection properties of RDP when connecting to RDP farm the checkbox "Reconnect if the connection is dropped" is checked and grayed out.
Why RDP doesn't try to reconnect itself in RDP farm and looses connection immediately? Are there any settings that control this behavior? Sometimes users are forced to manually reconnect to RDP farm several times per hour if network is unstable. If there is no such setting may be there is at least timeout setting that I can configure for higher values so that RDP session survive short network outages?
Hi,
I have a newly installed Windows 2016 Terminal server. I sat up HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\fSingleSessionPerUser registry setting to allow one user multiple login.
As I expected the users could log in multiple times, but the second, third ... login could not run programs, explorer restarts.
Eg: cmd wont run, but the registry editor runs.
Did i miss a required settings, anyone faced a problem like this?
Regards, Robert
Hello Experts,
I've configured a new RDS environment with all roles (Connection broker, RDSH, RDWeb) installed on a standalone 2016 server.
When trying to open RDWeb URL, getting error as below:
EVENT VIEWER LOGS:
Any help is much appreciated !
Thank you!
Best Regards,
Srujan C.
Best Regards, Srujan C.
Does anyone have a resolution for this issue?
I'm trying to implement this in our Azure environment: https://gallery.technet.microsoft.com/scriptcenter/Automatic-Scaling-of-9b4f5e76/view/Discussions#content
When we run this script against our RD Connection Broker that has multiple collections, we have an issue with all servers in a single collection being set to drain mode.
Details: We have 2 Collections on the RD Connection Broker. Both Collections have 3 RD Host Servers. The RD Host servers in each Collection are each in their own Resource Group, meaning all RD Host Servers for a collection are grouped into a single resource group. I set the Config to keep up 2 Servers in off peak mode and run the script against a resource group. All servers in Collection A were put into Drain Mode. All 3 RD Host servers in the collection had a user logged in, so that may have caused an issue as well. Can anyone offer suggestions on how to force this script to only focus on a single collection? Or is there a better way of accomplishing this?
Thanks in advance!
The problem I'm seeing is that I have Windows 10, Windows 7, and Mac, all with RDC clients trying to connect to a Windows Server 2016.
With any Win7-8-10, when an initial connection to the 2016 server is made, the RPC server crashes and renders the server inaccessible for about 10 minutes.
I found that, when I use the Remote Desktop Client VERSION 8 on the Mac, it works just fine. I also have a version 10 that shows the same problem.
After 10 minutes in locked state, it seems that the RPC server comes back alive and I can connect again - and now, I am connected to the previous connection.
I am guessing nothing else anymore. I disabled Audio services, firewall is open (otherwise it would never connect), works just fine with RDC version 8 so, obviously Terminal Services is running, there are no bad files or something alike.
IT IS the version 10 of RDC that made things bad; or it is Windows 2016 that set something unexpected ? Any registry setup that could improve things ?
What are your experiences with this ?
Hi,
since a few days, we have issues while trying to connect from Windows 7 & 10 clients to a Windows Server 2012R2 RD Farm.
RD farm is composed of two RD session hosts + 1 RD Gateway.
Windows 10 clients are build 1809.
The clients and the servers are in different domains with one-way trust. It worked just fine until a few days ago, when clients started getting the below error message. In the TerminalServices-Gateway/Operational log file, I can find a lot of 312 and 313 events which indicate that connections are not authorized.
I have no clue what changed as compared to when the connections where working fine.
We introduced the Microsoft Remote Desktop app as a workaround, and strange enough that works, but it is not liked very much by our users cos it has some drawbacks.
Can anyone help me, or point me where to look at?
Thanks,
Hello
We have Hyper V running on server 2016. That Hyper V has a win server 2008 R2 VM. Users are unable to copy/paste text to there local machine or vice versa while rdp into the server, although they can do it from other VMs. Users have win 10.
I am not sure if it was working before as I just joined in. I have tried restarting the server, checked the rdp clipboard settings on rdp client. Killed the rdpclip processes and reinitiated that. Nothing seemed to be working. What should I be checking further? Anything on Hyper V which can be creating it as its only happening to this particular VM?
Thanks alot
Using 2016 server using Failover Cluster Manager running multiple VMs and RDS setup.
On one specific Vm for just a few of the users when they try to login the screen just keeps flashing and the login is never successful. Only a reboot of the VM fixes the problem temporarily but then it is back the next day.
All user accounts are domain accounts.
The error log shows this -
Faulting application name: explorer.exe, version: 10.0.14393.3053, time stamp: 0x5d01d1c5
Faulting module name: ntdll.dll, version: 10.0.14393.2969, time stamp: 0x5ccd148a
Exception code: 0xc0000409
Fault offset: 0x0000000000095ebf
Faulting process id: 0x2220
Faulting application start time: 0x01d54571ddd16db0
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 55df0ec3-4338-4090-afdf-c0657411d218
Faulting package full name:
Faulting package-relative application ID:
I have done a fair bit of googling and this seems to be a fairly common issue with no obvious fix other than to rebuild the VM from scratch.
The thing is it only applies to certain user accounts on the VM not all of them and when the issue is present I can still login with the domain admin account with no problems.
So couple of questions -
1) If it is only specific user accounts that display this problem does that suggest that it is not an issue with the VM or is that a false assmumption ?
2) If it just the user accounts then what I want to do is create new accounts for these users but then I need to replicate their profile in terms of desktop settings etc.
Can someone tell me how to go about doing that ?
Any help or suggestions on the above would be much appreciated.
Hi,
We have 2 session host and 1 license server, 1 session host working properly grace period return0 , another session host still showing grace period 119 days.
we have checked forum based on that changed the configurations but still showing grace period 119 days.
wmic/namespace:\\root\CIMV2\TerminalServices PATH
Win32_TerminalServiceSetting WHERE (__CLASS!="")CALL GetGracePeriodDays
Executing (\\RDLicenseServer\root\CIMV2\TerminalServices:Win32_TerminalServiceSett
ing.ServerName="RDLicenseServer")->GetGracePeriodDays()
Method execution successful.
Out Parameters:
instance of __PARAMETERS
{
DaysLeft = 119;
ReturnValue = 0;
};
Group Policy :
Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing
Use the specified Remote Desktop license servers Enabled RDLicenseServer
Set the Remote Desktop licensing mode Enabled per user
Rebooted
Registry Value:
It was 5, changed to 4
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licencing Core - 4psexec -s -i regedit.exe
Deleted
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Terminal Server\RCM\GracePeriod
Rebooted, but when reboot again this folder creating and Showing in Grace period.
Powershell Cmd:
$obj.GetSpecifiedLicenseServerList()Checked in rds license diagnoser , but no error / warning.
Please suggest on the same.
Regards,
Mani
I have a single domain controller. I am setting up profile path in Remote Desktop Services Profile tab for Vaidee(user). I have allowed vaidee to logon locally and through remote desktop services. I added him to Remote Desktop Users group. Even though he is not a domain admin, he can still login to the domain controller. When Vaidee logged in to the domain controller using Remote Desktop connection, the profile is not created in the specified location(C:\RemoteProfile\Vaidee).
Is there anything that I am missing?
Help me!
I have about 200 users running mostly remoteApp from many different locations. 95% of them work fine. I do have RDGateway but it is configured to bypass the RDGateway in the setup if it can connect to the broker. Things have been working fine for the past year or so. Recently on the last set up updates for windows 10 machines, they receive the error "Your computer can't connect to the remote desktop gateway server. Contact your network administrator for assistance" as soon as they try and launch and RemoteApp application.
The fix is this.
https://appuals.com/fix-your-computer-cant-connect-to-the-remote-desktop-gateway-server/
It forces it to disable UDP and use HTTP instead. As far as I can tell nothing has changed on the network and UDP is still open and clients are able to connect to it.
Has anyone ran into this?
Hi,
I am currently having alot of issue with RDS windows 2012 on windows 10 1803 (All servers and client PCs are patched up to July 2019). The issue started around 26th July and I have restarted all servers and nothing changed recently in our network.
The issue is happening within the network and also off the network. I have tried to removed some of my
Following is what I have on windows 10 pc for updates.
Could someone let me know if you also recently started seeing this issue?
thank you ver much
Pwint
Hi,
As RDS 2019 upgrade documentation seems to be non existing, I thought I'd ask this question here. Is it still necessary to migrate a connection broker from version 2016 to 2019 by doing an in place upgrade of the machine as was the case with 2012 to 2016? As the connection broker role is basically the same in both versions, I thought it might be possible to place the 2016 broker in HA mode, add a 2019 broker and remove the 2016 machine after that.
Is that possible?
We have RD Web on 2016 server (we use this server for administrative work on our network). The users access from RD Web from their desktops(using standard user credentials). When logging in to RD Web, the users us their administrative accounts (domain admin).
The users are able to run the remoteapps using IE11.
When using Microsoft Edge, accessing the remoteapps, RDP file is downloaded. I don't mind that. But, the connection wants to use the standard credentials instead of the admin account used to logon to web server. This does not happen in IE11.
How do I solve the credential issue in Microsoft Edge with the Remote Apps?
Thank you.