According to the PDF, administrator rights are not needed, but the change permission is needed for the data files, if not the Quickbooks directory (just like a normal LAN install). Fully agree Intuit drops the ball on install issues..yesterday I did a wk install for multiuser, install went south... the install changed the sharing permission of the wks QB data server.. (Why, and what right did they have to do this. an Ahole programmer)
I have not run QB on a TS but I love TS access speed, most programs run faster on a TS than on workstations if the TS has enough CPU speed, decent speed disk subsystem, and enough ram.
One security issue.. If you do not have a RD Gateway role setup on a 2008 server, users connect with port 3389 (or another specified port), which would need to be open on the firewall. More secure method is using an RD Gateway which is much more secure due to SSL and other security measures along with a TS (google it). Local users could also RD to the TS if necessary for QB access, but likely it is not and they should be able to access the QB data on the TS with a normal wks QB setup. RD Web Access role service, on the 2008 r2 or web access on 2008, can allow a browser connection to QB.
Regular RDP to local machines is not practical, as each accessing user needs an idle machine to log into. RDP access speed much is slower than TS access.
Best but more expensive
1. Server 2008, with the RD Gateway services role enabled, and/or RD Web Access role service enabled. A heavy duty server is not needed if the primary purpose is to act as a Gateway. A fairly cheap 3 GHz CPU ( a dual core is plenty), with say a raid1 SATA setup would do. Raid 1 for safety, as you do not want to rebuild a Gateway from scratch, even with a backup.
2. terminal Services server for QB and other programs. This needs to be fairly high powered, as to disk speed and especially the amount of ram.
........................................
Chernobyl disaster..a must see pictorial