Re: Clean SBS2003 install

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks for the info Steve.
TR

PS...once the migration is complete, do you have to do the 'connect
computer' process on the member servers and workstations?

"SteveB" <swb_mct@xxxxxxx> wrote in message
news:%23JcdSS4mGHA.4964@xxxxxxxxxxxxxxxxxxxxxxx
No, you have 30 days to activate and you don't activate the temp server.

There is one other related point.

You cannot run SBS2003 as a member server for more than a preset of amount
of time ( a few days ) because it has an enforcement system runninng that
requires that you promote it to a domain controller within a few days or
it will no longer let you login.

So dont install the temp server this week and then wait a week to promote
it to the temp replica domain controller.





"TR" <tsomething@somewhere> wrote in message
news:O9KDj%233mGHA.2252@xxxxxxxxxxxxxxxxxxxxxxx
Is there an issue with on-line activation with all of these intermediate
steps?
TR

"Steve" <newsgroup@xxxxxxxxxx> wrote in message
news:%23if59bvmGHA.4164@xxxxxxxxxxxxxxxxxxxxxxx
What was your source media for the Exchange install on the TempDC?

"SteveB" <swb_mct@xxxxxxx> wrote in message
news:eb8OYWvmGHA.2372@xxxxxxxxxxxxxxxxxxxxxxx
I did it that way and then moved all the mailboxes to the temp with move
mailbox feature, then later moved them back to orginal server.

The 'official' swing migration calls for restoring the original
exchange database back to the final server. Since I sometime get hung
up on exchange database restores working, I just moved the mailboxes
and then moved them back. Sort of the no brainer way to do it that
added an hour of data exchange but no chance of a screw up.





"TR" <tsomething@somewhere> wrote in message
news:%23Rm9XEvmGHA.3796@xxxxxxxxxxxxxxxxxxxxxxx
I can install Exchange on the TEMP DC too?
TR
"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



















.

Relevant Pages

  • Re: SBS 2003 - SBS 2008 migration issues
    ... The migration documentation starts and ends with the server, theres still plenty of things to do on the workstations. ... No part of the steps I followed in the migration failed as such, I just got to the end of it and still had plenty of work to complete. ... I'd expect the SBSMigration kit for SBS 2008 to be similar; allthough the way SBS 2008 is installed is way different than any previous version and therefore so will SBSMigration. ... A quick regedit and search for the original servers name shows vast quantities of entries. ...
    (microsoft.public.windows.server.sbs)
  • Re: Potential problems migrating from 4.5 to 2000 using different domain name
    ... I think this is the situation addressed in the migration upgrade white ... Create the new server from scratch, not connected to the existing LAN. ... copy the data immediately before shutting down the old SBS box. ... start changing over workstations, the whole thing should be foolproof. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: New SBS Server
    ... How many Workstations do you have? ... I did a Swing Migration ... Migration the Workstations plugged in to the new server without a hitch and ...
    (microsoft.public.windows.server.sbs)
  • Re: mail and ad migration
    ... I completed an ADMT migration. ... getting all the shortcuts and mapped drives on workstations working again. ... For step-by-step instructions to complete a server migration, ...
    (microsoft.public.windows.server.sbs)
  • RE: NT4 upgrade to 2k3 Server with WAN
    ... I have new exchange 2k3 ready to be installed and will import ... > You can use the migration or upgrade method to win2k3 domain. ... Use FSMT to migrate file server. ... >>workstations on the old domain to access info on the new domain. ...
    (microsoft.public.windows.server.migration)