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