After installing update rollup 2 for HMC 4.5 I noted a few issues with adding mailboxes and retrieving domains owned by a customer.
Thanks to Kip Ng's blog post (https://blogs.technet.com/provtest/archive/2009/02/14/hmc-4-5-rollup-2-has-been-released.aspx) his suggestion of executing the following procedures in the MPS deployment tool after installing UR2;
Good advice Kip. Thanks.
Lately I have been getting right into Powershell scripting and I have been trying to build an auditing utility which HMC 4.5 Cross Data Store (CrossDS) was supposed to provide. In building this auditing tool, I have built some basic Powershell scripts on the way that may help others understand how to develop for MPS.
A basic script I have uploaded is called GetUserPlan.ps1. I have placed it in the downloads section (http://www.msexperts.org/files/folders/powershell/entry88.aspx ). Note : I have renamed it to .txt extension just in case your proxy server filters .ps1 extensions.
This script should give you an idea on how to make MPS calls from within Powershell.
I will upload a few more scripts in the next few weeks.
After preparing to write up a guide on how Resource Management works in HMC I found a detailed article written by Arthur Fang and Shanming Xuan on Claudio Vacalebre's blog (http://www.mshosting.org/Tech-Bulletins/HMC/4%20-%20Exchange%202007%20Resource%20Manager.pdf).
Quite a detailed read, but a good one.
HMC has several roles in its delegated administration model, including the following below;
I have highlighted the ones that are important in Red.
HMC has a procedure within the "Hosted Active Directory" namespace called "GetCallerUiRoles". The response from the procedure contains a value called "highestUiRole". This value tells you the highest role the user has. It is returned in a 4-digit numeric form. The numbers are as follows;
This procedure (GetCallerUiRoles) works is as follows;
It then gets the largest number in that list and returns it in the value called "highestUiRole".
So put simply, if you are a member of Admins@CustomerName you will have read permissions to the "0500" group, if you are a member of Admins@ResellerName you will have read permissions to the "1500" group, etc.
All of these groups are setup when initially deploying HMC for the first time.
While staying up to upgrade our customer's HMC to v4.5 I watched the Virtual Launch of OCS 2007 R2.
Some good information little tidbits I have got from it so far;
Link to the technical guides of OCS 2007 R2 (Deployment, Planning, etc.)
http://technet.microsoft.com/en-us/library/dd440729(office.13).aspx
Link to the end user manuals for OCS 2007 R2 (Reference card for Conferencing, etc)
http://technet.microsoft.com/en-us/library/dd440728(office.13).aspx
Bandwidth Considerations for the new RTAudio Codec
Including security and packet overheads etc. worst case – RTAudio 8kHz (Narrowband – equivalent to standard public switched telephony (G.711)) uses 32.6Kbps or RTAudio 16kHz (Wideband audio – much higher quality) uses 49.9Kbps.
Voice quality monitoring and reporting
In this new version it is storing performance metric data in a SQL DB so that you can report on the quality of calls made within your environment
Desktop Sharing and Voice Conferencing using just a web browser
Using any of the popular web browsers (IE, Firefox, Safari, etc.) you can do application sharing and control someone else's desktop. No additional software included. Just connect to the Communicator Web Access URL for your company, and you have access to be involved in just an instant messaging chat or a full application sharing scenario. You can also make a call using Communicator Web Access where OCS dials the third party and also dials the phone number you specify (e.g. your mobile phone or desk phone etc.)
x64 Only
The new version only support x64 Windows server.
Migration options
Side-by-side, or new install. No In-place upgrade.
Time to go to bed!
Another little furfy I found tonight on a client's installation of HMC4.0. They had moved the folder "MSIShare" from C:\MSIShare to E:\MSIShare and shared the folder from there. It all worked until the HMC 4.0 to HMC 4.5 upgrade.
As it seems when upgrading to HMC4.5, the installation of the new Deployment tool doesn't update all of the namespaces unless the MSIShare folder is in the location C:\MSIShare, and no, it doesn't tell you!
So moral of the story, as with everything else on HMC, make sure you keep the configuration exactly as per the original guide.
Theme design by Cameron McFie