OCS R2 Group Chat - issues with IIS metabase?

Thank you to Mike who commented on my blog post here that the Metabase issue was because UAC needs to be disabled, and the Adminsetup.exe should be Right clicked and ran as an Administrator!

I had completely forgotten that this is how I worked around this, and had not been able to re-walk the install since I posted that.

Again, Thanks Mike!
Chris

Using ADModify to ensure inheritable permissions are set on user objects

Most Exchange migrations I might find 1-2 of these that can be addressed as one off issues, but today I had customer that had a lot more than usual.

I searched for a good adsiedit, ldp, or other query - no good, its an ACL, not an AD user object property, I did find some .NET examples that I did not want to venture down that road.

And then, I found admondify.net:
http://technet.microsoft.com/en-us/library/aa996216(EXCHG.65).aspx

This requires a PSS call (or google) to download. Not an install, just an unzip and use utility.

Click Modify Attributes

Select domain, select a DC, Hit the big green arrow

Then select the root or OU you want and enter a custom LDAP query of (objectClass=*) and select add to list

Then Ctrl-a or control select user objects and hit next.

Then you can go to the account tab (normally would be security->advanced in ADUC) and finally select the "allow inheritable permissions to propagate to this object" checkbox and go.

Quick, easy, and best of all, whatever you do generates an XML log file that you can also use to "undo" your changes!

Forefront for OCS released!

http://communicationsserverteam.com/archive/2009/03/16/383.aspx

This appears it would fit only in an environment where OCS is federated. At least until someone writes malware for communicator.

Exchange 2007 SP1 rollup 7 released today

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=2074fefd-fa1a-4c3e-bf72-94585e454150

As seen at http://www.bink.nu/

Update Rollup 7 for Exchange Server 2007 Service Pack 1 (SP1) resolves issues that were found in Exchange Server 2007 SP1 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP1 customers.

For a list of changes that are included in this update rollup, see KB960384.

This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM). For a list of update rollups applicable to Exchange Server 2007 RTM, refer to the section Update rollups for Exchange Server 2007 RTM in the Knowledge Base article KB937052.

MS exchange team blog article:

http://msexchangeteam.com/archive/2009/03/18/450863.aspx

OCS 2007 R2 Enterprise Edition and SQL requirements

I recently completed my first EE installation in a production environment. This was a migration from LCS 2005 SP1, and while LCS is not yet defunct, it so far has been VERY smooth.

This particular install was using a SQL 2005 cluster for the back end as well as the archive databases.

Things to know:

• Only SQL 2005 SP1 and SQL 2008 are supported.
  
• For Archiving, MSMQ and Directory integration are needed.
  

  
  

  Lessons learned:
  

• LCS 2005 didn't require a certificate to work properly at this particular customer. This prevented communications between OCS and LCS users. The choices were to fix this or just speed up the plans. Like I said above� completed :)
  

  
  

Exchange 2007 HT and CAS in NLB - Unicast versus Multicast

I have implemented about 4 NLB clusters for HT, CAS, or both now, and every time the rule of thumb has been, use what works.

From the MS Exchange page on IPv6 (also applies to IPv4) we know that:

• Unicast address A packet is delivered to one interface.
  
• Multicast address A packet is delivered to multiple interfaces.
  

More searching turned up this very helpful article describing the differences:

http://vittoriop77.blogspot.com/2006/03/nlb-unicast-vs-multicast.html

So, in one implementation, the customer had a Proventia M60 firewall, and unicast ended up working and performing more reliably. In another using an Juniper SSG firewall, unicast performed poorly and multicast ended up being the fix.

I searched the Exchange implementation guide and CHM thoroughly and didn't find any particular guidance, so I think at this point trial and error is the best bet. Learn what works in your config and go with it.