[sdw2003] GAL

[Tony Su]

:)
The swing migration kit Rick recommended is well worth the money to
avoid the things you're talking about. The info can be researched but
it's hard to know whether you really found all the articles you need and
whether what you found is reliable.

In a nutshell, with a Swing Migration

You create a temporary DC to hold your AD while you optionally wipe your
original machine and prepare your target machine (which can be the same
box).
When you "swing" off your source box and again when you "swing" to your
target you'll actually be intentionally creating duplicate AD objects
but destroying each in the nick of time before you actually cause a
conflict.

The Swing kit will describe each of the tools you need to edit and
destroy those AD objects, and yes... properly enabling/deploying the
GAL.

Many of us will swear by Jeff Middleton's Swing Migration as better than
the recommended upgrade and migration methods you'll see in MS KB
articles because it's low risk and can be accomplished without
disrupting a Production network more than a few seconds.

Tony

-----Original Message-----
From: sdw2003-bounces at mattware.com [mailto:sdw2003-bounces at mattware.com]
On Behalf Of James Eitzen
Sent: Thursday, September 04, 2008 12:26 PM
To: San Diego Windows 2003 User Group
Subject: [sdw2003] GAL

Ok,

So, we were trying to create a different default GAL. In doing so we
managed
to hose it, deny permissions were applied to the default global address
list
and now it is not accessible from the esm or the client.

In the ADSI editor I can not remove the entry that points to the old gal
and
I can not rename the new list to "default global address list" as it
says
the object already exists.

Any thoughts or recommendations are appreciated.

-- 
James Eitzen
_______________________________________________
sdw2003 mailing list
sdw2003 at mattware.com
http://lists.mattware.com/mailman/listinfo/sdw2003