How to retire a Windows 2003 standard server!

I am in the process of upgrading a small 2003 server (SRV1) with a new big
capacity Windows 2003 server (newsrv). What I would like to do is to retire
the old SRV1. The new server should be name at the end with the name of the
server that is retiring. The name of the new server should be SRV1. The new
file server should have the same name because of the UNC needs.

Questions:
How can I accomplish this?

In the case I renamed the Old server to SVR1ret- How can I rename that
server back to its original server name (SVR1)? Is this possible?

Setup the new server as a member server of the domain with a temporary name
and IP address.
If necessary Use robocopy to copy over the
files and retain the security. something like robocopy x:\ y:\ /sec /r:2
/w:2. Then use Windows GUI to share the folders. If necessary Use Print
migrator to
backup the printers on the old server and restore them to the new server.
See:
http://www.microsoft.com/windowsserv...grator3.1.mspx

I would keep the new server as a member server during this part.

Plan on about an hour of down time for the next part, maybe do this on a
Friday evening??/
Once you get all the printers and files to the new server, run DCpromo to
remove AD.
Once a member server rename and change IP address.
Give the new server the proper name and IP address
and promote to DC. If you have AD integrated DNS let it replicate. AD
integrated DNS makes the DNS part easy.
The longest task is to copy over the files but you can either do the
robocopy during the week and just do a refresh before starting or do the
robocopy after you make the new server a DC (if necessary) and cut the
robocopy script loose as the last step and let it run over the weekend.

You might consider stopping the shares on the existing server before running
the robocopy to make sure users are not in the files.



hth
DDS


"DMI" <> wrote in message
news:B67D2407-2785-466B-BA53-...
>I am in the process of upgrading a small 2003 server (SRV1) with a new big
> capacity Windows 2003 server (newsrv). What I would like to do is to
> retire
> the old SRV1. The new server should be name at the end with the name of
> the
> server that is retiring. The name of the new server should be SRV1. The
> new
> file server should have the same name because of the UNC needs.
>
> Questions:
> How can I accomplish this?
>
> In the case I renamed the Old server to SVR1ret- How can I rename that
> server back to its original server name (SVR1)? Is this possible?
>

As long as two don't have the same name at the same time you can name or
rename any way you want to. Just let the dynamic DNS entries "catch up"
between each rename (same for WINS entries).


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"DMI" <> wrote in message
news:B67D2407-2785-466B-BA53-...
>I am in the process of upgrading a small 2003 server (SRV1) with a new big
> capacity Windows 2003 server (newsrv). What I would like to do is to
> retire
> the old SRV1. The new server should be name at the end with the name of
> the
> server that is retiring. The name of the new server should be SRV1. The
> new
> file server should have the same name because of the UNC needs.
>
> Questions:
> How can I accomplish this?
>
> In the case I renamed the Old server to SVR1ret- How can I rename that
> server back to its original server name (SVR1)? Is this possible?
>

Thank you Danny so much. I do have a question - I will be using BackupExec
to copy and restore the information from the old server into the new server.
I am not going to be using the robocopy utility - In the information you sent
to me you mention to run the DCpromo to remove the DM. Can you please tell
me why should I run this? Both of the servers are part of the domain but
they are not DC. Do I still need to run the DCPromo to remove the old
server? If this is the case can you please provide some instructions on how
to accomplish this?

Thank you once again for the information!


"Danny Sanders" wrote:

> Setup the new server as a member server of the domain with a temporary name
> and IP address.
> If necessary Use robocopy to copy over the
> files and retain the security. something like robocopy x:\ y:\ /sec /r:2
> /w:2. Then use Windows GUI to share the folders. If necessary Use Print
> migrator to
> backup the printers on the old server and restore them to the new server.
> See:
> http://www.microsoft.com/windowsserv...grator3.1.mspx
>
> I would keep the new server as a member server during this part.
>
> Plan on about an hour of down time for the next part, maybe do this on a
> Friday evening??/
> Once you get all the printers and files to the new server, run DCpromo to
> remove AD.
> Once a member server rename and change IP address.
> Give the new server the proper name and IP address
> and promote to DC. If you have AD integrated DNS let it replicate. AD
> integrated DNS makes the DNS part easy.
> The longest task is to copy over the files but you can either do the
> robocopy during the week and just do a refresh before starting or do the
> robocopy after you make the new server a DC (if necessary) and cut the
> robocopy script loose as the last step and let it run over the weekend.
>
> You might consider stopping the shares on the existing server before running
> the robocopy to make sure users are not in the files.
>
>
>
> hth
> DDS
>
>
> "DMI" <> wrote in message
> news:B67D2407-2785-466B-BA53-...
> >I am in the process of upgrading a small 2003 server (SRV1) with a new big
> > capacity Windows 2003 server (newsrv). What I would like to do is to
> > retire
> > the old SRV1. The new server should be name at the end with the name of
> > the
> > server that is retiring. The name of the new server should be SRV1. The
> > new
> > file server should have the same name because of the UNC needs.
> >
> > Questions:
> > How can I accomplish this?
> >
> > In the case I renamed the Old server to SVR1ret- How can I rename that
> > server back to its original server name (SVR1)? Is this possible?
> >
>
>
>

"DMI" <> wrote in message
news:F011A59B-0D4B-470A-A8F5-...
> Thank you Danny so much. I do have a question - I will be using
> BackupExec
> to copy and restore the information from the old server into the new
> server.
> I am not going to be using the robocopy utility - In the information you
> sent
> to me you mention to run the DCpromo to remove the DM. Can you please
> tell
> me why should I run this? Both of the servers are part of the domain but
> they are not DC. Do I still need to run the DCPromo to remove the old
> server? If this is the case can you please provide some instructions on
> how
> to accomplish this?

Skip the DCPromo thing if they aren't DCs.

I'v never used Robo Copy so I didn't think of that,...I was thinking of
doing it with NTBackup from a fresh tape backup (as you are doing with
BackupExec). I'm pretty sure it preserves the permissions, but I haven't
actually done it. The last time I replaced a File Server is wasn't that
complex and so I just rebuilt the permission manually after creating a
report of them using DumpSec from Somarsoft. It was a good opportunity to
clean up the permissions anyway.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

If you are not dealing with Domain controllers that makes it even easier,
skip the dcpromo part. You can use NT backup but I would suggest robocopy
and use the /LOG option so you can go through the log and see everything
that happened.

Map a drive from the new server to the old.
New server(Drive where the files are to be stored)) = X, old server(Drive of
files to be moved) = Y run this script on the old server: robocopy y:\ x:\
/sec /r:2 /w:3 /log:c:\robocopylog.

This will create a log on the root of the C drive on the new server giving
all the details of the copy/failed files. You can save the script and run it
periodically during the week leading up to your friday cutover.


hth
DDS

"DMI" <> wrote in message
news:F011A59B-0D4B-470A-A8F5-...
> Thank you Danny so much. I do have a question - I will be using
> BackupExec
> to copy and restore the information from the old server into the new
> server.
> I am not going to be using the robocopy utility - In the information you
> sent
> to me you mention to run the DCpromo to remove the DM. Can you please
> tell
> me why should I run this? Both of the servers are part of the domain but
> they are not DC. Do I still need to run the DCPromo to remove the old
> server? If this is the case can you please provide some instructions on
> how
> to accomplish this?
>
> Thank you once again for the information!
>
>
> "Danny Sanders" wrote:
>
>> Setup the new server as a member server of the domain with a temporary
>> name
>> and IP address.
>> If necessary Use robocopy to copy over the
>> files and retain the security. something like robocopy x:\ y:\ /sec /r:2
>> /w:2. Then use Windows GUI to share the folders. If necessary Use Print
>> migrator to
>> backup the printers on the old server and restore them to the new server.
>> See:
>> http://www.microsoft.com/windowsserv...grator3.1.mspx
>>
>> I would keep the new server as a member server during this part.
>>
>> Plan on about an hour of down time for the next part, maybe do this on a
>> Friday evening??/
>> Once you get all the printers and files to the new server, run DCpromo
>> to
>> remove AD.
>> Once a member server rename and change IP address.
>> Give the new server the proper name and IP address
>> and promote to DC. If you have AD integrated DNS let it replicate. AD
>> integrated DNS makes the DNS part easy.
>> The longest task is to copy over the files but you can either do the
>> robocopy during the week and just do a refresh before starting or do the
>> robocopy after you make the new server a DC (if necessary) and cut the
>> robocopy script loose as the last step and let it run over the weekend.
>>
>> You might consider stopping the shares on the existing server before
>> running
>> the robocopy to make sure users are not in the files.
>>
>>
>>
>> hth
>> DDS
>>
>>
>> "DMI" <> wrote in message
>> news:B67D2407-2785-466B-BA53-...
>> >I am in the process of upgrading a small 2003 server (SRV1) with a new
>> >big
>> > capacity Windows 2003 server (newsrv). What I would like to do is to
>> > retire
>> > the old SRV1. The new server should be name at the end with the name
>> > of
>> > the
>> > server that is retiring. The name of the new server should be SRV1.
>> > The
>> > new
>> > file server should have the same name because of the UNC needs.
>> >
>> > Questions:
>> > How can I accomplish this?
>> >
>> > In the case I renamed the Old server to SVR1ret- How can I rename that
>> > server back to its original server name (SVR1)? Is this possible?
>> >
>>
>>
>>

Thank you so much for your help.

I just have two more question - How can we be sure we copy everything for
the share directories including directories and subdirectories into the new
location?

The following is the command I am using right now.

robocopy y:\ x:\ /sec /E /r:2 /w:3 /log:c:\robocopylog

This utility is really working great!

My second question is - How can we copy ONLY the files in all of the
directories and subdirectories that has been changed since the last time I
run this utility? What is the especial switch to do this?

Thank you once again for your great help!

"Danny Sanders" wrote:

> If you are not dealing with Domain controllers that makes it even easier,
> skip the dcpromo part. You can use NT backup but I would suggest robocopy
> and use the /LOG option so you can go through the log and see everything
> that happened.
>
> Map a drive from the new server to the old.
> New server(Drive where the files are to be stored)) = X, old server(Drive of
> files to be moved) = Y run this script on the old server: robocopy y:\ x:\
> /sec /r:2 /w:3 /log:c:\robocopylog.
>
> This will create a log on the root of the C drive on the new server giving
> all the details of the copy/failed files. You can save the script and run it
> periodically during the week leading up to your friday cutover.
>
>
> hth
> DDS
>
> "DMI" <> wrote in message
> news:F011A59B-0D4B-470A-A8F5-...
> > Thank you Danny so much. I do have a question - I will be using
> > BackupExec
> > to copy and restore the information from the old server into the new
> > server.
> > I am not going to be using the robocopy utility - In the information you
> > sent
> > to me you mention to run the DCpromo to remove the DM. Can you please
> > tell
> > me why should I run this? Both of the servers are part of the domain but
> > they are not DC. Do I still need to run the DCPromo to remove the old
> > server? If this is the case can you please provide some instructions on
> > how
> > to accomplish this?
> >
> > Thank you once again for the information!
> >
> >
> > "Danny Sanders" wrote:
> >
> >> Setup the new server as a member server of the domain with a temporary
> >> name
> >> and IP address.
> >> If necessary Use robocopy to copy over the
> >> files and retain the security. something like robocopy x:\ y:\ /sec /r:2
> >> /w:2. Then use Windows GUI to share the folders. If necessary Use Print
> >> migrator to
> >> backup the printers on the old server and restore them to the new server.
> >> See:
> >> http://www.microsoft.com/windowsserv...grator3.1.mspx
> >>
> >> I would keep the new server as a member server during this part.
> >>
> >> Plan on about an hour of down time for the next part, maybe do this on a
> >> Friday evening??/
> >> Once you get all the printers and files to the new server, run DCpromo
> >> to
> >> remove AD.
> >> Once a member server rename and change IP address.
> >> Give the new server the proper name and IP address
> >> and promote to DC. If you have AD integrated DNS let it replicate. AD
> >> integrated DNS makes the DNS part easy.
> >> The longest task is to copy over the files but you can either do the
> >> robocopy during the week and just do a refresh before starting or do the
> >> robocopy after you make the new server a DC (if necessary) and cut the
> >> robocopy script loose as the last step and let it run over the weekend.
> >>
> >> You might consider stopping the shares on the existing server before
> >> running
> >> the robocopy to make sure users are not in the files.
> >>
> >>
> >>
> >> hth
> >> DDS
> >>
> >>
> >> "DMI" <> wrote in message
> >> news:B67D2407-2785-466B-BA53-...
> >> >I am in the process of upgrading a small 2003 server (SRV1) with a new
> >> >big
> >> > capacity Windows 2003 server (newsrv). What I would like to do is to
> >> > retire
> >> > the old SRV1. The new server should be name at the end with the name
> >> > of
> >> > the
> >> > server that is retiring. The name of the new server should be SRV1.
> >> > The
> >> > new
> >> > file server should have the same name because of the UNC needs.
> >> >
> >> > Questions:
> >> > How can I accomplish this?
> >> >
> >> > In the case I renamed the Old server to SVR1ret- How can I rename that
> >> > server back to its original server name (SVR1)? Is this possible?
> >> >
> >>
> >>
> >>
>
>
>

Phillip - Thank you so much for sharing your wisdom and information with us -
We really appreciated very much.

"Phillip Windell" wrote:

> As long as two don't have the same name at the same time you can name or
> rename any way you want to. Just let the dynamic DNS entries "catch up"
> between each rename (same for WINS entries).
>
>
> --
> Phillip Windell
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
> "DMI" <> wrote in message
> news:B67D2407-2785-466B-BA53-...
> >I am in the process of upgrading a small 2003 server (SRV1) with a new big
> > capacity Windows 2003 server (newsrv). What I would like to do is to
> > retire
> > the old SRV1. The new server should be name at the end with the name of
> > the
> > server that is retiring. The name of the new server should be SRV1. The
> > new
> > file server should have the same name because of the UNC needs.
> >
> > Questions:
> > How can I accomplish this?
> >
> > In the case I renamed the Old server to SVR1ret- How can I rename that
> > server back to its original server name (SVR1)? Is this possible?
> >
>
>
>

> I just have two more question - How can we be sure we copy everything for
> the share directories including directories and subdirectories into the
> new
> location?


By using the /E switch like you have here.

> My second question is - How can we copy ONLY the files in all of the
> directories and subdirectories that has been changed since the last time I
> run this utility? What is the especial switch to do this?
>

That's why I use robocopy, It is smart enough to only copy the files that
change, you can see this if you create another log on the second robocopy
and compare the two.

hth
DDS

"DMI" <> wrote in message
news:AC80283A-8A5A-485B-8FFD-...
> Thank you so much for your help.
>
> I just have two more question - How can we be sure we copy everything for
> the share directories including directories and subdirectories into the
> new
> location?
>
> The following is the command I am using right now.
>
> robocopy y:\ x:\ /sec /E /r:2 /w:3 /log:c:\robocopylog
>
> This utility is really working great!
>
> My second question is - How can we copy ONLY the files in all of the
> directories and subdirectories that has been changed since the last time I
> run this utility? What is the especial switch to do this?
>
> Thank you once again for your great help!
>
> "Danny Sanders" wrote:
>
>> If you are not dealing with Domain controllers that makes it even easier,
>> skip the dcpromo part. You can use NT backup but I would suggest robocopy
>> and use the /LOG option so you can go through the log and see everything
>> that happened.
>>
>> Map a drive from the new server to the old.
>> New server(Drive where the files are to be stored)) = X, old server(Drive
>> of
>> files to be moved) = Y run this script on the old server: robocopy y:\
>> x:\
>> /sec /r:2 /w:3 /log:c:\robocopylog.
>>
>> This will create a log on the root of the C drive on the new server
>> giving
>> all the details of the copy/failed files. You can save the script and run
>> it
>> periodically during the week leading up to your friday cutover.
>>
>>
>> hth
>> DDS
>>
>> "DMI" <> wrote in message
>> news:F011A59B-0D4B-470A-A8F5-...
>> > Thank you Danny so much. I do have a question - I will be using
>> > BackupExec
>> > to copy and restore the information from the old server into the new
>> > server.
>> > I am not going to be using the robocopy utility - In the information
>> > you
>> > sent
>> > to me you mention to run the DCpromo to remove the DM. Can you please
>> > tell
>> > me why should I run this? Both of the servers are part of the domain
>> > but
>> > they are not DC. Do I still need to run the DCPromo to remove the old
>> > server? If this is the case can you please provide some instructions
>> > on
>> > how
>> > to accomplish this?
>> >
>> > Thank you once again for the information!
>> >
>> >
>> > "Danny Sanders" wrote:
>> >
>> >> Setup the new server as a member server of the domain with a temporary
>> >> name
>> >> and IP address.
>> >> If necessary Use robocopy to copy over the
>> >> files and retain the security. something like robocopy x:\ y:\ /sec
>> >> /r:2
>> >> /w:2. Then use Windows GUI to share the folders. If necessary Use
>> >> Print
>> >> migrator to
>> >> backup the printers on the old server and restore them to the new
>> >> server.
>> >> See:
>> >> http://www.microsoft.com/windowsserv...grator3.1.mspx
>> >>
>> >> I would keep the new server as a member server during this part.
>> >>
>> >> Plan on about an hour of down time for the next part, maybe do this on
>> >> a
>> >> Friday evening??/
>> >> Once you get all the printers and files to the new server, run
>> >> DCpromo
>> >> to
>> >> remove AD.
>> >> Once a member server rename and change IP address.
>> >> Give the new server the proper name and IP address
>> >> and promote to DC. If you have AD integrated DNS let it replicate. AD
>> >> integrated DNS makes the DNS part easy.
>> >> The longest task is to copy over the files but you can either do the
>> >> robocopy during the week and just do a refresh before starting or do
>> >> the
>> >> robocopy after you make the new server a DC (if necessary) and cut the
>> >> robocopy script loose as the last step and let it run over the
>> >> weekend.
>> >>
>> >> You might consider stopping the shares on the existing server before
>> >> running
>> >> the robocopy to make sure users are not in the files.
>> >>
>> >>
>> >>
>> >> hth
>> >> DDS
>> >>
>> >>
>> >> "DMI" <> wrote in message
>> >> news:B67D2407-2785-466B-BA53-...
>> >> >I am in the process of upgrading a small 2003 server (SRV1) with a
>> >> >new
>> >> >big
>> >> > capacity Windows 2003 server (newsrv). What I would like to do is
>> >> > to
>> >> > retire
>> >> > the old SRV1. The new server should be name at the end with the
>> >> > name
>> >> > of
>> >> > the
>> >> > server that is retiring. The name of the new server should be SRV1.
>> >> > The
>> >> > new
>> >> > file server should have the same name because of the UNC needs.
>> >> >
>> >> > Questions:
>> >> > How can I accomplish this?
>> >> >
>> >> > In the case I renamed the Old server to SVR1ret- How can I rename
>> >> > that
>> >> > server back to its original server name (SVR1)? Is this possible?
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>

DMI wrote:
> I am in the process of upgrading a small 2003 server (SRV1) with a new big
> capacity Windows 2003 server (newsrv). What I would like to do is to retire
> the old SRV1. The new server should be name at the end with the name of the
> server that is retiring. The name of the new server should be SRV1. The new
> file server should have the same name because of the UNC needs.
>
> Questions:
> How can I accomplish this?
>
> In the case I renamed the Old server to SVR1ret- How can I rename that
> server back to its original server name (SVR1)? Is this possible?
>

What is/are the role(s) of the server? In many cases, you can just
rename the server (assuming the old one is renamed or gone). There are a
few situations, like SQL server, where additional actions may need to be
taken....

--

Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://mypcassistant.blogspot.com/