Exchange Connector for System Center Service Manager

The System Center Service Manager – Exchange Connector connects Service Manager to Exchange for processing incoming emails related to incidents and change requests.

The emails can update the incident action log or change the status of an incident to resolved or closed. Incoming emails with special keywords allow a change request reviewer to approve or reject a review activity and activity implementers can mark activities assigned to them as completed. The SendEmail solution allows analysts to send messages to users via email from the console.

Feature SummaryThis release is compatible with Service Manager 2010 SP1. It contains the final set of features for this version, including

•Create incident from email
•Update incident action log from email
•Resolve or close incidents from email
•Approve/reject change requests from email
•Update change request “action log” from email
•Mark manual activities completed from email
•Add email file attachment to work items as attachments
•Send notifications to users from the console
Go get it @ http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0b48d1f1-434a-4ee6-8017-fc13f4c16785.

Performance Monitoring on Exchange 2010

Here is the good tool to do performance monitoring for exchange 2010 role vice.

How to download
To download these XML files to your computer, right click the file of your choice, select Save Target As… , and then save it to a directory location of your choice on your Exchange ServerRole Based
Use these as a high level look in to how the server is performing and if you need to branch out with more counters, use the Full Counter/Instance set below.

Exchange_2010_Perfwiz-MBX.xml
Other roles coming soon….

All Counters/All Instances
Use this counter set at your own discretion as this could potentially cause performance degradation on your server trying to log this amount of counters.

Exchange_2010_Perfwiz-Full.xml

  1. Open Performance Monitor
  2. Expand Reliability and Performance and then expand Data Collector Sets
  3. Right click User Defined, Select New, and then Data Collector Set
  4. Enter a unique name for this Data Collector set (ie. ExPerfwiz), select Create from a template (Recommended) and then click Next
  5. Select the Browse button, navigate to the XML file that was saved in Step 1, select Open
  6. Select Next on the next screen
  7. Enter in a root Directory of where you would like to store the performance log files. Click Next
  8. If you need to run this performance log under different credentials, enter it on this page. Click Finish

White Space on Exchange 2010 Database

With Exchange 2007 and older versions, one of the key elements that an Exchange administrator needed to keep an eye on, and caused confusion for newcomers to Exchange was the amount of white space in the database.
This is reported as free space in the event viewer via event ID 1221 during the night and is the result of content being removed from the database by the online defrag process.

Reffer this article for moer information:
http://www.amset.info/exchange/event1221.asp

With Exchange 2010, the behaviour of the database has changed.
Instead of doing a online defrag during a fixed time window, it now does it constantly. This means that content that has passed the deleted item retention period, is removed from the database shortly afterwards, rather than waiting for the next online defrag window.

However because the process is running constantly, event ID 1221 isn’t written to the event log. Therefore an administrator may not have a clue as to how much of the database is white space, and how much is actual content.

This question can be easily answered, using EMS, as the amount of free space in the database is available via get-mailboxdatabase -Status:

Get-MailboxDatabase -Status | Select Servername, Name, AvailableNewMailboxSpace

This command will show you the name of the Server the database is mounted on, the name of the database (which is unique across the Exchange org with Exchange 2010) and the mount of space available in the database for new content.
The result will be something along the lines of this:

ServerName Name AvailableNewMailboxSpace
———- —- ————————
XXTCAX010 Mailbox Database 27.75 MB (29,097,984 bytes)

The command used -get-mailboxdatabase -status can provide quite a bit of information about the databases in your Exchange org, use the |fl command to see the full list.