way migate to new computer?

Hi,
Can anyone please suggest a simple way to migrate/copy the relevant
information to keep the client computers happy after I connect them to a new
domain? Should I use the same domain name, user names etc?

I have a sbs2003 server that is almost impossible to manage due to
corruption. I have bought another computer which I have just installed the
same OS onto.
I am thinking of completing the installation all the way(to domain
controller add users etc) There are only 10 users that use the server and
only a few programs that need to be reinstalled. Due to the level of
corruption it is not practicle to use the microsoft KB article(Migrating
Windows Small Business Server 2003 to New Hardware) as I cant get some of
the required tools to run.
I am thinking it is easier to do a fresh install but is there a way to
minimize disruption to the users when I phyically disconnect the the client
computers and reconnect to the new server? the only programs and settings
that are essential for the users are the office suite if this makes any
difference.
I would appreciate anyones thought on the best way to go
regards

 

you might consider talking to the folks at sbsmigration.com


--
Cris Hanna [SBS - MVP]
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.


"Eric S" <eistacey@adam.com.au> wrote in message news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
Hi,
Can anyone please suggest a simple way to migrate/copy the relevant
information to keep the client computers happy after I connect them to a new
domain? Should I use the same domain name, user names etc?

I have a sbs2003 server that is almost impossible to manage due to
corruption. I have bought another computer which I have just installed the
same OS onto.
I am thinking of completing the installation all the way(to domain
controller add users etc) There are only 10 users that use the server and
only a few programs that need to be reinstalled. Due to the level of
corruption it is not practicle to use the microsoft KB article(Migrating
Windows Small Business Server 2003 to New Hardware) as I cant get some of
the required tools to run.
I am thinking it is easier to do a fresh install but is there a way to
minimize disruption to the users when I phyically disconnect the the client
computers and reconnect to the new server? the only programs and settings
that are essential for the users are the office suite if this makes any
difference.
I would appreciate anyones thought on the best way to go
regards

 

When you create a Windows domain, it installs its own unique Security ID, or
SID. Each user and computer that connect to that domain are also assigned a
unique SID, so that you can't have duplicate computer names or numbers.
When you attach an existing computer to a new root domain controller, which
SBS is, you get a new sid, so you have to disjoin from the old SBS domain
then join the new SBS domain, which is a new user and a new SID, for both
the user and the computer. This is part of Windows Server security, and is
not unique to SBS.

The only way to preserve all the settings for the users is to copy them out
and back to the new profile, in XP that's c:\documents and
settings\user.domain.

SBS Migration has figured out a way to preserve all the original settings,
the server name and the domain name, all the shares and permissions, and all
the emails, and to do it off line while the old box continues to run. The
only thing carried over from the old server to the new one is the AD,
including the users and computers with their SIDS. The only downtime of any
significance is the actual moving of the user data from SBS_OLD to SBS_NEW.

Highly recommended.

--
Larry
Please post the resolution to your
issue so that others may benefit.


"Cris Hanna [SBS - MVP]" <crisnospamhanna@cpunospamservices.net> wrote in
message news:uIV6VXh3JHA.2336@TK2MSFTNGP02.phx.gbl...
you might consider talking to the folks at sbsmigration.com


--
Cris Hanna [SBS - MVP]
Co-Contributor, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
Owner, CPU Services, Belleville, IL
A Microsoft Registered Partner
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.


"Eric S" <eistacey@adam.com.au> wrote in message
news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
Hi,
Can anyone please suggest a simple way to migrate/copy the relevant
information to keep the client computers happy after I connect them to a new
domain? Should I use the same domain name, user names etc?

I have a sbs2003 server that is almost impossible to manage due to
corruption. I have bought another computer which I have just installed the
same OS onto.
I am thinking of completing the installation all the way(to domain
controller add users etc) There are only 10 users that use the server and
only a few programs that need to be reinstalled. Due to the level of
corruption it is not practicle to use the microsoft KB article(Migrating
Windows Small Business Server 2003 to New Hardware) as I cant get some of
the required tools to run.
I am thinking it is easier to do a fresh install but is there a way to
minimize disruption to the users when I phyically disconnect the the client
computers and reconnect to the new server? the only programs and settings
that are essential for the users are the office suite if this makes any
difference.
I would appreciate anyones thought on the best way to go
regards

 

If you just need (Office 2003) settings, the Office 'Save My Settings
Wizards' may be the way to go for each user account.

If you need more (like Favorites, etc.), theWindows XP Files and Settings
Transfer Wizard may do what you need:

Step-by-Step Guide to Migrating Files and Settings
http://technet.microsoft.com/en-us/library/bb457074.aspx

or maybe the User State Migration Tool...

Description of the User State Migration Tool for Windows XP Professional
http://support.microsoft.com/Default.aspx?kbid=321197

User Profile Wiaard has also been mentioned in similar posts
http://www.forensit.com/domain-migration.html

--
Merv Porter [SBS-MVP]
============================

"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
message news:eHYmmUj3JHA.5728@TK2MSFTNGP03.phx.gbl...
> When you create a Windows domain, it installs its own unique Security ID,
> or SID. Each user and computer that connect to that domain are also
> assigned a unique SID, so that you can't have duplicate computer names or
> numbers. When you attach an existing computer to a new root domain
> controller, which SBS is, you get a new sid, so you have to disjoin from
> the old SBS domain then join the new SBS domain, which is a new user and a
> new SID, for both the user and the computer. This is part of Windows
> Server security, and is not unique to SBS.
>
> The only way to preserve all the settings for the users is to copy them
> out and back to the new profile, in XP that's c:\documents and
> settings\user.domain.
>
> SBS Migration has figured out a way to preserve all the original settings,
> the server name and the domain name, all the shares and permissions, and
> all the emails, and to do it off line while the old box continues to run.
> The only thing carried over from the old server to the new one is the AD,
> including the users and computers with their SIDS. The only downtime of
> any significance is the actual moving of the user data from SBS_OLD to
> SBS_NEW.
>
> Highly recommended.
>
> --
> Larry
> Please post the resolution to your
> issue so that others may benefit.
>
>
> "Cris Hanna [SBS - MVP]" <crisnospamhanna@cpunospamservices.net> wrote in
> message news:uIV6VXh3JHA.2336@TK2MSFTNGP02.phx.gbl...
> you might consider talking to the folks at sbsmigration.com
>
>
> --
> Cris Hanna [SBS - MVP]
> Co-Contributor, Windows Small Business Server 2008 Unleashed
> http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
> Owner, CPU Services, Belleville, IL
> A Microsoft Registered Partner
> ------------------------------------
> MVPs do not work for Microsoft
> Please do not submit questions directly to me.
>
>
> "Eric S" <eistacey@adam.com.au> wrote in message
> news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
> Hi,
> Can anyone please suggest a simple way to migrate/copy the relevant
> information to keep the client computers happy after I connect them to a
> new
> domain? Should I use the same domain name, user names etc?
>
> I have a sbs2003 server that is almost impossible to manage due to
> corruption. I have bought another computer which I have just installed the
> same OS onto.
> I am thinking of completing the installation all the way(to domain
> controller add users etc) There are only 10 users that use the server and
> only a few programs that need to be reinstalled. Due to the level of
> corruption it is not practicle to use the microsoft KB article(Migrating
> Windows Small Business Server 2003 to New Hardware) as I cant get some of
> the required tools to run.
> I am thinking it is easier to do a fresh install but is there a way to
> minimize disruption to the users when I phyically disconnect the the
> client
> computers and reconnect to the new server? the only programs and settings
> that are essential for the users are the office suite if this makes any
> difference.
> I would appreciate anyones thought on the best way to go
> regards

 

Thanks for replies.
we are only small not-for-profit community group and sbsmigration.com looks
to expensive.
please forgive my inexperience but I think the best way to go will be to
logon as administrator to the client computers, remove them from the old
domain and then join the new domain. There is nothing wrong with the 5
client computers(which are shared by 10 roaming users) and I am not sure why
I need to tranfer their settings in this scenario.
Thanking you in advance for any further thoughts
regards

"Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in message
news:uWBP4kl3JHA.1372@TK2MSFTNGP05.phx.gbl...
> If you just need (Office 2003) settings, the Office 'Save My Settings
> Wizards' may be the way to go for each user account.
>
> If you need more (like Favorites, etc.), theWindows XP Files and Settings
> Transfer Wizard may do what you need:
>
> Step-by-Step Guide to Migrating Files and Settings
> http://technet.microsoft.com/en-us/library/bb457074.aspx
>
> or maybe the User State Migration Tool...
>
> Description of the User State Migration Tool for Windows XP Professional
> http://support.microsoft.com/Default.aspx?kbid=321197
>
> User Profile Wiaard has also been mentioned in similar posts
> http://www.forensit.com/domain-migration.html
>
> --
> Merv Porter [SBS-MVP]
> ============================
>
> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
> message news:eHYmmUj3JHA.5728@TK2MSFTNGP03.phx.gbl...
>> When you create a Windows domain, it installs its own unique Security ID,
>> or SID. Each user and computer that connect to that domain are also
>> assigned a unique SID, so that you can't have duplicate computer names or
>> numbers. When you attach an existing computer to a new root domain
>> controller, which SBS is, you get a new sid, so you have to disjoin from
>> the old SBS domain then join the new SBS domain, which is a new user and
>> a new SID, for both the user and the computer. This is part of Windows
>> Server security, and is not unique to SBS.
>>
>> The only way to preserve all the settings for the users is to copy them
>> out and back to the new profile, in XP that's c:\documents and
>> settings\user.domain.
>>
>> SBS Migration has figured out a way to preserve all the original
>> settings, the server name and the domain name, all the shares and
>> permissions, and all the emails, and to do it off line while the old box
>> continues to run. The only thing carried over from the old server to the
>> new one is the AD, including the users and computers with their SIDS.
>> The only downtime of any significance is the actual moving of the user
>> data from SBS_OLD to SBS_NEW.
>>
>> Highly recommended.
>>
>> --
>> Larry
>> Please post the resolution to your
>> issue so that others may benefit.
>>
>>
>> "Cris Hanna [SBS - MVP]" <crisnospamhanna@cpunospamservices.net> wrote in
>> message news:uIV6VXh3JHA.2336@TK2MSFTNGP02.phx.gbl...
>> you might consider talking to the folks at sbsmigration.com
>>
>>
>> --
>> Cris Hanna [SBS - MVP]
>> Co-Contributor, Windows Small Business Server 2008 Unleashed
>> http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
>> Owner, CPU Services, Belleville, IL
>> A Microsoft Registered Partner
>> ------------------------------------
>> MVPs do not work for Microsoft
>> Please do not submit questions directly to me.
>>
>>
>> "Eric S" <eistacey@adam.com.au> wrote in message
>> news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
>> Hi,
>> Can anyone please suggest a simple way to migrate/copy the relevant
>> information to keep the client computers happy after I connect them to a
>> new
>> domain? Should I use the same domain name, user names etc?
>>
>> I have a sbs2003 server that is almost impossible to manage due to
>> corruption. I have bought another computer which I have just installed
>> the
>> same OS onto.
>> I am thinking of completing the installation all the way(to domain
>> controller add users etc) There are only 10 users that use the server and
>> only a few programs that need to be reinstalled. Due to the level of
>> corruption it is not practicle to use the microsoft KB article(Migrating
>> Windows Small Business Server 2003 to New Hardware) as I cant get some of
>> the required tools to run.
>> I am thinking it is easier to do a fresh install but is there a way to
>> minimize disruption to the users when I phyically disconnect the the
>> client
>> computers and reconnect to the new server? the only programs and settings
>> that are essential for the users are the office suite if this makes any
>> difference.
>> I would appreciate anyones thought on the best way to go
>> regards
>
>
>

 

>>the only programs and settings that are essential for the users are the
>>office suite if this makes any difference.

From your original post, I presumed you wanted to save the MS Office 2003
settings for each user account. However, as long as the users are OK with
losing all Favorites, Word and Excel customized settings, desktop items and
shortcuts, etc., simply joining the workstations to the new domain is a
viable option.

And if your non-profit qualifies...

DonorTec (bringing technology donations to nonprofits)
http://www.donortec.com.au/

--
Merv Porter [SBS-MVP]
============================

"Eric S" <eistacey@adam.com.au> wrote in message
newstCdnRZbZpjbHIHXnZ2dnUVZ_sqdnZ2d@adnap.net.au...
> Thanks for replies.
> we are only small not-for-profit community group and sbsmigration.com
> looks to expensive.
> please forgive my inexperience but I think the best way to go will be to
> logon as administrator to the client computers, remove them from the old
> domain and then join the new domain. There is nothing wrong with the 5
> client computers(which are shared by 10 roaming users) and I am not sure
> why I need to tranfer their settings in this scenario.
> Thanking you in advance for any further thoughts
> regards
>
> "Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in message
> news:uWBP4kl3JHA.1372@TK2MSFTNGP05.phx.gbl...
>> If you just need (Office 2003) settings, the Office 'Save My Settings
>> Wizards' may be the way to go for each user account.
>>
>> If you need more (like Favorites, etc.), theWindows XP Files and Settings
>> Transfer Wizard may do what you need:
>>
>> Step-by-Step Guide to Migrating Files and Settings
>> http://technet.microsoft.com/en-us/library/bb457074.aspx
>>
>> or maybe the User State Migration Tool...
>>
>> Description of the User State Migration Tool for Windows XP Professional
>> http://support.microsoft.com/Default.aspx?kbid=321197
>>
>> User Profile Wiaard has also been mentioned in similar posts
>> http://www.forensit.com/domain-migration.html
>>
>> --
>> Merv Porter [SBS-MVP]
>> ============================
>>
>> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
>> message news:eHYmmUj3JHA.5728@TK2MSFTNGP03.phx.gbl...
>>> When you create a Windows domain, it installs its own unique Security
>>> ID, or SID. Each user and computer that connect to that domain are also
>>> assigned a unique SID, so that you can't have duplicate computer names
>>> or numbers. When you attach an existing computer to a new root domain
>>> controller, which SBS is, you get a new sid, so you have to disjoin from
>>> the old SBS domain then join the new SBS domain, which is a new user and
>>> a new SID, for both the user and the computer. This is part of Windows
>>> Server security, and is not unique to SBS.
>>>
>>> The only way to preserve all the settings for the users is to copy them
>>> out and back to the new profile, in XP that's c:\documents and
>>> settings\user.domain.
>>>
>>> SBS Migration has figured out a way to preserve all the original
>>> settings, the server name and the domain name, all the shares and
>>> permissions, and all the emails, and to do it off line while the old box
>>> continues to run. The only thing carried over from the old server to the
>>> new one is the AD, including the users and computers with their SIDS.
>>> The only downtime of any significance is the actual moving of the user
>>> data from SBS_OLD to SBS_NEW.
>>>
>>> Highly recommended.
>>>
>>> --
>>> Larry
>>> Please post the resolution to your
>>> issue so that others may benefit.
>>>
>>>
>>> "Cris Hanna [SBS - MVP]" <crisnospamhanna@cpunospamservices.net> wrote
>>> in message news:uIV6VXh3JHA.2336@TK2MSFTNGP02.phx.gbl...
>>> you might consider talking to the folks at sbsmigration.com
>>>
>>>
>>> --
>>> Cris Hanna [SBS - MVP]
>>> Co-Contributor, Windows Small Business Server 2008 Unleashed
>>> http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
>>> Owner, CPU Services, Belleville, IL
>>> A Microsoft Registered Partner
>>> ------------------------------------
>>> MVPs do not work for Microsoft
>>> Please do not submit questions directly to me.
>>>
>>>
>>> "Eric S" <eistacey@adam.com.au> wrote in message
>>> news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
>>> Hi,
>>> Can anyone please suggest a simple way to migrate/copy the relevant
>>> information to keep the client computers happy after I connect them to a
>>> new
>>> domain? Should I use the same domain name, user names etc?
>>>
>>> I have a sbs2003 server that is almost impossible to manage due to
>>> corruption. I have bought another computer which I have just installed
>>> the
>>> same OS onto.
>>> I am thinking of completing the installation all the way(to domain
>>> controller add users etc) There are only 10 users that use the server
>>> and
>>> only a few programs that need to be reinstalled. Due to the level of
>>> corruption it is not practicle to use the microsoft KB article(Migrating
>>> Windows Small Business Server 2003 to New Hardware) as I cant get some
>>> of
>>> the required tools to run.
>>> I am thinking it is easier to do a fresh install but is there a way to
>>> minimize disruption to the users when I phyically disconnect the the
>>> client
>>> computers and reconnect to the new server? the only programs and
>>> settings
>>> that are essential for the users are the office suite if this makes any
>>> difference.
>>> I would appreciate anyones thought on the best way to go
>>> regards
>>
>>
>>
>
>

 

Hello Eric,

I am not certain about the extent of your AD corruption..Do you have
policies, GPOs that you need to migrate? If not then it will be easier to go
with your current plan..You can use robocopy to copy the files and folders
over.
"Eric S" <eistacey@adam.com.au> wrote in message
newstCdnRZbZpjbHIHXnZ2dnUVZ_sqdnZ2d@adnap.net.au...
> Thanks for replies.
> we are only small not-for-profit community group and sbsmigration.com
> looks to expensive.
> please forgive my inexperience but I think the best way to go will be to
> logon as administrator to the client computers, remove them from the old
> domain and then join the new domain. There is nothing wrong with the 5
> client computers(which are shared by 10 roaming users) and I am not sure
> why I need to tranfer their settings in this scenario.
> Thanking you in advance for any further thoughts
> regards
>
> "Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in message
> news:uWBP4kl3JHA.1372@TK2MSFTNGP05.phx.gbl...
>> If you just need (Office 2003) settings, the Office 'Save My Settings
>> Wizards' may be the way to go for each user account.
>>
>> If you need more (like Favorites, etc.), theWindows XP Files and Settings
>> Transfer Wizard may do what you need:
>>
>> Step-by-Step Guide to Migrating Files and Settings
>> http://technet.microsoft.com/en-us/library/bb457074.aspx
>>
>> or maybe the User State Migration Tool...
>>
>> Description of the User State Migration Tool for Windows XP Professional
>> http://support.microsoft.com/Default.aspx?kbid=321197
>>
>> User Profile Wiaard has also been mentioned in similar posts
>> http://www.forensit.com/domain-migration.html
>>
>> --
>> Merv Porter [SBS-MVP]
>> ============================
>>
>> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
>> message news:eHYmmUj3JHA.5728@TK2MSFTNGP03.phx.gbl...
>>> When you create a Windows domain, it installs its own unique Security
>>> ID, or SID. Each user and computer that connect to that domain are also
>>> assigned a unique SID, so that you can't have duplicate computer names
>>> or numbers. When you attach an existing computer to a new root domain
>>> controller, which SBS is, you get a new sid, so you have to disjoin from
>>> the old SBS domain then join the new SBS domain, which is a new user and
>>> a new SID, for both the user and the computer. This is part of Windows
>>> Server security, and is not unique to SBS.
>>>
>>> The only way to preserve all the settings for the users is to copy them
>>> out and back to the new profile, in XP that's c:\documents and
>>> settings\user.domain.
>>>
>>> SBS Migration has figured out a way to preserve all the original
>>> settings, the server name and the domain name, all the shares and
>>> permissions, and all the emails, and to do it off line while the old box
>>> continues to run. The only thing carried over from the old server to the
>>> new one is the AD, including the users and computers with their SIDS.
>>> The only downtime of any significance is the actual moving of the user
>>> data from SBS_OLD to SBS_NEW.
>>>
>>> Highly recommended.
>>>
>>> --
>>> Larry
>>> Please post the resolution to your
>>> issue so that others may benefit.
>>>
>>>
>>> "Cris Hanna [SBS - MVP]" <crisnospamhanna@cpunospamservices.net> wrote
>>> in message news:uIV6VXh3JHA.2336@TK2MSFTNGP02.phx.gbl...
>>> you might consider talking to the folks at sbsmigration.com
>>>
>>>
>>> --
>>> Cris Hanna [SBS - MVP]
>>> Co-Contributor, Windows Small Business Server 2008 Unleashed
>>> http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
>>> Owner, CPU Services, Belleville, IL
>>> A Microsoft Registered Partner
>>> ------------------------------------
>>> MVPs do not work for Microsoft
>>> Please do not submit questions directly to me.
>>>
>>>
>>> "Eric S" <eistacey@adam.com.au> wrote in message
>>> news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
>>> Hi,
>>> Can anyone please suggest a simple way to migrate/copy the relevant
>>> information to keep the client computers happy after I connect them to a
>>> new
>>> domain? Should I use the same domain name, user names etc?
>>>
>>> I have a sbs2003 server that is almost impossible to manage due to
>>> corruption. I have bought another computer which I have just installed
>>> the
>>> same OS onto.
>>> I am thinking of completing the installation all the way(to domain
>>> controller add users etc) There are only 10 users that use the server
>>> and
>>> only a few programs that need to be reinstalled. Due to the level of
>>> corruption it is not practicle to use the microsoft KB article(Migrating
>>> Windows Small Business Server 2003 to New Hardware) as I cant get some
>>> of
>>> the required tools to run.
>>> I am thinking it is easier to do a fresh install but is there a way to
>>> minimize disruption to the users when I phyically disconnect the the
>>> client
>>> computers and reconnect to the new server? the only programs and
>>> settings
>>> that are essential for the users are the office suite if this makes any
>>> difference.
>>> I would appreciate anyones thought on the best way to go
>>> regards
>>
>>
>>
>
>

 

"Eric S" <eistacey@adam.com.au> wrote in message
news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
> Hi,
> Can anyone please suggest a simple way to migrate/copy the relevant
> information to keep the client computers happy after I connect them to a
> new domain? Should I use the same domain name, user names etc?
>
> I have a sbs2003 server that is almost impossible to manage due to
> corruption. I have bought another computer which I have just installed the
> same OS onto.
> I am thinking of completing the installation all the way(to domain
> controller add users etc) There are only 10 users that use the server and
> only a few programs that need to be reinstalled. Due to the level of
> corruption it is not practicle to use the microsoft KB article(Migrating
> Windows Small Business Server 2003 to New Hardware) as I cant get some of
> the required tools to run.
> I am thinking it is easier to do a fresh install but is there a way to
> minimize disruption to the users when I phyically disconnect the the
> client computers and reconnect to the new server? the only programs and
> settings that are essential for the users are the office suite if this
> makes any difference.
> I would appreciate anyones thought on the best way to go
> regards
>

Your plan will work just fine. Keeping in mind that the workstations will
have to be rejoined to the Domain and the users will lose their profiles
(unless you do something to xfer them or back them up) becuase they will
have a different SID after you re-created them. Also the server shares and
permissions will have to be recreated.

Other than that, on a small network like yours where re-creating these
things is reletively trivial, your method will be fine.

As long as you use the same share names and SBS server name, any logon
scripts or share mapping scripts will continue to work as expected.

-Frank

 

Ghost your disk image or do a backup and restore (make sure the restore disk
is as big or bigger than the original). In eather case you will need to
provide a unique name and IP for each, as was mentioned in another post.

"Eric S" <eistacey@adam.com.au> wrote in message
news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
> Hi,
> Can anyone please suggest a simple way to migrate/copy the relevant
> information to keep the client computers happy after I connect them to a
> new domain? Should I use the same domain name, user names etc?
>
> I have a sbs2003 server that is almost impossible to manage due to
> corruption. I have bought another computer which I have just installed the
> same OS onto.
> I am thinking of completing the installation all the way(to domain
> controller add users etc) There are only 10 users that use the server and
> only a few programs that need to be reinstalled. Due to the level of
> corruption it is not practicle to use the microsoft KB article(Migrating
> Windows Small Business Server 2003 to New Hardware) as I cant get some of
> the required tools to run.
> I am thinking it is easier to do a fresh install but is there a way to
> minimize disruption to the users when I phyically disconnect the the
> client computers and reconnect to the new server? the only programs and
> settings that are essential for the users are the office suite if this
> makes any difference.
> I would appreciate anyones thought on the best way to go
> regards
>

 

thanks for all your replies,
Is there a way for me to change the way the users profiles are stored -
locally instead of on the server so when I change the server they are not
comletely lost?
I have read about the admin/user state migration tool but I get too many
errors on the original server to trust it(don't think it will even run).
Also is there a repair option for sbs2003?
the main problem is that whenever I try to run any tools I get mmc.exe
application error failure to initialize(0xc0150004) - WBEM is in my path.
Have searched microsoft technet, kb, and Internet with no luck.
I was wondering if a repair would help the server.
Thanking you again - in advance
please forgive my inexperience
regards
"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
message news:eHYmmUj3JHA.5728@TK2MSFTNGP03.phx.gbl...
> When you create a Windows domain, it installs its own unique Security ID,
> or SID. Each user and computer that connect to that domain are also
> assigned a unique SID, so that you can't have duplicate computer names or
> numbers. When you attach an existing computer to a new root domain
> controller, which SBS is, you get a new sid, so you have to disjoin from
> the old SBS domain then join the new SBS domain, which is a new user and a
> new SID, for both the user and the computer. This is part of Windows
> Server security, and is not unique to SBS.
>
> The only way to preserve all the settings for the users is to copy them
> out and back to the new profile, in XP that's c:\documents and
> settings\user.domain.
>
> SBS Migration has figured out a way to preserve all the original settings,
> the server name and the domain name, all the shares and permissions, and
> all the emails, and to do it off line while the old box continues to run.
> The only thing carried over from the old server to the new one is the AD,
> including the users and computers with their SIDS. The only downtime of
> any significance is the actual moving of the user data from SBS_OLD to
> SBS_NEW.
>
> Highly recommended.
>
> --
> Larry
> Please post the resolution to your
> issue so that others may benefit.
>
>
> "Cris Hanna [SBS - MVP]" <crisnospamhanna@cpunospamservices.net> wrote in
> message news:uIV6VXh3JHA.2336@TK2MSFTNGP02.phx.gbl...
> you might consider talking to the folks at sbsmigration.com
>
>
> --
> Cris Hanna [SBS - MVP]
> Co-Contributor, Windows Small Business Server 2008 Unleashed
> http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
> Owner, CPU Services, Belleville, IL
> A Microsoft Registered Partner
> ------------------------------------
> MVPs do not work for Microsoft
> Please do not submit questions directly to me.
>
>
> "Eric S" <eistacey@adam.com.au> wrote in message
> news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
> Hi,
> Can anyone please suggest a simple way to migrate/copy the relevant
> information to keep the client computers happy after I connect them to a
> new
> domain? Should I use the same domain name, user names etc?
>
> I have a sbs2003 server that is almost impossible to manage due to
> corruption. I have bought another computer which I have just installed the
> same OS onto.
> I am thinking of completing the installation all the way(to domain
> controller add users etc) There are only 10 users that use the server and
> only a few programs that need to be reinstalled. Due to the level of
> corruption it is not practicle to use the microsoft KB article(Migrating
> Windows Small Business Server 2003 to New Hardware) as I cant get some of
> the required tools to run.
> I am thinking it is easier to do a fresh install but is there a way to
> minimize disruption to the users when I phyically disconnect the the
> client
> computers and reconnect to the new server? the only programs and settings
> that are essential for the users are the office suite if this makes any
> difference.
> I would appreciate anyones thought on the best way to go
> regards

 

Install and run a scan with the SBS 2003 BPA to see if it can find any
problems with your configuration:

Microsoft Windows Small Business Server 2003 Best Practices Analyzer
http://www.microsoft.com/downloads/...7A-DE19-49BB-800F-352F3B6F2922&displaylang=en

Revert roaming profiles to local profiles
http://groups.google.com/group/micr...n&ie=UTF-8&q=sbs+2003+revert+roaming+profiles

--
Merv Porter [SBS-MVP]
============================

"Eric S" <eistacey@adam.com.au> wrote in message
news:HYCdnZ6r_5a5SYDXnZ2dnUVZ_s2dnZ2d@adnap.net.au...
> thanks for all your replies,
> Is there a way for me to change the way the users profiles are stored -
> locally instead of on the server so when I change the server they are not
> comletely lost?
> I have read about the admin/user state migration tool but I get too many
> errors on the original server to trust it(don't think it will even run).
> Also is there a repair option for sbs2003?
> the main problem is that whenever I try to run any tools I get mmc.exe
> application error failure to initialize(0xc0150004) - WBEM is in my path.
> Have searched microsoft technet, kb, and Internet with no luck.
> I was wondering if a repair would help the server.
> Thanking you again - in advance
> please forgive my inexperience
> regards
> "Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@mis-wizards.com> wrote in
> message news:eHYmmUj3JHA.5728@TK2MSFTNGP03.phx.gbl...
>> When you create a Windows domain, it installs its own unique Security ID,
>> or SID. Each user and computer that connect to that domain are also
>> assigned a unique SID, so that you can't have duplicate computer names or
>> numbers. When you attach an existing computer to a new root domain
>> controller, which SBS is, you get a new sid, so you have to disjoin from
>> the old SBS domain then join the new SBS domain, which is a new user and
>> a new SID, for both the user and the computer. This is part of Windows
>> Server security, and is not unique to SBS.
>>
>> The only way to preserve all the settings for the users is to copy them
>> out and back to the new profile, in XP that's c:\documents and
>> settings\user.domain.
>>
>> SBS Migration has figured out a way to preserve all the original
>> settings, the server name and the domain name, all the shares and
>> permissions, and all the emails, and to do it off line while the old box
>> continues to run. The only thing carried over from the old server to the
>> new one is the AD, including the users and computers with their SIDS.
>> The only downtime of any significance is the actual moving of the user
>> data from SBS_OLD to SBS_NEW.
>>
>> Highly recommended.
>>
>> --
>> Larry
>> Please post the resolution to your
>> issue so that others may benefit.
>>
>>
>> "Cris Hanna [SBS - MVP]" <crisnospamhanna@cpunospamservices.net> wrote in
>> message news:uIV6VXh3JHA.2336@TK2MSFTNGP02.phx.gbl...
>> you might consider talking to the folks at sbsmigration.com
>>
>>
>> --
>> Cris Hanna [SBS - MVP]
>> Co-Contributor, Windows Small Business Server 2008 Unleashed
>> http://www.amazon.com/Windows-Small...bs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1
>> Owner, CPU Services, Belleville, IL
>> A Microsoft Registered Partner
>> ------------------------------------
>> MVPs do not work for Microsoft
>> Please do not submit questions directly to me.
>>
>>
>> "Eric S" <eistacey@adam.com.au> wrote in message
>> news:g6udnfP4q6Zjn4HXnZ2dnUVZ_rqdnZ2d@adnap.net.au...
>> Hi,
>> Can anyone please suggest a simple way to migrate/copy the relevant
>> information to keep the client computers happy after I connect them to a
>> new
>> domain? Should I use the same domain name, user names etc?
>>
>> I have a sbs2003 server that is almost impossible to manage due to
>> corruption. I have bought another computer which I have just installed
>> the
>> same OS onto.
>> I am thinking of completing the installation all the way(to domain
>> controller add users etc) There are only 10 users that use the server and
>> only a few programs that need to be reinstalled. Due to the level of
>> corruption it is not practicle to use the microsoft KB article(Migrating
>> Windows Small Business Server 2003 to New Hardware) as I cant get some of
>> the required tools to run.
>> I am thinking it is easier to do a fresh install but is there a way to
>> minimize disruption to the users when I phyically disconnect the the
>> client
>> computers and reconnect to the new server? the only programs and settings
>> that are essential for the users are the office suite if this makes any
>> difference.
>> I would appreciate anyones thought on the best way to go
>> regards
>
>