MAS 4.0 to 5.2 Upgrade with Exchange 2003
H E L P : Anyone have similar issues or have any RECOMMENDATIONS????
SATURDAY:
Upgrade completed successfully (third party software installed properly, WebLM installed properly) but could not open VMSC – error that it could not reach the Peer Mail Server. Two Avaya Tier 3 Engineers were in the system – verified Permissions were fine. Reinstalled the Exchange Management Tools to try to get the MAPI connectivity back – to no avail. Avaya finally said we needed to reload and install 5.2 to correct the MAPI connectivity issue.
SUNDAY:
Reloaded MAS at 5.2 and did a new install with NEW DCT file. 5 hours later, after the reload and all components installed and SQL install completed, the wizard did not complete and gave same type of error: VERIFY PEER MAIL SERVER NAME. Avaya Tier 3 Engineer still believed to be a permissions issue. Ran Permissions checker and went step by step through pre-requisites. Made some permission changes and seemed to resolve the PEER MAIL SERVER connectivity issue.
With Tier 3 Engineer, re-ran NEW DCT and next error was CANNOT CREATE VOICE MAIL DOMAIN. Ran an ANALYZE DCT and got same CANNOT CREATE VOICE MAIL DOMAIN. We are using the SAME VMD name as the Rel 4.0 system. With Tier 3 Engineer, ran a DCT with a NEW VMD name – still to no avail.
Tier 4 Engineer advised us to reload the MAS again and use the ANALYZE DCT with the wizard to configure the system. 5 hours later, after the reload and all components installed and SQL install completed, the wizard did not complete and gave same type of error as in previous step: VERIFY PEER MAIL SERVER NAME.
Now working with a different Tier 3 Engineer and a different Tier 4 Engineer only for them to tell us that the ANALYZE DCT was not a good one and did not contain all of the registry information. Found an older ANALYZE DCT from 2009. Avaya said we needed to RELOAD again and run the good ANALYZE DCT.
Also, seem to be having an issue with the INHERIT PERMISSIONS being disabled in AD – we check the box and at the top of the hour, it’s automatically unchecked again …. anyone have this issue?
MONDAY:
Going to Reload the system a third time today and use the good ANALYZE DCT. Meanwhile….the customer has no voicemail until this is resolved!!!!!!!!!
H E L P : Anyone have similar issues or have any RECOMMENDATIONS????
H E L P : Anyone have similar issues or have any RECOMMENDATIONS????
SATURDAY:
Upgrade completed successfully (third party software installed properly, WebLM installed properly) but could not open VMSC – error that it could not reach the Peer Mail Server. Two Avaya Tier 3 Engineers were in the system – verified Permissions were fine. Reinstalled the Exchange Management Tools to try to get the MAPI connectivity back – to no avail. Avaya finally said we needed to reload and install 5.2 to correct the MAPI connectivity issue.
SUNDAY:
Reloaded MAS at 5.2 and did a new install with NEW DCT file. 5 hours later, after the reload and all components installed and SQL install completed, the wizard did not complete and gave same type of error: VERIFY PEER MAIL SERVER NAME. Avaya Tier 3 Engineer still believed to be a permissions issue. Ran Permissions checker and went step by step through pre-requisites. Made some permission changes and seemed to resolve the PEER MAIL SERVER connectivity issue.
With Tier 3 Engineer, re-ran NEW DCT and next error was CANNOT CREATE VOICE MAIL DOMAIN. Ran an ANALYZE DCT and got same CANNOT CREATE VOICE MAIL DOMAIN. We are using the SAME VMD name as the Rel 4.0 system. With Tier 3 Engineer, ran a DCT with a NEW VMD name – still to no avail.
Tier 4 Engineer advised us to reload the MAS again and use the ANALYZE DCT with the wizard to configure the system. 5 hours later, after the reload and all components installed and SQL install completed, the wizard did not complete and gave same type of error as in previous step: VERIFY PEER MAIL SERVER NAME.
Now working with a different Tier 3 Engineer and a different Tier 4 Engineer only for them to tell us that the ANALYZE DCT was not a good one and did not contain all of the registry information. Found an older ANALYZE DCT from 2009. Avaya said we needed to RELOAD again and run the good ANALYZE DCT.
Also, seem to be having an issue with the INHERIT PERMISSIONS being disabled in AD – we check the box and at the top of the hour, it’s automatically unchecked again …. anyone have this issue?
MONDAY:
Going to Reload the system a third time today and use the good ANALYZE DCT. Meanwhile….the customer has no voicemail until this is resolved!!!!!!!!!
H E L P : Anyone have similar issues or have any RECOMMENDATIONS????