Re: Newby and QBES in TS

Your clients access the Terminal Server with the remote desktop
client (mstsc.exe). This client is already present on XP Pro
workststaions, under Start - All Programs - Accesories -
Communication - Remote Desktop Connection.

Configure the client with the name of the Terminal Server and
connect. Hit the "Options" button to configure redirection of local
drives, printers, available bandwidth, etc. You can save these
settings in an rdp file.
You will be asked for your username and password, and then you'll
see the Terminal Server desktop, from where you can start the
application.

If QB is going to be the *only* application that users will be
running from the TS, you can configure the TS to automatically
start QB as soon as users connect. That way, they will never see
the TS desktop.
When users quit QB, they will automatically be logged off from the
TS again.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
___ please respond in newsgroup, NOT by private email ___

"BoboTWG" <bobotwg@xxxxxxxxxxxxxxxxxxxxx> wrote on 25 jun 2005 in
microsoft.public.windows.terminal_services:

> OK, this is going to be a stupid, easy question. After I install
> the app. on the TS, how does the client access it? What do they
> actually do to get into the application from their (XP Pro) Work
> Station? I cannot find any info on this and I am guessing it is
> so simple that I should know it. Sorry and thanks in advance.
>
> AAron
>
> "BoboTWG" <aaron.nospam@xxxxxxxxxx> wrote in message
> news:HkZue.8808$lv.3773@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Thank you very much Vera. I really appreciate that. I will
>> ensure that the printers have short names prior to setting this
>> up. Thanks again.
>>
>> Aaron
>>
>> "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
>> in message
>> news:Xns967FCFB20E751veranoesthemutforsse@xxxxxxxxxxxxxxxx
>>> Hi Aaron and Patrick,
>>> thought I'd just jump into your discussion with a small
>>> detail:
>>>
>>> One more thing that can be good to know in advance is that QB
>>> can't handle long printer names. And redirected printers can
>>> get rather long names....
>>> So if you can print to your redirected printer from all other
>>> applications like notepad and Word, but not from within QB,
>>> make sure that the local printer name is *not* something like
>>> "HP LaserJet xxxx PCL version n.nn", but call it something
>>> short like "LocalPrt".
>>>
>>> Good luck!
>>> _________________________________________________________
>>> Vera Noest
>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>> http://hem.fyristorg.com/vera/IT
>>> ___ please respond in newsgroup, NOT by private email ___
>>>
>>> "BoboTWG" <aaron.nospam@xxxxxxxxxx> wrote on 24 jun 2005 in
>>> microsoft.public.windows.terminal_services:
>>>
>>> > Thank you again. That last part looks like it can save some
>>> > serious headaches.
>>> >
>>> > I got kinda nervous at the first part because QB is the ones
>>> > that said we would have to do the whole TS thing (after we
>>> > purchased everything else including SBS2003, workstations,
>>> > etc.).
>>> >
>>> > Thanks again.
>>> >
>>> > Aaron
>>> >
>>> > "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx>
>>> > wrote in message
>>> > news:F7A1C5C6-D1C4-4446-84E6-168E29169F76@xxxxxxxxxxxxxxxx
>>> >> Here is some great info from a colleague of mine (Vera
>>> >> Noest).
>>> >>
>>> >> http://hem.fyristorg.com/vera/IT/TS_apps_QB.htm
>>> >>
>>> >>
>>> >> --
>>> >> Patrick Rouse
>>> >> Microsoft MVP - Terminal Server
>>> >> http://www.workthin.com
>>> >>
>>> >>
>>> >> "BoboTWG" wrote:
>>> >>
>>> >> > Thank you very much Patrick. Just what I was looking for.
>>> >> > Yep. Sure will
>>> > be
>>> >> > calling QB ahead of time (again) and I will probably make
>>> >> > our "dedicated tech." stay on line with me through the
>>> >> > install.
>>> >> >
>>> >> > I am going to do the install and then play around with a
>>> >> > test company
>>> > for a
>>> >> > few days to ensure there are no connectivity issues and
>>> >> > then bring their data over from the other server that is
>>> >> > housing it for their present
>>> > usage
>>> >> > of QB Pro. I will keep that up and running for a while
>>> >> > with them doing double data entry until the beginning of
>>> >> > the next quarter so that should take care of anything
>>> >> > going horribly wrong, etc. Plus the server that
>>> > this
>>> >> > is going on is a brand new chassis, new install, and will
>>> >> > only be used
>>> > for
>>> >> > this purpose.
>>> >> >
>>> >> > Thank you very much again for the great advise and link.
>>> >> >
>>> >> > Aaron
>>> >> >
>>> >> > "Patrick Rouse" <PatrickRouse@xxxxxxxxxxxxxxxxxxxxxxxxx>
>>> >> > wrote in
>>> > message
>>> >> > news:9D5358A1-D759-438D-88BE-54030396739E@xxxxxxxxxxxxxxxx
>>> >> > > Application install info here:
>>> >> > > http://www.workthin.com/tsai.htm
>>> >> > >
>>> >> > > Check with QB for any caveats specific to their
>>> >> > > software. You should
>>> >> > always
>>> >> > > setup a test machine with the software you want to use
>>> >> > > to make sure it
>>> >> > works,
>>> >> > > and to resolve any issues "before" going live on a
>>> >> > > production system. Obviously you should have a
>>> >> > > bare-minimum of a full system backup w/
>>> > system
>>> >> > > state, and preferrably an image backup w/ something
>>> >> > > like Ghost so if something goes horribly wrong you can
>>> >> > > be back to the previous state in
>>> > a
>>> >> > half
>>> >> > > an hour, instead of 8 hours. (or more)
>>> >> > > --
>>> >> > > Patrick Rouse
>>> >> > > Microsoft MVP - Terminal Server
>>> >> > > http://www.workthin.com
>>> >> > >
>>> >> > >
>>> >> > > "BoboTWG" wrote:
>>> >> > >
>>> >> > > > Hello, I am a newby at this whole T.S. thing. I have
>>> >> > > > been reaading everything I can find on it though. I
>>> >> > > > have a server running SBS2003.
>>> > I
>>> >> > also
>>> >> > > > have a member server setup on the network. It's whole
>>> >> > > > reason for
>>> > being
>>> >> > is
>>> >> > > > going to be to run QuickBooks Enterprise Edition in
>>> >> > > > Terminal
>>> > Services.
>>> >> > > >
>>> >> > > > I can access this server already via RWW. I have
>>> >> > > > told it that it is
>>> > a
>>> >> > > > Terminal Server. I will be going in and installing
>>> >> > > > QBES this
>>> > weekend. Is
>>> >> > > > there anything that I should know about this install
>>> >> > > > before I
>>> > proceed.
>>> >> > Is it
>>> >> > > > going to be just like installing any other
>>> >> > > > application? I have never installed anything on a
>>> >> > > > Terminal Server before. Thanks in advance
>>> > for
>>> >> > your
>>> >> > > > assistance.
>>> >> > > >
>>> >> > > > Aaron
.

Loading