Arthur Prokosch
2007-08-01 22:14:19 UTC
All --
After years of forgetting most details of best practices, primary vs
secondary domains, etc, I started prep for a server migration this
week.
The Situation: single-domain, single-PO system with 35ish users.
Administration been neglected for most of a decade. We don't use
Libraries, but are heavy users of shared folders.
The Goal: to move groupwise system to new box, and to end up with
everything better documented & closer to defaults.
The (very loose) Plan:
(1) Create a new single domain with new PO and new agent & gateway
objects
(2) Perform user moves (and resource and distribution list moves), say
in blocks of 10?
(3) Once the POA is populated, test new system and get to work on
configuring the gateways
Anyhow, I was doing testing out this process on dummy users and
objects, but wasn't remembering well enough (a) the distinction
between primary and secondary domain, or (b) the full significance of
the little "connect" plug on a domain. As a result, I now have two
out-of-sync views of what NEWPO contains. If I'm connected to OLDDOM,
it has only an external entity (TempResourceOwner). If I'm connected
to NEWDOM, it contains the one successful move (user jpublic). And a
distribution list I tried to move (Bogus Distribution List) is nowhere
to be found.
So...OT1H, this is all okay because they're useless test objects
anyhow. OTOH, I want to get my domains in sync with each other before
doing actual user moves, and if I'd be better off recreating NEWDOM, I
need to know that now. I've run Synchronize on a couple ConsoleOne
objects to no effect. I think what I need to do is Rebuild NEWDOM
from OLDDOM (I'm okay if jpublic disappears, no actual data there),
but I'm not completely confident that OLDDOM is still the primary.
How can I check?
And where should I be connected to at which parts of a user move to
make sure that all my domain databases stay in sync?
Any pointers to basic migration guides?
Thanks much,
-arthur prokosch
Online Services Manager
Third Sector New England
http://www.tsne.org/
After years of forgetting most details of best practices, primary vs
secondary domains, etc, I started prep for a server migration this
week.
The Situation: single-domain, single-PO system with 35ish users.
Administration been neglected for most of a decade. We don't use
Libraries, but are heavy users of shared folders.
The Goal: to move groupwise system to new box, and to end up with
everything better documented & closer to defaults.
The (very loose) Plan:
(1) Create a new single domain with new PO and new agent & gateway
objects
(2) Perform user moves (and resource and distribution list moves), say
in blocks of 10?
(3) Once the POA is populated, test new system and get to work on
configuring the gateways
Anyhow, I was doing testing out this process on dummy users and
objects, but wasn't remembering well enough (a) the distinction
between primary and secondary domain, or (b) the full significance of
the little "connect" plug on a domain. As a result, I now have two
out-of-sync views of what NEWPO contains. If I'm connected to OLDDOM,
it has only an external entity (TempResourceOwner). If I'm connected
to NEWDOM, it contains the one successful move (user jpublic). And a
distribution list I tried to move (Bogus Distribution List) is nowhere
to be found.
So...OT1H, this is all okay because they're useless test objects
anyhow. OTOH, I want to get my domains in sync with each other before
doing actual user moves, and if I'd be better off recreating NEWDOM, I
need to know that now. I've run Synchronize on a couple ConsoleOne
objects to no effect. I think what I need to do is Rebuild NEWDOM
from OLDDOM (I'm okay if jpublic disappears, no actual data there),
but I'm not completely confident that OLDDOM is still the primary.
How can I check?
And where should I be connected to at which parts of a user move to
make sure that all my domain databases stay in sync?
Any pointers to basic migration guides?
Thanks much,
-arthur prokosch
Online Services Manager
Third Sector New England
http://www.tsne.org/