Site to Site Network

[Moby-Dick]

Workstation profiles are designed to run on a workstation , where as TS profiles are more server based. There are ways round it however.

more info here :

http://www.msterminalservices.org/ar...challenge.html

[Jay]

ok

So if I do what i have said

eg this will only be a basic test

I will setup terminal services on a Win2000 server system (i think its about £60 a licence) Create a Terminal Service Profile in AD

Then Connect via VPN from an outside line to the server, use remote desktop and log in using the name and password of the TS profile I just created

If this works I assume I need to make sure I got to mmc and force "Delete cached copies of roaming profiles"?

also currently in AD - User Properties - Profile, i set a H: drive to connect as a "home folder" and also setup a profile on the disk and use the profile path in the "User profile" section. I assume this would now be ok to use with TS?

[Moby-Dick]

you can certainly deploy H drives within TS. Also ensure that your group policy is set up correctly to prevent accidental missues of the TS drives ( ie hide the C: drive ! )

[Jay]

you can certainly deploy H drives within TS. Also ensure that your group policy is set up correctly to prevent accidental missues of the TS drives ( ie hide the C: drive ! )

good point

I have worked with citrix in the past so i assume the setup for citrix users would also work for TS users?

If i do all the above do you think this should work?

[Moby-Dick]

Citrix has some subtle differences ( has been a while since I've played with it )

Sounds liike your test should work in principle ( I think you can set up trial 120 TS licences without the need for a licencing server on win2k - it changes again when you use 2003 ) you'll only know once you try !

[Jay]

Citrix has some subtle differences ( has been a while since I've played with it )

Sounds liike your test should work in principle ( I think you can set up trial 120 TS licences without the need for a licencing server on win2k - it changes again when you use 2003 )

well i'll test it if it works then I will need to start looking at bandwith. The switches you pointed me to look fantastic for the money. What switch would you advise and you didn't seem to think SDSL was a good idea, what have you used in the past?

[Moby-Dick]

Its not that SDSL is a bad idea , I just havn't played much with hardware for it

The draytek ethernet routers should work fine for your branch offices + they are quite admin friendly in terms of configuration. Stability is very important , as if you loose conntectivity , you'll have 4 people who suddenly can't work at all ! Ensure that you have tested any hardware to your own satisfaction before deploying it to your branch sites.

What do you currently have at your HQ ?

I wouldn't nessesarily use a combined SDSL router / modem / firewall. You'll possibly end up with greater flexibility with a seperate firewall. Ensure that all your services will enable your firewall / VPn end point to have a public IP address. NAT and VPN's do not make good bedfellows

[Jay]

Currently we have just a standard ADSL Connection, Router, firewall and a single Dell Server running the Domain. I left the company 12months ago after setting up this small office network (it worked well for them)

They have now asked me to rejoin as they have expanded and need this setting up. They know what they want it to do but of course they have no idea the amount of work this is going to be.

I need to get these tests started to show that this is a viable way of setting up the network, once they see that it works they will give me the funds I need to make this really a small / medium business network. I also see that this type of setup is easily scalable so any growth after the initial setup will be easy to accommodate.

The main reason for this setup is that people work at different sites nearly every day but need access to their info. Data protection means they can not carry it on them and it must stay within our network.

Its going to be a pain to setup be I see that once its up and running it should be easier to maintain than the current setup of lots of small individual networks and me with a setof tapes driving round the sites all the time to backup / move data around.

[Moby-Dick]

Using something like a hosted sharepoint portal (alternate collaboration software ) wouldn't be practical then ?

Are these road warriors with laptops ? ( if theres info you'd rather not post in public , feel free to Pm me )

[Jay]

no, they will only use the network from the sites, there will be no initial users that are on the road.

Apart from myself that is!

I could see that in the future there may be a max of 2 people who wish to work from home.

[Moby-Dick]

You should be ok then

one last thing - your domain controller / file server is going to be a seperate box from the terminal server isn't it ?

[Jay]

yes

I will put the actual TS/apps on one server and the file server / DC / AD will be on another server. I will also use a seperate email server.

[Jay]

thanks for your help on this by the way.

and don't worry, this wont be my last post in this thread i bet! lol

also if I have some sort of PDF printing solution would this help with the bandwith issues while printing?

[Moby-Dick]

thats ok , bill's in the post

If you are considering a complete refresh , then there are a couple of other solutions that do work that I can recommend that may work out cheaper.

If look you at SBS2003 , not only would it include Exchange and a couple of other interesting features , it has some very usefull remote working features that 'Vanilla' 2k3 server doesn't have. Namely the 'Remote Web workspace' ( have a google for it ) , which allows you to remote connect to client machines in HQ from the branch. You'd then have a pool of headless workstations in your server room ( or workstation blades if you are posh ) that would correspond with the branch system.

these are accessed via an SSL RDP session ( so pretty safe if you have godd passwords )

You woudl be doubling up on workstations , but would save the costs of a terminal server + licences + hassle

[Jay]

thats ok , bill's in the post

If you are considering a complete refresh , then there are a couple of other solutions that do work that I can recommend that may work out cheaper.

If look you at SBS2003 , not only would it include Exchange and a couple of other interesting features , it has some very usefull remote working features that 'Vanilla' 2k3 server doesn't have. Namely the 'Remote Web workspace' ( have a google for it ) , which allows you to remote connect to client machines in HQ from the branch. You'd then have a pool of headless workstations in your server room ( or workstation blades if you are posh ) that would correspond with the branch system.

these are accessed via an SSL RDP session ( so pretty safe if you have godd passwords )

You woudl be doubling up on workstations , but would save the costs of a terminal server + licences + hassle

Fantastic!

I'll look into this right now!

I could probably just get a full setup from a company like HP or Dell (I know we all wince when we hear these names but they will offer a next business day warranty and take the haste off my back!)

[Moby-Dick]

Dont let Dell install it I've seen their SBS builds and they where attrocious.

I dont wince when I hear HP ( that may be something to do with the 300 HP servers in the room next door to me ) Their Workstations are no frills and will do the job you need them to do .