Re: Rolling back from going to native mode

From: Al Mulnick (amulnick_No_SPAM_at_ncDOTrr.com)
Date: 02/17/05 

Date: Thu, 17 Feb 2005 11:01:02 -0500

>From your previous post:
These may be impacted by security changes such as SMB signing but
that too is not mode related)

Hmm... I do realize that the security changes can be changed after the fact.
Trust me, I know. Some older stuff won't like it at all until you totally
dumb it down all the way to NT4 compatible. You need to check and have a
contingency should it occur to you.

As for a way to back out of such a change? You *can* but it essentially is
a forest restore. The result is that you have it back to the original
state. The consequence is that you basically destroyed the forest to the
point of having to go to tape and rely on it working. Not pretty, but can
be done and is certainly more feasible in smaller environments than in
larger ones.

By rip it out, I'm talking about removing the DC from the forest altogether
using tools such as NTDSUTIL. That's usually a last resort concept, but
that's what we're talking about right?

>From experience, I can tell you that it's better to a) do your homework to
identify apps that may stop working and b) have a plan to fix the offending
app vs. backing out of such an issue. Restoring anything is always riskier
than I like if I can help it.

FWIW, I've seen a lot of people get twisted about flipping the switch. Once
done, the usual question is, "that's it?" I have often recommended doing so
during the lunch hour in a given timezone and then grabbing a beer.

Do your homework and then go to native mode. More often than not, your apps
will be fine.

My $0.04 worth anyway.

"Mike Brannigan [MSFT]" <mikebran@online.microsoft.com> wrote in message
news:%23bWjEGQFFHA.1932@TK2MSFTNGP14.phx.gbl...
> "Eshprof" <Eshprof@discussions.microsoft.com> wrote in message
> news:2393F636-D022-4B4F-8B5D-443A5BADBFFF@microsoft.com...
>>I have never needed to roll back from going native and to the best of my
>> knowledge, once you go native that's it. There is no roll back. But...
>>
>> Do any of you have any "tricks" on how to roll back if necessary?
>>
>> Could I do a system state backup of a DC and take it offline, then check
>> the
>> box to say native mode. I could then confirm the change. If all is
>> well, I
>> could bring it back online and let it replicate the change. Or... if
>> something went wrong (I can't think of what would), I could do a restore
>> while it's still offline and confirm that it's back to mixed and then
>> bring
>> it back online?
>>
>> Is that workable? Any thoughts?
>
> Correct you cannot reverse a mode switch.
> There are no tricks around this.
>
> --
>
> Regards,
>
> Mike
> --
> Mike Brannigan [Microsoft]
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights
>
> Please note I cannot respond to e-mailed questions, please use these
> newsgroups
>
> "Eshprof" <Eshprof@discussions.microsoft.com> wrote in message
> news:2393F636-D022-4B4F-8B5D-443A5BADBFFF@microsoft.com...
>>I have never needed to roll back from going native and to the best of my
>> knowledge, once you go native that's it. There is no roll back. But...
>>
>> Do any of you have any "tricks" on how to roll back if necessary?
>>
>> Could I do a system state backup of a DC and take it offline, then check
>> the
>> box to say native mode. I could then confirm the change. If all is
>> well, I
>> could bring it back online and let it replicate the change. Or... if
>> something went wrong (I can't think of what would), I could do a restore
>> while it's still offline and confirm that it's back to mixed and then
>> bring
>> it back online?
>>
>> Is that workable? Any thoughts?
>
>