There is no documentation on configuring the OCS Deployment Validation Tool in the Agent/Organizer Scenario. Setting up the Auto-Answer Agent is pretty straight forward and is documented in detail at Byron Spurlock’s blog here: http://blogs.msdn.com/byrons/archive/2009/06/23/test-posting.aspx
The Agent/Organizer scenario however is a bit more interesting.
To start, you can find the Deployment Validation Tool installation files in the OCS 2007 R2 Resource Kit files which can be downloaded here: http://www.microsoft.com/downloads/details.aspx?familyid=9E79A236-C0DF-4A72-ABA6-9A9602A93ED0&displaylang=en
In the installation directory there is a sub folder for Deployment Validation Tool which has DVTAgent.MSI and DVTOrganizer.MSI.
First off both installs require you to install the UCMA Redistributable package which you can find in the OCS 2007 R2 setup files under SetupAMD64Setupucmaredist.msi
Once that package is installed you will also need to install SQL Express 2005 SP2 on the server you have picked as the organizer. This should not go on any heavy utilized OCS roles like the front end servers, in my environment I chose to put this on the Monitoring Server. Install SQL Express with all of the default options and continue with the Organizer install.
Before you run the organizer install be sure to create a SIP enabled account for the organizer. In my examples my account is DVT_Organizer@winxnet.com .
Once SQL Express 2005 SP2 is installed you can run the DVTOrganizer.MSI.
The organizer service installs are pretty straight forward, the defaults should work for the installation. However, there is one piece in the Organizer Configuration that will throw you off. By default using the guides for Auto Answering Agent configuration you are instructed to leave the box checked for Use Default Credentials when configuring the Agents. I was having issues where all of my agents were showing offline and the Organizer server would report this error in the event logs:
Warning 8/3/2009 9:15:19 PM OCS Deployment Validation Tool 51019 (1050)
The service wasn’t able to register with focus. It will attempt to reregister automatically.
Service : Organizer, URI: firstname.lastname@example.org
Cause: This might be due to a configuration error, or due to network or focus problems.
Please check the configuration of the service including the account credentials used to register with focus.
After adjusting the Organizer configuration to specify the actual user credentials I was able to get the organizer to register with the focus and recognize the agents as Online.
Once you have the organizer installed you will want to install a couple of agents, try to put them across different subnets or different physical locations to make sure you get diverse scenarios for your call testing. Also try not to put the agent on any OCS roles if possible, I have mine located on terminal servers and desktops in the environment. You will need to create SIP enabled accounts for each agent in the environment. In my example I have DVT_SERVERAGENT@winxnet.com, DVT_DCAGENT@winxnet.com and DVT_DESKTOPAGENT@winxnet.com these represent three separate subnets in my environment. Install the UCMARedist.MSI package on the agent machine and use the default information for the installation.
During the installation you may also see this error pop up which you can ignore:
At the end of the installation you will see the Agent Configuration tool pop up.
You will want to configure the agent as a Unified Communications agent with the SIP URI you have created for the agent and to be safe, manually configure the server information.
If you receive an error while configuring this agent and you are using Server 2008 or Vista/Windows 7 you will want to make sure UAC is off, or you will want to re open the agent configuration by choosing Run As Administrator.
Once this configuration is complete you will need to setup the service in windows to use the sip account of the agent.
Hit OK and start the service, jump back over to the organizer server and open the Organizer Admin Console to add your agents to the roster.
Its important to note that you will need at least 2 agents and an organizer to perform any tests. The organizer will perform tests between the agents in your roster with peer to peer as well as conference calls.
Once in the Admin Console you can view your test suite status, the easiest thing to do is to hit restore to default and it will configure the default tests between all of the agents in your roster.
The screenshot above shows the test suite tab with tests in progress and tests that have completed.
You can also view reports and alerts from all of your tests in their respective Tabs. The reports tab will show all tests that were done, if you choose a test and right click you can choose to see the complete details of the test which will look like this.
The report above shows the agents and details such as MOS Scores and Network connectivity and test length. This can be very useful when troubleshooting call quality issues.
If you have any additional questions about configuration please reach out to me, I am constantly testing new ways to use this tool and I will try to do another write up on the MOM Integration for alerting purposes as well.