Learn the fundamentals of the popular programming language JavaScript so that you can explore the realm of web development.
Server 2012 R2 RDS and QB
Environment:
Box #1
HV1: 2012 R2 hyper-V host
SVR1: hyper-V VM running 2012 R2 is the main server. It's used for file and print and Quickbooks and Lacerte (accounting firm)
SVR1 is replicated to REP1
SVR1 is also continuously backed up to REP1 using ShadowProtect Server
Box #2
REP1: 2012 R2
REP1 replicated to an offsite server for DR purposes
REP1 receives the backups from SVR1 then FTPs them to the same offsite server for DR and ransomeware protections purposes
Problem: Need to be able to allow offsite Win7 and Win10 usage (2-3 users) of QB and Lacerte.
Tried an SSL VPN. Aside from the fact it's not supported, QB couldn't open company files on the server, although full file access through Windows Explorer was fine.
So...RDS seems to be the solution, although I've never used it.
Plenty of RDS installation/configuration
QB Enterprise is supported with RDS, but client will use QB Pro. I suspect this will not really be a problem.
Where I'm fuzzy...
Ideally I'd think RDS should be installed on REP1 because it's a very low utilization server, however from reading, I get the impression QB Server Manager should be installed on the same server as RDS. Currently QB Server Manager is installed on SVR1 where all the QB files live, and that's not gonna change.
Am I barking up the wrong tree? Do we need an RDS server?
Would appreciate all suggestions.
Thanks
Mark
Box #1
HV1: 2012 R2 hyper-V host
SVR1: hyper-V VM running 2012 R2 is the main server. It's used for file and print and Quickbooks and Lacerte (accounting firm)
SVR1 is replicated to REP1
SVR1 is also continuously backed up to REP1 using ShadowProtect Server
Box #2
REP1: 2012 R2
REP1 replicated to an offsite server for DR purposes
REP1 receives the backups from SVR1 then FTPs them to the same offsite server for DR and ransomeware protections purposes
Problem: Need to be able to allow offsite Win7 and Win10 usage (2-3 users) of QB and Lacerte.
Tried an SSL VPN. Aside from the fact it's not supported, QB couldn't open company files on the server, although full file access through Windows Explorer was fine.
So...RDS seems to be the solution, although I've never used it.
Plenty of RDS installation/configuration
QB Enterprise is supported with RDS, but client will use QB Pro. I suspect this will not really be a problem.
Where I'm fuzzy...
Ideally I'd think RDS should be installed on REP1 because it's a very low utilization server, however from reading, I get the impression QB Server Manager should be installed on the same server as RDS. Currently QB Server Manager is installed on SVR1 where all the QB files live, and that's not gonna change.
Am I barking up the wrong tree? Do we need an RDS server?
Would appreciate all suggestions.
Thanks
Mark
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
RDS is really the only supported option with QuickBooks, and enterprise... not pro... will indeed be REQUIRED.
So long as the user can log into the server and use QuickBooks on the server, that will work. QB is not supported for remote access (QB on a remote client machine and database on a server).
Intuit won't support QuickBooks Premier/Pro installed on an RDSH (Remote Desktop Session Host).
https://community.intuit.com/articles/1019015-install-quickbooks-on-a-terminal-server.
We install, configure, and support Premier and Accountant's Editions in a RDSH environment for our accounting firm clients among others.
The Database Manager can be installed anywhere on the network. We usually put it on a VM dedicated to all LoB (Line-of-Business) applications. Make sure to poke the necessary holes in the Windows Firewall to allow it to listen for incoming calls.
Intuit has a troubleshooting tool that helps figure out what may be blocking the Db Manager connection.
https://community.intuit.com/articles/1019015-install-quickbooks-on-a-terminal-server.
We install, configure, and support Premier and Accountant's Editions in a RDSH environment for our accounting firm clients among others.
The Database Manager can be installed anywhere on the network. We usually put it on a VM dedicated to all LoB (Line-of-Business) applications. Make sure to poke the necessary holes in the Windows Firewall to allow it to listen for incoming calls.
Intuit has a troubleshooting tool that helps figure out what may be blocking the Db Manager connection.
Philip
If I've understood you correctly, while Intuit doesn't support it, you still install non-Enterprise editions of QB on RDSH, and they work just fine.
My client's QB Mgr also runs on a VM, SVR1 in the config I outlined in my initial post.
So install RDS on REP1. Install QB Accountant for remote access (I have to figure out how to do tha1!). Make sure there's access to the QB DB Mgr. That's it?
Thank you!
Mark
If I've understood you correctly, while Intuit doesn't support it, you still install non-Enterprise editions of QB on RDSH, and they work just fine.
My client's QB Mgr also runs on a VM, SVR1 in the config I outlined in my initial post.
So install RDS on REP1. Install QB Accountant for remote access (I have to figure out how to do tha1!). Make sure there's access to the QB DB Mgr. That's it?
Thank you!
Mark
You should do what Intuit supports, but if you are using QuickBooks on this server (not a remote computer) AND if the company database is on this server (so local to QB) AND if you can install the Server Manager on this server, it might work OK.
Mark,
Just run the installer, key the product, and activate once done. Then click the Sync My License option under Help --> License. From there run the update process.
I suggest turning Automatic Updates off on the RDSH since it's a shared setting and the Public\Downloads folder shouldn't be available for standard users anyway.
Once QB is installed run the Publish Wizard in Server Manager to get it up on RDWeb, RemoteApp, and the RemoteApp RSS.
EDIT: @John We've been running QB in a RDSH setting since around v2008. We've not had any issues other than it's a resource and bandwidth hog between the RDSH/RDS Farm and the company file(s) location.
Just run the installer, key the product, and activate once done. Then click the Sync My License option under Help --> License. From there run the update process.
I suggest turning Automatic Updates off on the RDSH since it's a shared setting and the Public\Downloads folder shouldn't be available for standard users anyway.
Once QB is installed run the Publish Wizard in Server Manager to get it up on RDWeb, RemoteApp, and the RemoteApp RSS.
EDIT: @John We've been running QB in a RDSH setting since around v2008. We've not had any issues other than it's a resource and bandwidth hog between the RDSH/RDS Farm and the company file(s) location.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial