Upgrading Domain from AD 2000 to AD 2003

[jsailers]

I have Cisco CallManager 3.3(3) and Unity 4.0(3)SR1. Unity is in a UM configuration with Exchange 2000. CallManager is using the Customer Directory Plugin for the current AD 2000 domain. I am about to Upgrade the AD to 2003. What concerns should I have if any for both CallManager and Unity, and what procedures are there for me to follow.

So far from looking through CCO I have found the following:

CallManager - Re-run the AD Plug-in configuration. If found a procedure that included a manual schema update:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_3/install/plugins/plugin33.htm

Unity - The only thing I found here is a procedure to run if I need to change the Directory or Global Catalog Server:

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_upgrade_guides_chapter09186a0080205a80.html

We are not upgrading to Exchange 2003 in this run of it, but will be shortly. Is there anything that I have missed? Any help would be appreciated.

[kechambe]

Unity doesn't require any changes. Basically it will see that the DC/GC is down while the upgrade of Windows is occurring.

You won’t be able to add new users, locations or distribution lists and updates to from SQL to the DC won’t occur while the upgrade is in progress.

While the GC which Unity is using to resolve message recipients is being upgraded mail will not get to Exchange but once it is back Unity shouldn't even need a reboot to start working again.

Outside called will be able to leave messages but Unity will not be in UMR mode and subscribers will not be able to login to their mailbox until the upgrade is complete.

That is all that I can think will happen...

If post-upgrade you have any issues reboot Unity and they should clear up but I really don't think you will have to even do that.

Thanks,

Keith

[jsailers]

Keith, Thanks for your help with the Answer for Unity. I was also thinking through any necessary changes for CallManager, and initially I was thinking that I would just need to re-run the Customer Directory Plugin configuration, but now I'm wondering if I even need to do that. We are only upgrading the AD to 2003, not replacing it, so I would think that all of the Schema additions wouldn't be touched.

Do you think I need to re-run this to be sure, or is it safe to assume the necessary schema additions would remain through the AD Upgrade?

Thanks in advance for any assistance anyone can provide.

Jeff

[kechambe]

Actually I am looking here and CallManager does not officially support it yet. It looks like support is coming soon but it will only be for 3.3.4 and 4.0(1)SR2.

The issue is a conflicting labeledURI property. The following error occurs when the MS utility ADPrep is run on a Windows 2000 AD server in preparation to upgrading it to Windows 2003 AD:

…

Importing directory from file "C:\WINNT\System32\sch18.ldf"

Loading entries........................

Add error on line 333: Unwilling To Perform

The server side error is "Schema update failed: attribute in may-contain does not exist."

23 entries modified successfully.

An error has occurred in the program

ERROR: Import from file C:\WINNT\System32\sch18.ldf failed. Error file is saved

in ldif.err.18.

We have a script that will correct the issue and that is what we are going to release soon to CCO. Until then I would hold off on running ADPrep.

Thanks,

Keith

[jsailers]

That's interesting... We ran the ADPrep utility in our lab on an exact copy of the our Schema and didn't run into that error.

There is a MS Knowledgebase article (325379) that details a fix for the inetOrgPerson object. Did you run that in your environment? inetOrgPerson is defined in Sch18.ldf. This problem appears to be related to that.

From KB 325379:

The Exchange 2000 schema defines three inetOrgPerson attributes with non-Request for Comment (RFC)-compliant LDAPDisplayNames: houseIdentifier, secretary, and labeledURI.

The Windows 2000 inetOrgPerson Kit and the Windows Server 2003 adprep command define RFC-complaint versions of the same three attributes with identical LDAPDisplayNames as the RFC-compliant versions

So does Cisco use that same attribute? Is CallManager non-compliant with the Exch2000 version, the fix version or the Win2K3 version of that attibute? If we've already run the inetOrgPerson fix, will that cause a problem? I guess I'm kinda confused about what is going on here. Could you send me a snip-it of your script (not to use, but to better understand the issue)?

Thanks very much for your help.

[kenjohnson]

Does anyone know if this script was ever released? I'm having trouble finidng it - running into the same issue trying to upgrade from w2k --> w2k3 AD with CM4.0 installed.

- Ken

[kenjohnson]

Nevermind, I was blind - I found the avvidADPrep.1-0-3.exeforum on the voice page, I wasn't looking for the right file name.

Thanks!

- Ken