xp @ home is like having a car but no where to go. It's more fun to have other cars on the road to play chicken with (ie. set a network up). Never used anything but the pro version, so knowledge is limited, but It's the domain system and the permissions that are different, IMLK (in my limited knowledge).
We use either Remote Desktop (Terminal Service) or Dameware to remote admin the W2K/XP servers and its pretty good. Leaves obvious security holes, but allows us to admin 24/7 all our severs (we're global). Dameware is awesome for desktops, cause if it ain't on the remote host, and you have the right access it installs itself! (without a reboot). Remote Desktop makes you login to the server your trying to admin, so a local PC admin, won't allow server admins unless they have the right account.
Although you wanna do something, try WSH (windows scripting host) with the right accounts. Basically a helpful (depending on usage) virus. Good idea but f'ing scary.
EDIT: Also you probably don't want an XP desktop, you'd get more value out of a server/client arch. Although would be 'spensive to set up. Try getting your training course to set up a TEST domain and clients.
MSCE's are good but I'd rather hire people with hands on experience.
DBL EDIT: On a networking side it's the XP domain structure thats trickyish. Although the best networking experience outside an OS I got was setting up a public/private structure (NAT/No NAT) on my DSL router. That effected the lowest few layers of the stack. (Took a month to get stable, self taught!)
__________________
[color=bright blue]W[/color]e Stick To Glass
"If three of us travel together, I shall find two teachers."
Confucious
Last edited by Mad_Gecko; 09-19-2003 at 02:00 PM..
|