Hi Team,
We bought Windows 2016 RDS Client Access Licenses through Microsoft Store, can we install these licenses with windows 2012 R2 Standard. If yes Please let me know the steps to proceed. We tried to activate through direct, Website and telephone but not able to succeed.
Regards,
Ashokan.M
Hi,
We do have a Windows 2016 Server with English-US as default language. We installed the French language pack on it and everything work well.
After that, if i add the RDS Web role, i do have the C:\Windows\Web\RDWeb\Pages\en-US and the C:\Windows\Web\RDWeb\Pages\fr-CA folder on my server but the content of both files (en-US or fr-CA) are in English.
My next step is to remove the language pack and to reinstall it but is it expected to get this or the language pack must be installed after the RDWeb role ?
Thanks!
This posting is provided AS IS without warranty of any kind
Hi
Got an issue with the New-RDSessionDeployment cmdlet when running it via an PSSession, the cmdlet is executed but returns an error. FYI the cmdlet works perfectly locally on the 2016DSC01 server... ?
$ForestFQDN = "DEMO-AD.dk"
$RemoteServerDCServerName = 2016DSC01
$RemoteServerRDSHostServerName= 2016DSC02
} -ArgumentList $("$RemoteServerDCServerName.$ForestFQDN"), $("$RemoteServerRDSHostServerName.$ForestFQDN"), $("$RemoteServerDCServerName.$ForestFQDN")
Error returned from the Invoke-Command via the PSSession:
New-RDSessionDeployment : Validation failed for the "RD Connection Broker" parameter.
2016DSC01.DEMO-AD.dk Unable to connect to the server by using Windows PowerShell remoting. Verify that you can connect to the server.
At line:19 char:17
+ ... New-RDSessionDeployment -ConnectionBroker $ConnectionBrok ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-RDSessionDeployment
hi
in rdsh when enable use the remote desktop easy print driver and run the wordpad in local Client hard
on windows 10 Client can save and printe by microsoft print to pdf
but in windows 7 Client cant save or printe by microsoft print to pdf
Hello guys,
This is an old problem in one secundary Windows Server 2012, where after a while(between 1h 2h) of closing a RDP session, that session is logged off, closing all the current work.
After searching about it I notice that on Server Manager>>RD Services it would be an option Quick Session Colletion(here) with some settings for that(), who doesnt exist in this Server:
Also on Dashboard I have a problem with RD Services:
where I dont know if it could be the source of that missing option.
Anyone?
We have a machine that is running our shipping software with a scale. The software goes out to a SQL server and pulls some data. This makes the application run very slow as the node is distant from the SQL server.
To get around this, we are running the application through an RDP window on the RDS server (which is on the same rack). However, now the scale that is hooked to the local machine doesn't populate the weight in the shipping application.
so far I have tried:
1. Making sure "ports and other plugnplay" devices is checked in the RDP session setup.
Any other ideas on this?
Hi,
I have a built an RDS farm in a domain using .local for the server hosts, I have a wildcard certificate that resolves to rdsserverfarm.com.
Can I use the wildcard cert for all servers within deployment properties and rename the connection broker to match?
What is the best method for this type of deployment?
Thanks
Nick
Hello,
Quiet a confusing subject, googeling was not helpful,
There are 3 to configure Session Idle Timeout, 1. GPO 2. User properties, Session tab 3. on the RD server/gateway itself.
In my situation, GPO is not configured, user settings is set to never, RD Gateway settings is set to 2 hours to DC and another 2 to end DC'ed session.
Assuming I want to bypass the limit for a certain user, what would be the best course of action?
Regards, Avi.
I am also getting the same error
The computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable.
Recent Change Implemented: Renewed Wild Card Certificate
Issue: This issue occurs only when users are connecting from outside network but when they try to access RDS withing network it works flawlessly
Steps Followed So far;
1) Verified RDGateway Certificate and its expiry date
2) Verified Internet Explorer Settings - TLS1 , 2 and 3
3) Imported Server Certificate into the client machine's trusted root store
4) Verified Public facing domain and its resolution over internet
5) TSGateway service Restarted
6) Created/Edited a 32 bit DWORD value called RDGClientTransport in Client Machines registry at Computer\HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\PublisherBypassList
7) IIS -> Default Web Site -> RDWeb -> Pages -> Application settings -> Defaults TS Gateway (Verified URL)
Please help
Hi
Currently setting up two HA connection brokers pointing to a single sql express 17 instance I know that currently I don't have HA Sql we would like to do this however as we understand it to do this we need to have an sql server CAL for each user connecting through the broker is this correct also Do you have to have the same sql version across the two sql instances Thanks
Hi All,
I have followed some guide and succesfully to built a testlab RDS, but still have confuse one thing about RemoteApp / RDSH . Here my server info:
+ server 1 running roles Remote Desktop Connection Broker , RD Sessions Host
+ server 2 running role RDWEB , RD Gateway
All is worked fine, RemoteApp can access from internal / external .
but if i add 1 more server to running RDSH , and created collection for this server. All new RemoteApp visible on RDWEB ( both 2 RDSH) , but cannot run remoteapp drom new RDSH with information: "your computer cannot connect to the remote computer because
a error occurred on the remote computer that you want to connect to..."
Do i miss somthing to config on RDWEB ? or anything else ?
Please help.
yukistvn
Hello everybody.
We have an old Citrix farm, there each published application points to an Excel file (an individually customized BI report). Around 500 applications we have there.
So now we migrating this repository to a new RDS 2016 deployment, based on the Windows Server 2016 Standard x64.
We've created a PowerShell script, which make this publications automatically.
But after publication of around 60 RD apps Server manager stops responding, and RDS stops functioning. We've tried to reproduce this behavior under the Windows Server 2012 Standard x64 deployment - same result.
We've deployed 58 RD apps, and started to add RD apps one by one manually. Same result, after the publication of 61 or 63 Server manager stops refreshing, High Availability (but not necessary) RD Connection broker stops responding, and all the RD apps stops functioning.
An example of 23 published apps here:
It obvious that I could provide two files: the .ps script and the .ini so anyone could reproduce this situation (publish dummy RD apps) in their environment to check the situation... But would you? )
Hi,
Wondered if someone could please help/advise.
We have 3 VM Servers. When users are logging off one of them it says 'signing out' and take around 10 - 15mins?
We do have roaming profiles going on between the 3 servers however it only happens on this particular one.
Also when we sign out as the administrator we still get the issue which suggests it has nothing to do with roaming profiles.
Help??
I recently setup a brand new server 2016 RDS Farm. The issue I am having is that one of the servers is showing session IDs of zero. This is the same issue I was having with our server 2012 R2 farm. That is why I wanted to replace the old farm with the new one. I have been through so many documents that spelled out possible solutions, but none of them has fixed my issue. It is a simple setup. One server has the license server, broker, gateway, and session host. The other two have just the session host installed. The server I am having trouble with is the one with just the Session Host installed I have tried rebooting the broker server to no effect. Other things I have tried are removing the server in question from the collection and then removing it from the deployment and then re-adding it back in. The server IS added to the “RDS Management Servers” group in AD. I even went so far as removing the server off of the domain, uninstalling the remote desktop role, re-adding it back into the domain, and then installing the remote desktop roles again. The server is still showing session IDs of zero. At this point I am at a loss as how to fix this issue. Any help would be immensely appreciated because I need to get this new farm into production as soon as I can.
I just configured RDWeb-access on the server by setting the PasswordChangeEnable as true (IIS -> Pages -> Application settings)
Page shows up, Users can login..all good.
The problem is, when they try to change their password, it says:
Your new password does not meet the length, complexity, or history requirements of your domain. Try choosing a different new password.
No matter what password you put it, it would not take the password. I even tried something like A19G8fczAe!!W
** I have disabled password complexity in Group policy. ** still no hope.
BUT - when i go to AD and set the user to : Must change password at next login.
Then I go to RDWeb and try. It successfully changes the password..
So it only works when i set the user up to MUST CHANGE PASSWORD NEXT LOGIN..
is it how it should work?
Users want to change their passwords whenever they want..but it doesnt work.
am I missing something?
When try to connect from public network to RDS 2016 environment web page is loaded, but when try to connect on RDP clinet, it will ask for credentials and after that it will connect to remote machine. Error shows as " your computer can't connect to the remote computer because remote desktop gateway server is temporarily unavailable"
When checking on error log found that even id 312 on gateway server
The user "abc@xyz.com", on client computer "xx.xx.xx.xx:2985", has initiated an outbound connection. This connection may not be authenticated yet.
I tried the registry key fix recommended for 2012 server (HKLM\SYSTEM\CurrentControlSet\Control\Lsa) and (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\TerminalServerGateway\Config\Core) but no joy. It did not work for 2016 server. Please help.
hello folks,
today one of our branch offices had a power loss after a big lightning hit, all clients except one could reconnect to the central 2016 ts server and take up their work again, so i can eliminate network components such switch or firewall, vpn etc as source of failure.
also i am able to connect with this clients credentials from the central to the ts it can not be the server itself or the users profile nor its account.
yet i am unable to connect the rdp session from another local account on that particular machine, what eliminates the local users profile also.
what is left is just the win 10 client itself and the striking lightning - curious right?
what is written in the clients eventlog are just some informations, no related warnings, errors nor criticals - same on server side (yet it says client auth succeeded and then its silent)
on the client side the last information entry is as stated in the topic title and the reason code is undocumented (again). i only found a table that tells about 3847 and 3848 being related to expired password and general account troubles. but as mentioned before, the rdp session can be opened from other client, but not other local accounts.
anyone seen that in the wild? any advice?
today i tried about fifty (literally) hints from all over the web from a few hundred sites, without effort. its tiring and frustrating... (other network services still work between particular server and client, such as share access)
kind regards :(
We have two RDP servers running our ERP application runs as a published app. Server RS1 acts as the connection broker and is also where the RD Session Collection is normally seen
The RD Session Collection for our published app keeps disappearing. It will be visible under collections for days or weeks, then it will disappear for days or weeks. Then it will show up again. What are some of the possible causes to this and how can I get
it back and make it stay.
Currently, the collection is missing. However, if I use the Powershell command Get-RdSessionCollection it returns the collection name.
If I look in Server Manager, RS1 and RS2 show up under Servers. Collections is blank. Only RS2 shows up under Host Servers
(My company upgraded our servers 5 months ago to windows server 2016. (new DC server, SQL server and 2 RDP servers) Our ERP application runs as a published app that we access through an RDP connection.)