• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Terminal server

EightySix Four

EightySix Four

Diamond Member
I have a small server only used for quickbooks, quickbooks reccomends installing the quickbooks on the server, and using a terminal server for everyone to open and run it. I don't have access to multiple servers so I can't complete MS's stupid client server model that's needed, any other way to do it in windows server 2003?

And if not, anyone know how I could set up a system for people to be capable of running quickbooks like this?
 
eh, not sure, but does quickbooks say to use "application mode" TS or "administration mode" TS?

If it's adminstration mode, then you shouldn't need a client server model. If it's application, then I am not sure (never done app ts before)
 
It's quickbooks enterprise, can do either P2P or Server to Client model, they suggest over anything using a terminal server, and installing a client liscense for Quickbooks on each machine... I don't know what the heck I'm gonna do, the other way I can do it is through windows file sharing and a VPN but I'm even more lost when I go that direction
 
sorry, I don't understand how quickbooks works. You could put it in adminstrative mode, and then 2 remote users at a time can connect to the server using remote desktop clients (built into XP, downloadable for 9X/2K). They would then run quickbooks as though they were sitting at the machine.
 
I don't have access to multiple servers so I can't complete MS's stupid client server model that's needed, any other way to do it in windows server 2003?
Click to expand...

I don't understand the need for multiple servers. You already have one server, why can't you use that?
 
MS has a special server model for using a Terminal Server where your required to have a second server to handle all liscensing
 
You just need to setup the licensing server on the same server. What OS are the clients that will be connecting to the TS Server?

John
 
so far remote desktop is the best idea, and since this has a multi-user mode for just that kinda thing... we'll see how it works (testing now)
 
Why dont you use the TS server? You dont need to setup the licensing server on a different machine. It can be setup on the same machine as the TS Server.

I love it when people make things more complicated and difficult than they need to be.

John
 
Usually the license comes with your seat or in this example your client machine that is probably running Win2K or WinXP.

They say licensing for when you are using an actual terminal or thin client. On something like that you arent running an MS OS.
 
We don't require that the licensing server be on a separate box. Install it on the TS.

Usually the license comes with your seat or in this example your client machine that is probably running Win2K or WinXP
Click to expand...

Not when those clients are connecting to a 2003 TS. All clients connecting to a 2003 TS need a TS CAL.

Yes OP, you do need to pay for TS licensing. I'm sorry you feel this is 'gay' but that's the way it is. How many clients need to connect to the terminal server at one time? You might find that it doesn't cost as much as you think.
 
I have it working perfectly through remote desktop at the moment, and it would probably be a 10 client liscense if I ended up doing it that way.
 
Originally posted by: STaSh
We don't require that the licensing server be on a separate box. Install it on the TS.

Usually the license comes with your seat or in this example your client machine that is probably running Win2K or WinXP
Click to expand...

Not when those clients are connecting to a 2003 TS. All clients connecting to a 2003 TS need a TS CAL.

Yes OP, you do need to pay for TS licensing. I'm sorry you feel this is 'gay' but that's the way it is. How many clients need to connect to the terminal server at one time? You might find that it doesn't cost as much as you think.
Click to expand...

Dump 2003 then and run 2000 if you can. What a joke of a licensing system they have implemented.
 
Well, CDW sells per-device terminal server CALs (open license) for $29.11, so that would $291.10 for 10. You may be able to find better prices if you shop around.
 
ouch... I guess I don't have too much of a choice eh? Do people log in thourhg a Remote Desktop Connection when I buy the liscenses also? One last question, by default what port does Remote Desktop run at?
 
Do people log in thourhg a Remote Desktop Connection when I buy the liscenses also?
Click to expand...

You have to install terminal services (through add/remove components) to enable what used to be called TS in application mode. But client access is the same no matter which mode the server is in. Clients use the RDP client (mstsc.exe) to access the server.

One last question, by default what port does Remote Desktop run at?
Click to expand...

Both remote desktop and terminal services use TCP 3389.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top