RE: I am an educated Beginner with some questions:



QuickBooks 2005 and higher Enterprise Edition *is* supported on TS.
And for instructions on how to install and configure QB 2003 on a
TS, see:

http://ts.veranoest.net/ts_apps_qb.htm

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___


=?Utf-8?B?TWF0dFNoZWxs?= <MattShell@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 21 mar 2007 in
microsoft.public.windows.terminal_services:

Actually, you may want to consider the 2007 version of
Quickbooks (It makes me throw up that I just said that). 2007
runs well in TS, even thought they don't officially support it
and doesn't not require giving a user admin rights to run the
program. If you are really against having to buy 2007 look into
a script (we used to run it but I have deleted it since) which
utilizizes the Run program as... feature. This allows you to
have specific users run one program as an admin but not the
whole server. You put in the admin username and password once,
and tell it to remeber and from there on out you should have no
problems running it in the TS envoriment. We did it with
Quickbooks 2004 for about 9 months until we were forced into
upgrading to 2007 due to payroll taxes needing to be done
through Quickbooks. You might check to see if you have to do
payroll taxes through Quickbooks and upgarde now to save
yourself a headache later.

Matt

"Mark" wrote:

How kind of you to reply so fast. Thank you for sharing your
knowlege with those of us trying to upgrade and learn that
can't always afford 1800-Help-Me

Don't laff

But we have a Dell Power Edge SC420 with 4 megs of ram.

We have to change programs for our company for many reasons.
Intuit in all of it's wisdom will not run in Terminal Services
mode even tho they do not tell you that on thier multi-user
expensive program. Plus their 2005 Premier edition will not run
with Vista, and they plan no patch. I'm not buying 2007, trust
me.

Right now:

We have 2 employess that remote into the static IP.

We have 3 employees local that have static IP's that log in. (2
at a time with W2k#) I was so happy that our seller explained
the limitations as we explained our needs. (I hope you realize
I was joking.) We were horribly undersold, and now catching up.

How bout those IP's we have 5 and can get more.. That the
route.

I will when ready make a clean install of all programs.

Thank you again. You are very kind .

mark

"MattShell" wrote:

Mark,

The licences are not hard to install and TS works pretty
well, although a warning is you will need to uninstall and
reinstall your applications for them to use. The reason is
because Terminal Server needs to install in a little bit of a
different way. I honestly would recomend reformatting just
so there is nothing left over that could cause problems
later.

Remeber that a CAL licences you for either a device or a
user, but you need to chose which you want to do. Device
runs by the number of devices that connect to it, so if you
have multiple users using the same computer, device is the
option for you. If you have users using multiple devices to
connect to your TS server then licence by user.

Adding users is not too bad as long as you get them added
into the right groups. Permissions will setup differently on
each server, but the Remote Desktop group is the one I would
start with.

Install your TS server before buying licences, as it will let
you run for 120 days before require bought CAL's. This
allows you to decide if TS is for you before you buy the
appropritate licences.

The only thing that will limit you are your servers
rescourses. Feel free to post your machine's specs and I
will tell you what I think.

Matt

"Mark" wrote:

Didn't want to seem realllll dumb so here goes: Place
appropriate graphitti at the end. Thanks in advanced!

Presently run W2K3 SP2.

We want to add more than 2 simo. employees. SO..

I hope to Mangae my server to be a TS..

If I buy 10 TS Cals, are they hard to install?

Is it easy to add users?

Does it limit how many remote access connections can
simultaneously log in? Or any combo of clients and remotes?

The server runs on static IP. with dhcp off. Clients have
static IP's. Would they need to change for any major
reason?

Guess I have to ask, since I have already been burnt..Any
problems with Vista/XP networking?

Thanks,

Mark
.



Relevant Pages

  • Re: Quickbooks 2006
    ... and QB 2006 is now running fine on the SBS server. ... > Installing QuickBooks 2006 in a Networked Environment ... > installation as QB 2006 has trashed some computers during its install ... > This update has solved my problems at a client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Quickbooks 2006
    ... >> Installing QuickBooks 2006 in a Networked Environment ... >> This update has solved my problems at a client. ... If someone wishes to install 2006 for any reason they should do ... >> the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Quickbooks 2006
    ... Installing QuickBooks 2006 in a Networked Environment ... installation as QB 2006 has trashed some computers during its install ... Intuit has put R3P update for Quickbooks 2006 on their website today. ... server or second it has a new alternate mode a workstation needs to start up ...
    (microsoft.public.windows.server.sbs)
  • RE: I am an educated Beginner with some questions:
    ... I will when ready make a clean install of all programs. ... Remeber that a CAL licences you for either a device or a user, ... to your TS server then licence by user. ... Permissions will setup differently on each server, but the Remote ...
    (microsoft.public.windows.terminal_services)
  • RE: I am an educated Beginner with some questions:
    ... you may want to consider the 2007 version of Quickbooks (It makes ... users run one program as an admin but not the whole server. ... I will when ready make a clean install of all programs. ... Remeber that a CAL licences you for either a device or a user, ...
    (microsoft.public.windows.terminal_services)

Loading