RDS roles

Currently 2012 R2 RDS server carry :Connection Broker, Web Access (for Remote App only) and RDSH.
Planning to add RDSHs. One right now and couple of more in the future.
I prepare to activate Licensing. Dedicated Server 2012 VM is ready.
Load Balancing will be enabled for RDSHs.
Questions:
1. would Load Balancing in RDS 2012 allow kind of high availability. Let say on host goes down (for maintenance).
Or it should be achieved in other way?
2. Would it be normal approach to run Broker and licensing services on a dedicated server. If the answer is YES I have to move my Connection Broker Role to the dedicated Server where Licensing will be enabled. Is it difficult :) ?. How to do that?
3. And now the logic pushes me to ask about RD Web Access roles that is deployed on the single server now.
I feel that the right way to keep RDSHs clean. Would it be right to keep one Server for 3 roles: RD Connection Broker, RD Web and Licensing services.
There are no GATEWAY involved and no plans for it. Each server in RDS deployment running in Powerful VMs and is backed up with easy way for about instant recovery. During the year the farm will grow to max 300 REMOTE APP connections.
Does my Roles placement planning make sense?
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Hi,
Thank you for posting in Windows Server Forum.
In regards to your farm deployment, I would like to say some points. As per my knowledge, Load balancing will reach your goal as HA and can get the same app when your host is down. Also seems that always it good for farm to have RD Licensing server on separate
server than other RDS role (If you have availability of stock (Hardware server or VM’s Server).
You can keep RDCB and RDSH on single server but if possible transfer RDL server role on other server.
You can refer beneath article for RDL Server across AD\Workgroup.
http://support.microsoft.com/kb/2473823
Also you can go through following article for deployment of RDS Farm.
Step by Step Windows 2012 R2 Remote Desktop Services – Part 2
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Similar Messages

[Forum FAQ] "Unable to connect to the server by using Windows PowerShell Remoting" error while installing RDS roles on Server 2012 R2

When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
“Unable to connect to the server by using Windows PowerShell remoting”.
Figure 1: Unable to connect to the server by using Windows PowerShell remoting
First of all, we need to verify the configurations as it suggested:
1. The server must be available by using Windows PowerShell remotely.
2. The server must be joined to a domain.
3. The server must be running at least Windows Server 2012 R2.
4. The currently logged on user must be a member of the local Administrators group on the server.
5. Remote Desktop Services connections must be enabled by using Group Policy.
In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
Enable-PSRemoting -Force
Figure 2: Enable PowerShell Remoting
However, if issue persists, we need to check whether it has enough memory to work.
By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
the memory via the PowerShell command below:
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
Then, you need to restart the server and the issue should be resolved.
You can get more information regarding Remote Troubleshooting by below link:
about_Remote_Troubleshooting
If you need further assistance, welcome to post your questions in the
RDS forum.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

i found another possible reason, this solution worked for me:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
I tried to set up powershell remoting on a server and kept getting this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann
ot process the request. It cannot determine the content type of the HTTP response from the destination comput
er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to
pic.
After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very
many security groups or in my case because of the SidHistory attribute.
The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters
If the keys does not exists you can create them, be sure to use the DWORD type.
I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

Microsoft // Winlogon 4005 (The Windows logon process has unexpectedly terminated) on one Windows Server 2012 VM with working RDS roles installed

Hello experts,
I have deployed all essential RDS roles and features on one Windows Server 2012 Virtual Machine
a few months ago and I recently ran into issues with users not being able to access it through RDP all of a sudden after entering credentials successfully.
Every time that happens I get an event ID Winlogon 4005 (The Windows logon process has unexpectedly
terminated). I am also receiving but not all the time event ID 6000 and 6003 referring to being unable to handle critical or normal events from AUinstallAgent.
Any help on this problem would be greatly appreciated.
Thank you in advance for your support.
Massimiliano

Hello experts,
I have deployed all essential RDS roles and features on one Windows Server 2012 Virtual Machine
a few months ago and I recently ran into issues with users not being able to access it through RDP all of a sudden after entering credentials successfully.
Every time that happens I get an event ID Winlogon 4005 (The Windows logon process has unexpectedly
terminated). I am also receiving but not all the time event ID 6000 and 6003 referring to being unable to handle critical or normal events from AUinstallAgent.
Any help on this problem would be greatly appreciated.
Thank you in advance for your support.
Massimiliano

RDS role configuration

Hello,
I have a single server that is going to be used to download large video files by end users and then transferred over to their desktops. The department accessing the server will be logging in using a single account so they all have access to each others downloads,
etc..
I've installed Server 2012 R2 and want to add the RDS role to the server so that multiple users (more than 2) can RDP into it at one time. I can add the role easily enough and figure that session based deployment is what I should go for but there's licensing
and so much more to it that ends up really complicating it. I'm a little confused as to how to configure the RDS role to do what I need. By the way, I work in a company that is a MS partner and has multiple CAL licenses to use. What do I need to configure
after adding the role to make sure that several people can log into the machine? Thanks in advance for any assistance you give.

Hi Jedi,
Here are some guiding articles below regarding configure licensing for RDS on Windows Server 2012/2012R2.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
Test Lab Guide: Remote Desktop Licensing
https://technet.microsoft.com/en-us/library/jj134160.aspx
Managing RDS licensing using PowerShell on Windows Server 2012
http://social.technet.microsoft.com/wiki/contents/articles/13293.managing-rds-licensing-using-powershell-on-windows-server-2012.aspx
In addition, after the RDS host server is configured, Microsoft provides a grace period during which clients are able to use terminal services without licenses.
Understand the licensing grace period
https://technet.microsoft.com/en-us/library/hh553157(v=ws.10).aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Issue with Server 2012 RDS roles

I have a Server 2012 system where the Remote Desktop Services roles were installed manually, not using Remote Desktop Services Installation. This was picked up because of the licensing errors which popup from time to time. From what I have read, it is not
possible to fix the licensing issues without installing the RDS roles correctly.
I have tried to uninstall the roles but Server Manager hangs with an empty progress bar and never completes the task.
I have run Remote Desktop Services installation, but it fails as the roles are already installed. The error message is "Failed to open the runspace pool. The Server Manager WinRM plug-in might be corrupted or missing."
I am reluctant to reload the operating system and start again, as various pieces of software have already been installed. Is there a way to successfully remove the RDS roles or successfully run the RDS installation wizard with the roles already installed?

Hi FissioPB, could you give us a reference about how to detect and remove the internet filter?
I´ve tried the following, but the same issue “Failed to open the runspace pool. The Server Manager
WinRM plug-in might be corrupted or missing" and "ERROR_WINHTTP_TIMEOUT" events.
netsh http add iplisten 127.0.0.1
netsh http add iplisten ::1
"netsh winhttp show proxy"
netsh winhttp reset proxy
Block GPOs
Any advice could be helpful. Thanks!!
:S
H1R@M

Windows 2008 R2 Remote Desktop Service Role pickup 2012 RDS License Server.

I am installing Citrix onto a Windows 2008 R2 server as part of this I need to setup the RDS Role on the same box and then point it to the Windows RDS License server.
Our plan is to have a Windows 2012 License server for RDS Licenses i.e. install 2012 RDS Licenses.
I was wondering if it was possible for a 2008 R2 RDS role to pick up 2012 RDS Licneses from a Windows 2012 RDS Server?
Many thanks,
Steve

Hi Steve,
Thank you for posting in Windows Server Forum.
Yes, agree with TP’s comment. You can also check below interoperability matrix link for details.
RDS and TS CAL Interoperability Matrix
http://social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Remote Desktop Services Role on a Virtual Machine (VM) Requirements

Does MS recommend installing RDS Role on Hardware or Virtual Machine? I have a use case where I have about 35 people that will be using the Internet Explorer and possibly run additional piece of software. I'm having trouble determining if the RDS Role on
Virtual Machine will be able to sustain the load of so many users. Should the same performance metric used in hardware selection be appropriate to apply for Virtual Machines. We are using VMware on pretty powerful DELL hardware, which is also hosting
120 existing VMs as of now. So my questions is would VM with 4 CPU's, 8GB of RAM, 80 GB Virtual Disk and 1 GBPs NIC would be handle the job?

Hi,
Thank you for posting in Windows Server Forum.
There is no any particular requirement to run RDS on physical or virtual machine. But if you want to install RD Virtulization role then you need to see that Hyper- V role installed because “when the RD Virtualization Host role service is installed, Server
Manager checks to see if Hyper-V is installed. If Hyper-V is not installed, Server Manager will install it”. And Hyper-V role cannot be installed on virtual machine so for that you need to install on Physical machine. Other all RDS role can be installed
on virtual machine also.
Install the Remote Desktop Virtualization Host Role Service
In addition, please check below articles.
1. Remote Desktop Services: Server and client requirements
2. RDS Hardware Sizing and Capacity Planning Guidance.
Hope it helps!
Thanks,
Dharmesh

Office 2013 VL and app-v 5 SP2 on RDS server - package add fails with script error

We have used the MS Office Depolyment Tool for click-to-run to download the latest Office 365 version, and flatten it into an app-v 5 package - not a problem.
When we try to add the package to our client machine (Server 2008R2 running the app-v 5 SP2 client software), it fails with an message that a script has failed and not returned a 0 code. We have not added any scripting to this automatically created
package, so it seems that the app-v client does not like the "official" package. Any hints and tips gratefully accepted, thanks
App-v client has scripting enabled.
The powershell command line we are using is:
PS C:\windows\system32> Set-ExecutionPolicy Unrestricted
PS C:\windows\system32> Add-AppvClientPackage -path file://hostname/app-v/o365-noaccess/ProPlusVolume_en-us_zh-cn_x86.appv -DynamicDeploymentConfiguration \
\hostname\app-v\O365-NoAccess\ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml
with a result of:
Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than 0). Please ensure that Embedded
Script process can complete successfully and exits with 0.
Operation attempted: Configure AppV Package.
AppV Error Code: 100000000C.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ Add-AppvClientPackage -path
file://hostname/app-v/o365-noaccess/ProPlusVolum ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
    + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
and these are the error messages we see in the debug app-v client logs:
Script Launcher successfully waited for script with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=D24C3BDD-8FAD-44d3-998C-933F8F053682
PackageRoot="C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
PRIDName=ProPlusVolume'.
and...
Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {cd9725ce-4503-4932-863b-4fcda3f9551d} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D' with error 0x79100E10-0xC.
and...
machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe"'
exited with failure error code: The extended attributes are inconsistent.. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.
We believe this last error message is the kicker, but can't debug any further.

Just to validate the problem, I started again.
I have just downloaded the latest ODT from MS, and then downloaded the latest Office 2013 packaged - volume license. Then created the app-v package - all went perfectly, no error messages. Uploaded the package to the app-v 5 server and published
it. I have made NO changes to any of the files.
I have just built a brand new Windows Server 2008R2 Datacentre VM, patched it to the hilt, and installed the RDS role, powershell 3 and appv 5.0 SP2 client for RDS.
I then use powershell as above:
          scripting unrestricted
          app v client scripting enabled
         app v server added
          global and user update enabled
         add-appvclient package "url of office package.appv"
             and received exactly the same error message.
It is not complaining that scripting is not allowed, it is complaining that the script is invalid.
Help!!!!

Server 2012 R2 RDS- Only want the Session Host, Connection Broker and Licensing Server!

Hi all,
Wondering if anyone has experience with implementing Remote Desktop Services (RDS) on Windows Server 2012 R2.
I am doing an RDS design for a platform where we only need an RDS Session Host, Licensing Server and Connection Broker. We do not need web access as these servers will simply be jump boxes internally!
However, implementing this correctly in our test environment has proved to be tricky. The options are:
Use the Server Manager and do a traditional install via Roles and Features ( specifically add the Session Host, Licensing Server and Connection Broker). The installation process seems to go through ok in this scenario but when I head over to the Remote
Desktop Services section of the Server Manager I simply get the message 'An RDS Deployment does not exist in the server pool. To create a deployment head to Roles and Features'.
Use the specific ‘Remote Desktop Services installation’ option on the Server Manager and do a Session Based Desktop deployment and Quick Start. This installation process seems to go through correctly and the Remote Desktop Section seems to be working
correctly via the Server Manager. However this process is ‘hard locked’ i.e. it installs the session host, web access and connection broker. I can then remove the web access component later from Roles/ Features.
Is there a best practice (if any) for installation? i.e. Will there be any issues down the line if I remove RDS Web Access from my server while following method 2?
There is a complete lack of documentation from Microsoft here so not sure what to do! Just need a basic RDS session based deployment.

Hi,
As I know from server 2012\R2 the best deployment skill is to perform via “Remote Desktop Services” installation mode with Standard deployment and don’t let single role to install. Because when we install through RDS mode, there are specific extra tools and
services activated along with that deployment which you can’t find with single role installation. And that is for sure, when we install RDS role as of this, by default we will get install RDCB, RDSH and RDWA role installed.
Sorry don’t have any option to try to remove that role as that role basically needed for RemoteApp and Desktop purpose. But if you want then you can try it with help of “Remove-RDServer”Powershell command.
https://technet.microsoft.com/en-us/library/jj215506.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Moving user profiles from Server 2012 with RDS services to User profile disks Server 2012R2

Hello i have a question about moving my C:\users profiles.
My current settings on the servers are:
AD-Server 2012
SQL-Server 2012
TS- server with RDS roles (RDwebacces, RDs broker, RD session host) 2012
everything about user profiles is now in C:\Users
My new settings for the server will be:
AD-ActiveDirectory - server
SQL-Server
TS1- RDS (RDwebacces, broker, RDS server group management) 2012R2 (I have enabeld userProfileDisks to Filesistem server)
TS2- RDS(Session host) load balance 2012R2
TS3- RDS (Session host) load balance 2012
FileSistem - server ( here i will have on E: partition the new functionality UserProfileDisks) 2012R2
So is there a way to move profiles from TS - C:\Users to FileSistem - E:\UserProfileDisks
I am new to this so any idea wil be helpful.

Hi,
If the UPD is configured on the server which holds existing user profiles, just select the option:
store all user settings and data inside the profile disk.
Since you are moving user profiles between different servers, then user profile contents need to be migrated manually.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

New to RDS - What do I need to set up for 3 users on 2008R2?

I need to set up an existing 2008R2 server with the RDS role so that 3 users can remote into the server and use Office applications. I've been on the phone with MSFT for 45 minutes and I think I get it, but I wanted to get a second opinion, and possible
rant....
As I understand it, I need 3 licenses for Office 2013 ProPlus in this situation.
I install Office 2013 on the server with the RDS role using the Office installer.
I register/license each User account
that will be logging in to the server (3 of them) as legitimate to use the Office 2013 installed on the server.
I do not *need* to install Office 2013 on the workstations of the three User's, but I may and not run afoul of the licensing terms.
Assuming all of that is true (and I doubt it is), I have the following questions:
Do I have to use 'volume licensing' for this, or can I just buy 3 retail copies of ProPlus?
Do I *have* to use ProPlus? I do need Outlook.
Can I use Office 365 ProPlus, and is it cheaper (up front) than the one-time perpetual license? Small Business Premium (see previous Question)?
Does the server need it's own license, meaning I need 4? If not, is there a special way I need to install Office on the server so it doesn't ask for a license?
Could a non-registered user (like a server Admin) use the Office installed on the server?
How many licenses are built into RDS? I recall hearing 2, to be used for admin purposes. So I would need to buy 3 CAL for the three Users intended in this setup?
What other questions should I have asked?!
I can't believe it's so complicated. And expensive! A quick perusal suggest a single ProPlus license is about $500! I'm sure once I have had time to digest it things will be fine, but up front, this system is really a pain in the rear.
Anyway, thanks to those brave enough to attempt to untangle this for me!

For the O365-on-RDS aspect, bad news, it's not a valid installation scenario.
You would need a Volume License edition of Office2013 to install upon RDS, because O365 only offers the Click-to-Run installable, and that can't be installed upon RDS:
http://technet.microsoft.com/en-us/library/ee624360.aspx#Table
http://community.office365.com/en-us/forums/156/t/138757.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Question about model driven dev and RDS configuring

I am testing the model driven development that is brought up by Flash Builder4 and LCDS3 recently, and it went pretty well. However i've noticed that the configuration of the RDS for development mode is not recommanded for a production environment.
My first quetion is can I simply disable the RDS on the server when I want to deploy my app to a production environment and still be able to use all of the features such as data management service and remote service etc.? I've tried to do so but it gave me a 404 page. I felt it was a little bit confusing when you know you DO have a html template located in the right location. If RDS can be disabled without interfering the functionality of the app, where can I find a doc to follow?
My second question is if the RDS is a must, then how to configure the security setting? I knew some of the requirements by visiting this url:http://help.adobe.com/en_US/LiveCycleDataServicesES/3.1/Developing/WS6822bf3ec1c7b2e9-30fb 9b22126b9ca84aa-8000.html,
however, when I followed the steps and test it, I got a 400 error in FB4 RDS configuration page.
Since I am testing this under Tomcat 5.5, I am not sure where should I put the flex-tomcat-common.jar and flex-tomcat-server.jar file in, cause the dir structure of Tomcat 5.5 is a little bit different than that of Tomcat 6.0. Then I put these files under both of the tomcat 5.5\common\lib folder and the tomcat 5.5\server\lib folder. I've doubled checked the the catalina.properties file which is located under tomcat5.5\conf folder and I see the following environment param has been there : ${catalina.home}/common/lib/*.jar.
The other configuration I made that differs from the doc was: I put <valve classname="flex.messaging.security.TomcatValve"></valve> into the context.xml, which is under the folder Tomcat 5.5/conf. Since I put the Resource definition in the same file, I guess this should not be the problem.
Does anyone has any successful experience on setting this up?
Any hint will be appreciated.

Thanks for the quick reply.
I solved my first problem, it was because I accidentally commented out part of the RDS configuration and left the servlet-mapping part un-commented. After I generate all the client and server codes and re-deploy them to the environment, I finally got my running demo with RDS disabled.
For the second problem, I am still stucking in. I've tried to switch to the Tomcat 6.0 and follow both of the LCDS installation doc and the LCDS3.1_using doc. None could work me out. I constantly get the error message said that "The RDS server was successfully contacted, but your security credentials were invalid". So after struggling a whole day, I found the following statement, which is appeared in the ColdFusion configuraton doc:"Note: If you are using ColdFusion MX 7 or earlier, the message "The RDS server was successfully contacted, but your security credentials were invalid," appears. The message indicates that the password was not validated, even if it is correct. Click OK to close the message. ". That's interesting cause it seems it was exact the situation I was encountered. However, in my case, ignoring the error message does not give me a successful RDS connection.
For your information, I am pasting the configurations I had on my machine and maybe some ppl could give me a correction.
service-config.xml:
<security>
<login-command class="flex.messaging.security.TomcatLoginCommand" server="Tomcat"/>
        
        <security-constraint id="basic-read-access">
            <auth-method>Custom</auth-method>
            <roles>
                <role>guests</role>
                <role>accountants</role>
                <role>employees</role>
                <role>managers</role>
                <role>rds</role>
            </roles>
        </security-constraint>
    </security>
tomcat-user.xml:
<tomcat-users>
<role rolename="rds"/>
<user username="rdsuser" password="rdspassword" roles="rds"/>

</tomcat-users>
web.xml:
<servlet>
        <servlet-name>RDSDispatchServlet</servlet-name>
    <display-name>RDSDispatchServlet</display-name>
        <servlet-class>flex.rds.server.servlet.FrontEndServlet</servlet-class>
        <init-param>
      <param-name>useAppserverSecurity</param-name>
      <param-value>true</param-value>
    </init-param>
        <load-on-startup>10</load-on-startup>
    </servlet>
    <servlet-mapping id="RDS_DISPATCH_MAPPING">
        <servlet-name>RDSDispatchServlet</servlet-name>
        <url-pattern>/CFIDE/main/ide.cfm</url-pattern>
    </servlet-mapping>
lcds.xml:
<Valve className="flex.messaging.security.TomcatValve"/>
<Transaction factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60"/>
<Resource name="jdbc/codedata" auth="Container"
   type="javax.sql.DataSource"
   username="root"
   password="******"
   driverClassName="com.mysql.jdbc.Driver"
   url="jdbc:mysql://localhost:3306/codedata?autoReconnect=true"/>
   <Resource name="jdbc/atlantis" auth="Container"
   type="javax.sql.DataSource"
   username="root"
   password="******"
   driverClassName="com.mysql.jdbc.Driver"
   url="jdbc:mysql://localhost:3306/atlantis?autoReconnect=true"/>
Note that both of the flex-tomcat-common.jar and flex-tomcat-server.jar were already under Tomcat 6.0/lib folder.

RDS 2012 R2 Collection - Published Remoteapps not visible

Hello,
I have a strange issue with a RDS Deployment I´m setting up for a customer.
RDS Roles setup:
Server1: RD Licensing / RD Gateway
Server2: RD Connection Broker / RD Sessions Host / RD Web Access
I´m all done with the LOB Apps as well as adding ~30 users and migrated their profiles, I have set up UPD etc. All is working great and I´m almost ready to take it into production...apart from this annoying thing.
I have created a Session Collection and published some remoteapps.
However when I log in to the rdweb site it doesn´t show the published Remote Apps.I have tried to unpublish / republish, reboot and so on to no avail.
How can I troubleshoot and solve this?
Sure I could delete the session collection and create a new one, but what will happen with the created UPDs that has all the customized settings for the users (store all ?
Can those be redeployed to the new Session Collection ?
Also, I cannot be sure that this will even fix the issue.
Any advise are very welcome.
Thx /Tony

Hello Darmesh,
I did not assign any specific permissions, domain users is set. I ended up moving the RDGW role to the RDSH server though I know it´s not BPA. However this customer does not have more than one available Public IP. And as they wan´t to use both RDWeb and
RDP through RDGW that was the solution. Othern than that I had to fix 2 things in IIS on the RDSH.
1. Change the RDWebAccess Application Pool identity from ApplicationPoolIdentity to NetworkService
2. RDWeb/Pages-Applications
Settings, put in remote.company.com as value for "DefaultTSGateway
Volia it works. As a sidenote I also added the "reghack" ShowInPortal" value
1 so the full desktop connection is also available in the RDweb portal, not supported I know, but will keep it for now.
Any comments to this solution ?
Thx /Tony

RDS Farm

Is it safe/good practice to use hyper-v 2012 r2 for all the RDS roles on different VM's on different servers? For example, the gateway server would be a hyper-v guest, the session host a separate hyper-v guest on a different server and so on

Hi,
Yeah we can implement the scenario as you want for setting up all the required RDS role on Hyper-v VMs. But please be noted that if you want RDVH role then you must install on Host\Physical server. Apart other all RDS role can install on VM.
Thanks for your understanding and Support!
Regards.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

In-place upgrade of Windows Server 2012 RDS to R2 fails

Hi All
I have a Server 2012 Standard RDS virtual machine (vmware) on which I have tried doing an in-place upgrade to 2012 R2 but it constantly fails.
It sits at the "Collecting files, settings and applications" process for quite a while - always on 0% and then says: Installing Windows was Canceled "Setup can't continue. Restart the computer and restart Setup. When prompted, try getting
the latest updates."
I have tried combinations of all the settings during setup to look for updates, not look for updates, etc., rebooted several times, even disabled the RDS services and still the same result.
As a test, I tried doing an in-place upgrade on the base OS installation that was used to create this VM and it works perfectly. The only difference between the servers is that the live has RDS role installed.
Is there any Microsoft documentation on the 2012 RDS in-place upgrade process to R2?
Can anyone offer any suggestion as to why the in-place upgrade might be failing with the RDS role installed?
Thanks heaps

As I stated I have already tried an in-place upgrade on the base 2012 vm that I used to create the production RDP server and it worked.
It seems that the RDS role may be preventing the upgrade?
Ideally I want to go down the in-place upgrade on the production server as we have alot of users using this machine. I would rather not have to build an R2 RDS server from scratch.
if you really think the RDS is preventing the upgrade, how about stopping the RDS service then do an in place upgrade.
check how it goes.. :)
Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

RDS roles

Similar Messages

Maybe you are looking for