Re: Clean SBS2003 install
- From: "Steve" <newsgroup@xxxxxxxxxx>
- Date: Wed, 28 Jun 2006 10:04:16 -0700
The usual cause for this is that the Windows 2003 SP1 firewall is turned on
and must be off before you dcpromo the TempDC and then again on the final
DC. Jeff has this documented as well.
"SteveB" <swb_mct@xxxxxxx> wrote in message
news:uGBTiNtmGHA.1488@xxxxxxxxxxxxxxxxxxxxxxx
On this subject keep this somewhere. When adding a second domain
controller to the domain in this process, the new server sometimes does
not ends up with missing SYSVOL and NETLOGON shares and it will seem like
there is no way to fix it. ( it happened on two migrations this month
that I was doing)
Credit goes to someone on experts-exchange.com
This is the Fix
Rebuild Sysvol for the domain and wake up the new DC.
1) Stop the FRS service on both DCs.
2) On the primary DC (the one with the GOOD sysvol), open Regedit and
find this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Cumulative
Replica Sets\GUID\BurFlags
(where GUID is the domain GUID)
3) Change the value of this entry to D4
4) On the other server, open Regedit and go to the same key but set the
value to D2.
5) Start the FRS service on the server you made D4 *FIRST* - this is
important.
6) Wait a few minutes.
7) Start the FRS service on the server you made D2.
8) Go have a coffee.
be patient. Don't force anything after this, but let the errors stabilize
so we can see if there are any other things going on.
"TR" <tsomething@somewhere> wrote in message
news:ehVvQ1smGHA.1912@xxxxxxxxxxxxxxxxxxxxxxx
The existing SBS2K is 2.4GHZ dual Xeon with 2 GB memory, RAID SATA drives
and dual GB NIC's. I will be adding more memory and the drives array is
being increased.
Does this mean I do just a minimal install of W2K3 and Exchange 2K3 on
the TempDC using the SBS2K3 CD's?
oohhh i guess this is all detailed in the the Kit?
Thanks
TR
"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:OeSKuismGHA.5100@xxxxxxxxxxxxxxxxxxxxxxx
Swing covers the return to the original hardware (are its specs good
enough for SBS 2003?). You will need a computer to be the temp DC but it
can be relatively low end. Your down time will be at the final step when
you have to swing back to your original box with the SBS 2003 install,
but hopefully that will be minimal down time especially since you won't
need to touch the workstations in the process.
"TR" <tsomething@somewhere> wrote in message
news:egUf3NsmGHA.2316@xxxxxxxxxxxxxxxxxxxxxxx
Yes, I am interested and it sounds like what I need except that we are
not purchasing new hardware.
The clean install of SBS2K3 needs to be on the existing SBS2K box.
Does the swing migration cover this and how much downtime is there?
Can the network continue to function while i bring down the existing
SBS2K box and do a clean install of SBS2K3 on it?
TR
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:ObsyturmGHA.3752@xxxxxxxxxxxxxxxxxxxxxxx
Yes, Swing It! is a process described by Jeff at www.sbsmigration.com.
It is, basically, a defined process of using MS KB's to satisfy
several things.
You wish to move from SBS 2000 to SBS 2003. Not for normal reasons
(ie. because we don't like to) but due to problems with the existing
installation you would prefer NOT to upgrade the current system
directly, a 'clean' installation is considered desirable. Yes?
In the process of replacing this 'dodgy old server' with a new one,
you 'do not want to lose the desktops, settings, and profiles for all
users.', Yes?
During the process you do not wish to switch:
2 member W2K Server boxes running various proprietary applications
1 member W2K Server box running in Terminal Server Application mode
1 member W2K3 Enteprise Box running a propietary database and web
application
to a workgroup and then into the newly created AD. right?
You'd also like to avoid having to touch 15 workstations, swinging
them to workgroup and back to the newly created AD. right?
I'm guessing that you would also like to maintain both the same
primary server name and AD DNS & NETBIOS domain names. right?
and you'd like to minimise downtime through the whole procedure.
right?
www.sbsmigration.com and the Swing It! procedure allow you to
accomplish all of this. As well as the not easily replicated procedure
(which basically consists of following a series of MS KB articles)
Jeff's product includes tools which make auditing the existing AD and
recreating various items easier. And includes 'support' of the
project.
Interested?
"TR" <tsomething@somewhere> wrote in message
news:Oqd2KgrmGHA.3632@xxxxxxxxxxxxxxxxxxxxxxx
Is there a kit that needs to be purchased for this swing migration?
TR
"Arthur" <mynewsgroupaccount@xxxxxxxxxxxxxx> wrote in message
news:ewUMyWjmGHA.4052@xxxxxxxxxxxxxxxxxxxxxxx
"Swing it"
It will save you so much grief :o)
"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:eO7H5HjmGHA.748@xxxxxxxxxxxxxxxxxxxxxxx
This Steve agrees that using a swing migration will probably be
best for your needs.
"SteveB" <swb_mct@xxxxxxx> wrote in message
news:ewjE60imGHA.3632@xxxxxxxxxxxxxxxxxxxxxxx
Then you are talking about a full Swing Migration. This only takes
a temporary computer to use as the inermediary. It can be any old
p3 workstation with 512 ram and reliable drive.
You can use the same SBS 2003 media to install right out for i386
folder and exchange out of the Setup folder for the temporary
computer. You dont want to run the SBS2003 shell on the temp, Just
Server and Exchange.
"TR" <tsomething@somewhere> wrote in message
news:ebmt1timGHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
The clean install of SBS2K3 is to be on the same box as the old
SBS2K. For Budget reasons we are not adding a new server, we will
be using the existing server hardware as it is still quite
capable.
TR
"SteveB" <swb_mct@xxxxxxx> wrote in message
news:%2351tAnimGHA.1552@xxxxxxxxxxxxxxxxxxxxxxx
Are you sure you want to abandon the old domain identity. It is
pretty simple to retain the old domain and account identies when
you do the new clean install with the new server by making it a
second domain controller in the existing domain, tranfering FSMO
roles, moving mailboxes and Exchange roles etc. I use Jeff
Middletons Swing Migration as guidance to deal with the the
behind the scenes adustments.
This gives you a clean install without days of 'H" getting the
clients and member servers straighted out. This is a great time
saver, headache saver and you learn something that useful.
To answer your question, this is how you can save profiles. If
there is a better way I would like to know.
1. join the member server to the new domain
2. login with the new instance of the the users new domain
account
3. Restart the serve and log in with another admin account
4. Make sure the user is an admin of the machine you are on, or
the old ntuser.dat file will not be read. ( i dont know why )
5. empty the Contents of the new user profile folder. Not the
folder
6. Copy the contents of the old users profile folder to the new
empty profile folder that was created when you logged in with
his account for first time.
Thats it, it works every time . . but maybe there is a better
way.
however you will be a MUCH happier if you migrate the old domain
and accounts to the new server using the method I describe
above. I highly recommend getting the current version of Jeff
Middleton Swing Migration kit. Just find it with Google.
You are not doing a full swing but all the right info is in
there for active directory cleanup and role tranfers.
"TR" <tsomething@somewhere> wrote in message
news:%230837ZimGHA.2112@xxxxxxxxxxxxxxxxxxxxxxx
I have a client network I am supporting that is running SBS2K
Premium. They have finally decided to upgrade to SBS2003
Premium. This company has gone through many IT support changes
over the last 5 years. The SBS2K box is really messed up and the
decision has been made for obvious reasons to backup all data,
do a clean install of SBS2003 and start fresh with a new Domain.
The configuration of the network right now is:
1 SBS2K Box
2 member W2K Server boxes running various proprietary
applications
1 member W2K Server box running in Terminal Server Application
mode
1 member W2K3 Enteprise Box running a propietary database and
web application
15 Workstations running WinXP PRo
3 Laptops running WinXP Pro
I do not want to lose the desktops, settings, and profiles for
all users. I know I can use the Settings and Transfer Wizard
for the Workstations, but is there anything that I can use so
that I do not lose the desktops and settings of the domain
accounts for the server boxes?
Thanks
TR
.
- Follow-Ups:
- Re: Clean SBS2003 install
- From: TR
- Re: Clean SBS2003 install
- References:
- Clean SBS2003 install
- From: TR
- Re: Clean SBS2003 install
- From: SteveB
- Re: Clean SBS2003 install
- From: TR
- Re: Clean SBS2003 install
- From: SteveB
- Re: Clean SBS2003 install
- From: Steve
- Re: Clean SBS2003 install
- From: Arthur
- Re: Clean SBS2003 install
- From: TR
- Re: Clean SBS2003 install
- From: SuperGumby [SBS MVP]
- Re: Clean SBS2003 install
- From: TR
- Re: Clean SBS2003 install
- From: Steve
- Re: Clean SBS2003 install
- From: TR
- Re: Clean SBS2003 install
- From: SteveB
- Clean SBS2003 install
- Prev by Date: Re: Update SBS2003 Premium with WSUS
- Next by Date: Re: Display question in Outlook/Exchange
- Previous by thread: Re: Clean SBS2003 install
- Next by thread: Re: Clean SBS2003 install
- Index(es):
Relevant Pages
|