Hmmm... the article I linked to above works somewhat. It lest you browse the domains in the Network Neighborhood but they don’t show as a login domain.
Establishing a connection between both domains and putting in place a trust between them is sadly not an option. I did some googling and found a lot of this kind of questions but they all come down to the same answers.
-Add the computer to the domain each time the user switches domains.
This will prevent the user from accessing the "old" domain. I can’t/won’t ask my users to do this so this is not an option.
-Establish a connection and a trust between both domains.
They need the two companies to have strictly separated networks and due to limited funding (it is a small office and they need to pay for this themselves) this is not an option.
-Have the roaming user(s) setup terminal server session on each foreign network and a regular login at the home network.
This might be an option. Will investigate.
-Using hardware profiles.
I doubt it but I’ll have a look at it.
-Writing some kind of app that does the domain switching for the user. Restarts the system and lets them logon.
Sort of the same as the first option.
The terminal server option is my favorite for now but I’ll look into some of the other options.
_________________________
Mart
- Chuck Norris once sold ebay to ebay on ebay.
