User Local Profiles.... Do you mean you guys use at the moment Roaming Profiles? I would host the roaming profiles as close to the users as possible and I assume it will be the same as you now or not? Now you have: LOCATION1 with DOMAIN1 LOCATION2 with DOMAIN2 In the future you will have (with option 2 and if you migrate domain2 objects to domain1... it could also be domain1 objects to domain2... migrate the SMALLEST domain to the other because that will be less work. Smallest domain in terms of number of objects to migrate, number of servers to migrate and data to re-acl): LOCATION1 WITH DOMAIN1 LOCATION2 WITH DOMAIN1 Host the roaming profiles for users in location1 on a server that is also in location1 Host the roaming profiles for users in location2 on a server that is also in location2 Have a DC in each location Setup site and replication topology and tweak that because of the ISDN line (you could is possible upgrade that line to something else thats faster) When users from location2 log on to clients from location1 you may think the roaming profile goes across the ISDN line. Well that would be true but some GPO settings exist to prevent that below some bandwidth threshold (default is 500Kb I think). Have a look at those to tweak them to meet your needs. How do you di that now? Do users have accounts and personal data (homedirectory and profile) in each location and domain? If so you might want to "merge" those Cheers, Jorge
________________________________ From: [EMAIL PROTECTED] on behalf of Ravi Dogra Sent: Sat 9/10/2005 4:55 AM To: [email protected] Subject: Re: [ActiveDir] Child Domain I will go with option 2 Jorge. But can u explain the effect on User Local Profiles for users on domain 2 when they are migrated to child domain. I am new to this organisation and i have no idea about why they have 2 AD's. Regards RD This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
<<inline: winmail.dat>>
