Re: Migration Delima Old Domain To New Domain
- From: "Frank McCallister SBS MVP" <anonymous>
- Date: Wed, 13 Sep 2006 19:05:56 -0500
Thanks Super G I got called away but it might very well be better for him to
start over the right way with that many WS's and Servers!
--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:u2Ha7A41GHA.4976@xxxxxxxxxxxxxxxxxxxxxxx
forgot a question.
Do you know of any reason why the new AD has been implemented?
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:OtDrx831GHA.3516@xxxxxxxxxxxxxxxxxxxxxxx
STOP!
I have to worry about the guy who installed SBS, first, as Frank points
out the most obvious way of introducing SBS to your original domain would
have been to keep the AD intact, secondly he takes a couple of weeks
holiday with a partially migrated domain in place.
Despite my concerns you need to speak to him before proceeding, find out
what his plan was, find out why he has approached the move in the manner
he has. Find out just how much has been moved, it may be easier to back
out and install SBS into your existing domain.
We can do some of this.
Has the installation process been completed in standard manner? Start,
Control Panel, Add/Remove programs, does an entry exist for 'Windows
Small Business Server 2003'?
Has the 'To Do List' been completed? (Do you have a 'To Do List'?) Start,
Server Management, To Do List.
Is there, on the desktop or in the recycle bin a shortcut to 'Continue
Setup'?
Have any of the workstations been moved to the new domain? or have they
all been moved and are accessing resources in the old domain via
passthrough authentication? Inspect the SBS, Start, Server Management,
Client Computers and Server Computers, what entries exist?
Is there content in the Exchange mailboxes and are people accessing these
boxes from Outlook? Server Management, Advanced Management, First
Organisation, Servers, SBS, First Storage Group, Mailbox Store,
Mailboxes.
Is CompanyWeb in use?
Are Shares and/or Printers accessed via the SBS?
Question to community, what else do we need to check?
<irtheman@xxxxxxxxx> wrote in message
news:1158172348.976291.91230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Greetings!
My problem is that I have been asked to migrate our users from our old
domain (windows 2003 active directory) to a new domain (windows 2003
sbs) and there are few hitches that I am not sure how to approach. I
am inexperienced with ADs and domains but things like this get dumped
on me often and this time I am stumped. I want to tell you what things
were like before and how they are now so forgive me if this gets wordy.
Here is a quick run-down:
My company has been using "AppSci" as their domain for a long time.
For servers the domain has a windows 2003 machine called "Office"
running the Active Directory as the PDC, one windows 2000 machine
called "Dns1" running the DNS and acting as SDC, one windows 2003
machine running a mail server, and about 5 other windows 2003 servers
that just hold data. There are about 25 employee accounts, 37
workstations (mix of windows 2000 pro and windows xp pro), and 10
printers (4 connected directly to the lan and 6 connected via host pc).
The company wanted to upgrade their mail server to MS Exchange 2003 and
decided to go with SBS 2003 which was installed on a new pc called
"asasbs" by a local pc support/repair person who is gone for the next
few weeks on vacation. I don't know the exact details of how he
installed all of this but we now have a new domain called "ASA" running
on asasbs as a PDC with all the bells-and-whistles and completely
parallel to our AppSci domain with now modifications to Office or Dns1.
It appears that the user accounts were migrated over by hand so the
Exchange server could be used in place of our old mail server. The ASA
domain is currently on the same ip address range as our other AppSci
domain and apparently the magic of DNS and duplicate accounts in both
domains make it possible for us to use asasbs for sending and receiving
email thus retiring our old mail server.
All the users, computers, printers, and servers are still using the
AppSci domain but Office is getting full. The bright idea from the
higher-ups is to move everyone to the new domain and have them use the
much more powerful and larger asasbs while retiring Office and just
using it for storage. There are no roaming profiles here and it has to
remain that way. I have to move all these computers, printers and
servers to the new ASA domain. Then I have to somehow convert all the
local and domain profiles on every computer so they work perfectly
under the new ASA domain. All of this while causing as little
disturbance as possible.
At present I feel like I have to do a lot of running around to manually
migrate all of these things. I need to manually add the printers to
the ASA domain. Then I have to go to each machine and convert any
domain profiles to local profiles using tips found in the newsgroups
followed by connection to http://asasbs/connectcomputer. Uggg! Sounds
like a nightmare!
If you can offer any help or suggestions at all I would really
appreciate it.
That was a lot writing up there but hopefully it will answer any
questions you might have when suggesting a solution.
Thank You!
Matthew Hanna
.
- References:
- Migration Delima Old Domain To New Domain
- From: irtheman
- Re: Migration Delima Old Domain To New Domain
- From: SuperGumby [SBS MVP]
- Re: Migration Delima Old Domain To New Domain
- From: SuperGumby [SBS MVP]
- Migration Delima Old Domain To New Domain
- Prev by Date: Re: 550 Missing purported...
- Next by Date: RE: ISA 2004 REPORT FAILURE
- Previous by thread: Re: Migration Delima Old Domain To New Domain
- Next by thread: Re: Migration Delima Old Domain To New Domain
- Index(es):
Relevant Pages
|
