If you havent already, install QuickBooks Database Server Manager on your server for each version of QuickBooks. However, some functionality might not work accurately since the version that youre using is no longer supported.
The Server 2012/2012 R2 Standard license allows you to have it installed on the physical server with only Hyper-V, plus installed on 2 VMs on the same server. QuickBooks 2012 can still be used on Windows Server 2012 R2. Step 2: Install QuickBooks Database Server Manager. Once the RDS deployment is created you would configure certificates, configure settings, install and publish QuickBooks, etc. RDS, as it is abbreviated, allows you to have a powerful server that all your users connect to using the Remote Desktop Protocol (RDP). If you’re using any other server operating system, follow the basic H202 troubleshoot steps. Starting with Server 2008 R2, Terminal Services has been renamed to Remote Desktop Services. I am tired of roaming the internet searching for answers. If you’re using Windows Server 2012 Essentials R2, continue with the steps below. In my lab deployment there is no NLB anymore (as Connection Broker should take care of the load balancing) so when I connect (using Remote Desktop) to (resolves to the public IP of the RDS Gateway), I am presented with the "Only members of the Remote Desktop Users group is allowed" message which makes no sense as I am using my domain admin account for testing.Īs I mentioned, at this point, I am ready to pay ayone that makes this thing works. Here's the issue, my 200+ users in three countries are used to open remote desktop connection on their Windows desktops and connect to which resolved to an NLB cluster of two 2008 R2 servers. Locate and run the QuickBooks/Quicken setup program (i.e. At this point, I am willing to pay anyone (out of my pocket) to get it done. On the Server Folders tab, select/highlight the Intuit Setup Files folder and then click on the Open the folder task in the Tasks pane. I have followed Molan's tutorial as well as many others and can't get it to work.
All we want is to provide the same RDC experience my users had with 2008 Terminal Server.
I am struggling to understand this new RDS.