Re: Transfering Active Directory Information from old SBS to new S
- From: "Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 6 Feb 2006 14:08:27 -0800
Thanks for the reply,
I've managed to remove the references to the old Domain Controller.
Unfortunately Exchange will now not install. When I use the SBS setup
wizard, the option to install Exchange remains steadfastly unticked and no
matter how many times I change the option to "install" it simply reverts to
blank. Any idea as to why this might be so because there is no information
given by the wizard.
"SuperGumby [SBS MVP]" wrote:
Brian, people are both watching and answering your posts, however we can.
only go 'so far'.
Please note before continuing: JeffM is a person I consider a friend but if
you google this group you will seee multiple references where other friends
have suggested www.sbsmigration.com and I have told the OP it is unnecessary
in their circumstances. I use a similar 'migration strategy' developed
before Jeff gave me access to his procedure.
and on to the meat.
Your AD believes it cannot connect to all domain controllers. Whether this
is true or not is irrelevent, AD has a reference somewhere which is stopping
you from going further. This is, UMMM, easily rectified, use MS tools/KB's
to identify why. The various AD consoles my help, ADSIEDIT may be useful,
NTDSUTIL also, but if you're heading off on your own on this you can expect
to put in some hard time. I _know_, I _have_, and I bear the scars to prove
it.
The alternative is to stop wasting your time and use a proven process (which
includes 'domain audit' tools) to achieve your goal.
"Brian" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:898A5A1E-539A-420E-9577-517DF0FD2E18@xxxxxxxxxxxxxxxx
Because of what you said, I decided to review the dcpromo method and to
redo
everything, step by step, to make sure I had missed nothing.
I am now at the stage where I have seized control of all the fsmo roles.
Made the new sbs (to be) server the global catalog server. Suddenly
though,
I have hit a strange new twist. I disconnected the new sbs server from
the
network to make sure it was not going to fight with the old sbs server,
while
I installed SBS. I then rebooted the server in order to make the global
catalog "take".
I then started the installation of SBS. Once it had done its checking,
it
reports that it is "unable to contact all domain controllers" and refuses
to
progress further in the installation.
As far as I am aware, this server is now the only domain controller on its
own network. All other references to the old SBS have been expunged from
the AD "Sites and Services" command module. It is the global catalog
server. It has "seized" all the roles.
So what gives?
Why isn't anybody answering my messages?
"Susan Bradley, CPA aka Ebitz - SBS Rocks" wrote:
Then we need to debug that.
As that is the sbsmigration method and it should work just fine.
Brian wrote:
""Justin Crosby [MSFT]"" wrote:
Hello Brian,
Please review:
http://go.microsoft.com/fwlink/?LinkId=16414 (uses ADMT) and
I'm migrating SBS 2003 to SBS 2003, not 2000 to 2003.
http://support.microsoft.com/kb/884453/en-us (uses DCPROMO)
Tried that one. As I pointed out, for some reason as a consequence of
these
method, sharepoint will not then install. Didn't you read my previous
message? :-|
- References:
- Re: Transfering Active Directory Information from old SBS to new S
- From: SuperGumby [SBS MVP]
- Re: Transfering Active Directory Information from old SBS to new S
- Prev by Date: Re: actually feeling ripped off by microsoft, I'd like input from
- Next by Date: Re: Authentication failures
- Previous by thread: Re: Transfering Active Directory Information from old SBS to new S
- Next by thread: Re: How do I setup a inhouse exchange server?
- Index(es):
Relevant Pages
|
Loading
