IM Messages Received/Sent number of messages received or sent for all sessions. Incoming/Outgoing Calls Attempted Total number of incoming/outgoing instant messaging calls attempted. Incoming/Outgoing Calls Established number of incoming/outgoing instant messaging calls established. Number of participants Total number of participants currently connected to conferences. Conference Schedule Failure Total number of failures while trying to schedule a conference. Join Conference Failure Total number of failures while trying to connect to a conference. Received 480 (Temporarily Unavailable) The number of 480s that clients receive This counter should remain near constant all users sign-in. During user you MAY see some 480s. This is expected behavior. Examples of Failed Performance Runs To better understand how your virtualized Office Communications Server Enterprise pool should function optimally, it is necessary to push the boundaries and observe how the system’s performance decreases. This document includes two examples to illustrate this point. 50,000 Internal When a test run that had 50,000 users signing-in to the Enterprise pool was performed, we observed that the %processor% performance counter on the back-end server reached 100% usage in approximately 40 minutes as shown in Figure 13. Figure 13 Back-end server CPU usage When we looked at the back-end virtual machine properties on Hyper-V, we saw that the “Virtual Machine reserve (percentage)” value was set to 0. By increasing this value to 100, we observed that it took 2 hours for the back-end server's CPU usage to reach 100%. After the back-end server's CPU usage reached 100%, the rate of endpoints being ended rapidly increased. This resulted in users not being able to sign-in to the Enterprise pool as shown in Figure 14.
Repeat the above steps on all internal client computers (make sure you copy respective “Client<X>_all” file on each of the computers) Setting up external client computer: Install OCSStress MSI Make sure you ran “MaxRegports.reg” and restarted the computer Copy one of the directories eg: Client0_all to OCSStress installation directory Verify communicator can from this computer (make sure communicator is pointed to edge) Edit the XML file – change target serer from pool FQDN to Edge FQDN and KerboroesAuthPercentage to 0 Run the file – it takes two parameters a. Directory where OCSStress is installed and b. directory where IM_Client0.xml resides Settings used for virtualization testing CommonConfiguration TargetServer – pool FQDN UserGlobalPassword – use this if you have set same password for all users, otherwise tool assumes username is same as password KerberosAuthPercentage - Default is 80, for external users select it as 0 EnableMPOP – Enable it if you want MPOP users and select percentage UserSignInPerSec – Sign in rate BasicConversationConfiguration TwoPartyConversationPercentage – Default is 97 ( 1:1 IMs will be 97% ) ConversationsPerDay – it will be filled up by the user model you choose InviteUsersInContactList – If it is false, you need to select the range of users BasicPresenceConfiguration Enabled – true to enable this, rest defaults ABSQueryConfiguration Enabled – true ABSQueryIntervalInSeconds – set it to 3333 ( every one hour client makes an ABS query ) QueryPrefix – your user prefix ABSDownloadConfiguration Enabled – true DLExpansionConfiguration Enabled – true DlxPerfix – prefix of the DLs you created DLXCallsPerUserPerDay – 12 ( one call every 2 hours ) Appendix C: Virtualization Checklist Here is a summary of the different recommendation that you should follow when virtualizing Office Communication Server 2007 R2: