Re: Decommissioning an Exchange 2003 server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

One final question. And BTW, thank you very much for the help and support
here. This has been extremely helpful.

Avaya has gotten all MAS objects created on the new Exchange, so things are
good there. While looking over the Avaya documentation to verify permissions
in AD, I found something that I wonder if it should be removed.

In Sites and Services, switch to "show services mode", then under Services /
Microsoft Exchange, there is an Active Directory Connections folder, with an
object "Default ADC Policy". Is this 2003 related or is this a left over
from removing the AD connection services?

Joel

"Michael Dragone" wrote:

Okay, so it should be relatively smooth sailing from here on out.

"JF" <JF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:21F1D457-6A3C-44CF-83B0-9468CE91A489@xxxxxxxxxxxxxxxx
I believe all I have left is:
-Set our Exchange environment to Native, from Mixed mode.
-Work with Avaya to complete the creation of the OctelVMD object.
-Uninstall Exchange from the old server.

You can probably go Native now without running into any trouble.

SRS has been removed, and the two AD connectors have been remove (both
from
the Exchange servers and from Sites and Services).

Good.

Yes, the new exchange server had an "External Caller (Exchange server host
name)". After the AD hickup was resolved, and the MAS was rebooted,
again,
the correct "External Caller (MM server host name)" object was created.
I'm
now combing through Avaya's documentation to see if all the permissions
are
set correctly, burried deep within AD.

If I remember correctly, there's one "External Caller (MAS_hostname)" per
MAS created in the "Octel System Objects" (or whatever the bizzare hidden
container that MM creates is called). This is a user account without a
mailbox.

There's one "External Caller (Exchange_hostname)" mailbox created for each
peer and non-peer Exchange server, plus one "OctelVMD" mailbox per MM
installation. Again, if I remember correctly.

Our users whose mailboxes were moved to the new Exchange server were
reporting slow launch of Outlook. Once loaded, it was far faster than our
old Exchange (260 gig info store that hasn't been compacted or anything
since
the server went into production back in 06). Unchecking the add-in
"OutlookVFRegister" (ocolvfreg.dll) corrected the speed issue. Avaya
support
can't even tell me what this add-in does! I have a feeling that once the
OctelVMD is created on the new Exchange server, the performance issue will
go
away.

I think it's the voicemail form, the one that gives you the playback
controls. What version of Outlook? Avaya updates the MM Outlook add-in
pretty frequently and you might want to try the very latest version. The
most current for 3.1 is 7.1.546.2 from August 31st.


.

Relevant Pages