Re: New Server Transition question

"PorBar" <> wrote in message
news:7771a176-4240-4607-971c-...
> We are replacing an SBS2003 server with a Windows 2003 Server R2 on
> new hardware. The SBS2003 will be removed from service when this is
> done. The new server will be the domain controller. We would like to
> begin establishing the roles for this new server--particularly the DC
> role so we can setup the AD manually. We would like to use the same
> domain name-such as (Company.local).
>
> When we are done making the new server a DC (obviously not on the
> current network) we would like to be able to transfer data files from
> the old server through a LAN connection to the new server.
>
> However, since the SBS will still be a DC at that point, how is it
> possible to connect our new server to the LAN as a DC and copy/
> transfer files? Can we just plug it into the LAN switch and be ok for
> that purpose? This new server has a different name if that helps.
>
> For instance, could we do this if we made the domain name on the new
> server something different-such as (Companyxxx.local)?
>
> We would use an external drive but the old server does not have a high-
> speed USB port and it is taking forever to copy files to the Maxtor.
>
> Thanks


Hi PorBar,

You can simply promote the machine as a DC into the SBS domain. This way it
preserves the domain name, users, groups, etc. Then you can simply unplug
the SBS when done, and run a metadata cleanup on the new DC to remove the
SBS DC's references from the domain.

However, SBS has other factors to keep in mind, such as Exchange, SQL and
ISA. Are any of them in use? If using Exchange, what are your plans to
handle the mailboxes?

Keep in mind too, there's licensing involved, including with Exchange. Not
to overwhelm you, but here are some of my notes on moving from Exchange. I
hope they help.

================================================== ================
================================================== ================
Moving away from SBS:

SBS 2003 to Server 2008/Exchange 2007
Discusses the Windows Small Business Server 2003 R2 Transition Pack, as well
as guidelines in moving from SBS
http://social.technet.microsoft.com/...1-65720c1019f5

Microsoft Windows Small Business Server R2: Windows Small Business, Jul 11,
2006. [PDF about the Transition Pack, how to acquire it, etc]
The Windows Small Business Server 2003 R2 Transition Pack helps your
business grow as your technology grows...
http://www.microsoft.com/WindowsServ...ransition.mspx

The black hole of the transition pack - THE OFFICIAL BLOG OF THE ...SBS 2003
has a 'transition pack'. A method that you can upgrade from SBS ...
Installed the Transition pack on SBS SP1 Premium (running SQL but not ISA).
....
http://msmvps.com/blogs/bradley/arch.../11/80849.aspx

The Official SBS Blog : Activation Loop After Completing the SBS ...[Today's
tip comes to us from Damian Leibaschoff ]
We've seen a few cases now where a server is in an activation loop
(activation never completes ...
http://blogs.technet.com/sbs/archive...tion-pack.aspx

Replace SBS 2003 with Windows Server 2008 & Exchange 2007
http://social.technet.microsoft.com/...f-636bdbf13eda

If you don't want to purchase the pack, you can manually do it. Basically,
here's the 30,000 foot view if you want to keep the same domain name:

1. Promoting a 2008 or 2003 server to a DC (installing DNS, DHCP, WINS,
etc).
2. Installing a separate server for Exchange into the org.
3. Move mailboxes
4. If using SQL, installing a separate server for SQL and move the databases
5. Move any other apps over
6. Unplug the SBS
7. Move FSMO roles over
8. Manually remove SBS' Exchange instance out of the org

If you don't want to keep the same domain name, then you would install a
fresh 2008 server, Exchange 2007 on another, etc. You can export/import the
user accounts using LDIFDE or CSV method. Use Exmerge two-step, or PSTs to
export/import mailboxes. You can manually re-target profiles with the new
user account or use a third party profile tool.

There's a another migration method that you may hear about through the
grapevine, but it's not supported nor follows Microsoft legal compliance for
SBS, so I won't mention it.

Don't forget, minimal recommendation is to have two DCs per domain. It's to
your advantage.
================================================== ================
================================================== ================

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

"PorBar" <> wrote in message
news:451237dd-6444-4eea-9a7f-...
On Oct 26, 1:45 pm, PorBar <compsos...@gmail.com> wrote:
> On Oct 26, 1:06 pm, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
> wrote:
>
>
>
>
>
> > "PorBar" <compsos...@gmail.com> wrote in message
>
> >news:7771a176-4240-4607-971c-...
>
> > > We are replacing an SBS2003 server with a Windows 2003 Server R2 on
> > > new hardware. The SBS2003 will be removed from service when this is
> > > done. The new server will be the domain controller. We would like to
> > > begin establishing the roles for this new server--particularly the DC
> > > role so we can setup the AD manually. We would like to use the same
> > > domain name-such as (Company.local).
>
> > > When we are done making the new server a DC (obviously not on the
> > > current network) we would like to be able to transfer data files from
> > > the old server through a LAN connection to the new server.
>
> > > However, since the SBS will still be a DC at that point, how is it
> > > possible to connect our new server to the LAN as a DC and copy/
> > > transfer files? Can we just plug it into the LAN switch and be ok for
> > > that purpose? This new server has a different name if that helps.
>
> > > For instance, could we do this if we made the domain name on the new
> > > server something different-such as (Companyxxx.local)?
>
> > > We would use an external drive but the old server does not have a
> > > high-
> > > speed USB port and it is taking forever to copy files to the Maxtor.
>
> > > Thanks
>
> > Hi PorBar,
>
> > You can simply promote the machine as a DC into the SBS domain. This way
> > it
> > preserves the domain name, users, groups, etc. Then you can simply
> > unplug
> > the SBS when done, and run a metadata cleanup on the new DC to remove
> > the
> > SBS DC's references from the domain.
>
> > However, SBS has other factors to keep in mind, such as Exchange, SQL
> > and
> > ISA. Are any of them in use? If using Exchange, what are your plans to
> > handle the mailboxes?
>
> > Keep in mind too, there's licensing involved, including with Exchange.
> > Not
> > to overwhelm you, but here are some of my notes on moving from Exchange.
> > I
> > hope they help.
>
> > ================================================== ================
> > ================================================== ================
> > Moving away from SBS:
>
> > SBS 2003 to Server 2008/Exchange 2007
> > Discusses the Windows Small Business Server 2003 R2 Transition Pack, as
> > well
> > as guidelines in moving from
> > SBShttp://social.technet.microsoft.com/Forums/en-US/winserverMigration/t...
>
> > Microsoft Windows Small Business Server R2: Windows Small Business, Jul
> > 11,
> > 2006. [PDF about the Transition Pack, how to acquire it, etc]
> > The Windows Small Business Server 2003 R2 Transition Pack helps your
> > business grow as your technology
> > grows...http://www.microsoft.com/WindowsServ.../planning/tran...
>
> > The black hole of the transition pack - THE OFFICIAL BLOG OF THE ...SBS
> > 2003
> > has a 'transition pack'. A method that you can upgrade from SBS ...
> > Installed the Transition pack on SBS SP1 Premium (running SQL but not
> > ISA).
> > ...http://msmvps.com/blogs/bradley/arch.../11/80849.aspx
>
> > The Official SBS Blog : Activation Loop After Completing the SBS
> > ...[Today's
> > tip comes to us from Damian Leibaschoff ]
> > We've seen a few cases now where a server is in an activation loop
> > (activation never completes
> > ...http://blogs.technet.com/sbs/archive...ion-loop-after...
>
> > Replace SBS 2003 with Windows Server 2008 & Exchange
> > 2007http://social.technet.microsoft.com/Forums/en-US/winserverMigration/t...
>
> > If you don't want to purchase the pack, you can manually do it.
> > Basically,
> > here's the 30,000 foot view if you want to keep the same domain name:
>
> > 1. Promoting a 2008 or 2003 server to a DC (installing DNS, DHCP, WINS,
> > etc).
> > 2. Installing a separate server for Exchange into the org.
> > 3. Move mailboxes
> > 4. If using SQL, installing a separate server for SQL and move the
> > databases
> > 5. Move any other apps over
> > 6. Unplug the SBS
> > 7. Move FSMO roles over
> > 8. Manually remove SBS' Exchange instance out of the org
>
> > If you don't want to keep the same domain name, then you would install a
> > fresh 2008 server, Exchange 2007 on another, etc. You can export/import
> > the
> > user accounts using LDIFDE or CSV method. Use Exmerge two-step, or PSTs
> > to
> > export/import mailboxes. You can manually re-target profiles with the
> > new
> > user account or use a third party profile tool.
>
> > There's a another migration method that you may hear about through the
> > grapevine, but it's not supported nor follows Microsoft legal compliance
> > for
> > SBS, so I won't mention it.
>
> > Don't forget, minimal recommendation is to have two DCs per domain. It's
> > to
> > your advantage.
> > ================================================== ================
> > ================================================== ================
>
> > --
> > Ace
>
> > This posting is provided "AS-IS" with no warranties or guarantees and
> > confers no rights.
>
> > Please reply back to the newsgroup or forum for collaboration benefit
> > among
> > responding engineers, and to help others benefit from your resolution.
>
> > Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
> > 2003/2000, MCSA Messaging 2003
> > Microsoft Certified Trainer
>
> > For urgent issues, please contact Microsoft PSS directly. Please
> > checkhttp://support.microsoft.comforregional support phone numbers.-
> > Hide quoted text -
>
> > - Show quoted text -
>
> Do not want to preserve old AD. Just need to transfer files. Can we do
> this?- Hide quoted text -
>
> - Show quoted text -

> Anyone? Thanks

What kind of files?

No Exchange mailboxes?

If no Exchange mailboxes, and all you want to do is move files...

1. a.) If you want to keep the same domain FQDN and NetBIOS names without
adding a DC to the current AD, then copy the data to an interim drive (USB
drive), build your brand new AD, create your user and group accounts,
disjoin the old machines, join to the new domain, and copy the files from
the interim drive.

1. b.) If you don't want to use an interim drive, install it with a
different name.

2. If you have Exchange mailboxes (whether 1a or 1b), you can use Exmerge
two-step method to PST all mailboxes, install your new AD, install Exchange,
mailbox enable the new accounts, and use Exmerge to import the mailboxes.

Ace

> On Oct 26, 4:22*pm, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
> wrote:
>> "PorBar" <compsos...@gmail.com> wrote in message
>>
>> news:451237dd-6444-4eea-9a7f-...
>> On Oct 26, 1:45 pm, PorBar <compsos...@gmail.com> wrote:
>>
>>
>>
>>> On Oct 26, 1:06 pm, "Ace Fekay [MCT]" <ace...@mvps.RemoveThisPart.org>
>>> wrote:
>>
>>>> "PorBar" <compsos...@gmail.com> wrote in message
>>>> news:7771a176-4240-4607-971c-...
>>>>> We are replacing an SBS2003 server with a Windows 2003 Server R2 on
>>>>> new hardware. The SBS2003 will be removed from service when this is
>>>>> done. The new server will be the domain controller. We would like to
>>>>> begin establishing the roles for this new server--particularly the DC
>>>>> role so we can setup the AD manually. We would like to use the same
>>>>> domain name-such as (Company.local).
>>>>> When we are done making the new server a DC (obviously not on the
>>>>> current network) we would like to be able to transfer data files from
>>>>> the old server through a LAN connection to the new server.
>>>>> However, since the SBS will still be a DC at that point, how is it
>>>>> possible to connect our new server to the LAN as a DC and copy/
>>>>> transfer files? Can we just plug it into the LAN switch and be ok for
>>>>> that purpose? This new server has a different name if that helps.
>>>>> For instance, could we do this if we made the domain name on the new
>>>>> server something different-such as (Companyxxx.local)?
>>>>> We would use an external drive but the old server does not have a
>>>>> high-
>>>>> speed USB port and it is taking forever to copy files to the Maxtor.
>>>>> Thanks
>>
>>>> Hi PorBar,
>>
>>>> You can simply promote the machine as a DC into the SBS domain. This way
>>>> it
>>>> preserves the domain name, users, groups, etc. Then you can simply
>>>> unplug
>>>> the SBS when done, and run a metadata cleanup on the new DC to remove
>>>> the
>>>> SBS DC's references from the domain.
>>>> However, SBS has other factors to keep in mind, such as Exchange, SQL
>>>> and
>>>> ISA. Are any of them in use? If using Exchange, what are your plans to
>>>> handle the mailboxes?
>>
>>>> Keep in mind too, there's licensing involved, including with Exchange.
>>>> Not
>>>> to overwhelm you, but here are some of my notes on moving from Exchange.
>>>> I
>>>> hope they help.
>>
>>>> ================================================== ================
>>>> ================================================== ================
>>>> Moving away from SBS:
>>
>>>> SBS 2003 to Server 2008/Exchange 2007
>>>> Discusses the Windows Small Business Server 2003 R2 Transition Pack, as
>>>> well
>>>> as guidelines in moving from
>>>> SBShttp://social.technet.microsoft.com/Forums/en-US/winserverMigration/t...
>>>> Microsoft Windows Small Business Server R2: Windows Small Business, Jul
>>>> 11,
>>>> 2006. [PDF about the Transition Pack, how to acquire it, etc]
>>>> The Windows Small Business Server 2003 R2 Transition Pack helps your
>>>> business grow as your technology
>>>> grows...http://www.microsoft.com/WindowsServ.../planning/tran...
>>>> The black hole of the transition pack - THE OFFICIAL BLOG OF THE ...SBS
>>>> 2003
>>>> has a 'transition pack'. A method that you can upgrade from SBS ...
>>>> Installed the Transition pack on SBS SP1 Premium (running SQL but not
>>>> ISA).
>>>> ...http://msmvps.com/blogs/bradley/arch.../11/80849.aspx
>>>> The Official SBS Blog : Activation Loop After Completing the SBS
>>>> ...[Today's
>>>> tip comes to us from Damian Leibaschoff ]
>>>> We've seen a few cases now where a server is in an activation loop
>>>> (activation never completes
>>>> ...http://blogs.technet.com/sbs/archive...ion-loop-after...
>>>> Replace SBS 2003 with Windows Server 2008 & Exchange
>>>> 2007http://social.technet.microsoft.com/Forums/en-US/winserverMigration/t...
>>>> If you don't want to purchase the pack, you can manually do it.
>>>> Basically,
>>>> here's the 30,000 foot view if you want to keep the same domain name:
>>>> 1. Promoting a 2008 or 2003 server to a DC (installing DNS, DHCP, WINS,
>>>> etc).
>>>> 2. Installing a separate server for Exchange into the org.
>>>> 3. Move mailboxes
>>>> 4. If using SQL, installing a separate server for SQL and move the
>>>> databases
>>>> 5. Move any other apps over
>>>> 6. Unplug the SBS
>>>> 7. Move FSMO roles over
>>>> 8. Manually remove SBS' Exchange instance out of the org
>>>> If you don't want to keep the same domain name, then you would install a
>>>> fresh 2008 server, Exchange 2007 on another, etc. You can export/import
>>>> the
>>>> user accounts using LDIFDE or CSV method. Use Exmerge two-step, or PSTs
>>>> to
>>>> export/import mailboxes. You can manually re-target profiles with the
>>>> new
>>>> user account or use a third party profile tool.
>>>> There's a another migration method that you may hear about through the
>>>> grapevine, but it's not supported nor follows Microsoft legal compliance
>>>> for
>>>> SBS, so I won't mention it.
>>
>>>> Don't forget, minimal recommendation is to have two DCs per domain. It's
>>>> to
>>>> your advantage.
>>>> ================================================== ================
>>>> ================================================== ================
>>>> --
>>>> Ace
>>
>>>> This posting is provided "AS-IS" with no warranties or guarantees and
>>>> confers no rights.
>>
>>>> Please reply back to the newsgroup or forum for collaboration benefit
>>>> among
>>>> responding engineers, and to help others benefit from your resolution.
>>>> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
>>>> 2003/2000, MCSA Messaging 2003
>>>> Microsoft Certified Trainer
>>
>>>> For urgent issues, please contact Microsoft PSS directly. Please
>>>> checkhttp://support.microsoft.comforregionalsupport phone numbers.-
>>>> Hide quoted text -
>>
>>>> - Show quoted text -
>>
>>> Do not want to preserve old AD. Just need to transfer files. Can we do
>>> this?- Hide quoted text -
>>
>>> - Show quoted text -
>>> Anyone? Thanks
>>
>> What kind of files?
>>
>> No Exchange mailboxes?
>>
>> If no Exchange mailboxes, and all you want to do is move files...
>>
>> 1. a.) If you want to keep the same domain FQDN and NetBIOS names without
>> adding a DC to the current AD, then copy the data to an interim drive (USB
>> drive), build your brand new AD, create your user and group accounts,
>> disjoin the old machines, join to the new domain, and copy the files from
>> the interim drive.
>>
>> 1. b.) If you don't want to use an interim drive, install it with a
>> different name.
>>
>> 2. If you have Exchange mailboxes (whether 1a or 1b), you can use Exmerge
>> two-step method to PST all mailboxes, install your new AD, install Exchange,
>> mailbox enable the new accounts, and use Exmerge to import the mailboxes.
>>
>> Ace

> We have created a new FQDN & NetBIOS name for the new server and made
> it a DC. And we do not have Exchange boxes to keep.And the USB drive
> is too slow. So it looks like answer "1.b.)" is our best option. I
> just did not know if it would show up within the "Entire Windows
> Network". I thought of it after my post, but we could always copy
> data to a workstation prior to disconnecting the current SBS2003 box.
> Thanks for your reply

You are welcome. I'm glad I was able to help.

Ace