Quickbooks Pro 2006 on terminal server

Is it possible to install Quickbooks Pro 2006 on a terminal server Win2k3, or do i need to buy quickbooks enterprise?
It is a small company that does not want the expense of enterprise edition but does want to be able to run quickbooks on the terminal server.
I have seen posts in other forums that say it should work but I have had no luck.

Any help would be greatly appreciated.

I used to work at an accounting firm and I was able to get previous versions of Quickbooks Pro to run on the terminal servers.  I remember it involved a lot of time using regmon and filemon and setting permissions to reg keys and folders to full control.  It took awhile to grind through them but I got it to work...  

We ended up using the most recent version (at the time) of enterprise after a couple years and it still required some tweaks...

Quickbooks 2006 is entirely different than previous versions, as it MUST be installed on a server if it's a multi-user version.

I haven't installed 2006 yet, but previous versions did not require Enterprise to install on TS, although, as twoody54 mentioned, it takes some time to get the registry permissions working correctly.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

Hi swns,

       I have quickbooks Premier 2004 installed on TS. This involved tweaks, and a bit of patience. From recolecction it involved copying a specific intuit folder from the c:\windows\ directory and placing it in the required users base profile (Documents and Settings) directory. These specific users then required local administrative (power user??) access to the local (TS) machine.
Then it worked pretty well. There was a document on the quicken website detailing what needed to be done.

I now also have quicken quickbooks premier 2005/2006 installed on the same TS machine.
From memory (it was a while ago) there was no requirement for any 'hacks'. I believe it worked straight out of the box.

Don't know if this (2005/2006) is any different that straight 2006, but we are 'quicken professional partners' and I have received no releases/updates of late...

Goodluck - it is worth searching the quicken site as they don't seem to mind TS usage.

Cheers.

We've had 2005 installed on a TS box with no more problems than 2004.

But 2006 is different.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

2006 is different. It installs okay on the TS server, but it won't open aferwards. This was supposed to be fixed with R3 but don't you have to open and register the program before you can apply ant patches? Can I grequest a new CD with the latest patches on it?

We initially experimented with a 2002 version of QuickBooks and have since graduated to 2006 Professional, using the same setup as shown below.

Vera Noest is a MS VIP, and provided this information on her site.  It works like a champ, but you must follow the steps exactly as she has detailed, or it just won't work for you.

1.  perform a normal installation of QuickBooks (in install mode!)
2.  reboot
3.  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
4.  go back to execute mode (change user /execute)
copy the %systemroot%\Intuit folder into each users %userprofile%\Windows folder
5.  create a Quickbooks Users group
6.  add your users to this group
7.  give the group Full Control to HKEY_LOCAL_MACHINE\Software\Intuit\QuickBooksRegistration
8.  give the group Full Control to HKEY_CLASSES_ROOT\.QPG
9.  give the group Full Control to HKEY_CLASSES_ROOT\obja.obja
10.  give the group Full Control to HKEY_CLASSES_ROOT\Quickbooks.application
11.  give the group Modify rights to the Program Files\Intuit\Quickbooks Pro folder
12.  Also make sure that clients use short names for printers if they need to print to a redirected local printer. Quickbooks cannot handle long printer names. You will get an "assertion failure" error message if the name is too long.

Thanks lb63640,

I had talked to tech support at intuit and got the directions as you have laid out.
Like you said, works like a champ.

Too bad it is such a pain to get these things to work properly on a terminal server.