Migrating an SBS network into a larger domain Andrew Mackintosh 10.07.2007 05:20:02 Hi, One of my clients running SBS is merging with a larger company running full version products over 12 servers. I am wanting to migrate everything to the larger company's domain. This includes 30 users and their mailboxes, 30 PCs, a terminal server, and their data. I am hoping to get some advice about the best way to approach this. As I see it there are two broad routes: a) Upgrade using the transition packs on the SBS network and create trust relationships to the larger domain. b) Use ADMT and Exchange Server Migration Wizard to migrate everything to the larger domain (including the terminal server) then shutdown the SBS box. At the moment, I am leaning toward b as it doesn't require the transition pack, and gives a simpler final product. Can anyone advise on possible gotcha's with the two methods?

Re: Migrating an SBS network into a larger domain "kj [SBS MVP]" <KevinJ.SBS[ at ]SPAMFREE.gmail.com> 10.07.2007 05:47:26 Andrew Mackintosh wrote: [Quoted Text] > Hi, > > One of my clients running SBS is merging with a larger company > running full version products over 12 servers. > > I am wanting to migrate everything to the larger company's domain. > This includes 30 users and their mailboxes, 30 PCs, a terminal > server, and their data. > > I am hoping to get some advice about the best way to approach this. > As I see it there are two broad routes: > a) Upgrade using the transition packs on the SBS network and create > trust relationships to the larger domain. > b) Use ADMT and Exchange Server Migration Wizard to migrate > everything to the larger domain (including the terminal server) then > shutdown the SBS box. > > At the moment, I am leaning toward b as it doesn't require the > transition pack, and gives a simpler final product. > > Can anyone advise on possible gotcha's with the two methods? You probably should have a clear picture of what the new parent has in mind for it's new acquisition. Will your users be assimilated into their (single domain?) forest? Will retaining the investment in user CALs be important, or does the parent want them under their licensing model. 30 users make for an 'interesting' migration scale. Just about too big to scrap, nearly too small to make ADMT worthwhile. What's the parent IT admin have to say? -- /kj

Re: Migrating an SBS network into a larger domain Andrew Mackintosh 10.07.2007 21:10:02 I'm still discussing just what it is the new network needs to be. The perference would be to have all users and PCs in the same domain (single forest, single domain). However, in a few months, this new network will be transitioned into a much larger standardised international network. This means that at the moment, the priority for this smaller merge is speed and ease of migration, rather than the best / tidiest final network. This means if its easier to have 2 domains with trusts, then that's fine. Thanks for the tip though, I will look into the licensing side of things. We are going to be the merged networks IT support. I'm not sure exactly what help we will get from the larger company's current IT support, but am looking into it currently.

Re: Migrating an SBS network into a larger domain "Henry Craven {SBS-MVP}" <sme[ at ]nevernever.lan> 10.07.2007 22:02:24 This may be a rod worth exploring: http://www.windowsitpro.com/Articles/ArticleID/45933/45933.html?Ad=1 ---Quote--- The free Microsoft Identity Integration Feature Pack 1a for Windows Server Active Directory, which is a subset of Microsoft Identity Integration Server (MIIS) 2003 Enterprise Edition, lets you take advantage of MIIS's directory synchronization features to synchronize AD forests. The full MIIS 2003 Enterprise Edition lets a large organization connect scores of different directories and databases for a full identity-management solution. Smaller companies that don't have the resources to roll out a full MIIS implementation can deploy Identity Integration Feature Pack 1a, which supports integration between AD and AD Application Mode (ADAM) installations and comes with a management agent for the AD Global Address List (GAL). The agent is preconfigured with rules for synchronizing data between AD forests in which you've enabled Exchange Server 2003 or Exchange 2000 Server to create a GAL across the entire enterprise. . . . --------- -- Henry Craven {SBS-MVP} "Andrew Mackintosh" <AndrewMackintosh[ at ]discussions.microsoft.com> wrote in message news:97D534BC-811D-4B40-9883-5D4235E698B1[ at ]microsoft.com... [Quoted Text] > I'm still discussing just what it is the new network needs to be. The > perference would be to have all users and PCs in the same domain (single > forest, single domain). > > However, in a few months, this new network will be transitioned into a > much > larger standardised international network. This means that at the moment, > the priority for this smaller merge is speed and ease of migration, rather > than the best / tidiest final network. This means if its easier to have 2 > domains with trusts, then that's fine. > > Thanks for the tip though, I will look into the licensing side of things. > We are going to be the merged networks IT support. I'm not sure exactly > what > help we will get from the larger company's current IT support, but am > looking > into it currently.