I haven't used SPLA for doing any RDS licenses and am having trouble finding info on where to get the licenses.
Where do I get licenses from? I can't find any info on the SPLA site or on the Microsoft Volume Licensing Service Center site.
Thanks!
I haven't used SPLA for doing any RDS licenses and am having trouble finding info on where to get the licenses.
Where do I get licenses from? I can't find any info on the SPLA site or on the Microsoft Volume Licensing Service Center site.
Thanks!
I HAVE WINDOWS SERVER 2012 R2
LICENSES APEAR CONFIGURED OK ON LICENSING MANAGER BUT ON LICENSING DIAGNOSER I HAVE NO LICENSES Y CANT CONECT TO THE LICENSE SERVER
A MESSAGE TELS ME I HAVE FEW DAYS FOR THE LICENSES TO STOP WORKING
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
Environment:
Server 2012 R2 stand-alone not on a domain (workgroup)
RDS feature has been installed
All users have been placed in the built-in group "Remote Desktop Users"
I have a total of 15 users (local accounts). 7 of the accounts were created the day I placed the server in production. The other 8 were created yesterday (6 days later). The first 7 users have no problem connecting to the server through RDS. The other 8 all receive the error message at login "The credentials that were used to connect to x.x.x.x did not work. Please enter new credentials."
I have verified the user name and password as correct. I have checked local policies and they are fine. I have restarted the server as well. I deleted the user account and added back with no luck. Changed the passwords with no luck. Does not matter what device/OS they are trying to login in from.
Now I am reaching out for assistance. Thanks
Hi,
We have built a Windows 2012 RDS "farm" and have also purchased 100 RDS CALs from MPSA.
Would someone instruction what do I need to do to make the 120 days warning goes away? How do I apply the license to each RDS host? Do I need to do anything on my connection broker? I also have a file server that holds the roaming profile of the user. I should not need to apply the CALs to it, right?
Hi all,
I am trying to build a network where RDP connections are allowed to users only if they have a valid personal user certificate issued by our internal certificate authority. I understood it would be possible, as some forums and articles note that it could be done through NPS RAP and CAP configurations, but I cannot find a tutorial on how to actually do that. Can someone share how to do it preferably on 2012 R2 environment, or point me into the right direction/link?
Background: I have already built a test environment with AD DC, CA enterprise server and RDS server, all on Windows Server 2012 R2. Remote desktop connections are enabled and working through Gateway and Web Access, and I have successfully implemented User, Computer and Web Server certificates for different machines and users (new templates duplicated from original templates, minor changes).
Any advice is greatly appreciated!
-LearnSomeMore
hello
I am new to CAL licensing.
I need to completly format and reinstall windwes 2012 Server Essentials with Remote Desktop services enabled and CAL licences installed.
Will there be no problem with reinstall CAL licenses on operating system after reinstallation?
Or maybe it depends on something? I just need to besure before format my server.
Server will be the same, version of operating system and license key for it also.
thanks in advance for any help
jan
on a new windows server 2012 with the "remote desktop session host" role enabled, and "Remote desktop Licensing" we are unable to locate the "remote desktop services manager" snapin.
can you please advise
Hi.
Is it possible/supported to put a 2012R2 RDS Gateway in front of a 2008R2 session host farm with rds 2008R2 broker?
Ty
Folks,
Just noticed this becoming an issue on a Windows 2012 R2 Terminal Server after the last round of Patch Tuesday updates stemming from August 9th, 2016.
Typically, I'm rebooting the server every 24 hours to over-correct the issue - rebooting not being the best option here.
In previous discussions, it's advised to remove KB3002657 or KB3035132 from the server. Is this still the best option to restore full functionality even with the last round of patches and updates? Just to confirm, we are not using webroot as an AV solution.
Ivanildo Teixeira Galvão
I noticed some strange thing on one of my servers which is a hosted VM with Server 2012R2 on it and session-based RDS installed. First on the list of Administrators I found a non resolved SID then when I went to RDS Connections I noticed users from domainB connected to the server however in Session Connection properties the "domain\B Domain Users" group was missing. I tried adding the group and Check Name resolved it just fine yet after clicking OK an error popped up saying "The security identifier could not be resolved.... The network path was not found". I enabled debugging and found the following errors. Where to go next to fix this issue?
40963: Component RdmsUI: Error in script execution on: server
40963: Component RdmsUI: Failed to fetch local DB connection string from server: server: System.Management.Automation.RemoteException: Property DBConnString does not exist at path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tssdis\Parameters. at Microsoft.RemoteDesktopServices.Common.DeploymentModel.ExecutePowerShellScript(String serverName, String script, Object argumentList, Boolean isLocalhost) at Microsoft.RemoteDesktopServices.Common.DeploymentModel.IsHighAvailabilityConfigured(String managementServer)
40962: Component RdmsUI: Exception occurred in GetSecurityDescriptorFromPath with parameters path: WinNT://domainB/Domain Users. Exception details: System.Runtime.InteropServices.COMException (0x80070035): The network path was not found. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_AdsObject() at System.DirectoryServices.PropertyValueCollection.PopulateList() at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) at System.DirectoryServices.PropertyCollection.get_Item(String propertyName) at Microsoft.RemoteDesktopServices.RDManagement.Utils.CommonUtils.GetSecurityDescriptorFromPath(String path)
40963: Component RDExceptionHandler: The security identifier could not be resolved. Ensure that a two-way trust exists for the domain of the selected users. Exception: The network path was not found.
yaro
Hi
I have a single Windows 2012 R2 RDS server, which acts as all the RDS roles, including RD Gateway.
I also have an Windows 2012 R2 IISARR server setup to reverse proxy 443 connections to the server, and have port 3391 open on our firewall to allow UDP connections.
In short, if I connect using an RDP 8 client, I get three connections as expected. One HTTP and two UDP. If I connect using an RDP 7 client, I get one RPC-HTTP connection, again as expected.
The problem is that whereas the RPC-HTTP connection is stable, the HTTP & UDP connections disconnect every 2-5 minutes. The client screen goes black and a Reconnect Attempt 1/20 windows is displayed. Each time though the connection re-establishes itself and the session is not reset.
In the gateway manager, monitoring page, you can witness these connections disconnecting and re-connecting. It's very puzzling. The event logs acknowledge the disconnect, stating reason 0.
On the Windows 8 clients, I've tried the recent hotfix 2897602 and tried turning off Windows Location Services. But that doesn't help.
I've read a lot about UDP and RDP8, with some saying it doesn't work properly and that you should turn it off. However, I have it turned on as I was having problems scrolling PDF files in the remote session, which the UDP connections fixed.
Any help with this would be much appreciated. I've done so much research and spent so much time on it...
Thanks
Andrew
I've set up a HA Connection Broker cluster, and in order to get the web gateway working again, I need to set up a new RAP policy that specifies the RD Broker RR Address, but every time I try, when I click 'Add' in 'User Groups' (And anywhere else in the MMC, it seems), the MMC crashes with the following output:
Problem signature:
Problem Event Name: BEX64
Application Name: mmc.exe
Application Version: 6.3.9600.17415
Application Timestamp: 54504e26
Fault Module Name: clr.dll
Fault Module Version: 4.6.1055.0
Fault Module Timestamp: 563c12de
Exception Offset: 00000000002fdbd8
Exception Code: c0000409
Exception Data: 0000000000000002
OS Version: 6.3.9600.2.0.0.400.8
Locale ID: 1033
Additional Information 1: 96f9
Additional Information 2: 96f9c5010a52aa0dfa6dd4f9281ffe93
Additional Information 3: 7b9b
Additional Information 4: 7b9b3ea08d2dac897bb696ccf51055a9
As far as I can tell from searching, it seems to be .NET that's crashing, but I haven't found any solutions.All three servers (Web Gateway and both Connection Brokers) are fully patched.
has anyone else sen this and/or have any ideas how to either fix it or maybe some kind of workaround?
I've just setup 3 new Windows 2012 R2 servers. Names and their intended roles as below:
- DC-SVR01 - roles: Domain Controller, DNS, DHCP and RDS Broker (VMWare VM)
- RDS-SVR01 - role: RDS Session Host server (HP Physical server)
- RDS-SVR02 - role: RDS Session Host server (HP Physical server)
All there servers were joined to the domain, given static ipv4 addresses and all available MS updates were applied.
At this point no roles or features had been installed on any of these servers.
I then deployed RDS using Server Manager from DC-SVR01. The RDS Broker and RDS Web role installed onto DC-SVR01 and the RDS Session Host role installed onto RDS-SVR01 & 02. After a reboot of all three servers i could successfully see and manage the servers
using the 'Remote Desktop Services' feature within Server Manager. This morning i installed the ADDS role and promoted DC-SVR01 to a domain controller (existing forest/domain with 4 Win2008 DC's). After reboot of this server i now get the following error from
server manager when navigating to 'Remote Desktop Services > Overview':
"The server pool does not match the RD Connection Brokers that are in it. Errors:
1. Cannot connect to any of the specified RD Connection Broker servers. Ensure that at least one server is available and that the Remote Desktop Managment, RD Connection Broker, or RemoteApp and Desktop Connection services are running on DC-SVR01.
I checked the services on DC-SVR01 and found the Windows Internal Database failed to start due to logon issues. I changed the logon account from NT Services to a domain admin account and it now starts successfully.
The problem only seems to have come about since promoting DC-SVR01 into a DC.
I've read many other similar issues on the net but these seem to indicate this is only an issue when ADDS and the RDS broker role is installed on a server which is running Windows 2012 RTM. All of my RDS servers are running Windows 2012 R2.
I cannot find anything to suggest that ADDS and RDS Broker roles are not supported on a single server running Windows 2012 R2? Any assistance would be appreciated.
Hey guys. Hopefully an easy question for you but I have not been able to find a case that 100% matches this question. I have been tasked with renewing the SSL certificate for my company's RDS deployment for SAP. I am actually not 100% new to RDS as I have done some administration for this deployment in the past, but I have never needed to handle certificates up to this point (I am taking over for a previous systems engineer who is no longer with us who is the original architect of this deployment) and would like to get confirmation on the process.
Before I continue, let me give a brief breakdown of my environment (Server 2012 R2):
As I understand it, all I should need to do is:
I believe that is all I need to do. From what I understand I do not need to individually apply the certificates on the session hosts, rather, the certificate simply needs to have SAN entries covering the FQDN of each session host. Am I missing anything or should this cover it?
Thanks all!
I need to enable Restricted Admin Mode for MSTSC across my 2008 R2/W7 domain. I need Authenticated Users (with RD access) to be able to access a Remote App available on RD Web Access Gateway. With RA mode enabled, they get a "restricted access" error when attempting to connect via MSTSC (prior to application launch). If I attempt this while logged in as Domain Admin I am able to connect over MSTSC and launch the application as normal.
I tried adding "remoteapplicationcmdline:s:/restrictedadmin" to the Custom RDP Settings in Session Host configuration, but I get an error that I "cannot override global settings".
Is it possible to apply this cmd line argument to a RemoteApp application, or is there another way to enable Auth Users to connect while still using Restricted Admin mode across domain MSTSC connections?
Hello
We recently did a migration of our RDS Server to a brand new Windows 2012 R2 server.
All was working fine but we started to have this messages in the RemoteConnectionManager event log:
Log Name: Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin
Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager
Date: 9/14/2016 8:42:53 AM
Event ID: 20499
Task Category: None
Level: Warning
Keywords:
User: NETWORK SERVICE
Computer: XXXXX.com
Description:
Remote Desktop Services has taken too long to load the user configuration from server\\xxxxx for user xxxx
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-TerminalServices-RemoteConnectionManager" Guid="{C76BAA63-AE81-421C-B425-340B4B24157F}" />
<EventID>20499</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2016-09-14T15:42:53.300353800Z" />
<EventRecordID>388</EventRecordID>
<Correlation />
<Execution ProcessID="28452" ThreadID="50892" />
<Channel>Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin</Channel>
<Computer>XXXX.com</Computer>
<Security UserID="S-1-5-20" />
</System>
<UserData>
<EventXML xmlns="Event_NS">
<ServerName>\\XXXXX</ServerName>
<UserName>agranados</UserName>
</EventXML>
</UserData>
</Event>
Everytime this error message is logged the user gets disconnected from their RDS session.
So far we tried the following:
- Validate AD health (sites,subnet,replication, sysvol)
- We changed the DisableTaskOffload option as suggested in other posts
- We verified the group policy settings applied
Unfortunately we still haven't found what the root cause of this issue is.
Any suggestion of similar previous experience is welcome.
Thanks in advance!
Cristian
Regards. Cristian V.