Solved

Windows Server 2003 and Quikbooks Enterprise

Posted on 2008-10-20
8
503 Views
Last Modified: 2010-05-18
I have a Windows 2003 server that is a Domain controller, DNS, and Terminal server. All the users connect to the server using Remote desktop connection. The server is used for several versions of Quickbooks.  We have not been able to run Quickbook Enterprise with any of the other versions. As a result, we have installed another Windows 2003 server into the Domain, with Terminal server on it.  We have installed Quickbook enterprise onto the other server. We wanted to install it on to a network drive, but Enterprise would not allow us to do so. We are currently running QB enterprise through another terminal session from the new server.  Is there a better way?  This works, but isnt very efficient  Thanks.
0
Comment
Question by:notme_9000
  • 3
8 Comments
 
LVL 24

Expert Comment

by:ryansoto
ID: 22762452
You need to first remove the major security risk of terminal server on your first domain controller.  
Now on the second server you have....You are trying to install it to a local drive on that machine right such as the C: or D:?
Uninstall the version(s) on the old server
Once you install it there you need to move the company file to a spot somewhere on the network for simplicity I would put in the same location as the installation.
Now since you have QB on this new server you will just need to add the workstation/client piece to a workstation.  Then open the company file from whereever you place it on the network.
0
 

Author Comment

by:notme_9000
ID: 22773058
QB Enterprise will only allow you to install it on a local drive.  It will not recognize a network drive at all during the installation process.  There are no security issues with the terminal server.  The two servers are in the same domain. When I have installed Enterprise on the same server as the other versions of QB, they stop working. All the clients use remote desktop sessions. The servers you see are at another location.  This is an unusual situation. In order to make this work, I have to terminal into the server1, and then terminal into server2 from server1 in order to use QB Enterprise. This is the only way that I have been able to make it work consistently.  I was hoping there would be a better way. Thanks for your help.
0
 
LVL 24

Accepted Solution

by:
ryansoto earned 100 total points
ID: 22777721
Again here is what I would do -


Uninstall QB from all servers/terminal servers/etc and start fresh
Install QB and the company file on a server you choose.  Make it a server that your end user will not use as the terminal server.

Now map a drive to that location from the terminal server and make it something like Q:

Now install the QB client on the terminal server your end users will be  using.  When the run QB they will click the open company file box and choose the Q drive.  They should see the company file there and open it.
That will work fine its how it set up in a few of my clients offices with no issue
0
 

Assisted Solution

by:scdaren
scdaren earned 100 total points
ID: 23397219
So do you need QB users from other non-Enterprise versions to connect in to the terminal server for quickbooks?  Last I checked on Enterprise supports Terminal Server.

We also have a mix of QB Enterprise and QB 200x for a few users.  We also keep data files centralized.  The configuration we have is a main domain controller and file server where the data is stored.  This machine has QB Enterprise installed on it with the Database Manager for the data files.  Then we have two Terminal Servers, which run QB Enterprise for two different companies.  All the data files are stored on the file server for everyone.

The users of QB 200x have that software installed on their desktop locally, with the data files store don their network file share drives (which are on the same file server discussed above).

The security issue he mentions is that it is best to have as few communications as possible from your domain controller to the outside world (ie Terminal Server).

This configuration should work fine, as long as you are not trying to mix Enterprise and non-Enterprise versions of QB on a Term Server.  Non-enterprise qb will not perform well with a Term Server configuration.
0
 
LVL 24

Expert Comment

by:ryansoto
ID: 24642039
I feel that the information I provided has fulfilled the askers question
0

Featured Post

Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

So you have two Windows Servers and you have a directory/folder/files on one that you'd like to mirror to the other?  You don't really want to deal with DFS or a 3rd party solution like Doubletake. You can use Robocopy from the Windows Server 200…
This may not be a text book method to resolve VSS backup issues but it seemed to have worked on few of the Windows 2003 servers we had issues while performing a Volume Shadow Copy backup. If you have issues while performing a shadow copy backup usin…
This Micro Tutorial demonstrates using Microsoft Excel pivot tables, how to reverse engineer competitors' marketing strategies through backlinks.
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now