Customer is having Exchange issues to the point right now where the System Manager services will not start. All normal troubleshooting have been attempted on their side. The opened a case with Microsoft and, since the only major changes made have been the schema updates for Unity, they are looking at Unity as the cause. MS recommended re-executing a forestprep and a domainprep for Exchange 2000, and possibly re-installing Exchange over itself. Should I have any concerns on the Unity side or anything I'll need to re-apply?
First, the schema extensions were reviewed and approved by standards bodies, including Microsoft - I know it's always tempting for folks to lay their network/Exchange problems at the doorstep of the last guy on the scene when you can't figure out what's going on, but the chances of the schema extensions we made in AD causing the Exchange problems they're experiencing is very, very remote.
If the extensions are left in place an the users in the directory are not touched this shouldn't cause Unity any issues - although re-installing Exchange over itself would give me pause...
Just so you know, re-executing the forestprep and domainprep, installing Exchange 2K over itself in REINSTALLATION mode, and reapplying the Exchange SP worked well. So far, there are no adverse effects on Unity. All messages that were held in SQL while Exchange was offline synced up as expected.
Microsoft's take on the matter were that the security permissions wihin AD for some of the Exchange objects somehow were affected/corrupted. The reinstallation fixed everything.
So, if the need to reinstall Exchange ever arises, it SHOULD not affect the Unity implementation as long as no changes are made.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.