Thanks once again Lanwench
It was worth asking. I have worked the web pages code a bit to rearrange the
menu page etc so I will customise it a bit more to make it look sweet for
them or make it step through the menu page since they never use ony of the
menu items other than than their own desktop - yep 'never'. I will of course
keep the original pages as there really is no such thing as never. They won't
do another IP. They will accept this login but they asked if I could
investigate a simpler method. Thanks again.
"Lanwench [MVP - Exchange]" wrote:
> Bazzar <Bazzar@newsgroup> wrote:
> > I'm a complete newbie to TS. The current setup is a main server with
> > SBS2003 SP2, setup as domain server etc, Echange, 2 NICs - 1 for LAN
> > and 1 for Internet.
> I'm setting up my reply to crosspost to microsoft.public.windows.server.sbs.
> SBS does many things its own way and you should definitely post there even
> if you also crosspost to a non-SBS group.
> > Everything has run from here to date. Currently
> > use the 2 licenses for remote admin login. They now want to start
> > running remote practices so I see TS as the answer. I made up another
> > server with Server2003, set it up only as a TS and Apps server. It
> > has 2 NICs as well.
> <cringe> Don't do that. Just a single NIC is all you need.
> In fact, if you're not using SBS2003 Premium with ISA, you don't need two
> NICs on your SBS box either. Multihomed DCs are generally frowned upon. It
> buys you virtually nothing from a security standpoint and immensely
> complicates troubleshooting - and it can cause all sorts of fun problems.
> I'd just get a good firewall appliance and use a single NIC in the SBS box
> if you don't use ISA.
> Connect all workstations & servers & firewall into the same Ethernet
> > I have installed a 5 User TS cals pack on the main server so it acts
> > as the License server for TS. So far the license server (main server)
> > is not seen by the TS server.
> Did you tell the TS box where the license server is?
> http://support.microsoft.com/kb/237811 (I presume you already did all this)
> http://support.microsoft.com/?id=301932 has info on how license server
> discovery works & what you can do to manually specify.
> > They do communicate over the LAN and I
> > can log in to the TS server over the LAN using RDP for multiple
> > logins. I am not certain what I need to activate on the TS server and
> > License server to complete the setup. It will only be serving Office
> Do you have 5 extra Office licenses? You'll need that to install & run
> Office on the TS box.
> > and a 3rd party app - that 3rd party app stays on the main server
> > and
> > short cuts and ini files are placed in each users profile on the TS
> > server.
> Make sure you set TS profile paths up for them in ADUC or via group policy.
> You can create a GPO for this and also lock down the TS box via policies.
> Too much to get into in one post, though.
> > I have read various articles, B Madden etc and MS stuff. None of this
> > explains the physical connections. EG, does the TS server need to
> > only be connected to the LAN to run?
> Yes. See above. If you *do* use ISA you will want to configure the TS box
> with the ISA config/client. I do not use ISA so I don't know how to tell you
> to do that.
> > Or does the Internet now have to
> > come through on the TS server and not the main server?
> No. And if you aren't using ISA nobody goes through the SBS box to get to
> the Internet anyway.
> > If so the
> > local network users would then need to access through that? The
> > proposed remote users are already on the domain server and so remote
> > access would need to link to these user accounts if possible.
> They will have only one account - the domain account.
> All users can connect to the TS box via the Remote Web Workplace page.
> (Connect to my company's application sharing server)
> > Local
> > Users on the local LAN will remain on the main server, they are not
> > thin clients locally. Remote users will use RDP on laptops with XP or
> > Vista. What would I need to add for Vista?
> Just make sure you've got all the updates & patches for SBS. Run the SBS
> Best Practices Analyzer.
> > Remote users would like to
> > access emails, can this be done in TS or do they need to go on using
> > OWA?
> They could use OWA, they could use TS, they could use RPC over HTTP (aka
> "Outlook Anywhere") on their existing laptops or remote PCs.
> Did you join the TS server to the domain using the /connectcomputer script?
> If not, move the server to the correct SBS OU.
> > There are several questions above so answers to each one would be
> > greatly appreciated.
> In the future it's best to break out your questions into separate posts, for
> what it's worth.
> > Remember I'm a newbie so don't assume anything,
> > I guess I need simple fully explained steps that take into account
> > all I have said above. Barry
> Hope this helps.