ryank85
asked on
Remote Desktop Services
Hi
We have a client that has purchased a Windows Server 2012 Standard Machine. They need to be able to access sage remotely for two users.
We have purchased the relevant CALS etc but need to know a little more info on the Setup.
The machine is a domain controller with sage installed.
When we go into the Roles and Features > Click Next > do we install the role via 'role-based or feature based installation' or 'remote desktop services installation' I have researched on the internet and everyone is different.
As a test I installed this from the first option, role based.
I have added the 2 user CALS to the RDS Licensing manager ok - when they both login to the server now it's not showing then as connected through the remote access dashboard, is that right?
However when you go into task manager and select the users tab they appear in here.
I do notice when I open the Server Manager Dashboard and click Remote Desktop Services from the left hand pane I get the message 'there are no RD connection broker servers in the server pool. To manage a deployment, you must add all the servers in the deployment from the server pool?
I am confused?
thanks
R
We have a client that has purchased a Windows Server 2012 Standard Machine. They need to be able to access sage remotely for two users.
We have purchased the relevant CALS etc but need to know a little more info on the Setup.
The machine is a domain controller with sage installed.
When we go into the Roles and Features > Click Next > do we install the role via 'role-based or feature based installation' or 'remote desktop services installation' I have researched on the internet and everyone is different.
As a test I installed this from the first option, role based.
I have added the 2 user CALS to the RDS Licensing manager ok - when they both login to the server now it's not showing then as connected through the remote access dashboard, is that right?
However when you go into task manager and select the users tab they appear in here.
I do notice when I open the Server Manager Dashboard and click Remote Desktop Services from the left hand pane I get the message 'there are no RD connection broker servers in the server pool. To manage a deployment, you must add all the servers in the deployment from the server pool?
I am confused?
thanks
R
ASKER
Thanks for this. Makes sense.
I'm guessing that even though I have installed RDS from the role based option it doesn't matter.
It's just a case of me going through the Remote Desktop services option and following the screenshots in the list?
Thanks
R
I'm guessing that even though I have installed RDS from the role based option it doesn't matter.
It's just a case of me going through the Remote Desktop services option and following the screenshots in the list?
Thanks
R
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok we only have one server and this is running as a domain controller.
Why can't you install these roles on a DC?
Why can't you install these roles on a DC?
At first - it is a bad practice as now by purchasing Windows Server 2012 Standard you get license for 2 VMs
You can find the answer here in the common topic:
https://www.experts-exchange.com/questions/28441188/Configuring-RDS-on-a-Windows-Server-2012-R2-DC.html
You can find the answer here in the common topic:
https://www.experts-exchange.com/questions/28441188/Configuring-RDS-on-a-Windows-Server-2012-R2-DC.html
ASKER
This is the guide I went through a while ago and the install and configuration worked ok
http://www.wackytechtips.com/installing-and-configuring-remote-desktop-services-rds-on-windows-server-2012/
http://www.wackytechtips.com/installing-and-configuring-remote-desktop-services-rds-on-windows-server-2012/
Before we go any further, can you please confirm whether you are running Windows Server 2012 or Windows Server 2012 R2?
- One (physical) to act as your Hyper-V host machine (you can't install any other role on the host, not even backup software as you'll violate the agreement which lets you fire up the two 2012 VMs)
- One (virtual) you can use for your DC and files
- One (virtual) you can use for RDS
With that being said, if you want to stick with using a single 2012 server and want to deploy RDS on this server then Microsoft have a knowledge base article you can follow to set it all up: http://support.microsoft.com/kb/2833839
Why can't you install these roles on a DC?You can install RDS on a Domain Controller, it's just not generally recommended seeing as a Server 2012 Standard license allows you to run two more virtual instances of Server 2012. This gives you three Windows Server 2012 servers in total:
- One (physical) to act as your Hyper-V host machine (you can't install any other role on the host, not even backup software as you'll violate the agreement which lets you fire up the two 2012 VMs)
- One (virtual) you can use for your DC and files
- One (virtual) you can use for RDS
With that being said, if you want to stick with using a single 2012 server and want to deploy RDS on this server then Microsoft have a knowledge base article you can follow to set it all up: http://support.microsoft.com/kb/2833839
ASKER
ok as a test I am going to us Disk2Vhd to create an image of the current server to have a play around with it virtually.
I will report back.
With regards to the 2 VMs you can create on the Server Standard, when you create the 2 VMs can they see each other?
i.e if I had Sage data installed on the main physical server can the other two VMs browse to that network share?
Sorry I am new to all this Visualization.
thanks
R
I will report back.
With regards to the 2 VMs you can create on the Server Standard, when you create the 2 VMs can they see each other?
i.e if I had Sage data installed on the main physical server can the other two VMs browse to that network share?
Sorry I am new to all this Visualization.
thanks
R
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It sounds like all you have done so far is install the RD Licensing role, which does not make your 2012 server a RD Session Host. You will need to use the Remote Desktop Services Installation wizard (which you mentioned originally) in order to actually set up your server for RDS. This will allow your users to log into the server to run Sage. At the moment they're using up the two active RDP sessions which are really only meant to be used for administrative purposes.
Have a read of these articles which should get you pointed in the right direction:
http://blogs.technet.com/b/yungchou/archive/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style.aspx
http://ryanmangansitblog.com/2013/03/11/deploying-rds-2012-single-server-session-based-deployment/