IActually I have my only windows 2003 server standard that runs all my
company administrative programs and acts as DC Controller, I need to upgrade
to R2.

I do have the new license of R2 ready to install but I am afraid to put the
server down and have all the consequences.

Could anyone of this list indicate me the steps to follow to avoid any
problems?

I do have to reconfigure the server or it`s an smooth process???

Thanks for your

Hello voipsistemas,

First step, CREATE A GOOD BACKUP BEFORE STARTING!!!!

Second, insert the second disk on the DC and run adprep command from it,
to upgrade the schema to version 31.

Then you can install the additional features if you need them.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> IActually I have my only windows 2003 server standard that runs all my
> company administrative programs and acts as DC Controller, I need to
> upgrade to R2.
>
> I do have the new license of R2 ready to install but I am afraid to
> put the server down and have all the consequences.
>
> Could anyone of this list indicate me the steps to follow to avoid any
> problems?
>
> I do have to reconfigure the server or it`s an smooth process???
>
> Thanks for your
>

Mainolf,
Thanks for your reply.
My question is the damages could be suffered at DC level? or at application
level?
Because one of the administrative applications it`s installed by the
provider and if it`s damaged no backup will until their techinicians
arrive to reinstall the application.
Suggestions welcome

Thanks

"Meinolf Weber" wrote:

> Hello voipsistemas,
>
> First step, CREATE A GOOD BACKUP BEFORE STARTING!!!!
>
> Second, insert the second disk on the DC and run adprep command from it,
> to upgrade the schema to version 31.
>
> Then you can install the additional features if you need them.
>
> Best regards
>
> Meinolf Weber

Hello voipsistemas,

So in this case you can create an image from the complete machine. If the
upgrade fails or something does not work correctly bring the image back and
you're at the level before the upgrade.

But do NEVER use this image for creating additional servers/DC's!!!

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Mainolf,
> Thanks for your reply.
> My question is the damages could be suffered at DC level? or at
> application
> level?
> Because one of the administrative applications it`s installed by the
> provider and if it`s damaged no backup will until their
> techinicians
> arrive to reinstall the application.
> Suggestions welcome
> Thanks
>
> "Meinolf Weber" wrote:
>
>> Hello voipsistemas,
>>
>> First step, CREATE A GOOD BACKUP BEFORE STARTING!!!!
>>
>> Second, insert the second disk on the DC and run adprep command from
>> it, to upgrade the schema to version 31.
>>
>> Then you can install the additional features if you need them.
>>
>> Best regards
>>
>> Meinolf Weber
>>

> My question is the damages could be suffered at DC level? or at
> application
> level?
> Because one of the administrative applications it`s installed by the
> provider and if it`s damaged no backup will until their techinicians
> arrive to reinstall the application.
> Suggestions welcome

I would ask why you are updating to R2. R2 is just a feature update. What
features of R2 are you trying to take advantage of? You may be able to set
up a second DC, move the schema master to the second DC and move the content
that you want to use the new R2 features with, to the second DC. Then you
won't have to touch the DC with the special software on it.

hth
DDS


"voipsistemas" <voipsistemas@discussions.microsoft.com> wrote in message
news:F67B34B3-722A-4C65-8A12-03B23CC170A5@microsoft.com...
> Mainolf,
> Thanks for your reply.
> My question is the damages could be suffered at DC level? or at
> application
> level?
> Because one of the administrative applications it`s installed by the
> provider and if it`s damaged no backup will until their techinicians
> arrive to reinstall the application.
> Suggestions welcome
>
> Thanks
>
> "Meinolf Weber" wrote:
>
>> Hello voipsistemas,
>>
>> First step, CREATE A GOOD BACKUP BEFORE STARTING!!!!
>>
>> Second, insert the second disk on the DC and run adprep command from it,
>> to upgrade the schema to version 31.
>>
>> Then you can install the additional features if you need them.
>>
>> Best regards
>>
>> Meinolf Weber
>

Meinolf Weber wrote:
> Hello voipsistemas,
>
> So in this case you can create an image from the complete machine. If
> the upgrade fails or something does not work correctly bring the
> image back and you're at the level before the upgrade.
>

Restoring an image of a DC to the same DC will likely result in USN
rollback, so unless it's the only DC, or you recreate the domain from this
restored image, then that's a bad idea.

But I've had zero issues with R2 besides the MMC 3.0 peculiarities. SP2 has
caused many more problems.

If you really need to thoroughly test this, then take it in a lab and verify
it.

> But do NEVER use this image for creating additional servers/DC's!!!
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Mainolf,
>> Thanks for your reply.
>> My question is the damages could be suffered at DC level? or at
>> application
>> level?
>> Because one of the administrative applications it`s installed by the
>> provider and if it`s damaged no backup will until their
>> techinicians
>> arrive to reinstall the application.
>> Suggestions welcome
>> Thanks
>>
>> "Meinolf Weber" wrote:
>>
>>> Hello voipsistemas,
>>>
>>> First step, CREATE A GOOD BACKUP BEFORE STARTING!!!!
>>>
>>> Second, insert the second disk on the DC and run adprep command from
>>> it, to upgrade the schema to version 31.
>>>
>>> Then you can install the additional features if you need them.
>>>
>>> Best regards
>>>
>>> Meinolf Weber

--
/kj

kj [SBS MVP] wrote:
> Meinolf Weber wrote:
>> Hello voipsistemas,
>>
>> So in this case you can create an image from the complete machine. If
>> the upgrade fails or something does not work correctly bring the
>> image back and you're at the level before the upgrade.
>>

Oh, and installing R2 on a DC requires schema upgrade to v31, a little more
difficult to role back since this will replicate forest wide (from the
schema master).

Again though, a pretty well tried and proved product at this point.

>
> Restoring an image of a DC to the same DC will likely result in USN
> rollback, so unless it's the only DC, or you recreate the domain from
> this restored image, then that's a bad idea.
>
> But I've had zero issues with R2 besides the MMC 3.0 peculiarities.
> SP2 has caused many more problems.
>
> If you really need to thoroughly test this, then take it in a lab and
> verify it.
>
>> But do NEVER use this image for creating additional servers/DC's!!!
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** us YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>
>>> Mainolf,
>>> Thanks for your reply.
>>> My question is the damages could be suffered at DC level? or at
>>> application
>>> level?
>>> Because one of the administrative applications it`s installed by the
>>> provider and if it`s damaged no backup will until their
>>> techinicians
>>> arrive to reinstall the application.
>>> Suggestions welcome
>>> Thanks
>>>
>>> "Meinolf Weber" wrote:
>>>
>>>> Hello voipsistemas,
>>>>
>>>> First step, CREATE A GOOD BACKUP BEFORE STARTING!!!!
>>>>
>>>> Second, insert the second disk on the DC and run adprep command
>>>> from it, to upgrade the schema to version 31.
>>>>
>>>> Then you can install the additional features if you need them.
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber

--
/kj

Danny,
Thanks for asking, I will detail in what kind of situation I am inmersed
right now, and will look for any memeber of this forum that would like to giv
me ideas

I am running a server Compaq ML150 with mirrored disks and Windows 2003
Server, this server has also the company`s business aplication running under
sql server 2000

All the users data & profiles are saved in directories, this is an small
company and the owner decides to migrate to a new more powerful server and he
asked me to provide redundancy at server level, for critical data


I installed windows 2003 Server R2 in the new server and make the new
machine the secondary DC and the AD were replicated into it.

I try robocopy to move the folders and got some errors in copying it,
because some data will be replicated I want to install DFS between both
servers but this feature does not work the same in both versions of windows
2003

My main idea was move all the data & app to the new server then promote the
new server as main controller and put the older one as secondary controller
and then via DFS keep the critical data exactly the same in both servers

We purchased another license of R2 for the old server but because it`s the
only production server I am afraid to make a mistake to makes me run a lot :-(

Procedures , warnings welcome.

Best regards,
Javier

"Danny Sanders" wrote:

> > My question is the damages could be suffered at DC level? or at
> > application
> > level?
> > Because one of the administrative applications it`s installed by the
> > provider and if it`s damaged no backup will until their techinicians
> > arrive to reinstall the application.
> > Suggestions welcome
>
> I would ask why you are updating to R2. R2 is just a feature update. What
> features of R2 are you trying to take advantage of? You may be able to set
> up a second DC, move the schema master to the second DC and move the content
> that you want to use the new R2 features with, to the second DC. Then you
> won't have to touch the DC with the special software on it.
>
> hth
> DDS
>
>
> "voipsistemas" <voipsistemas@discussions.microsoft.com> wrote in message
> news:F67B34B3-722A-4C65-8A12-03B23CC170A5@microsoft.com...
> > Mainolf,
> > Thanks for your reply.
> > My question is the damages could be suffered at DC level? or at
> > application
> > level?
> > Because one of the administrative applications it`s installed by the
> > provider and if it`s damaged no backup will until their techinicians
> > arrive to reinstall the application.
> > Suggestions welcome
> >
> > Thanks
> >
> > "Meinolf Weber" wrote:
> >
> >> Hello voipsistemas,
> >>
> >> First step, CREATE A GOOD BACKUP BEFORE STARTING!!!!
> >>
> >> Second, insert the second disk on the DC and run adprep command from it,
> >> to upgrade the schema to version 31.
> >>
> >> Then you can install the additional features if you need them.
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >
>
>
>