Exchange 2010 RU2 Released
Exchange 2010 RU2 was released today and can be downloaded from the following link
The link below is a list of fixes included in Ru2
Exchange 2010 RU2 was released today and can be downloaded from the following link
The link below is a list of fixes included in Ru2
http://msexchangeteam.com/archive/2010/01/29/453908.aspx
Exchange CXP team has released Update Rollup 2 for Exchange Server 2007 Service Pack 2 (KB 972076) to the download center.
In addition to bug fixes reported by customers we have added new rules to the Exchange Best Practices Analyzer to check the health of your system. Starting this rollup, customers who wish to deploy the new BPA health rules to a server with no internet connection can do so by downloading the installing the update rollup on the server. Until Exchange Server 2007 Service Pack 2, updates to the BPA rules were available only via the web which meant customers wanting to deploy the new health check rules to servers not connected to the internet would have had to copy over the XML files manually. In Exchange 2007 SP2, we implemented a work item which allows us to ship updates to the BPA health check rules via the rollup and as well as via the traditional web based channel. More on this via a blog post in the near future.
KBA 972076 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we’d like to call out:
More information on the values to set in the above registry keys is documented in KB 972705.
KB 972076 has more details about this release and a complete list of all fixes included in this rollup. Exchange CXP team has released Update Rollup 2 for Exchange Server 2007 Service Pack 2 (KB 972076) to the download center.
In addition to bug fixes reported by customers we have added new rules to the Exchange Best Practices Analyzer to check the health of your system. Starting this rollup, customers who wish to deploy the new BPA health rules to a server with no internet connection can do so by downloading the installing the update rollup on the server. Until Exchange Server 2007 Service Pack 2, updates to the BPA rules were available only via the web which meant customers wanting to deploy the new health check rules to servers not connected to the internet would have had to copy over the XML files manually. In Exchange 2007 SP2, we implemented a work item which allows us to ship updates to the BPA health check rules via the rollup and as well as via the traditional web based channel. More on this via a blog post in the near future.
KBA 972076 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we’d like to call out:
More information on the values to set in the above registry keys is documented in KB 972705.
KB 972076 has more details about this release and a complete list of all fixes included in this rollup.
Microsoft has provided a nice easy command to show you how large your current databases are, this one line command can be pipped to a file or used in a report
Get-MailboxDatabase -Status | fl name,databasesizes
Name : DB001
DatabaseSize : 141.8 GB (152,220,270,592 bytes)
Name : DB002
DatabaseSize : 98.17 GB (105,412,362,240 bytes)
Let me start out with this is not a supported item by Microsoft however is vary functional!
Today in Exchange 2010 when a user logs onto OWA and selects the options button they are taken into what is now called the Exchange Control Panel or ECP which has added some functionality for users. One problem that I have found is that Microsoft has provided users with some nice links telling them how to configure their mobile device or Outlook anywhere but those links directt users to Outlook.Com configuration which tends to generate support calls.
Those links are controlled by a file located here C:\Exchange\ClientAccess\ecp\PersonalSettings\QuickLinks.ascx , this file can be copied and modified with company faq settings to direct users to the appropriate place. I must note that every RollUp applied or Service Pack will overwrite your custome file and you must recopy the file back to this directory. The 2nd point I need to make is that every build of Exchange (after rollup or service pack) you need to copy the new file and modify that file because Microsoft could have made changes in security or configuration, reusing the same old file could cause issues. You will also have to copy this file to each CAS server.
Lets logon to OWA and take a look at the default settings:
You can see when I hover over Connect Outlook to this account the url is set to http://help.Outlook.com
Close OWA
1. On your CAS server browse to the following file C:\Exchange\ClientAccess\ecp\PersonalSettings\QuickLinks.ascx copy this file to your desktop so we can edit it
2. Open the QuickLinks file with Notepad
3. I have highlighted the section we are going to work on which is the Mobile section
4. We are going to remove this line <div><asp:Literal ID=”ltlMobileDevices” runat=”server” Text=”<%$ Strings:QLPushEmail %>” /></div>
5. Insert and href like this : <ecp:<P><A HREF=http://www.exchange-genie.com target=”_blank”> Configure your mobile device with Active Sync for Beta Mail </A></P>
6. Save our file
7. Rename the origianl file to .old or some other extension
8. copy and paste our new file into the following location C:\Exchange\ClientAccess\ecp\PersonalSettings\QuickLinks.ascx
9. Logon to OWA into ECP
10. Hover over the Mobile link and you will see the url now points to http://exchange-genie.com
The only 2 items you should modify in this file are related to Mobile and Outlook connections
Thanks to my friend Ilse who has outlined the steps on how to upload a picture for consumption in the gal
I wanted to leave this post open and make is more of a user poll.
Please leave a post about an item or configuration you think is difficult to manage with Exchange server or if you had one wish what would you add to the product?
I just wanted to drop a little note and wish everyone a Happy and Safe New Year!
Instead of reinventing the wheel I am going to use Devin blog to reference how to do this task.
http://blogs.3sharp.com/deving/archive/2007/01/08/2738.aspx
First, let’s start with a command that lists all of the mailboxes in a given server, sorted by size. There are two variants for ascending and descending, differing only in the inclusion of the -Descending paramter in the Sort-Object cmdlet in the latter:
Get-MailboxStatistics -Server RED-MSG01 | Sort-Object -Property TotalItemSize | ` Format-Table DisplayName,TotalItemSize Get-MailboxStatistics -Server RED-MSG01 | Sort-Object -Property TotalItemSize -Descending | ` Format-Table DisplayName,TotalItemSize
Pretty simple stuff, really; your basic pipeline exercise. You can also use Get-Mailbox -Server SERVER | Get-MailboxStatistics like I originally was, but since the Get-MailboxStatistics cmdlet already supports the -Server parameter it would be redundant. If you have some other way you need to define your collection of mailboxes, once you figure out how to define it, pipe the collection into Get-MailboxStatistics and away you go.
Next up, a variant of the same, only this time I want to only show those mailboxes larger than, say 1GB:
Get-MailboxStatistics -Server RED-MSG01 | Where {$_.TotalItemSize -gt 1GB} | `
Sort-Object -Property TotalItemSize -Descending | Format-Table DisplayName,TotalItemSize
The Where cmdlet gives me access to comparisons against any propertDispy on the collection of objects passed into it, so be careful where you use it in the pipeline. The collection of objects given by Get-Mailbox is not the same collection of objects given by Get-MailboxStatistics, and they will have different sets of properties. And yes, you put multiple Where cmdlets into different places in your pipeline to fine-tune your selections, as the following search for the Kelly brothers illustrates:
Get-Mailbox -Server RED-MSG01 | Where {$_.DisplayName -imatch "kelly"} | `
Get-MailboxStatistics | Where {$_.TotalItemSize -gt 1GB} | `
Sort-Object -Property TotalItemSize -Descending | Format-Table DisplayName,TotalItemSize
This would show me all mailboxes whose display name contains the string “kelly” (without considering the case of the characters) and that was larger than 1GB in size. The -imatch comparison is a case-insensitive regular expression match, so I could have gotten fairly fancy in my comparison.
Last one: let’s take the list of mailboxes, in ascending order, and feed it to the Move-Mailbox cmdlet. This way, we’ll be moving the smaller mailboxes first, allowing us to get through more moves in the beginning and saving the real packrats for last:
Get-MailboxStatistics -Server RED-MSG01 | Sort-Object -Property TotalItemSize | ` Move-Mailbox -TargetDatabase "RED-MSG02\Mailbox Database"
Let me know if you have questions or comments!
Since I am on the east cost and we are getting a nice little snow storm I thought it woudl be fitting to add the snow theme to the site
Today Mircosoft released its first rollup (RU1) for Exchange 2010 http://www.microsoft.com/downloads/details.aspx?FamilyID=371add31-d7a0-4c8b-8325-a6fced2d05e6&displaylang=en
One of the biggest advantages to RU1 is allowing functionality with RIMs BES servers, however RIM is suppose to release an MR1 soon for Exchange 2010 intergration that will be required on the BES servers
Changes http://support.microsoft.com/?kbid=976573
RIM information to configure Exchange 2010 and BES
http://na.blackberry.com/eng/services/server/exchange/2010support.jsp