K_Wilke
asked on
Quickbooks Enterprise 16, Excel 2013 on Windows 2012 R2 RDP (terminal server)
Hello all,
Here is the setup for a client of mine.
Two servers. One is a domain controller and has Windows 2012 R2 on it. All the data (Quickbooks included) resides on this server. This server is also running the database manager for the Quickbooks databases. The second server is not a domain controller. Just a Windows 2012 R2 server with RDP/terminal services on it. This server has 16 gig RAM and a 3.5 i7 Ghz processor in it.
We have two people who uses this remote server. The only things they get into is Excel 2013 and Quickbooks Enterprise 16.
This is happening to both users but so far I am only testing one user.
This user is the only one on the RDP server and when she is in both Quickbooks and Excl 2013 then Excel gets extremely slow, times out and then she gets errors that that the remote connection has dropped.
Here is what I have done so far:
1) On the RDP server I have unselected Network Level Authentication.
2) Under the user's Excel I disabled hardware graphics acceleration
3) Under the user's Excel I disabled Automatically Flash Fill
4) Under the user's Excl I disabled AutoComplete for cell values
I have no idea what else to do. I have a suspicion that Quickbooks is a major player in this issue but I have no idea what to do in Quickbooks to have it run correctly in an RDP session.
Any help would be greatly appreciated.
Thanks,
Kelly W
Here is the setup for a client of mine.
Two servers. One is a domain controller and has Windows 2012 R2 on it. All the data (Quickbooks included) resides on this server. This server is also running the database manager for the Quickbooks databases. The second server is not a domain controller. Just a Windows 2012 R2 server with RDP/terminal services on it. This server has 16 gig RAM and a 3.5 i7 Ghz processor in it.
We have two people who uses this remote server. The only things they get into is Excel 2013 and Quickbooks Enterprise 16.
This is happening to both users but so far I am only testing one user.
This user is the only one on the RDP server and when she is in both Quickbooks and Excl 2013 then Excel gets extremely slow, times out and then she gets errors that that the remote connection has dropped.
Here is what I have done so far:
1) On the RDP server I have unselected Network Level Authentication.
2) Under the user's Excel I disabled hardware graphics acceleration
3) Under the user's Excel I disabled Automatically Flash Fill
4) Under the user's Excl I disabled AutoComplete for cell values
I have no idea what else to do. I have a suspicion that Quickbooks is a major player in this issue but I have no idea what to do in Quickbooks to have it run correctly in an RDP session.
Any help would be greatly appreciated.
Thanks,
Kelly W
John
The QuickBooks database is a very chatty database. I would try keeping the database and the Database manager on the Terminal Server and then let local users access it there. Then the database usage would be more direct (and quicker) for the terminal server users.
What speed network between the two servers? How many switches in between?
Can you run a continuous ping test between the servers without latency or dropped packets?
What drive configuration on Terminal server (i.e. RAID and type)?
What brand and model server? I have seen terrible problems on some Dell RAID controllers.
Quickbooks best performance would definately come from being on the Terminal server as John suggests, but How many quickbooks users are connecting to the domain controller for QBE?
If you remote into the Terminal server from inside your network (LAN), do the problems also exist?
Can you run a continuous ping test between the servers without latency or dropped packets?
What drive configuration on Terminal server (i.e. RAID and type)?
What brand and model server? I have seen terrible problems on some Dell RAID controllers.
Quickbooks best performance would definately come from being on the Terminal server as John suggests, but How many quickbooks users are connecting to the domain controller for QBE?
If you remote into the Terminal server from inside your network (LAN), do the problems also exist?
ASKER
1 gig between the two servers.
All one gig switch. Total of four computers, one printer and these two servers on the network.
Continuous ping is a yes.
Server is only 4 months old brand new.
Just found out from the user everything was okay until Windows updates were done on the RDP server.
Will have to uninstall the updates and see what happens.
All one gig switch. Total of four computers, one printer and these two servers on the network.
Continuous ping is a yes.
Server is only 4 months old brand new.
Just found out from the user everything was okay until Windows updates were done on the RDP server.
Will have to uninstall the updates and see what happens.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ping results indicated no latency issue, correct?
If Windows update doesn't resolve your issue, please indicate the RAID controller (if any) and model of server.
If Windows update doesn't resolve your issue, please indicate the RAID controller (if any) and model of server.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I agree with John. We tried a similar setup for a group of 3 users and they complained every other day about how slow it all was. We ended up using one person's PC to serve as the QB host, then set it up to backup the main company file to a server every night.
ASKER
For the hard drives we have one 1 terabyte hard drive for the OS and three 1 terabyte hard drives in a RAID 10 configuration for all data.
It is a locally built server.
I guess I don't understand about moving the QB manager and database to the RDP server. There are two local Windows 7 computers that are over three years old with only 3 gig RAM that doe the same thing but not using RDP and they do not have a problem.
Much older processors and less than 4 gig RAM on the older PCs no issues.
On the RDP server much faster processor and 16 gig RAM and there is this issue?
I understand QB is chatty but don't get why this isn't happening on all PCs as well.
Also found updates 3126033 and 3102467 were for RDP issues that were just installed.
Going to uninstall those first to see if this fixes it.
Thanks,
Kelly W.
It is a locally built server.
I guess I don't understand about moving the QB manager and database to the RDP server. There are two local Windows 7 computers that are over three years old with only 3 gig RAM that doe the same thing but not using RDP and they do not have a problem.
Much older processors and less than 4 gig RAM on the older PCs no issues.
On the RDP server much faster processor and 16 gig RAM and there is this issue?
I understand QB is chatty but don't get why this isn't happening on all PCs as well.
Also found updates 3126033 and 3102467 were for RDP issues that were just installed.
Going to uninstall those first to see if this fixes it.
Thanks,
Kelly W.
John is recommending you install Quickbook Ent and host the data on the Terminal Server.
If the network (Non RDP) users don't have trouble, then I wouldn't suspect hard drive issues. I would post back after removal of the two Windows updates you mentioned.
If the network (Non RDP) users don't have trouble, then I wouldn't suspect hard drive issues. I would post back after removal of the two Windows updates you mentioned.
ASKER
Though this wasn't the fix it pointed me in the right direction.
The Charter internet speed went from 60 mbps down to .5 mbps. Got Charter to fix their issue and everything is working fine.
Thank you all for your help.
The Charter internet speed went from 60 mbps down to .5 mbps. Got Charter to fix their issue and everything is working fine.
Thank you all for your help.
Thanks for the update and I was happy to help.