Same computer being used in multiple Domains in multiple AD forrests
Posted on 2003-11-30
I have a notebook computer that I use as my primary workstation running WinXP Pro. It is part of a Win2k domain for my "main" job. Additionaly, I do some freelance consulting and have a couple Win2K (small business server) networks that I setup and maintain(each are completely seperate entities and have their own AD namespaces). Also, will probably want to install a similar configuration (win2k network with an AD structure/namespace) at my home.
I am "forced" to use a cisco VPN client for my "main" network(which i do not have admin access to); the other SBS networks I deal with support standard Win2K VPN client/connectivity.
How can I use the same notebook computer to log into whichever Win2k AD enabled network that I choose at the time. I am only worried about 1 session at a time, but if there is actually support for multiple XP login sessions into multiple domains at the same time (using different vpn connections or something) that would be interesting to hear.
I would like to walk into any of these locations, plug in the network cable, and log into the appropriate domain that I am in and have the computer able to "switch itself" to the correct domain and process login scripts, GPO policies, etc... just like the other workstations on that particular network; without fear that it is somehow "messing-up" workstation setting/configs that could cause problems when attempting to login/use the computer on other domains.
Is this possible? Can WinXP "support" being part of many AD domains and process GPO policies, etc.. appropriately depending upon which network it is plugged intio and what logon is used? I understand that I can use Terminal Server and Remote Desktop solutions to take over sessions of other computers on these disparate networks; that is not the solution I am looking for.
Any help/suggestions/best practice recommendations would be appreciated.