True, but then Watt went off topic and raised the specter of users needing administrator rights on a server hosting the QB 2006. Watt's post said the following:
Looking at buzz on quickbooksgroup.com about installing QB2006 Pro makes your security comment quite timely.
Apparently you have to grant full administrator privs on the server to anyone who uses QB 2006 Pro.
Here's a 12/2/2005 post from MiaAPQB. (I'll clip the parts about 3 hour hold times to talk to an unhelpful tech in India)
If you take the time out to actually read the post from MiaAPQB there is no mention of Terminal Services.
Back when we installed QBP2004 on our Win2003 with Terminal Services we were told by the buz on the internet that users would have to have administrator privliges to run QBP, and that registry files would need to be altered or given access to, etcetera.
We found the following to work.
QBP2004 was installed on the Win2003 server by the Administrator in "change user /install" mode, the server was rebooted. The server was changed back to "change user /install" mode again, and QBP was run once by the Administrator. Then the server was returned to "change user /execute" mode, and all users could login and run QBP just fine as regular users with no special administrator privliges. (Users need read/write access to the QBP program directory.)
If anyone is using QBP2006 on with Terminal Services and finds that the above doesn't work, then we'd be very interested to know about it...
We just setup server std 2003 and terminal services was running just fine. We just got a 5user QB Pro 2006 and using the change user /install method doesn't work. When you run setup, the "don't close this window until its done or elst" box pops up but the QB setup NEVER starts. QB support first told us to msconfig and remove all startup items... on a server?? I asked... he then hung up. On the second call, the support lady told us that QB Pro isn't supported with term svcs only Enterprise editions. I really want to make this work as the client needs to access this from home via VPN... and term svcs would work a lot quicker!
We just setup server std 2003 and terminal services was running just fine. We just got a 5user QB Pro 2006 and using the change user /install method doesn't work. When you run setup, the "don't close this window until its done or elst" box pops up but the QB setup NEVER starts. QB support first told us to msconfig and remove all startup items... on a server?? I asked... he then hung up. On the second call, the support lady told us that QB Pro isn't supported with term svcs only Enterprise editions. I really want to make this work as the client needs to access this from home via VPN... and term svcs would work a lot quicker!
So far, though, they only offer it for Premier and higher, using the logic (anti-logic?) that you can toggle Premier to a Pro environment. Problem is, you have to toggle EVERY TIME YOU START YOUR SESSION!! (caps intentional) IMHO this is a less than desirable option. (Are you listening Intuit??) The toggle option is great for its intended use, which is for the accountant or consultant (moi) to be able to verify a client's data in the version the client actually uses without having to buy and install several different versions. It is not very good for an end-user to evaluate a particular version. This is what Intuit says about Terminal Server usage: "To run QuickBooks Enterprise Solutions in a terminal server environment, you must have Windows XP Pro, Windows 2000 Server, or Windows Server 2003 along with client access licenses for multiple users. "In a terminal server network, Quickbooks Enterprise Solutions is installed on a centralized terminal server, so that licensed users from remote locations can access the company file without having QuickBooks installed on their computer. Companies must purchase a software license for each local and remote user. Windows Terminal Services enables remote users to access Enterprise Solutions over lower bandwidth connections (such as DSL)." (2006 ProAdvisor Reference Guide, page 61). And that's all they have to say about that. My guess is that they will tell you that QB Pro and Premier are not supported in Terminal Server environments. I also suspect that the product is so new that few if any users have installed even Enterprise Solutions in a Terminal Server Environment. I would wait as long as possible, research as much as possible and even go so far as to fork out the $700 or so for a
60 day trial with the full intention of requesting a refund if it didn't work, before committing to it. "Mike Schumann" wrote in message news:yn7lf.428$ snipped-for-privacy@newsread2.news.atl.earthlink.net...
The toggle feature is not there so you can verify a clients data, what ever that means. It is there so you can see the same screens as the end user you are trying to help.
Right... That's sort of what I was trying to say. Point is, its not a very viable option for evaluating QB Pro (or any of the other flavors of QB, for that matter) but for now seems to be the only eval resource except for the
60 day money back route. I don't find that very helpful.
The longer answer is that QBP is nott really designed to have multiple people running it in a terminal services environment. Some of the printing issues with QBP2004 in terminal services that we've discovered are not seen unless you have a lot of users accessing the program. The culprit is the qbprint.qbw file. It looks like maybe putting the qbprint.qbp file in an application isolation environment (so that each user has his own qbprint.qbp file) may solve these problems. Similarly, the qbw.ini file keeps track of the last x (user set) number of QBP datafiles that were opened, and putting this file in an application isolation environment makes it so that each user can see the last x datafiles that they opened, not the last x datafiles that EVERYONE opened.
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.