hello,
I have an RDS server farm with self-signed certificate and soon it will not be validation.
What I need to do for them is that they update automatically ?
According to this article:
I have to delete them and its documentation should be renewed
hello,
I have an RDS server farm with self-signed certificate and soon it will not be validation.
What I need to do for them is that they update automatically ?
According to this article:
I have to delete them and its documentation should be renewed
A few users are experiencing this problem.
Event ID: 5973
Activation of app Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI failed with error: The remote procedure call failed. See the Microsoft-Windows-TWinUI/Operational log for additional information.
And event ID: 1000
Faulting application name: ShellExperienceHost.exe, version: 10.0.14393.2125, time stamp: 0x5a990817
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.14393.2125, time stamp: 0x5a9909e5
Exception code: 0xc000027b
Fault offset: 0x00000000006d710b
Faulting process id: 0x6b78
Faulting application start time: 0x01d3c1fbf1890ced
Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 7c1dae0b-eec7-416c-b5c9-5148b1bc7ba6
Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.14393.2068_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App
When this happens the start menu will not work. This corresponds with me enabling the roaming of C:\Users\user\AppData\Local
I'm wondering if there is a folder I should exclude from roaming.
If it's not being caused by roaming the local folder then it may be caused by some GPO settings I also changed. I did this because windows search was out of control and consuming too many resources. Unfortunately I cannot disable search completely because of Outlook. My discussion on Outlook and search I had to re enable indexing outlook.
Any guidance on this is appreciated.
So far the only fix I've come up with is temporary, which is to delete the local profile and on the next login the start menu works. After a day or 2 it stops working again. I haven't totally recreated the user profile and I'm hoping this is not the ultimate fix because that would be a PITA to have to do that for all the users that have this happen.
Hi.
Environment:
The Outlook window dissaperars or looses focus when the cursor is moved between e-mails or tasks. Resulting in the application behind Outlook showing instead.
The problem is sporadic and it does not matter what window is behind Outlook. PDF reader, Excel, etc...
The video below shows the problem.
Remember: In the video the user is only moving the mouse cursor. No mouse clicks and no keyboard keys are in play here.
./ Lars Olsen
hello
how many RAM und CPUs does we need for 100 Users on one RDP Server?
our 2008 has 32GB RAM und4 CPU for 100-150 User.
Chris
We have migrated users from Windows 2012 R2 Remoteapps to Windows 2016. The Windows Server 2016 was built with fresh OS and users migrated to the new server by pointing the GPO (Windows Components/Remote Desktop Services/RemoteApp
and Desktop Connections/
Specify default connection URL) to the new server.
We are now seeing the above warning "The installation of the default connection has been cancelled. A default connection cannot be used on a system that is part of a Remote Desktop Services deployment." when a user connects to a Remoteapp.
We also have an issue when user's session is idle for sometime the Remoteapps stops responding and clicking on "Reconnect to Workspaces" throws an error "Unable to launch resource:0x800705b4" I am not sure if both these are related.
We currently manage an 8 node Windows 2008 RDS farm which serves approximately 250 users. We utilise roaming profiles and redirected folders. The majority of our users operate from workgroup thin clients. Users connect to a full RDS desktop session rather than using local client desktops and published apps.
As well as replacing the old thin clients, with either new domain joined t/clients or full fat laptops, we're also looking to deploy a new Windows 2016 RDS farm. Our initial plan was to stick with RDSH rather than VDI, however, this time the idea was to go with published apps and local client desktops. We would also look to use a combination of redirected folders and user profile disks. VDI looks interested but its unknown territory to us and we're struggling to get to grips with the pros, cons, costs,& licensing implications of RDSH vs VDI. There seems to be a lot of inconsistent and confusing documentation out there!
Anyone been in a similar situation or can point us in the direction of some straight forward documentation?
I have set up a standard 3 node 2012 R2 RDS for testing. All virtualized on VMware ESXi 5.0. I have a connection Broker, session host, and web access server. I have published several applications and I can access them without a problem. Here is my issue:
When I try to log on to my session host server either locally or thru RDP, I am always logged in with a Temporary profile. It does not mater what user account I use. Even logging on locally as the administrator I get a temporary profile.
All windows updates are installed and current.
I have removed the server from the domain, deleted the account, and rejoined it to the domain.
I have deleted all .bak registry entries from here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
There is a hotfix here for a similar issue on 2012 but it does not apply to 2012 R2
The only event viewer errors are:
1515 (Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on.)
1511 (Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.)
Any suggestions to resolve would be greatly appreciated.
Russ
Hello All,
I am expecting a little help from you. I have RDS installed and configured with Trusted SSL using 15 Session host servers and 1 broker server and 2 (Gateway, RDweb, and License) server. All the user workstations are on Windows 7.
Currently, we have published the RemoteApp on the RDWeb and whenever the user tries to launch the RemoteApp it just spins forever and after we kill the RDP from Task manager if we relaunch the RemoteApp then it is launching fine.
I tried
!. "Computer Configuration/Policies/Admin Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Remote Session Environment: Use advanced RemoteFX graphics for RemoteApp – Disabled"
2. unchecked the Local resources -drives for the Collection.
Both the tries were not successful. I'll need to know what is the exact solution to my issue. Since this is a behavioral issue I don't have much knowledge on this where to look.
Could anyone please give me a suggestion.
I tried on Windows 10 workstation and see this when I launch the RemoteApp.
While spinning it says
1.initiate remote connection
2.securing remote connection
3.configuring remote session
4.securing remote connection
5.configuring remote session then keeps spinning at this step until I kill this from Taskmanager.
Since I have a trusted certificate that is not the issue. this is happening only sometimes not all the time so I really do not know where to look.
Pls advise
Thank you
Shekar-Technet
In RD Licensing Diagnoser on Server 2016, I get a message that the licensing mode for the Remote Desktop Session Host server is not configured. How does one set this. I cannot find the "RD Session Host Configuration Tool" like I we have used in the past with Windows Server 2008 R2 to accomplish this task.
Thanks
NK
I cannot get my users to connect to their RDS desktop. I have a test network that I'm using for my server certification. I have a server running 2012r2 that is configured as a domain controller. I have another server connected as a member server to the domain. The member server is configured as RDS(terminal Services). This is the scenario: My users login to their Active directory desktop. From there, the users attempt to connect with remote desktop connection to their RDS session host desktop. From what I can see, the user is connecting to the the RDS server itself, just like the normal RDS connection, instead of their session host desktop. When a user connects to their desktop, and opens the start menu, they can see the server manager and everything that's on the RDS server desktop. It's not the the user session host desktop. Can someone help me to fix this configuration. I will send any screenshot or log you may need. Thank you.
Hi
I have only the user name and password for the client.
How can I access to his terminal through remoteApp manager?
Regards
I need to test User connectivity against thousands of remote servers and i would like to have a powershell script for it.
What is i would like to do is,
1) I have a server list (around 16000 servers)
2) I have username and password where i can use to connect
3) I have port no. (445 and 137).
Now, i would like to have script to connect to those servers on the perticuler port no's using the credentials.
Most Important i want to capture the errors it is throwing back like (Access denied, RPC Server not available)
Can any one help me on this ?
I have a user that uses his Windows 10 laptop to connect to the Windows 2008 R2 server using remote desktop. He was working fine for a while then all of a sudden started getting kicked off. He will connect for about 5 - 10 minutes and then get disconnected.
Event logs on the laptop are:
Event ID 1026 - RDP Client ActiveX has been disconnected (Reason = 516) - 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.
But he is able to connect so we know that remote access is enabled, the remote computer is not turned off (it's the main file server - never off), and the remote computer is available on the network or he would have never connected to get disconnected.
Event ID 226 - RDP Client_TCP: An error was encountered when transitioning from TcpStateConnectingTransport to TcpStateDisconnected in response to TcpEventConnectionTimeout (Error code:0X80004004)
We only use IPv4 so we have IPv6 unchecked. We specify the IP address and DNS settings so they are on the same network as the server. He remains connected to the network, just not to the server.
Event ID 1105 - The multi-transport connection has been disconnected.
I found an article with similar errors that pointed to inactive ports as the culprit. I checked the registry and found there were over 500 inactive ports. I ran the "fix-it" and it deleted all of the inactive ports. I will apply the HotFix tonight while everyone is logged off and am able to let it reboot. However, clearing those ports didn't stop him from disconnecting.
The event logs on the server are:
Event 25, TerminalServices-LocalSessionmanager - 1:47:14pm
Remote Desktop Services: Session reconnection succeeded:
User: ServerName\UserName
Session ID: 3
Source Network Address: Laptop's IP Address
Event 24, TerminalServices-LocalSessionManager - 1:52:20pm
Remote Desktop Services: Session has been disconnected:
User: ServerName\UserName
Session ID: 3
Source Network Address: Laptop's IP Address
This will continue like this all day. He can't stay connected for no more than 20 minutes. Some sessions are only a couple minutes. Does anyone know what we need to do to fix this?
Thanks,
Jessica
Hi,
I have a setup with the following servers running Windows Server 2016
1x RDGW, RDCB, RDWA, RDLicensing.
5x RDSH
Im using UPD on the collection.
I have noticed very long login times, after policys etc are shown on screen it sits at a black screen for between 20sec and sometimes up to 5min.
I have also noticed that the svchost.exe that controls the Windows Firewall is using 25% to 50% when a user logs in and using around 1200Mb memory.
After I found this I checked the Windows Firewall with Advanced Security and found thousands of Cortana, Work or school account, Your account, Contact Support rules.
I found a script in this thread that could delete the rules https://social.technet.microsoft.com/Forums/windows/en-US/9aad7675-d1ba-4900-9d85-0cd117f5514f/new-firewall-rules-created-for-each-user?forum=win10itprosetup
This made the CPU usage and memory usage go down to normal levels, but after every login a user does it builds up the list of rules again. With many users logging in to the system the rules build up very fast and the login times gets high and every server gets slow.
Example on our RDSH01 server that have been running in production since 2017-04-13 the script found and deleted 66153 rules that it found with "$Rules = Get-NetFirewallRule -All | Where-Object {$profiles.sid -notcontains $_.owner -and $_.owner }"
The script also tryed to get rules with this command "$rules2 = Get-NetFirewallRule -All -PolicyStore ConfigurableServiceStore | Where-Object { $profiles.sid -notcontains $_.owner -and $_.owner }" but fails with an "not enough space error"
The script removes the rules from here with the content of $rules "HKLM:\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules"
and $rules2 was meant to clean up at "HKLM:\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\Configurable\System"
but doesnt do anything because of the error on the Get-command. If I try to access it with regedit it stops to respond, guessing there are too many items in that container for it to handle.
Anyone know a solution for this problem?
Regards Fredrik
Okay, we currently have an RDS 2016 Configuration, with the following:
- 1 x RDS 2016 License Manager server
- 2 x RDS 2016 Gateway/Web Access servers
- 2 x RDS 2016 Connection Broker servers
- 4 x RDS 2016 Session Host servers (2 x Session Hosts on load-balanced servers)
The RDS 2016 Connection Broker server is configured in High Availability Mode, and stores it's database on a SQL 2016 Cluster. The initial setup doesn't allow you to specify SQL 2016 *until* you later configure CB to be in High Availability Mode, so it's my understanding that it initially uses a WID (Windows Internal Database) and continues to do so even after configuring High Availability Mode?
Is there any way of "removing" the dependency between the CB and WID, as this TechNet Article seems to suggest that TLS 1.2 can't be configured if WID is involved in the installation?
The reason for asking this, is that we configured the SCHANNEL registry settings to disable everything apart from TLS 1.2, and this broke the connection between RDS and the Connection Broker. The only way to "recover" this was to re-enable TLS 1.0 (TLS 1.1 didn't work).
Any ideas appreciated.
Many thanks.
When attempting to add another virtual desktop to my remote desktop collection I'm getting an error.
A new virtual desktop could not be created from the virtual desktop template.
Verify that all the Hyper-V servers in the deployment have the correct network configuration and available hardware resources, and then try again.
I'm trying to figure out what that means. I've looked at the settings of the template vm and it would seem that the network looks right. Mac address set to dynamic.
What could be the cause of this?
VM host [PRECRDSVDI01.PRECEDENT.LOCAL] failed to execute VM Provisioning operation [Task: To initialize pool creation at VMHostAgent:] for virtual machine [] in pool [Virtual_Desktop], Error: [Error code: 0x8813020C.]
Hey all,
In the process of putting in an RDS farm which will be administered by a team of 16 admins.
I've only recently found (never really looked before) that when creating a group within server manager, it is user specific and stored under \appdata\roaming\Microsoft\windows\servermanager\serverlist.xml
Considering RDS requires that a server group exists that contains all of the RDS CB's and SH's - it seems ludicrous to require each admin to update their list each time there is a change to a membership of the farm.
I realise I can copy the serverlist.xml around to each persons profile - but that will trash their existing server lists - and seems pretty backwards.
How do other admins out there get around this issue? I get the feeling that managing RDS via server manager isn't really intended for anything other than small organisations.
I have seen this - https://social.technet.microsoft.com/Forums/en-US/d9f95be9-40a4-47f9-855f-5636a18e9405/rds-connection-broker-managing?forum=winserverTS and while "TP" comes across as correct - none of them are an enterprise solution....
Hi all,
I'm trying to setup high availability in a 2016 Connection Broker server using as DB an existing SQL 2016 Cluster Always On AG.
I created a new DB on the SQL Server and added it to the AG (also tried without adding it to the AG); created a new sql logon and given db_owner and securityadmin permissions to the new DB. I can access the DB from both SSMS and SQL Client from the RDCB server, but when I try to configure HA using shared server I get this error message:
"The database specified in the database connection string is not available from the RD Connection Broker server".
I also tried to create HA using dedicated server, but login fails with the same error even if I add the RDCB server to SQL Server with sa permissions.
This is the connection string I'm using:
Driver={SQL Server Native Client 13.0};Server=sqlcluster_dns_name;Database=ClusterRDS;Uid=user;Pwd=password;Encrypt=yes;TrustServerCertificate=yes;Connection Timeout=30;MultiSubnetFailover=yes;
I also tried with Native Client 11, nothing changed. Both clients (11 and 13) are installed on the RDCB Server and I can configure a connection from ODBC data sources.
Firewalls are off everywhere.
Any idea? Am I missing something?
Thank you,
Marco
Hello,
We have a RDS 2016 evironment en randomly some client have strange screen issue's, distorted screen in their RDS session. People with the problems are switching often between application and it looks like screen caching problem. When disconnecting the session and reconnect the problem is solved. See screenshot:
What have we done:
* Disabled persistent cache under advanced RDP settings clients.
* Disabled other settings under advanced RDP settings clients
* There is nog difference between connecting with thin client or fat client