o On server HFWMXMSG01PH-HFWMXMSG020 implemented the following registry ke

y to increase the MaxConcurrentAPI from 2 to 5

? HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters
\MaxConcurrentAPI (DWORD = 5)
o Moved all active database copies off the server this registry key was ap
plied to, and confirmed the operation completed without an issue.
o Rebooted the server. Confirmed that all database copies were healthy.
o Rebalanced the database copies on each server
o Tested the following to ensure each Exchange service was functioning pro
perly
? o MAPI connectivity
? o Mail flow
? o DB replication
? o Outlook Web App
? o Outlook Anywhere
o Confirmed on each server the MaxConcurrentAPI was set to 5
o Setup performance monitors on HFWAPMSG02PV to monitor all servers Netlog
on stats for Semaphore Waiters / Holders
? Netlogon / Semaphore Waiters \ _All
? Netlogon / Semaphore Holders \ _All
TMG Change Request:
o Placed 09PH back into the web load balanced pool for Exchange
o Confirmed using performance monitors on the Exchange server HFWMXMSG09PH
that new OA (Outlook Anywhere) requests were being processed
Networking Change Request:
o Implemented HFWMXMSG09PH back into the load balancing pool for the HUB t
ransport traffic (e.g: SMTP)
o Confirmed that this was working as expected via queue viewer.
o Intel CRQ000000140549 is scheduled between 5pm and 10pm
o Messaging CRQ000000140814 is scheduled for 8:00pm
o Plan is that we Intel & Messaging teams will put in emergency changes at
8:00pm central, to do the following:
? Intel: Apply Patch, update the MaxConcurrentAPI to 5, reboot and the set
up monitoring one at a time
? Messaging: We uploaded baseline counters for four servers 02, 07, 12, 13
.