Monthly Archives: January 2010
OCS 2007 R2 Schema Prep Failure “failure occurred attempting to check the schema state. please ensure active directory is reachable"
A customer called in today with an issue preparing their OCS 2007 R2 environment. The customer had previously started installation on a 2008 R2 server, and started over with a 2008 R1 server. They had only completed the Active Directory Preparations prior to starting over. The issue was when they started on the server they were unable to see the schema prep, they were receiving this error in the install GUI:
A few interesting things here, the machine is joined to the domain, I could contact all domain controllers, I could modify the schema using the schema MMC snapin. However, the OCS install run via command line or GUI would not contact active directory.
Through some quick googling I found that the installer queries the SRV records for contacting the PDC in active directory. This SRV record is:
After pointing to a DNS issue, the customer realized their server was pointing to a public DNS server, not an active directory integrated server, which did not have the SRV records needed to perform these tasks. Once the DNS server was changed, the installer read the Active Directory Preparation as Completed and you could do a proper nslookup on those SRV records
Everyone is reposting the links for downloads to the new updates. The links for all of the updates can be found below….
Conferencing Add-in for Outlook http://office.microsoft.com/en-us/help/HA102368901033.aspx (now with a 32-bit and 64-bit option)
LiveMeeting Client http://office.microsoft.com/en-us/help/HA101733831033.aspx
Cumulative update installer is the way to go on the server side, and if you are using client version filter and device updater, I can report success (in conjunction with the link below) in our internal environment. So far nothing to report as far as bugs with the new updates, patch away!
I did want to point out a couple of blog posts coming out of these updates. One from Mike Stacy, which points out that with this newest communicator release you can now properly integrate with Outlook 2010 64bit. http://mikestacy.typepad.com/mike-stacys-blog/2010/01/january-2010-communicator-r2-update-compatible-with-office-2010-64-bit.html
Another being from Michael Sneeringer who is an OCS 2007 R2 MCM. With the newest update 64bit machines are requesting a 64bit version of communicator, or atleast a directory that has that specified. His post outlines resolving this issue, this has helped clear up a bunch of update issues internally. http://michaelsneeringer.blogspot.com/2010/01/client-version-filtering-on-windows-x64.html
It has been a while since I have had a post over here, guess you can blame the holiday season as well as the busy beginning of the year at Winxnet. Anyways, I have been working with PSS on an issue with external live meeting through the edge for quite some time now, and with that has been lots of performance monitor collection, after clicking through all of the different collectors multiple times, I decided to create some templates to have for future use and wanted to share them. Its nothing special, no awesome script or anything complicated, but a very basic tool that may be useful to anyone going forward.
Above is a link for access to these files on my sky drive. If you have any issues accessing these please leave a comment or contact me via email and I will get them to you.
They are very easy to use, once downloaded, open Reliability and Performance Monitor from either your Front End or Edge Server…
Expand “Data Collector Sets” and right click on the User Defined folder. Choose New->Data Collector Set
Name the collector set whatever you would like and make sure to choose Create from a template.
Click next to access the next page in the configuration wizard. Choose Browse and locate the XML file you downloaded containing the template information. Once you select that file the page should look like this:
The next two screens will ask you where to save this file, I would suggest a drive with plenty of space as these can get very large depending on the amount of traffic on your server and how long they are running.
When you are ready to collect data simply right click on the set you created and choose start.
Once you are ready to analyze data, or send to Microsoft PSS for data analysis you simply choose stop, and you will have a file in the location you specified. Microsoft PSS uses a tool called PAL(Performance Analysis of Logs) which is an open source application written by a Microsoft employee. This tool can be found here: http://www.codeplex.com/PAL If you are feeling up to performing some of your own analysis this is a great tool to use. I may try to post some more detailed information on using this tool soon.
The templates included in my link include the following Counters:
All <LC: > Counters
Hopefully soon I will have a new post describing the fix for this strange live meeting issue, until then, Enjoy!