1. Home
  2. QuickBooks Discussions
  3. Terminal Services

Terminal Services

I have installed QB 2004 Pro on our TS 2003 Server and using the following 'mod' which I found online I have managed to get it to actually run within the TS environment. However it only seems to work on the account I was logged in as when I installed/mod'd the software.

Any ideas on getting it working for all my users?

Thanks

o perform a normal installation of QuickBooks (in install mode!) o reboot o enter install mode again (change user /install), start QuickBooks and activate it by entering the registration code (this is a crucial step, and must be performed immediately following the reboot o go back to execute mode (change user /execute) o copy the %systemroot%\Intuit folder into each users %userprofile%\Windows folder o create a Quickbooks Users group o add your users to this group o give the group Full Control to HKEY_LOCAL_MACHINE\Software\Intuit\QuickBooksRegistration o give the group Full Control to HKEY_CLASSES_ROOT\.QPG o give the group Full Control to HKEY_CLASSES_ROOT\obja.obja o give the group Full Control to HKEY_CLASSES_ROOT\Quickbooks.application - QB Premier 2004 only? o give the group Modify rights to the Program Files\Intuit\Quickbooks Pro folder

Reply to
K
Loading thread data ...

Are you using the 5 user pack?

I never did anything special, to get QBooks installed under Terminal Services, except for making sure that I was in install mode during the installation and the 1st time I ran the program. Note: Make sure you are running as the administrator when you install QBooks.

After you are installed and switch back to execute mode, you should be able to run QBooks from any user account, as long as that user is a "Power User".

Mike Schumann

Reply to
Mike Schumann

Mike,

We may have domain security set up differently than you.

We found that only users who were administrators could reliably get into Quickbooks files that were on our domain server.

This was a problem, because you don't want a user who accidentally trashes files access to the entire system.

So we created a QB Users security group. We set up the QB directory to be available only to those users specifically named in the "QB Users" security group. Otherwise, any Tom, Dick or Harriet in the Power Users group could get into Quickbooks and copy, edit, delete the files.

We had Power Users who had no need to be accessing Quickbooks.

While the reboot was not necessary for the 5 user pack, the registry edits and rights did allow "QB users" group to access Quickbooks, and ONLY the members of the QB users group (or administrators).

Cheers,

*Watt

Reply to
*Watt

I'm not a big fan of having QBooks Users running as Power Users. I just didn't have the time to figure out how to get it to work in a more restrictive environment.

Mike Schumann

Reply to
Mike Schumann

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.