INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

(OP)
Our Domain admins need to upgrade our AD from Win2k3 R2 to Win2k8 R2. Our telecom guys are saying that if we do that, the schema changes fro Windows 2008 R2 on our DC's/AD will cause the Avaya MM 4.0 Admin Tools to quit functioning and/or the Modular Messaging Tab will not be available in ADUC. Do the Modular Messaging Subscriber Administration Tools work with AD 2008 R2 and Exchange 2007 SP2 running on Windows 2003 R2? If not what are the alternatives for the MM Administrator Tools?

We are currently running:
'Modular Messaging 4.0 Service Pack 11' (WSO - 7.2.1279.11004)
'Modular Messaging 4.0 Service Pack 11' (MAS - 7.2.1279.11004)
'Modular Messaging 4.0 Service Pack 11' (ADMIN - 7.2.1279.11004)

Active Directory 2003 R2 (want to upgrade to at least AD 2008 R2)
Exchange 2007 SP2 running on Windows 2003 R2

Thanks in advance for any help!

RE: Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

below is right from the patch install so i dont know who your telcom guys are but they should read more.

Modular Messaging 4.0

MM401100 Service Pack 11 Release Notes
Currency Items
This software update includes support for the following software platforms not covered by the Products official documentation:

§ Added support for MSSQL 2005 SP3 (Express Edition) which can now be installed on MAS.

§ Added support for the Modular Messaging Subscriber Administration Tools running on Windows XP Professional with SP3 when used with Exchange 2007. However note that port 135 (DCOM) needs to be added into the Exception list of the Windows Firewall to allow connectivity to the MAS.

§ Added the support for Active Directory and Exchange 2007 running on Windows Server 2008 platform has been added. Additional configuration information can be found in “Support for Active Directory and Exchange 2007 running on Windows Server 2008 platforms” under Modular Messaging 4.0 White Papers on support.avaya.com. This support does not include the MAS being installed on a Windows 2008 server.

§ Microsoft Exchange Server 2007 Service Pack 2 is now supported.

§ Modular Messaging Web Client is now supported on Windows 7 64 bit.

§ Microsoft Windows Server 2008 R2 (Schema version 47) can now be used as Active Directory Server for Modular Messaging (Exchange Backend).
Modular Messaging Subscriber Administration is not yet supported on Windows Server 2008 R2

For NSPI connections settings please refer "Calculating the number of NSPI connections required by Modular Messaging" section from "Appendix C: Customer Environment" of "Modular Messaging Concepts and Planning Guide" of MM 5.2

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

RE: Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

In addition to what Ken wrote, the Modular Messaging tab will only be seen where that software was installed. So if they are doing MM user administration from a desktop or from the MM server itself today, it should function fine after the domain or forest is promoted to 2008 or 2008 R2.

RE: Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

With regard to this topic, I am using MM5.2 but same scenario otherwise. I have instructions how to change the peer on the MAS to the new DCs. My instructions include stopping the MSSQL$MMFEDB service but I cannot find that service - where is it located?

Also - curious what others are doing in the way of the NSPI connections - how many are you allowing on your 2008 DCs?

RE: Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

I found the SQL file - embarrassed so I will not share. Still curious what others are doing on the NSPI connections...

RE: Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

To the original poster and all, 2008 or later OS for DCs in a MM for Exchange environment need to have their NSPI settings configured properly. Failing to do so will impact MM, among other products that utilize NSPI type connections (MAPI is one of those NSPI type connections).

RE: Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

There is a disagreement about the amount of connections...what are you all doing?

RE: Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

Outside of the confusing calculations Avaya recommends, they generically says about 250 per MAS. Which in my experience is too low but greatly depends on the number of users that MAS is supporting.

Some customers just make it like Windows 2003 had it (4 billion something) and some make it 10000. I think the lowest I was able to do it was between 1000-5000, depending on the amount of MM subscribers the system (really the service account used) was supporting.

I had one customer that used the same account in the US for all their systems and we had to keep increasing the number until we no longer hit this condition. In a lab that's not hard to do, but in an enterprise production environment it is difficult to update the many 2008 or later OS DCs that Exchange may use for authentication as they would have to reboot those DCs or restart a service before the change would take effect.

It also depends on if the customer is using other products that use NSPI type connections as well. Like BlackBerry or something else. Those other products might have a higher number requirement. Always use the higher number requirement and the other products should function fine.

RE: Admin Tools for MM 4.0 and Windows 2008 R2 Active Directory

In my opinion it should be set to the limit so that it would not be an issue with any of the services that use it.

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close