Renaming computers in Win2012R2 Session Host Farm

We have Windows 2012 R2 RDS Session Host farm setup with the following numbers of servers
2 x RDWA in Win NLB
1 x RDLic Server
4 x RDSH Servers configured in two collections with each collection having 2 RDSH servers
1 x RDCB server
1 x File share cluster for UPD storage
All the above mentioned RDS servers are VM's on a HyperV 2012R2 3 Node Cluster.
We wish to achieve the following
Rename ALL the above mentioned RDS computers retaining the AD Domain name. e.g. server1.domain.com will become host1.domain.com
Is there a set procedure to rename computers those are part of RDS session host farm?

Hi,
There is no rename functionality for servers in a RDS deployment. What this means in general is that you need to remove the servers from the deployment, rename them, then add them back to the deployment.
The biggest "catch" is probably the RD Connection Broker. You cannot rename it since it is the heart of the RDS deployment which means you essentially need to wipe out your deployment (remove RDS Role Services from the broker), rename the server, then
install the deployment again.
I have not tested it but I think it would be possible to remove/rename/re-add a RDCB server if you had an HA deployment with at least one other RDCB server that you could leave in service while renaming the other broker.
It should not take too long to redo the deployment from scratch since you only have 2 collections, unless you have lots of published RemoteApps. Usually the longest part is installing all of the applications on the RDSH servers and configuring
custom settings, security, etc., which most likely you will not need to do. Some applications may have a problem if the server they are on gets renamed but that is specific to certain applications.
I would recommend you test the various steps of your rename so that you know what to expect.
So in general the steps would be:
Write down any customizations/settings/etc. for the deployment and the collections
Unpublish all RemoteApps from the collections
Remove all RDS servers from the RDS deployment except the broker (the various Role Services will remain installed on each server)
Delete all collections
Uninstall RD Connection Broker Role Service from the broker
Rename the broker server
Rename the other RDS servers
Install a fresh RDS deployment on the broker, verify there are no remnants of old deployment
Add the other RDS servers to deployment, create collections, configure, publish RemoteApps, etc.
Test everything, verify there are no "phantom" RemoteApps showing in RDWeb, etc.
I'm probably forgetting some details but the above should give you enough to figure it out.
-TP

Similar Messages

Creating Kerberos Identity for RD Session Host Farms for w 2012 r2

anyone knows how Creating Kerberos Identity for RD Session Host Farms for w 2012 r2.
I tried what they said the post
to w 2008, With
powershell I find the possibility and the
script indicates the error class is not
valid

Hi,
Referring to your comment, here providing you article for Kerberos authentication in server 2012. Please refer to the below article.
What's New in Kerberos Authentication (You can refer for Server 2012 R2)
http://technet.microsoft.com/en-us/library/hh831747.aspx
Hope it helps!
Regards.

Relation between RD Connection broker and RD session host farm in 2012 R2

Good Day
I have configured standard RDS session based deployment recently on 2012 R2 servers
Everything is working as expected
The setup has TWO RD Session host, 1 Session Broker, one RD Web access and one RD Gateway
I have created 2 DNS records named Rdsfarm.domain.com for my RDS1 and RDS2 session host servers and if I connect to this
rdsfarm.domain.com with RDP from TS clients, i am able to connect to any one of TWO rds servers without any problem
However some part is not clear to me
I have not added rdsfarm.domain.com any where except my RD Gateway server RAP policy
Also I have added my RD Broker server in RAP allowed group above.
I don't see any config where this farm name is associated with my RD Broker server
I have tried to connect to RD broker server from client, but it didn't redirect me to RD session host servers
If I try to connect to my RDS servers with their FQDN , it gives me error that I must connect thru farm name
Can you please help me to understand relation between RD session host servers farm and RD broker server ?
Also I would like to know what exactly happens in background when user start RDP session by entering RDS farm name
Note that RDS farm name is generic DNS Host(A) record pointing to my both RD session host servers
I wanted to know is there any command or configuration I missed out as I don't see any config where Generic RD Session Host Farm name (DNS Host(A) record) is associated with my RD Broker server ?
Thanks
Best Regards
Mahesh

Hi,
If you are opening Remote Desktop Connection and manually connecting to the broker then it will not work properly because you have no way of specifying the target collection in the user interface. If manually using the RD Client to connect is a requirement
what you can do is set the default collection in the RD Connection Broker server's registry.
To specify the default collection, please create the registry setting below in the broker's registry:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings
DefaultTsvUrl REG_SZ tsv://vmresource.1.<VDI pool ID>
To determine the correct value for DefaultTsvUrl please open RDWeb in a non-IE web browser and click on the icon for the collection you would like to be the default, then edit the downloaded rdp file with Notepad and copy the portion of the loadbalanceinfo
setting that is similar to the above.
An alternative would be to download the .rdp file from RD Web Access and double-click it to connect.
As I mentioned above it is generally intended to have users connect via RD Web Access or RemoteApp and Desktop Connections feed or Remote Resources (uses the feed) so that the client will obtain the proper .rdp file from the server.
To configure the FQDN that is published in the .rdp files you can use the cmdlet below:
Change published FQDN for Server 2012 or 2012 R2 RDS Deployment
http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80
Below is a sample configuration based on what you have written:
1. Published FQDN (using cmdlet above): rdsfarm.domain.com --> points to ip address of RDCB server. When launching a RemoteApp or Full Desktop connection from RD Web Access, the prompt window will show this FQDN next to Remote computer.
2. Gateway FQDN: gateway.domain.com --> externally points to public ip address of your RD Gateway server. TCP port 443 and UDP port 3391 need to be forwarded to the RDG's internal ip address. When launching a RemoteApp or Full Desktop
connection from RD Web Access, the prompt window will show this FQDN next to Gateway server. This FQDN is set in Server Manager -- RDS -- Overview -- Deployment Properties -- RD Gateway tab.
In RD Gateway Manager -- Properties of RD RAP -- Network Resources tab you should select Allow user to connect to any network resource or define a RD Gateway-managed group that has all of the FQDNs that the user will need to connect to.
3. RD Web Access FQDN: remote.domain.com --> internally points to the ip address of your RDWeb server, externally points to the public ip address of your RDWeb server. This is the name you give users if they want to use RD Web, for example,
https://remote.domain.com/rdweb
If you want users to manually connect using Remote Desktop Client as well as use RDWeb it will be a bit confusing to them since they will need to use one FQDN when manually using the client and a different FQDN when using RDWeb. You could fix this
by having them only use one method or run RDWeb directly on the RDCB server, that way users would only need to know a single FQDN for both RDWeb and manual connections.
4. You should have a wildcard certificate with subject of *.domain.com set for all RDS purposes in Deployment Properties.
Thanks.
-TP

Server 2012R2- RDS Farm Certificate Miss-Match on Session Hosts

Hi Guys,
I've another RDS2012R2 issue. Internal and external domains do not match. External: domain.com.au; Internal: domain.com.net.
I'm getting certificate miss-match errors when connecting to the Farm/RemoteApps.
I have performed the follow fixes:
Change published FQDN for Server 2012 or 2012 R2 RDS Deployment (http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80). This resolved the original issue where I was getting a certificate miss-match error externally
for the FQDN of the server.
Updated the RDP-Tcp certificate used on the Session Host Servers. This was to resolve an issue where using mstsc to RDP to the farm externally(via gateway) would give a Certificate is not trusted error on the RDSH side.
Now whenever RDWeb is used to launch a RemoteApp or the farm, I get a certificate miss match error as the RDSH server is called RDS1-TCC.domain.com.net and the certificate is for remote.domain.com.au.
I rolled back the last change so that RemoteApps and the Farm would work successfully internally without certificate issues. How do I go about resolving the certificate errors?
For extra background details see my orignal thread, It was marked as answered when only 1 out of 2 issues was resolved. http://social.technet.microsoft.com/Forums/windowsserver/en-US/b664ddaf-6c11-49e2-8a69-0df3b8ef13a1/server-2012r2-rds-farm-with-xp-and-windows-vista-clients?forum=winserverTS
Cheers,
Ben

Hi Ben,
Thank you for posting in Windows Server Forum.
In your case, I can suggest you to check that the certificate must match the FQDN of the server. If you are creating SSL certificate then it must be signed by trusted authority and also the certificate must be stored under “local computer/personal store“.
Also you can buy the certificate from 3rd party which is wild card certificate and only 1 certificate can be used for your network. Please check below links for more information regarding certificate issue.
1. Certificate Requirements for Windows 2008 R2 and Windows 2012 Remote Desktop Services
2. Configuring RDS 2012 Certificates and SSO
3. Windows 2012 RDS Certificate mismatch
Hope it helps!
Thanks,
Dharmesh

Count number of Session Hosts active in RD Connection Broker farm.

Hello,
Is there a way to count how many session hosts are active (not drained) in RD Connection broker farm at a given point of time.
Thank you,
Kashif

Hi,
What operating system version is this?
If Server 2012/2012 R2 you could use Get-RDSessionHost cmdlet:
Get-RDSessionHost
http://technet.microsoft.com/en-us/library/jj215469.aspx
-TP

RDS 2012 External access for Session Hosts over different port to default 443

Hello there
I am having problems solving this problem as you may see on other posts, so I am going to try again.
I have two Server 2012 machines for RDS. Server 1 one with all roles (Gateway, Broker, Session host etc.) and second machine, Server 2 as a session host only. I am running RDWeb Apps, with CA certificate installed and
everything works fine internally.
Due to limitations on the router I had to change the default SSL port on the gateway (Server 1) to 4043. I have this and 3391 for UDP open to Server 1 from the router.
Working externally, I can login to the RDS site and open apps form Server 1, but when I try to open an app installed on Server 2, I get a certificate error. The error is:
“Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address
and the certificate subject name do not match. Contact your network administrator for assistance".
The certificate address the error points to is referring to is an SBS 2011 cert for RWW and email. Experimenting, if I use 443 on the Server 1
gateway instead of 4043 and change the router accordingly, it then works. I can open apps form both session hosts externally . But not if is set to 4043.
For the record Server 2 session host also gives this error:
Event ID: 1280 Warning Microsoft Windows TerminalServcies-session broker client
Remote Desktop Services failed to join the Connection Broker on server sever-vm1.local.
Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.
Because everything works fine using default 443, I figure this is a communication or firewall issue between the gateway and the session host on Server 2.
Can anyone help here?
Many Thanks
MIS5000

Hi,
Thanks for your comment.
Have you check the connection on your second server?
Can you ping the server 2 from server 1?
As from the event ID 1280 it seems there is some network connectivity to RDCB server. Also please “Add the RD Session Host server to the Session Broker Computers group” & RDWeb server's computer account needs to be a member of the local TS Web Access Computers
group on your RDSH server. You can get the detailed information from this article.
In addition, do you have certificate purchased and install from trusted root authority. There is some requirement to use certificate for RDS environment, please consider following points.
1. The certificate is installed into computer’s “Personal” certificate store.
2. The certificate has a corresponding private key.
3. The "Enhanced Key Usage" extension has a value of either "Server Authentication" or "Remote Desktop Authentication" (1.3.6.1.4.1.311.54.1.2). Certificates with no "Enhanced Key Usage" extension can be used as well.
You can get more details regarding certificatehere.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Event ID: 1280 Server 2012 RDS - web app fail on second session host

Hello there
Topography
SBS 2011 (domain controller)
Two VM’s:
VM1 – All RDS rolls: RD Gateway , Connection broker, Licensing and RD access installed and acting as a session host with an active collection for RD web apps. A CA trusted certificate is installed.
VM2 – Session host with a second collection for RD web apps
Problem
I have a single app installed on both session hosts (the apps require their own servers). Both appear on the RDWeb site available for use. I can run the app hosted on VM1 no problem, but when I try to open the second app hosted on VM2 I get
two issues:
An error is returned
“Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address and the certificate subject name do not match. Contact your network administrator for assistance".
When viewing the certificate, it actually shows the CA cert installed on the
SBS server for RWW, not the cert on VM1. This has me puzzled
Secondly on VM 2, I get
Event ID: 1280 Warning Microsoft Windows TerminalServcies-session broker client
Remote Desktop Services failed to join the Connection Broker on server sever-vm1.local.
Error: Current async message was dropped by async dispatcher, because there is a new message which will override the current one.
When I run the app internally it seems to load but then disappears.
Some further config info if it is relevant:
I have port 4043 (443 used) as the only port directed to the gateway
Am I missing something simple? DNS? Port forwarding issue on the router? Its my first deployment of this nature with RDS 2012
Regards
MIS5000

Hi,
Thank you for posting in Windows Server Forum.
Firstly please check the RDP version you are using. I suggest you to update to RDP 8.1 for better feature and functionality. Now other thing verify that you have the RD Gateway certificate name matches the external FQDN of the RD Gateway Server. Also please
check that certificate is added under local computer\personal store and must be signed by trusted root authority.
Please check below article for more detail.
TS Gateway Certificates Part III: Connection Time Issues related to TS Gateway Certificates
http://blogs.msdn.com/b/rds/archive/2008/12/18/ts-gateway-certificates-part-iii-connection-time-issues-related-to-ts-gateway-certificates.aspx
In regards to resolve other issue (Event ID 1280), identify and fix any connectivity problems between the RD Session Host server and the RD Connection Broker by doing the following:
• Check network connectivity to the RD Connection Broker.
• Start the Remote Desktop Connection Broker service.
• Add the RD Session Host server to the Session Broker Computers group.
More information.
Event ID 1280 — RD Connection Broker Communication
http://technet.microsoft.com/en-us/library/ee890889(v=ws.10).aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Windows 2012 RDS - Session Host servers High Availability

Hello Windows/Terminal server Champs,
I am new middle of implementing RDS environment for one of my customer, Hope you could help me out.
My customer has asked for HA for RDS session host where applications are published, and i have prepared below plan for server point of view.
2 Session Host server, 1 webaccess, 1 License/connection
Broker & 1 Gateway (DMZ).
In first Phase, we are planning to target internal user
who connect to Session host HA where these 2 servers will have application installed and internal user will use RDP to access these application.
In second Phase we will be dealing with external Party who connect from external network where we are planning to integrate with NetIQ => gateway
=> Webaccess/Session host
I have successfully installed and configured 2 Session
Host, 1 license/Broker. 1 webAccess & 1 Gateway. But my main concern to have session Host High Available as it is hosting the application and most of the internal user going to use it. to configure it i am following http://technet.microsoft.com/en-us/library/cc753891.aspx
However most of the Architecture is change in RDS 2012. can you please help me out to setup the Session Host HA.
Note: we can have only 1 Connection broker /Licensing server , 1 webacess server & 1 Gateway server, we cannot increase more server due to cost
factor.
thanks in advance.

Yes, absolutely no problem in just using one connection broker in your environment as long as your customer understands the SPOF.
the session hosts however aren't really what you would class HA - but to set them up so youhave reduancy you would use either Windows NLB, an external NLB device or windows dns round robin. My preferred option when using the connection broker is DNS round
robin - where you give each server in the farm the same farm name dns entry - the connection broker then decides which server to allocate the session too.
You must ensure your session host servers are identical in terms of software though - same software installed in the same paths on all the session host servers.
if you use the 2012 deployment wizard through server manager roles the majority of the config is done for you.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
My Blog
LinkedIn:

Using Windows Server 2012 per-User RDS CAL on Server 2008 R2 Session Host

I have a Remote Desktop Licensing Server setup on my domain controller running Windows Server 2012 R2. I have installed a
’Windows Server 2012 Remote Desktop Services per-User CAL’ there and activated the licensing server already.
Currently I use ONLY Windows Server 2008 R2 machines as RDS Session Hosts (in the future I plan to transition them to 2012 R2, hence the CAL I bought is
already in the newest version).
I have already configured my WS 2008 RDS Session Hosts: set
Per-User licensing mode and specified license server address. The connectivity between my Session Host(s) and my License Server seems to be ok as the
Remote Desktop Session Host Configuration window on the Session Host correctly lists the 2012 per-user
license (CAL installed on server) from the license server.
On the License Server I can also see event logs entries (in
Microsoft-Windows-TerminalServices-Licensing/Admin), indicating that the user has been issued a license.
The issue I am having is that the license being issued is
2008 Per User CAL license (Build-in OverUsed - temporary) and not the 2012 Per User CAL license which is the only license installed on the server. According to the RDS CAL interoperability matrix at
social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx, I was expecting the 2012 license to be backward-compatible with 2008 client (and that
in the absence of legacy licenses, the (only) 2012 license would be used for all clients connecting to the licensing server)
Before I bought my license, I found this document:
download.microsoft.com/download/3/D/4/3D42BDC2-6725-4B29-B75A-A5B04179958B/WindowsServerRDS_VLBrief.pdf
which says that - "newer version RDS CALs can be used with an older version of the server software" (In section FAQ, Q4), which means to me that
the 2012 license would work as-is for the 2008 Server and gives me flexibility when upgrading to the new server version.
How can I make this CAL work in my environment?
Note:
I have already explicitly disabled
Prevent license upgrade Group Policy setting which I assumed would fix the issue but nothing has changed.
Then I have enabled License server security group Group Polity setting
and added computers from my domain to RDS Endpoint Servers AD group. I have also created new AD group called
Terminal Server Computers and added the computer accounts there, but it changes
nothing. Reference - technet.microsoft.com/en-us/library/ee791761.aspx , technet.microsoft.com/en-us/library/cc725704.aspx and blogs.msdn.com/b/rds/archive/2009/09/17/control-the-issuance-of-rds-cals.aspx.
I found one potential ‘workaround’ which involved manually downgrading my CAL license by calling
Microsoft Clearinghouse. I am very reluctant do to so because, as I upgrade parts of my infrastructure to Server 2012, I’d need to then ask Microsoft to manually upgrade a part of my license back as well.
Am I missing something? What should I do to get my 2012 CAL to be issued to 2008 R2 server

Hi, I have tried several other possibilities.
I change expire date for my temporary assigned license (2008 CAL overused). It can be done, by changing Active Directory user properties – msTSExpireDate. When I restart my Session Host server and logged again, my license was renewed
for next 60 days (event ID - 4145).
I also delete information about license for this user (clear msTSExpireDate and msTSLicenseVersion). And the license was successfully removed from License Manager. After another SH restart it gets the same – 2008 overused – license
(event ID 4143 - license server has successfully issued …)
I now, that changing info in AD attributes is a little trick, and this is not a real value - only a reference, but it was useful to delete or change expiration date of license. But it didn’t change type of license as I expected.
Reference -
http://discussions.citrix.com/topic/243320-windows-2008-licensing-questions/
To TP:
I have found your post with information:
If you have a Server 2012 RD Licensing server you may install your 2012 RDS CALs on it (no downgrade necessary) and then set your Server 2008 R2 RDSH to
use the 2012 RDL server. The 2012 RD Licensing server will automatically issue the CALs as 2008. -
https://social.technet.microsoft.com/Forums/windowsserver/en-US/6046ded1-96bf-4d79-89ce-38aac2a6694e/can-we-use-windows-server-2012-rds-cal-license-in-rds-2008-r2-server?forum=winserverTS
And it showing my situation in brief. I also found
similar problems, but the solutions don’t meet my expectations.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/dcfb1966-89a8-4b5d-bf5a-ff03ac0b7a66/rds-cal-licenses-not-recognized?forum=winserverTS
– “sudden all of the CALS were available”
https://social.technet.microsoft.com/Forums/windowsserver/en-US/f1228599-8452-4a3e-a263-061de14bfcfe/server-2012-rds-builtin-overused-cals-issue?forum=winserverTS
– “this should go away after a while”
Is there a way to determine this time you mentioned before? Or should I just wait patiently…

Load Balancing 2012 R2 Session Host Collection with External Network Load Balancer

Hi,
We are moving from a 2008 R2 Remote Desktop session host deployment to 2012 R2. Previously, we used our Kemp hardware load balancer to distribute load between RDSH servers. We had a connection broker deployed so that if an existing disconnected session was
detected during the initial connection, the user was directed back to that session.
In 2012 R2, we planned to again used the Kemp load balancer to main high availability for our RDSH collection, but are experiencing strange issues. It seems that the RD Connection Broker is also performing load balancing--the result being that initial connections
to the RDSH collection may go to one RDSH server with the least connections through the Kemp, but then be redirected to a different RDSH server by the broker, even when there is no existing session for the user on that second server.
Our question is: Should we not be using the Kemp balancer at all (how would this work)? Or should we disable load balancing by the connection broker (if so...how)?
Further complicating our redirection issue with that the RDSH servers have multiple interfaces--one with public addresses and others with private. The connection broker seems to abritrarily pick among the destination RDSH server's available IP addresses
for the redirection and trying to redirect to a private address will fail. We think we have worked around this by connecting to each RDSH server from a 2008 R2 server's RDSH Configuration console and choosing just the public adapter under the Network Adapters
tab--is there no way to access this setting in 2012 R2?
Thanks in advance!
Matthew

Hi Matthew,
As you are most likely already aware, inn Remote Desktop Services 2012 / R2 the Connection broker uses round robin DNS to load balance.
To simplify things I would recommend that you let the connection broker load balance the sessions and use the KEMP to Load balance the RDweb and Gateway servers.
Have a look at the following articles:
http://ryanmangansitblog.wordpress.com/2013/03/11/create-a-rdwa-farm-using-a-kemp-load-balancer/
http://ryanmangansitblog.wordpress.com/2013/03/31/rds-2012-configuring-a-rd-gateway-farm/
http://ryanmangansitblog.wordpress.com/2013/09/05/load-balance-rds2012-rdwa-and-rdgw-using-sub-interfaces-on-kemps-loadmaster/
As you have mentioned that you are migrating from a 2008R2 configuration, have a look at the following article:
http://ryanmangansitblog.wordpress.com/2014/01/05/publish-rds-2008r2-desktop-on-rds-2012/
Ryan Mangan | [email protected] | Help keep the forums tidy, if this has helped please mark it as an answer

RD Session Host lock down best practice document

Hello,
I am currently working on deploying an RDS Farm. My farm has several RD Session host servers. Today I learned that you can do some bad things to the RD Session hosts, if a user presses
CTRL + Alt + End when having a open session. I locked all of this down using different GPOs which include disabled access task manager, cmd, locking the server, reboot and shutdown etc.
However, this being sad how would I know what else to lock down since I am new to this topic. I tried to find some Microsoft document about best practices what should be locked down but I wasn’t
successful and unfortunately a search in the forum did not bring up anything else.
With all the different features and option Windows Server 2008 R2 has I do not even know where to start.
Can some please point me into the right direction.
Thank you
Marcus

Hi,
The RD Session host lock down best practices of each business is different, every enterprise admin can only to find the most suitable for their own solutions based on their IT infrastructure.
I collected some resource info for you.
Remote Desktop Services: Frequently Asked Questions
http://www.microsoft.com/windowsserver2008/en/us/rds-faq.aspx
Best Practices Analyzer for Remote Desktop Services
http://technet.microsoft.com/en-us/library/dd391873(WS.10).aspx
Remote Desktop Session Host Capacity Planning for 2008 R2
http://www.microsoft.com/downloads/details.aspx?FamilyID=CA837962-4128-4680-B1C0-AD0985939063&displaylang=en
RDS Hardware Sizing and Capacity Planning Guidance.
http://blogs.technet.com/iftekhar/archive/2010/02/10/rds-hardware-sizing-and-capacity-planning-guidance.aspx
Technical Overview of Windows Server® 2008 R2 Remote Desktop Services
http://download.microsoft.com/download/5/B/D/5BD5C253-4259-428B-A3E4-1F9C3D803074/TDM%20RDS%20Whitepaper_RC.docx
Remote Desktop Load Simulation Tools
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=c3f5f040-ab7b-4ec6-9ed3-1698105510ad
Hope this helps.
Technology changes life……

Configure which IP Win2012 R2 RD Session Host listens on

I have Windows 2012 R2 RD Session Host servers that are multihomed. One of the NICs is connected to an isolated management network. The management IP is NOT in DNS at all. However the RD Connection broker attempts to redirect sessions to
the management IP address of the session hosts - which is not available to users. This results in the connection failing. I found event log entries that showed that the broker is sending session requests to the management IP's of the hosts.
If I disable the management NIC then everything works just fine.
My question is: How can I either configure the Session Hosts to only listen for RDP connections on a specific IP/NIC, OR how can I accomplish this in the Connection broker by specifying an IP for each session host server that it will be redirecting to?

Hi,
You can use WMI to set the redirection ip, however, I have not tested to see if Server 2012 R2 will honor what you set. I do not have the WMI command handy so it would be faster if you change the registry or use RD Session Host Configuration from
Server 2008 R2. As a test please make the following change to one of the RDSH server's registry:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\ClusterSettings
SessionDirectoryRedirectionIps REG_MULTI_SZ 192.168.1.100
Replace the ip address above with the ip address that should be used for redirection for that RDSH server. After making the registry change please restart the server and then test to see if only the correct ip address is used.
As an alternative to the above you may use RD Session Host Configuration (tsconfig.msc) from a Server 2008 R2 box and connect over to the Server 2012 R2 RDSH. Before connecting the 2012 R2 RDSH should already be a member of a collection. Once
connected, double-click on Member of farm in RD Connection Broker and then select the ip address at the bottom. Since tsconfig is using WMI to make the change there is no need to restart the RDSH in order for the change to take effect.
If the test is successful then you would make a similar change to all of the RDSH servers.
Thanks.
-TP

Add Company Logo onto Desktop Background - RD Session Host 2012 R2

Hi, i'm hoping someone can help
I'm wondering if it's possible to put a company logo onto the desktop background on an RD Session Host, is there a way to do that? I remember seeing a 2008 R2 host on a Citrix farm with one. At the moment it's just a black screen so would be good to put
a white logo on there
Any help appreciated
Thanks!

Check these articles,
http://technet.microsoft.com/en-us/library/ee791905(v=ws.10).aspx
http://www.webapper.com/blog/index.php/2007/10/18/enabling-desktop-wallpaper-on-remote-desktop-terminal-services/

Unable to install new RDS Session Hosts 2012R2

We currently have an 2012R2 RDS environment running 8 farms across 12 session hosts from one connection broker. Recently I went to provision 2 new Session Hosts (one to a new farm and one to an existing) however they both fail with the following error in
the Server Manager Wizard:
Access is denied
The term 'Get-LocalMachineFqdn' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
I've also tried installing from PowerShell without success.
Has anyone come across this before? I haven't been able to find anything in my searches on the web let alone find anything of use in the event viewer.
Cheers,
Ryan.

When attempting to view the certificates via PowerShell I receive the following error, despite having the correct permissions:
PS C:\WINDOWS\system32> Get-RDCertificate -ConnectionBroker pv-rdcb02.ksgroup.com.au
New-PSSession : Access is denied
At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\Certificate.psm1:34 char:19
+     $M3PSession = New-PSSession -ConfigurationName Microsoft.Windows.ServerManag ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], RemoteExc
   eption
    + FullyQualifiedErrorId : PSSessionOpenFailed
Invoke-Command : Cannot validate argument on parameter 'Session'. The argument is null or empty. Provide an argument
that is not null or empty, and then try the command again.
At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\Certificate.psm1:36 char:40
+     $RDCerts = Invoke-Command -Session $M3PSession -ArgumentList @($optionalPara ...
+                                        ~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Invoke-Command], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.InvokeCommandCommand
New-Object : Cannot convert argument "6", with value: "", for "Certificate" to type
"Microsoft.RemoteDesktopServices.Common.CertificateRole": "Cannot convert null to type
"Microsoft.RemoteDesktopServices.Common.CertificateRole" due to enumeration values that are not valid. Specify one of
the following enumeration values and try again. The possible enumeration values are "None, RDGateway, RDWebAccess,
RDRedirector, RDPublishing"."
At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\Certificate.psm1:96 char:9
+         New-Object Microsoft.RemoteDesktopServices.Management.Certificate `
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [New-Object], MethodException
    + FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand
Does anyone have any thoughts?
Cheers,
Ryan.

RemoteApp and Session Host on same servers?

I have been asked to architected a new deployment of our RDS server with Windows 2012. I have identified that we are standing up a Gateway, Web access, RemoteApp and session host. VDI is a pain point for us so that will not be in this implementation.
My question is right now we have several RDS servers some performing the role of Session host and some as dedicate RemoteAppp servers. I am being told that the recommended way is to create one farm and have all the servers setup to support both
roles. Is this the best way to provide these services? Are there any gotchas with this approach?

Hello one and all : Fixed. You can. Im not a Microsoft Agent or other, Im often called an IT Fireman.
Anyhow, I Googled a lot and found how to "fix" this issue. This article...
http://support.microsoft.com/kb/2833839
...describes the process.
But in short:
1) You must make this a basic domain server, all be it self contained.
2) Use a bit of PowerShell to make the same server recognise the local
Remote Desktop Licensing server.
3) Reboot a few times and use the Install Rolles and Features to do the Quick RDS install. Let it choose all the options. It was at this point that I stopped writing down what I was doing, but I simply followed the error messages and recommended solutions.
Eventually, everything works. I have my 2008R2 looking RemoteApp and Remote Desktops on my wizzy new server with better WAN compression.
QED.
But I have to say, I needed no Googling nor two days to get this working on Server 2008, and no need for Linux style command line interface options either. Comme on guys... Even if someone makes a "PowerToy" to do all this... can someone please make it easier,
not harder ? I hate to think whats next... compile your own PowerShell before you can use it (and maybe write it in VI before you can compile it ... ?)
But its now working... so the little companies I help will be happy again.
Cymon

Renaming computers in Win2012R2 Session Host Farm

Similar Messages

Maybe you are looking for