Quickbooks Pro 2013 Terminal Server Errors after update

Foreword:

Intuit says they won't support quickbooks on a terminal server and you must buy an enterprise license. I think this means that to be in compliance and eligible to receive support you must fit their guidelines. Else you're up a creek without a paddle.

Problem:

Quickbooks Pro 2013 had failed to update and was subsequently failing to open.

This was on a terminal server (2008 r2 x64) with about 30 users total.

Cause:

Each terminal user login was starting approximately four quickbooks / intuit proceses - from "secure sync" to "update".

Quickbooks pro is designed for a single user workstation. 

Solution:

1. Uninstalling quickbooks, I ran CCleaner registry cleaner
2. Rebooted, Ran CCLeaner again
3. Reinstalled Quickbooks, it wants to reboot, choose to reboot later
4. Open Autoruns provided by technet
4b. Have autoruns scan your user account
4c. Look through the list for quickbook entries, on each one
5. Right click and choose properties, then security and remove all permissions except for the user who will be using quickbooks.
-- That's right, just one user.. So in my case I had about 35 users, only one was a book keeper and needed access - so I had to remove all login accounts from that list - meaning all users and even the administrator - only the book keeper was allowed access to launch those files.
6. That's it!

In my instance, I only allowed their admin to make changes while I set the program up and ensured it launched. Once everything was in place, updated and opening their QBB files, I changed the settings again to remove access from the admin and give it soley to the book keeper.

Workaround #2:

If you're on a terminal server, you're coming from a workstation. In this businesses case they had actual thick clients which had been managed to log into their terminal server - if I really had to meet compliance to have Intuit troubleshoot, I would have just installed on this machine instead of buying their corporate license.

Terminal Server CD Burning

Project:
Enable CD burning from a remote desktop to a local machine. Where The terminal client is the main mode for the user.

Edited: January 28, 2014

Environment
Client: Windows, a full client. Should be applicable xp-7.


Solution 1:
 To enable cd burning without any extra software,
I simply shared of the local CD burning drive so that they could access it via their remote session.. This can be achieved by sharing the cd burning folder located at %userprofile%\Local Settings\Application Data\Microsoft\CD Burning or by sharing the local C drive with the remote client and making a shortcut to //tsclient/c/users/%userprofile%\Local Settings\Application Data\Microsoft\CD Burning"

A shortcut should be mapped or linked to the users remote desktop.

users then drop the files they wish to burn into this folder, insert a blank disc and the local side autoplay would handle the rest.

Keep in mind:
-the  differences between local OS's (users vs documents and settings, ect.).
-The user must also remember to remove the old files after they have burned their final copy.
-May be helpful to remind users that this is on the local side, as clicking it behind the desktop is sometimes confusing.

Should the users accidently click on their remote desktop, hiding the autoplay, simply ejecting and reinserting the disc will have it pop back up.

Solution 2: 
To enable cd burning WITH extra software.
In my case, we had replaced the shell of a specific user account with a simple script to launch their remote desktop client. The cd burning software would not launch because explorer.exe was not loading.

CD burning in this instance was a bit of a hassle, especially since most modern network cd burning software won't run without admin privileges and that wasn't something we could provide our terminal users.

So, we created a very simple website that would load instead, with links pointing to bat files which would then load the programs from the local machine. This would launch either remote desktop or the cd burning software depending on the choice the user made, which was configured to point to their user folder, so they could place items on the server in a folder, then switch.

edit 7/9/2013:
In other words, create a .html that has links to whatever software you want to use. I also created simple .bat scripts to launch various programs and services. I put all this on the sever.

Then, I would make a login script which loads this html file.

 In my instance, I changed the shell from the terminal services script I had created, to this html file. I also set it up so that if a user were to close this html file, windows would log out. (The original script called for a logout when remote desktop was closed.)

This allowed users to access an advanced CD burning tool while being less complicated than using Windows.

I could easily add more programs and features to the html launcher.

Example:
>Root Folder
>> login.bat
>>> @echo off
start /wait "title" "C:\scripts\logon\HTML\Launch.html"
shutdown /l

>>Logon/Html Folder
>>> Contains a webpage.html with two image/links, one to "launch remote desktop", the other "Launch CD burn"
these links point toward two bat files which look like:

>>cdburn.bat
>>>echo "Starting CD BURN XP"
echo @off
"C:\Program Files\CDBurnerXP\cdbxpp.exe"
del "%userprofile%\downloads\cdburn.bat"