[cisco-voip] Changing FSMO roles

[Wes Sisk]

small addition - run the plugin once each time you upgrade CM to a new 
maintenance release or feature release
4.0(1)->4.0(2)
or 4.0(2)->4.1(3)
as we change schema in major versions.

not required for es/sr upgrades.

/Wes

Ryan Ratliff wrote:
> You only need to run the AD plugin against the schema master once  
> (when you extend the schema).  After that is done you can point CM at  
> any DC you wish.
>
> You will need to rerun the AD plugin to extend the schema each time  
> you upgrade the CallManager software.
>
> Short answer is if the current schema master is the DC you want CM to  
> talk to making it no longer the schema master won't effect CM.
>
> -Ryan
>
> On Mar 1, 2006, at 12:52 PM, David Strzemienski wrote:
>
> Hello all,
>
> We're running CCM 4.0(2a)sr2c, with Active Directory plug-in.
> When we initially ran the AD plug-in, it asked us to point everything  
> to the
> Schema Master domain controller, which we did, and everything worked  
> fine.
> We now need to change the holder of the Schema Master FSMO role to a
> different domain controller.
> Does anyone know if changing this role to another server will have an
> adverse effect on the CallManager?
> Will the AD plug-in need to be re-run after the change is made?
>
> Any advice is appreciated!
>
> -Dave
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>