> From: Ski Kacoroski [mailto:[email protected]] > > Users can > easily be migrated via Microsoft tools (keeps all their information and > profile).
Thanks for your input - I'd like to know some more detail on the mentioned MS tools. Any terms I should google for? Truly, the one disadvantage that I'm aware of, merging everything into a single domain, is ... Well, for the finance and HR and managers who just care about "My Documents" and MS Office, no big deal; they get a new user profile, they don't really care. But for the developers, engineers, product verification, etc, who go to a lot of pains to install their development environment and configure everything "just so," it represents a real loss of time for them to be forced into a new user profile. So if we can facilitate that change, without causing too much difficulty for users, I'd really like to do it. Ideally, I guess I'd like to see, admin simply joins user's computer onto new domain, runs some utility to convert TheUser's profile from the old domain to the new domain. User logs in with the new domain (and possibly new username or password). Doesn't really notice or care about anything after that ... It's back to "business as usual" after a few minutes of hand-holding with some IT staff. Is this too much to hope for? The server resources - shares and whatnot - I'm confident we can handle seamlessly. As you mentioned, trust with the new domain, set permissions in the new domain based on pre-existing permissions. And then phase out the old domain. Users generally don't need to know or care. > Apps need to be rebuilt in the new domain. I think this was probably just a tangential comment, unrelated to anything I need to care about. But just to be sure... What do you mean? _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
