Install Remote Desktop Services Failed on Windows 2012 Server

Wednesday, August 22, 2012 6:43 PM

Moderator

Hi,

What RDS roles did you (intent) to install? And what method of installing did you choose? Role-based deployment or Scenario-based deployment?

Besides that, you mention
"In \Administrative Tools\Terminal Services, I only have RD Licensing Diagnoser and RD licensing manager."
That is correct, all RDS management (besides RD Licensing and RD Gateway) is done using the Server Manager Console.

Kind regards,
Freek Berson
The Microsoft Platform
Twitter
Linked-in
Wortell company website

Wednesday, August 22, 2012 7:29 PM

1

I intend to install session-based RDS (RemoteApp). I tried both Role-based deployment and Scenario-based deployment after AD is configured. The server is clearn installed on vmware.

In Scenario-based deployment (quick deployment), the wizard says "unable to install the role services" at Remote Desktop Services role services stage, then Session collection and RemoteApp programs are cancelled.

After this error happens, Server Manager itself has this error: Role and feature refresh failed with the following error: The request to list features available on the specified server failed. The operation cannot be completed, because the server that you specified requires a restart.

In Role-based deployment, I select RD licensing, RDSH and RDWA. The dependent iis components are selected by the wizard. The installation went ok. But after restart, the RDS console says "There are no RD Connection Broker servers in the server pool. ...". The remote desktop service management service does not exist the services.

Then I try to add the broker feature. The dependent Windows Internal Database is selected by the wizard. The installation is not successful. The wizard says The request to add or remove features on the specified server failed. The operation cannot be completed, because the server that you specified requires a restart. The error persists after the restart. Now RDCB and RD Management services are installed. But RD Management services cannot be started successful. RDCB can be started manually.

Tuesday, August 28, 2012 8:38 AM

Moderator

1

Hi,

Pls follow the test lab guide to install from the scratch,you'd better not install the RDSH on the DC.
Test Lab Guide: Remote Desktop Services Publishing: http://technet.microsoft.com/en-us/library/hh831442

regards,

Clarence

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Tuesday, August 28, 2012 12:57 PM

2

I totally understannd that, and I am sure that will work. But some home users usually don't have the luxury to have multiple physical or virtual computers running 24 x 7. Even in Microsoft's trouble shooting guide, such scenario is just not recommended, but not impossible. Windows 2008 R2 handles such scenario without problem. I believe it has something to do with the new RD management service introduced in Windows 2012, which currently cannot be run on a DC controller.

I learned that it may be because that the Network Service account, which starts the service, cannot access Windows Internal Database required by RD management service. I tried to change it to a managed domain account and add the domain account in the local security user rights which allow Network Service, as suggested in another post. But I kept getting the service failed to run due to logon issue. Any one know how to correct it? Thanks.

Tuesday, September 04, 2012 3:46 PM

1

i have the same issue, it works fine on 2008 R2, why not 2012? did you ever figure out a fix for this? Microsoft always marketing "do more with less" but if this cant be done on a DC then that means we have to "do less with more"

Tuesday, September 04, 2012 11:05 PM

0

No, the issue is not solved. On Microsoft's document, such scenario is just not recommended, same as their view in 2008 R2. But now, it is impossible at this point. I think it all starts with the introduction of RD management service, which cannot be started if the computer is a DC. Hopefully Microsoft will give us some solution when Server 2012 is generally available. If any one has a fix, please let us know. Thanks.

Wednesday, September 05, 2012 4:50 PM

0

Thanks for this thread, now I know at least that it isn't me having broken the setup somehow. Same deal here.

Also, it's pretty obvious this isn't recommended but sometimes it's just the easiest thing to have or required. Even if it isn't recommended, it shouldn't fail with cryptic error messages in the event log and/or the server manager. If it's not supported at all anymore, Microsoft should have noted such and hard blocked the installation of RDS.

Lastly, it should be noted that RDSH, RDWA seem to work. What fails is RDCB - even if you only install RDCB and not RDSH on the DC.

I hope this gets a resolution since this is really somewhat painful.

Friday, September 07, 2012 8:53 AM

0

ZetaZynk, yes "seem to work", but you have no access to the RDII interface so ,you can't fix the license serveur, same with poweshell.

Broker was opptional with 2k8 r2 , seems to be needed with 2012.

cdlt

Chris

Sunday, September 09, 2012 1:53 AM

1

I have found a simple solution to this issue that I also believe to have no security implications for AD. If anyone thinks this is not the case, please tell.

The problem is that Network Service does not have access rights to WID. So why don't we give it those rights?

Do the following:

1) Connect to \\.\pipe\MICROSOFT##WID\tsql\query using SQL Management Studio.
2) Under Security\Logins, add a new login.
   On the General page:
    Login name: NT AUTHORITY\NETWORK SERVICE
    Default database: RDCms
    On the User Mapping page:
   Check RDCms, select the entry and check db_owner.

That's it. All services should start fine now.

Proposed As Answer by ResolutoR Sunday, September 09, 2012 1:54 AM
Edited by ResolutoR Sunday, September 09, 2012 2:03 AM

Tuesday, September 11, 2012 3:52 PM

0

Correct, but what I meant is:

Say you had two servers, one being DC running RDSH, RDWA, RD Licensing; the other one running RDCB and being domain joined. This would work, but would be equivalently insecure (since RDSH runs on the DC) to the setup where RDCB is on the DC.

Tuesday, September 11, 2012 7:45 PM

0

This enables you creating a deployment and running the services, but there's a reproducible error "Object reference not set to an instance of an object" when you try to create a session collection.

Good news is, it is resolvable - I have RDS now working on a DC here.

Bad news is, I don't know how. Something I did made it work, but I don't know what exactly. I didn't expect it to work when it worked. A simple reboot or similar won't fix this error though. Hopefully I can find out what I did to make it work.

Tuesday, September 11, 2012 9:16 PM

0

I have found a simple solution to this issue that I also believe to have no security implications for AD. If anyone thinks this is not the case, please tell.

The problem is that Network Service does not have access rights to WID. So why don't we give it those rights?
Do the following:

1) Connect to \\.\pipe\MICROSOFT##WID\tsql\query using SQL Management Studio.
2) Under Security\Logins, add a new login.
   On the General page:
    Login name: NT AUTHORITY\NETWORK SERVICE
    Default database: RDCms
    On the User Mapping page:
   Check RDCms, select the entry and check db_owner.

That's it. All services should start fine now.

Update:

After this step, create a new login for NT AUTHORITY\SYSTEM. You will see a message that the login already exists, however it will add NT AUTHORITY\SYSTEM to the list of users. Following a reboot of the machine, everything will work as expected.

If you omit this last step, you will run into said "Object reference is not set to an instance of an object" error. ResolutoR and I could both verify that these steps make a setup of RD Connection Broker on a Domain Controller possible.

WARNING: Please be aware that the setup of a DC and RDCB on one server is entirely unsupported. The above steps can make it work in some extend, but that's it. Also be aware that RD Gateway won't work this way.

YOU SHOULD NEVER RUN THIS ON A PRODUCTION SERVER.
USE THIS FOR EVALUATION PURPOSES ONLY.

Proposed As Answer by ZetaZynK Tuesday, September 11, 2012 9:16 PM
Edited by ZetaZynK Thursday, September 13, 2012 8:08 PM Warning added

Wednesday, September 12, 2012 2:34 AM

0

Thank you guys very much for the effort. Definitely big progress has been made. Maybe my question sounds silly. How did you guys install RDCB in the first place? Somehow I cannot even keep RDCB installed in my sever after I reinstalled the OS.

First I promoted the server to DC. Then I could add RD Licensing, RDSH and RDWA with no problem. When RDCB installation failed, and then I restarted the computer, the OS just reverted everything as if I never added RDCB. RDCms did not exist either. So what are the steps you guys took to keep RDCB in the system so that you can use SQL Management Studio to add proper users to RDCms?

Another question is whether I need assign NT AUTHORITY\SYSTEM as the owner of RDCms as well, or just simply adding it in login and setting RDCms as default database are sufficient?

Thanks.

Proposed As Answer by Edmundo096 Thursday, March 07, 2013 2:11 AM
Unproposed As Answer by Edmundo096 Thursday, March 07, 2013 2:11 AM

Wednesday, September 12, 2012 2:47 AM

0

No problem at all, we're in need of the same setup.

Setting RDCms as default database might not even be needed, but giving the login sufficient permissions - to be on the safe side, we just gave it db_owner - is required.

The trick for me was to install Remote Desktop Services first and then install ADDS and promote to domain. I started off like that, actually, because I figured I might be able to avoid more issues.

Wednesday, September 12, 2012 3:51 AM

0

Thanks a lot for the hint. I got all needed RD features installed. Network service and System have been added to the user list of RDCms. Now when deploying RD services, the process failed at Create session collections, so the last 2 of 3 steps were not completed. Also when manually adding gateway in RDS\Overview page, the process ended with "Configuratio failed. Unable to save the RD Gateway settings." Did you see these errors as well?

When clicking "Add RD Session Host servers", the Server Pool list is empty.

Edited by shimh Wednesday, September 12, 2012 3:54 AM To add addtional question
Edited by shimh Wednesday, September 12, 2012 3:55 AM

Wednesday, September 12, 2012 10:32 AM

0

To answer your previous question: NT AUTHORITY\SYSTEM already owns RDCms by default. Hence leaving the permissions on the default ones will work. It also has a login already, aliased as dbo. You shouldn't need to set RDCms as default database either.

Unfortunately, we can't tell you how to get RD Gateway to work. Our setup involves a single-machine one, for which we've only tested RDWA, RD Licensing, RDSH and RDCB as role features.

Saturday, September 22, 2012 5:46 PM

0

So Shimh did you get things working with the gateway? What was the trick?

Also were you able to figure out how to add the RDCB after you already had DC installed? Or was the only method to do it before promoting?

Thanks,

Terry

Saturday, September 22, 2012 8:27 PM

0

No, I haven't figured everything out, such as gateway, etc. Also computer list for rd session is empty too. I guess ms really does not want us to run everything in one server / license. :-(

Wednesday, October 03, 2012 3:32 AM

0

I just wanted to comment that I'm experiencing the same issue. Tried to use the RemoteApp functionality using the RDS Role but installation fails after configuring server as Active Directory Domain Controller (went through fine BEFORE configuring Active Directory).

Since RDS requires the server to be part of a domain I can't really use the functionality with only one server - which seems kinda lame. There should be an easy way to publish RemoteApps from Windows Server 2012 with simple authentication methods (outside of AD).

Best Regards,

Daniel

Proposed As Answer by ForbesCorporation Tuesday, October 16, 2012 12:58 AM
Unproposed As Answer by ForbesCorporation Tuesday, October 16, 2012 12:58 AM

Tuesday, October 16, 2012 2:04 AM

0

Server 2012 does not let you run Remote Desktop Server on a Domain Controller any more.

If you have already attempted to install the roles on an existing Domain Controller because you read that you need a Domain Controller before you can install RDP server you have just created a broken Remote Desktop Server Install. If this has happened you can attempt to uninstall the Remote Desktop Roles however this will not uninstall and it will leave RDP services and other registry information in the Domain Controller in a broken state. If you have done this I would recommend using a Backup restore to go back to before you installed the Remote Desktop Services on the Domain Controller.

Next we have a work around for this issue that you can use. You must create a Hyper-V Drive on the Domain Controller and once you have that created you can install Server 2012 using the free Hyper-V license. You are allowed one physical Server 2012 License which you will use for your Primary and Physical Drive and you are allowed 2 Server 2012 Hyper-V Licenses of Server 2012 on the same machine. You will not require the licenses if you are just testing but if you plan to issue the Server to a customer you must follow this procedure.

We are working with support to try and get a Document about these issues but until that has been released you will need to follow these steps and you need some background in Hyper-V and the server must support Hyper-V and you need to make sure the BIOS has Hyper-V turned on under processor configuration.

Step One

We will assume you have a new Machine at this point running and that you have created a proper Domain Controller from a clean install with DNS and also Certificate Server Running. You should have a Static IP like “192.168.1.1” or what ever.

Open Server Manager on the Domain Controller

Select Add Roles and Features

Select Next

Select Role-based or feature-based installation.

Select a server from the server pool.

Select Next

Expand Remote Desktop Services from the menu.

Select ONLY Remote Desktop Licensing. (DO NOT SELECT ANY OTHER ITEMS)

Select next until this finishes and the license server has been installed.

Register the License Server and then enter your Open Client Licenses or what ever kind you have if available.

Step Two

Create a Hyper-V Virtual Drive and install Server 2012 on it.

Next Set a Static IP for this Hyper-V Server “192.168.1.2”.

Name the Server something that makes sense “Server-2”

Join the Hyper-V Server to the Domain you created on the Primary Drive “DC-Server-1”.

Log into the Hyper-V Server Server-2 after it reboots and select Add Roles and Features.

Select Next

Select Remote Desktop Services Installation. (Do Not Choose Role Based)

Select Quick Start

Select Session-based desktop deployment

Select the server name Server2 or what ever you named your server (The Only Choice)

Select Finish after the roles get installed – the window will show the status on the install and should not have any errors using the wizard.

This completes the required steps in brief to allow you to run a Remote Desktop (Terminal Server) on a Domain Controller properly.

NOTE:

There is no SHADOW Service. (Used to Shadow a users active session)
There is no Session Monitor
There is no Processes Monitor (Used to terminate individual software processes on a user session).

These features were all part of the Terminal Services Manager that has been used for 20 years and this has been removed from Server 2012 and there is no current replacement. Please complain to the Remote Desktop Developers and post your comments on the blog sites to let the developers know if you are not happy.

You may also reference this article.

http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/ce2e8df1-2085-49db-a306-3eee20f21f05

Proposed As Answer by ForbesCorporation Tuesday, October 16, 2012 2:25 AM

Tuesday, October 16, 2012 3:55 PM

1

I thought if you had a SPLA license you could... is that not the case?

Friday, October 19, 2012 2:16 AM

0

To MATTW112

No the SPLA would not matter - you are not require to have a license to install the role of the Remote Desktop Services. The License Server could be setup before or after a deployment of Remote Desktop (Terminal Server). The license is not what causes the installation to fail, the reason an install will no longer work is because Microsoft has removed what was called the SOFT WARNING when you attempt to install a Terminal Server Role (Remote Desktop Server) on any Domain Controller within the same Physical drive of that AD. A SOFT WARNING in Server 2008R2 will present a message during the install telling you that this server is a Domain Controller and it’s not recommended that you install Terminal Services on a domain controller. You can check a box to continue anyway and it installs. The 2012 Server has removed the warning but failed to halt the install with a message telling you that it WILL NOT INSTALL, instead it creates a failed install.

The software should be telling you that you are attempting to install Remote Desktop Services on a Domain Controller and that is not permitted and then it should role back the partial install. It does not do that and then when you attempt to install you don't understand why the install fails but this is the reason.

Currently the only workaround that will run properly are the steps I have created and placed on this page. Again I understand your concern and if Microsoft Developers did their job properly it should have created a special partition for AD and then allowed the main physical drive to talk with the AD partition keeping the parts separate and secure.

If you wish to offer software services and host a domain controller for a customer you will need to create the server using a physical partition with the Domain Controller and a Virtual Partition as I described above on this page for the Remote Desktop to be installed.

Today’s Date is 10/18/2012 If Microsoft decides to fix this or change this at some point it would be nice but currently this is the only way it can be installed and installed and supported by MS.

Friday, October 26, 2012 12:11 PM

1

So where does that leave future installations of Server 2012 Essentials? MS are bringing out Essentials as a replacement to the Small Business Server editions and it automatically installs the DC role during the initial install. You don't have any choice in it. It's probably not advisable to run RDS on a Domain Controller but for small companies with single server installations it works well. It was a lot more cost effective in the long run than traditional client / server networks.

MS are pushing the Essentials as a solution to the SME market where there isn't always the IT expertise inhouse, hence why it's very menu driven. However, this isn't proving to be the case. How are the smaller companies supposed to run RDS if not spported in single server networks?

Sunday, October 28, 2012 1:58 PM

0

Thanks for this info, I'm trying to test RDS on my WS2012 and have the same problems of the people here.

Maybe my question is a bit stupid so I say sorry in advance, following your solution (create a Hyper-V Virtual Drive) I will need an additional WS2012 license, right?

Carlo

Tuesday, October 30, 2012 12:24 PM

0

Not necessarily. Microsoft are changing the licensing model for WS 2012 based on virtualisation and the number of physical processors per server. WS 2012 Standard edition comes with the rights to run 1 physical installation of WS 2012 or 2 virtual instances on a server with up to two CPU's. You will need the correct amount of CALs per server instance though.

WS 2012 Essentials and Foundation have different restrictions.

Wednesday, October 31, 2012 1:44 PM

0

Hi, I'm having the same problem.
Sorry to sound like an idiot but how can i connect to \\.\pipe\MICROSOFT##WID\tsql\query in SQL management studio. I tried typing that in and it didn't work are there some parts I'm supposed to replace?

Cheers,

Edited by Jon Hacking(EIB) Wednesday, October 31, 2012 1:45 PM

Friday, November 02, 2012 7:02 PM

0

Regardless of what Microsoft calls the new Small Business Server you still can not install Terminal Server Role on that servers primary partition of the SBS. You will need to follow my steps to setup a Virtual Drive. As far as licenses I have explained how Licenses works in the new platform on the posting we made above on the forum and the other post "Partner CN IT" has also explained this to you. Once you create a Virtual Drive you can install Microsoft Server 2012 into that Virtual Environment and install Remote Desktop Server there. On the Small Business Server they also limit the number of users to 2 that could connect using Remote Desktop - RD was intended for Administration purpose not for regular users. This is why we stopped selling the SBS product. We never use Small Business Servers because of the RDP restriction. Microsoft expects that SBS Server will not be used for Remote Desktop access by common users. You can create a Virtual Server and install it there you you can buy Graphon GO-GLOBAL Software and install it on your server and not use Microsoft Terminal Server at all. WWW.Graphon.com

Edited by ForbesCorporation Friday, November 02, 2012 7:20 PM
Edited by ForbesCorporation Friday, November 02, 2012 7:21 PM
Edited by ForbesCorporation Friday, November 02, 2012 7:23 PM

Friday, November 09, 2012 12:01 PM

0

So where does that leave future installations of Server 2012 Essentials? MS are bringing out Essentials as a replacement to the Small Business Server editions and it automatically installs the DC role during the initial install. You don't have any choice in it. It's probably not advisable to run RDS on a Domain Controller but for small companies with single server installations it works well. It was a lot more cost effective in the long run than traditional client / server networks.

MS are pushing the Essentials as a solution to the SME market where there isn't always the IT expertise inhouse, hence why it's very menu driven. However, this isn't proving to be the case. How are the smaller companies supposed to run RDS if not spported in single server networks?

I've just run into the same problem. No warning when you try to install RDS on Windows Server 2012 Essentials, so I ended up finding out it wasn't supported through this thread. Poor design on both levels - no facility and no warning.

Considering the high costs of the server license, Microsoft should really have allowed small business to install RDS on their one server. It's not feasible for small businesses to run two server. Virtualisation would be a possibility, except that, of course, Windows Server 2012 Essentials doesn't come with any additional virtualisation rights.

Hope Microsoft reconsider quickly.

Wednesday, November 21, 2012 7:05 PM

0

thank you, this is working now.

Tuesday, November 27, 2012 2:10 AM

0

I am new to Windows server 2012 Essentials/servers in general... I have run into the same issues as above.

I am under the impression that Windows Server 2012 Essentials can host applications to my users (all 3 of us) on the Remote Web Access page.?

I am trying to get this box set up so that my wife can remote into it (within our network) and run Quickbooks and have it backed up as well as her boss logging into the same company profile (outside of our network). I have Remote Web Access working and functional and all users can log in this way. I also have VPN working.

How can I publish this application for these users to access and perform their work as I discribed above?

I'm sure that I have not given enough information and I may have to provide additional details on my current configuration.

Should I have purchased Windows Server 2012 instead of Essentials to do what I want?

Have I messed anything up trying to install RDS over and over to the registry as discribed above?

This box is not for production, it's more for personal use but want to have my wife and her boss access this profile and are able to access Quickbooks for their work.

Thanks again for your help in advance.

Edited by Chrys Burge Tuesday, November 27, 2012 3:13 AM Additional information

Tuesday, November 27, 2012 10:05 PM

0

First off - best to post in the Essentials forum. Next are there workstations that your users (wife) use locally that remotely they can log into?

Essentials cannot be a RDS box - it's a domain controller and you don't want people to be logging into it. It can be the conduit to RWA into a local workstation from a remote location.

In the case of Essentials the RD gateway stuff is there, just needs a DISM command to be able to see the GuI.

But first let's back up a step and see what you have to log into from where.

Tuesday, November 27, 2012 10:08 PM

0

Essentials doesn't host terminal services is why.

Tuesday, November 27, 2012 10:10 PM

1

Here's how you do this folks, buy Windows 2012 standard. It does a 1+2 virtualization rights. Install the parent and only install the HyperV role. Now use your downgrade rights to install Essentials 2012 as a virtual machine. Install a second copy of Server 2012 as your Terminal server box.

Microsoft will not reconsider. TS should not now, nor ever should it have been supported on a domain controller.

Tuesday, November 27, 2012 10:35 PM

0

Sorry about posting here. It seemed to be a similar issue to mine.

My wife has a laptop that is her personal workstation, within our network, that currently has QuickBooks installed locally on. And her boss has his own workstation outside of our network.

What my goal to do was, create a user profile for the company that she works for on the WS2012E box that would host QuickBooks via the "Remote Web Access" as a remote app and also be a location to store and back up all of the company job folders and documents including the QuickBooks file. Both her and her boss could access the company's profile on the server from either inside or outside our network, simultaneously or consecutively.

I was under the impression that WS2012E could host remote applications through the "Remote Web Access" function. Is this not true?

Is there any way I can accomplish what I described above with WS2012E?

Thanks again.

Tuesday, November 27, 2012 10:46 PM

1

While your wife and her boss could access the file outside of your network, they cannot do so via her workstation at the same time.

Some will say "install QB on the server as well as on her workstation and then two users can access it"

Problems with this idea - QB program shouldn't be installed on the server itself and the remote desktop ability on the server is just for administrative use/not for a user to use.

How beefy is her workstation? Can it handle a virtual box install with an Win7 instance underneath that her boss can use as a workstation to remote back into? Can you throw more RAM at it?

Otherwise how about a cheap headless workstation that sits in the corner that is always turned on?

Bottom line you need a workstation to connect into, or the app needs to support a direct access/vpn connection (which QB hates).

Tuesday, November 27, 2012 11:30 PM

2

folks - if you just want a single server that runs RDS, look into super inexpensive Windows Multipoint Server. one box, up to 20 users, can be in a workgroup OR a domain (premium version only).

Kevin

SBS MVP

Wednesday, November 28, 2012 1:32 AM

0

Thank you for the information and guideance. I will look into other senarios as Susan has recommended.

I guess the thing that is confusing to me and keep in mind I'm a newb, is that when I was researching WS2012E before I purchased it, the documentation stated that "Remote Web Access provides access to applications and data from outside the network". And on the licensing data sheet it states that it can operate as an application server. This led me to believe that users could access third party applications that could be hosted on the server for my users to access. What applications can you host from a WS2012E box?

Thanks, Chrys

Edited by Chrys Burge Wednesday, November 28, 2012 2:08 AM Additional information

Wednesday, November 28, 2012 2:29 AM

0

Server 2012 does not let you run Remote Desktop Server on a Domain Controller any more.

If you have already attempted to install the roles on an existing Domain Controller because you read that you need a Domain Controller before you can install RDP server you have just created a broken Remote Desktop Server Install. If this has happened you can attempt to uninstall the Remote Desktop Roles however this will not uninstall and it will leave RDP services and other registry information in the Domain Controller in a broken state. If you have done this I would recommend using a Backup restore to go back to before you installed the Remote Desktop Services on the Domain Controller.

Next we have a work around for this issue that you can use. You must create a Hyper-V Drive on the Domain Controller and once you have that created you can install Server 2012 using the free Hyper-V license. You are allowed one physical Server 2012 License which you will use for your Primary and Physical Drive and you are allowed 2 Server 2012 Hyper-V Licenses of Server 2012 on the same machine. You will not require the licenses if you are just testing but if you plan to issue the Server to a customer you must follow this procedure.

We are working with support to try and get a Document about these issues but until that has been released you will need to follow these steps and you need some background in Hyper-V and the server must support Hyper-V and you need to make sure the BIOS has Hyper-V turned on under processor configuration.

Step One

We will assume you have a new Machine at this point running and that you have created a proper Domain Controller from a clean install with DNS and also Certificate Server Running. You should have a Static IP like “192.168.1.1” or what ever.

Open Server Manager on the Domain Controller

Select Add Roles and Features

Select Next

Select Role-based or feature-based installation.

Select a server from the server pool.

Select Next

Expand Remote Desktop Services from the menu.

Select ONLY Remote Desktop Licensing. (DO NOT SELECT ANY OTHER ITEMS)

Select next until this finishes and the license server has been installed.

Register the License Server and then enter your Open Client Licenses or what ever kind you have if available.

Step Two

Create a Hyper-V Virtual Drive and install Server 2012 on it.

Next Set a Static IP for this Hyper-V Server “192.168.1.2”.

Name the Server something that makes sense “Server-2”

Join the Hyper-V Server to the Domain you created on the Primary Drive “DC-Server-1”.

Log into the Hyper-V Server Server-2 after it reboots and select Add Roles and Features.

Select Next

Select Remote Desktop Services Installation. (Do Not Choose Role Based)

Select Quick Start

Select Session-based desktop deployment

Select the server name Server2 or what ever you named your server (The Only Choice)

Select Finish after the roles get installed – the window will show the status on the install and should not have any errors using the wizard.

This completes the required steps in brief to allow you to run a Remote Desktop (Terminal Server) on a Domain Controller properly.

NOTE:

There is no SHADOW Service. (Used to Shadow a users active session)
There is no Session Monitor
There is no Processes Monitor (Used to terminate individual software processes on a user session).

These features were all part of the Terminal Services Manager that has been used for 20 years and this has been removed from Server 2012 and there is no current replacement. Please complain to the Remote Desktop Developers and post your comments on the blog sites to let the developers know if you are not happy.

You may also reference this article.

To clarify for me, this senario only works with Windows Server 2012 Standard, not Essentials, correct?

Wednesday, November 28, 2012 5:22 AM

0

Yes. But keep in mind if you install Windows 2012 standard you get a 1+2 rights. You can downgrade one of the two virtual servers to essentials.

Wednesday, November 28, 2012 6:02 AM

0

There has to be some sort of desktops to connect to that application server. If the app can work over a vpn, you can have a vpn connection from a laptop/workstation back to the server. If it can't work over a vpn then you need either a desktop to get back to or an additional terminal server.

In the specific case of Quickbooks, it does not like VPN connections and prefers a desktop or terminal server.

Friday, December 21, 2012 4:35 PM

0

Here is the official answer from Microsoft. We had to roll back to 2008 server and will be meeting to decide where to go from here. Remote Desktop Management tools are essential for us. We have been using these tools for over 15 years and our entire business model is structured around MS RDP (training, setup and customer service). Where do we go from here?

Hi,

As discussed it is not possible to shadow remote desktop sessions using Windows 2012 server due to security reasons. Below is the summary;

Symptom
You would like to know if there are any alternatives for the removed Shadow Session(Remote Control) in Windows Server 2012

Cause
By design

Resolution
Due to the removal of the classic shell and the new architecture of the desktop window manager, in addition, consider to the security, we have removed the Remote Control(Shadow Session) in Windows Server 2012. As alternatives, we can use Remote Assistance or Remote Control in Live Message.

If Microsoft has published any other better alternatives, I will inform you as quick as possible, thanks for your understanding.

Additional Information
Managing RDS/VDI with Windows Server 2012

http://blogs.msdn.com/b/customer_reviews_of_stb_products/archive/2012/09/05/managing-rds-vdi-with-windows-server-2012.aspx

Supported Configurations for Configuration Manager

http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigRCViewer

Best Regards,
Prasanth Gopalkrishnan

Alternate contact :

Thursday, March 07, 2013 11:42 AM

0

Microsoft should reconsider this scenario in any case. Even if it's not supported, you shouldn't be able to put your installation in a state of no clean return (except by using a backup) by just installing roles.

Previous versions had a warning for this not being supported, and it doesn't matter whether this would work or not - if it does okay, otherwise hard-block the installation to prevent users ending up with a broken installation.

Secondly, the most problematic role is and was always RDSH. You can still install RDSH on a DC and won't even be warned anymore. If the RDCB is installed on another server you can install an unsupported setup without prior information that your actions just rendered the setup unsupportable.

Lastly, this doesn't work because of permissions not being set by the setup. This would speak for a non-supported setup simply not covered by tests. Enabling this for evaluation purposes should be rather feasible for Microsoft.

Friday, March 22, 2013 4:55 PM

0

Does the domain it self get damaged from trying to install RDS Quick setup on a DC?

I installed RDS on a DC, saw this post, then I demoted the domain controller (we have multiple), then reimaged the server as a exs-i box, installed 2 VMs, one is a DC, 2nd is a member server that I just tried to install RDS on. It fails with all the same errors/symptoms (from what I can tell) as if I was installing RDS on a DC (which I am not).

Any one have any insight on this?

--

The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.

---

The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.

Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID

This service account does not have the required user right "Log on as a service."

User Action

Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.

If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.

---

Tuesday, March 26, 2013 7:02 PM

0

We ended up having to install via the Add Roles and Features, selecting all the needed RDS Roles, not the separate RDS / Quick start options which continued to fail at different points in the process.

Since I configured session host scopes, it requires a separate option in the GPO which tells the session host what mode the license is. It does not pull it from the license server. Once updated, ran gpupdate /force on both machines.. License Diagnostics then passed with no issues.

Saturday, April 13, 2013 9:51 PM

0

Wow, isn't that overkill?

So we have to install SQL server management studio, do the query, and uninstall it?

I dont want a SQL server eating up my memory.

I think microsoft have gone backwards here. I've done what Server Manager has said, and it should have recommended me create a Domain Server as a Hyper V server from the offset. Solves this RDP problem.

"There are no RD Connection Broker servers in the server pool. ...". The remote desktop service management service does not exist the services"

Friday, May 03, 2013 3:37 PM

0

Asinine. Simply Asinine. Microsoft took it out because of $GREED$.
RemoteDesktop has become so popular, they had to break it to make more money. Thats why they discontinued SmallBusinessServer. If this practice is so tabooo... Why did MS go the opposite direction with SBS 2011 Premium Cal's? SBS2011 had DC, Exchange, RDS and Sharepoint,SQL, RemoteWebWorkplace, OWA all working in perfect harmony. It is an untrue statement then, that it was "allowed but not recommended"

Now you by Server2012 (core + two virtual) and its not enough for all this. You need at least another $700 for another sever licence to have it all and who knows if SQL will run on a DC, or Exchange, or R-DERP server. Another reacherous bridge to cross.

By far, the absloute worse release since Millennium. The product is not ready for production, we broke our rule of waiting until the first SP1 upgrade for this and Exchange 2013. Problems with USB drivers and networking running extreamly slow. Our 2003 SBS server was at least three times as fast, and this server has SAS and SSD drives running. It can't get out of its own way, and IE10 is the most unstable piece of crap to come out of Redmond. Open wide and swallow - Mother Microsoft knows whats best for you. YOU WILL EAT OUR SLOP AND LEARN TO LIKE IT. Server2012 AKA "METRO-SERVER"

Now here I sit after 50 Hours back to back setting up a new R-DERP server 2012, AD, Have my RDP licences in my hand at $100 each, and WTH does Microsoft care if I install it on my DC. ITS MY DC. And the cost savings versus the "risk" was previously MY decision.

Sure, I can install a couple of Virtual HyperV sessions but they are so tempremental to a power-outage in a small business its not worth it. I have to double up my server hard drive resources, buy a $800 battery backup unit and make sure to attach the cable, and even then, if that Bi**H does not shut down properly, one bit goes awry in a VHD or VHDX file and you are screwed. Restore from lastnights backup and forget about todays work. Not to mention it will probably take a half day to try to fix it, then recover it then tell the 30 users they lost a days worth of work.

HYPER-V is for test servers and has no place in a small (micro) business environment. 5-30 users.

Microsoft's solution, buy another server. Need Exchange? Buy another server or take the risky cheapskate route and spin up some VHD's. Might as well put a gun to your head and play russian roulette, at least you know you have a one in six chance of failure. With MS, its a 100% failure for a dirty shutdown power loss, motherboard blows, memory goes corrupt in a few years, your conventional method of recovery is gone, and you have some upchucked VHD file to try to recover some of TODAYS data from.

Screw server 2012 forever.

I will sell 2008 and SBS2011 Premium unitl it rots in hell like XP (of which there is NOTHING wrong with for the average, WORD, EXCEL, OUTLOOK and QUICKBOOKS that all SMB's use. Its MS $GREED$ Grab the world by the B**ls and squeeze with all your might to squeeze every dime you can out of *SMB* because big business is going to run thier 2003 Exchange and 2008 servers into ground before they switch to this garbage.

YOU CANNOT INSTALL EXCHANGE 2013 on DC , OR on R-DERP server.

Go buy another server license and server or MOVE TO THE CLOUD and get fleeced every month.

I have 30 DC/R-DERP/Exchange and SBS2011 Premium servers all running for years in perfect harmony, locked down with security so the users can't even WIGGLE with something they are not supposed to work with. They get their apps, cannot install anything and all these servers are running just fine behind the firewall and perfectly save. The track record of this combination is 100% stable and is up 24/7/365 with no problems. Do yourself a favor and throw this 2012 into the river, you don't need any weights because it is LEAD and will sink to the bottom by itself.

Why, you ask? Official is "Its for your protection" The real reason? To sell you more $700 server licences.

Maybe for SMB, we start selling Linux NAS Servers, host the Exchange in the cloud and be hearded like cattle to the Microsoft slaughterhouse. One way or another, you are going to bleed. A little each month to move to the cloud, or a small fortune if you want to have it in house. Microsoft wants it to be more expensive to have in house. No more buying a server and running it for six years before you upgrade. They can't have in house servers competing with their cloud, and small businesses are the low hanging fruit ripe for the pickin'.

Friday, May 03, 2013 4:06 PM

0

While I can relate to some of what you are saying, I'm running two hyperV boxes - one of which I've done now for 4 years. Granted it's fully gui HyperV not core or anything like that but it does have a place in small business. I'm under 30 seats and I honestly really like having a box that allows me to add additional virtual machines when I need them. For example I have a virtual XP up there for older applications.

Friday, May 03, 2013 4:10 PM

0

P.s. if you haven't seen or checked out MultiPoint - you should.

Proposed As Answer by RickkeeC Friday, May 03, 2013 4:48 PM

Sunday, May 19, 2013 8:43 PM

0

Sorry about posting here. It seemed to be a similar issue to mine.

My wife has a laptop that is her personal workstation, within our network, that currently has QuickBooks installed locally on. And her boss has his own workstation outside of our network.

What my goal to do was, create a user profile for the company that she works for on the WS2012E box that would host QuickBooks via the "Remote Web Access" as a remote app and also be a location to store and back up all of the company job folders and documents including the QuickBooks file. Both her and her boss could access the company's profile on the server from either inside or outside our network, simultaneously or consecutively.

I was under the impression that WS2012E could host remote applications through the "Remote Web Access" function. Is this not true?

Is there any way I can accomplish what I described above with WS2012E?

Chrys - Were you ever able to come up with a solution for your wife's QuickBooks situation? I have a very similar need.

Thanks,

Dustin Jackson

Install Remote Desktop Services Failed on Windows 2012 Server

All Replies

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support by product

Other support links

Not an IT pro?