Thank you for the speedy response. TAC has advised of the following. Your ldifde command suggestion was spot on with thier findings. Not being that confident in my syntax abilities and the supportability of them we are opting to install a 32-bit OS and tranfer the schema master role to it for this procedure.
CISCO BUG INFO
CSCsl48851 âADSchemaSetup should give error message when run on 64bit Windows server
When running ADSchemaSetup on a 64bit server you get no error prompting that it will not work.
You need to run adschemasetup on a 32 bit server. It will not currently run on a 64 bit server.
Further Problem Description:
It should detect 64-bit Windows, display an error message that says what's wrong, and then exit gracefully.
CSCsk10833 ârunning schemasetup errors outâ
Running ADschemaSetup.exe results in an error:
Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Time: 8:29:16 AM
Reporting queued error: faulting application ADSchemaSetup.exe, version
0.0.0.0, faulting module msvcrt.dll, version 7.0.3790.3959, fault address
Run schema extension scripts from the command line instead.
For all Unity systems:
The ldifde command line is: ldifde.exe -i -k -c "" "CN=Configuration,DC=achengdom,DC=ecsbu-lab-sea,DC=cisco,DC=com" -s "ACHENGDEV" -f "\Schema\LdifScripts\avdirmonex2k.ldf" -j "C:\Documents and Settings\Administrator.ACHENGDOM\Desktop\ldif logs\08162007_153115\avdirmonex2k"
If Unity system is using Unity Bridge also run:
The ldifde command line is: ldifde.exe -i -k -c "" "CN=Configuration,DC=achengdom,DC=ecsbu-lab-sea,DC=cisco,DC=com" -s "ACHENGDEV" -f "\Schema\LdifScripts\omnigateway.ldf" -j "C:\Documents and Settings\Administrator.ACHENGDOM\Desktop\ldif logs\08162007_153115\omnigateway"
If Unity system is using VPIM also run:
The ldifde command line is: ldifde.exe -i -k -c "" "CN=Configuration,DC=achengdom,DC=ecsbu-lab-sea,DC=cisco,DC=com" -s "ACHENGDEV" -f "\Schema\LdifScripts\vpimgateway.ldf" -j "C:\Documents and Settings\Administrator.ACHENGDOM\Desktop\ldif logs\08162007_153115\vpimgateway"
1) Replace "CN=Configuration,DC=achengdom,DC=ecsbu-lab-sea,DC=cisco,DC=com" with your target configuration container DN
2) Replace "ACHENGDEV" with your server name
3) Specify an applicable log file name after -j
Some users have had troubles generating a log file, and left out the -j and had it then run through fine.
According to the bug information, this is fixed with version 7.0(.148), however the version of ADSchemaUpdate.exe that comes on the Disk 1 for Unity 7.02 seem to be 4.0(0) and the version that comes on the Unity 5 CD seems to be 5.0.0. That alone seems a bit backwards to me. Anyone know where the current version of this utility can be found?
Just got off the phone with TAC, the "fix" is that the application now gives an error message. As I am sitting at a customer site trying to upgrade their unity to version 7 while their MS Server guys are whispering âWe have Exhange 07 already, there is no need for unityâ I'm having to make this call to TAC. It isn't like 64 bit OS can still be considdered new, I am disappointed that Cisco has not come up with a fix for this.
The suggested fix is to build a 32bit domain controller for running the AD setup.
I ran into issues running the update manually. However what I did, which seemed to work is use the Schema update that comes on the Unity 8.0 DVD that will run on 64-bit OS. According to the Docs It is the same schema update as in Unity 5.x and 7.x. This might be posted somewhere else here but I could not find it. So I hope this helps someone.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...