Office 2011 for Mac with it’s new Outlook
Entourage is out and a brand new fully functional Outlook client with Exchange support is introduced. This is both very exciting and important for all business users with exchange mail servers.
Office 2011 is being rewritten entirely in Cocoa and is expected to ship later this year.
Mac Mojo: The Office for Mac Team Blog
Image from BGR

Exchange 2010 recordings from Microsoft TechDays 2010
TechDays 2010: Exchange Information Protection & Control (including RBAC)
TechDays 2010: Exchange Performance/Scalability
TechDays 2010: Managing Exchange 2010
Features of Exchange 2010 SP1
Microsoft has just announced Exchange Server 2010 Service Pack 1! A beta of the feature-laden SP1 is headed your way come June 2010.
Mail.app, Exchange server – Inline attachments problem
When applying attachment in mail.app you are allowed to add your attachment anywhere in your body part. If you place it in between some text you end up with two attachment instead of one. One with your acctual attachment and one with the text below where you placed your attachment in the mail.
Here is a "solution" or should I say workaround at Apple support
http://support.apple.com/kb/TS2928?viewlocale=en_US
Symptoms
If you send messages with attachments via a Mail account that uses a Microsoft Exchange server, recipients of the message may see the text of the message as garbled, or split into several attachments.
Solution
As a workaround: In Mail, choose Attachments > Always Insert Attachments at End of Message from the Edit menu.
Additional Information
Tips
- If you are sending only images as attachments, send the message as Rich Text--add some rich text formatting, such as bold or italicized text, or a bulleted list.
- Alternatively, make sure to insert your attachments at the end of your message, after the body of the message.
Mailbox Access Auditing
http://technet.microsoft.com/en-us/library/ee221156(EXCHG.80).aspx
http://www.howexchangeworks.com/2009/09/mailbox-access-auditing-in-exchange.html
Exchange 2007 SP2 upgrade
SP2 adds support for Windows Powershell v2, and allows coexistence with Exchange Server 2010. SP2 also adds support for VSS backups of Exchange 2007 on Windows Server 2008.
Exchange 2007 SP2 updates the Active Directory schema. Details of schema changes, including new attributes and classes, and modifications to existing ones can be found in Active Directory Schema Changes (SP2).
Note, once you install SP2, you cannot uninstall it without uninstalling Exchange 2007 from the server.
Microsoft recommends upgrading Exchange 2007 servers in the following order:
- Client Access Servers (CAS)
- Unified Message (UM) servers
- Hub Transport servers
- Edge Transport servers
- Mailbox servers
More details and important deployment considerations in Exchange 2007 SP2 Release Notes.
Links:
What's New in Exchange Server 2007 SP2
http://technet.microsoft.com/en-us/library/ee221150(EXCHG.80).aspx
Exchange 2007 Service Pack 2 Prerequisites
http://msexchangeteam.com/archive/2009/08/28/452209.aspx
CCR upgrade:
http://www.howexchangeworks.com/2009/08/upgrading-exchange-2007-ccr-to-sp2.html
SendAs right using Exchange shell
Link: http://exchangepedia.com/blog/2007/03/how-to-assign-sendas-right-using.html
You can use the Exchange shell to assign SendAs right (e.g. on a Distribution Group) to a user:
Add-AdPermission "Group Name" -user "User Name" -AccessRights
extendedright -ExtendedRights "send as"
Checking Exchange 2007 transaction logfiles
Link: smtp25.blogspot.com
Verify all the transaction logs to see if they have any corruptions or not
E:\Program Files\Exchsrvr\bin>eseutil /ml E:\Logs\SG1-Logs\e00
"Knowing ESEutil /ML is great, you can use it against one log or all of the logs as I have done it. When ESEutility was stopped on the Log file which is locked, obviously data is either was written to this particular log or was getting committed to database, I did realized now I know which log files have been committed to a database, just in case backup won't happen logs won't get flushed and I get a call in the night, I cannot mount any of the stores due to no space on t he LUN,"
ESEutil /ML E:\Logs\SG1-Logs\e00
Will tell me which logs I can get rid off
Exchange 2007 and Shared Mailboxes
Great links:
http://knicksmith.blogspot.com/2007/03/exchange-2007-and-shared-mailboxes.html
http://net4geeks.com/index.php?option=com_content&task=view&id=14&Itemid=1
Exchange Exams, Microsoft Certified
Exchange 2010
70-662, MCTS, Technoloy Specialist, TS: Microsoft Exchange Server 2010, Configuring
70-663, MCITP, IT Professional, Pro: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010
No upgrade available
Exchange 2007
70-236, MCTS: TS:Exchange Server 2007, Configuring
70-237, MCITP, Pro: Designing Messaging Solutions with Microsoft Exchange Server 2007
70-238, MCITP, Pro: Deploying Messaging Solutions with Microsoft Exchange Server 2007
How to change log level in IIS 7
Describing "Advanced Logging" for IIS 7
How to lower or make log level in IIS higher.
Links:
http://learn.iis.net/page.aspx/579/advanced-logging-for-iis-70---custom-logging/
http://articles.techrepublic.com.com/5100-10878_11-1051006.html
http://technet.microsoft.com/en-us/library/cc754631%28WS.10%29.aspx
Log analyser for IIS/apache
For times when you need more info.
Links:
http://www.msexchange.org/tutorials/Using-Logparser-Utility-Analyze-ExchangeIIS-Logs.html
http://www.iis.net/downloads/Administration
Customising Mailbox Quota Messages
A quota message is an e-mail message that is automatically sent by Microsoft Exchange to the owners of a mailbox or a public folder when a size limit (called a storage quota) for the mailbox or public folder is exceeded. You can use the New-SystemMessage, Get-SystemMessage, Set-SystemMessage, and Remove-SystemMessage cmdlets in the Exchange Management Shell to view existing quota messages or to create, view, modify, or remove customized ones.
Note: |
|---|
| Quota messages are managed by using the Exchange Management Shell. You cannot manage quota messages by using the Exchange Management Console. For information about how to use the Exchange Management Shell, see Using the Exchange Management Shell. |
Note: |
|---|
| When you are working with quota messages, you must specify the language locale for the message (for example "EN" for English). For a list of the supported language locales that are available for use with quota messages, see Supported Locales for Use with System Messages. |
To perform the following procedures, the account you use must be delegated the following:
- Exchange Organization Administrators role
You can use the New-SystemMessage cmdlet in the Exchange Management Shell to create custom quota messages in the language locale that you specify on computers that have the Hub Transport server role installed. The following QuotaMessageType parameter values specify the types of quota messages that you can create with the New-SystemMessage cmdlet. For more information about quota messages, see Understanding Quota Messages.
QuotaMessageType Parameter Values for MailboxesThe following describes the QuotaMessageType parameter values for mailboxes:
- The WarningMailboxUnlimitedSize parameter value specifies the quota message that is sent in e-mail to the owners of a mailbox of unlimited size when the Issue warning storage quota is exceeded.
- The WarningMailbox parameter value specifies the quota message that is sent in e-mail to the owners of a mailbox of limited size (that is, one that has Prohibit send or Prohibit send and receive storage quotas) when the Issue warning storage quota is exceeded.
- The ProhibitSendMailbox parameter value specifies the quota message that is sent in e-mail to mailbox owners when the Prohibit send storage quota is exceeded.
- The ProhibitSendReceiveMailBox parameter value specifies the quota message that is sent in e-mail to mailbox owners when the Prohibit send and receive storage quota is exceeded.
New message
New-SystemMessage -QuotaMessageType WarningMailbox -Language EN -Text "This is a custom quota message."
View a custom quota message
Get-SystemMessage -Identity EN\WarningMailbox | Format-List
Modify a custom quota message
Set-SystemMessage -Identity EN\WarningMailbox -Text "This is a modified custom quota message."
Remove a custom quota message
Remove-SystemMessage -Identity EN\WarningMailbox
Links:
http://technet.microsoft.com/en-us/library/bb232089%28EXCHG.80%29.aspx
http://www.simple-talk.com/sysadmin/powershell/managing-exchange-2007-mailbox-quotas-with-windows-powershell/
http://www.redline-software.com/eng/support/articles/msexchange/2007/customising-delivery-status-notification-messages.php
#554 5.6.0 STOREDRV.Deliver; Corrupt message content ##rfc822; error
When using Thunderbird to send a .doc attachment the e-mail message is rejected by Exchange 2007 with the response: " #554 5.6.0 STOREDRV.Deliver; Corrupt message content
##rfc822;".
In some instances the Thunderbird mail client may send a .doc file (Word attachment) with the incorrect mime-encoding of 'application/applefile'.
See also: Thunderbird normally sends attachments inline (as part of the message body), not as real attachments.
Perform the following steps to resolve the problem:
- Close Thunderbird.
- Navigate to the following directory based upon your OS:
- Windows 2000/XP: %userprofile%\Application Data\Thunderbird\Profiles
- Windows Vista: %userprofile%\AppData\Roaming\Thunderbird\Profiles
- Mac OS X: \Library\Thunderbird\Profile
- Open the directory named with a random set of characters like "yo6luyl8.default". There may be multiple directories if you have multiple Thunderbird profiles.
- Delete the file named 'mimeTypes.rdf'.
Greylisting on Exchange 2007 – Issue with GlitchRetrySeconds
Issue with "When Exchange tries to send mails to certain domains that implement ‘greylisting’, the mails fail to get delivered and an NDR is generated"
- SMTP GlitchRetrySeconds configuration
- http://technet.microsoft.com/en-us/library/aa996601.aspx
- http://theessentialexchange.com/blogs/michael/archive/2007/11/16/exchange-2003-sp2-and-greylisting.aspx
- http://www.tekniken.nu/drift_och_underhall/varning_greylisting_kan_orsaka_problem_i_exchange_2003
- http://smarthost.blogspot.com/2007/08/greylisting-and-exchange.html
Message Tracking in Exchange 2007
Simple-talk, Message Tracking in Exchange 2007 : http://www.simple-talk.com/exchange/exchange-articles/message-tracking-in-exchange-2007/
Exchange 2007 articles
Artiklar som är värt och läsa
En bunta artiklar samlade på simple-talk - http://www.simple-talk.com/exchange/exchange-articles/
Simple-talk, Exchange 2007 Mailbox Server Clustering: http://www.simple-talk.com/exchange/exchange-articles/exchange-2007-mailbox-server-clustering/
Stop / Move a Clustered Mailbox Server in a CCR Environment
Stop a clustered mailbox server i CCR environment
Technet: http://technet.microsoft.com/en-us/library/aa996336.aspx
Technet: http://technet.microsoft.com/en-us/library/aa997179.aspx
PS: Stop-ClusteredMailboxServer -Identity <Name> -StopReason:<Comment>
Move a clustered mailbox server i CCR environment
Technet: http://technet.microsoft.com/en-us/library/aa998282.aspx
PS: Move-ClusteredMailboxServer -Identity:<CMSName> -TargetMachine:<PassiveNodeName> -MoveComment:<Comment>
Accessa bilagor i OWA, filrättigheter, spärrade bilagor
Länk hur man ändrar vilka bilagor som ska blockas i OWA:
How to handle file attachment access in OWA
http://searchexchange.techtarget.com/generic/0,,sid43_gci1307864,00.html
"One of the most important decisions regarding Outlook Web Access (OWA) in Exchange Server 2007 is how to handle file attachments. Users may access OWA from public computers. If you allow them to open file attachments, information contained in those files potentially could be left behind in the computer's pagefile, or in the browser cache. You may want to reconsider giving users the ability to open file attachments to avoid exposure to email viruses.You don't have to block users entirely from opening file attachments with OWA; often there are legitimate reasons to do so. OWA offers five different settings to allowing or prevent users from opening attachments:"
Problem med winmail.dat och Rich-text i Exchange 2007
Förklaring:
Hur man ändrar Rich-text formatet för hela sin organisationen i Exchange 2007
http://forums.msexchange.org/m_1800457416/mpage_1/key_/tm.htm#1800464955
Kb-artiklar från Microsoft
kb138053 : How to Prevent the Winmail.dat File from Being Sent to Internet Users
kb278061: Bifogade Winmail.dat-filer ingår i mottagna e-postmeddelanden i Outlook
Alert: The connector rejected an incoming connection because the maximum number of connections has been reached.
Technet om saken: http://technet.microsoft.com/en-us/library/bb218300.aspx
Exchange 2007 Mailbox Quotas
Bra länk om Quota och skriva egna quotavarningar:
http://www.simple-talk.com/exchange/exchange-articles/managing-exchange-2007-mailbox-quotas-with-windows-powershell/
Transporter Suite, Felmeddelande: TargetServer
När vi migrera IMAP-mailboxar från iPlanet till Exchange 2007 med Transporter Suite får vi följande felmeddelande:
Warning:An item has failed property validation and will be ignored.
IdentifierName: Subject of message in inbox
Error details:Required property is empty.
Property:TargetServer..
Anledningen till detta är att konto som vi kör migreringen ifrån inte har behörighet att lägga migreringsmailen i användarens mailbox.
För att fixa detta måste man sätta upp rättigheter i AD för migreringskonto. Dessa rättigheter "impersonalisation permissions" ska gälla på CAS (Client Access Servers)-rollen och man behöver även vara medlem i "Exchange Administrator".
För att få till impersonalisation rättigheterna kan man köra följande kommando i powershell:
Get-ClientAccessServer | select name,distinguishedname | fl
Vilket ger en DN för den CAS-roll som ska ta hand om migreringen. Denna sträng klistras sedan in i nästa kommando:
Add-ADPermission -Identity "<DN-värdet ovan>" -User <migrerings kontot> -ExtendedRights ms-Exch-EPI-Impersonation
Migrera IMAP mailkonto till Exchange med Transporter Suite
Efter Exchange 2003 finns inte något migeringsverktyg kvar i Exchange. För att migrera IMAP-mailboxar har Microsoft skapat nytt verktyg, Transporter Suite. Eftersom vi ska migera iPlanet IMAP mailboxar till Exchange 2007 kommer vi använda oss av Transporter Suite.
Guider
Transporter Suite
Problem att migrera stora mailbilagor till Exchange 2007
För er som migrerar mailkonto via IMAP till Exchange 2007 och använder verktyget Transporter Suite kan få problem då det inte standardmässigt går att ladda upp bilagor som är större än 4Mb. Anledningen till detta är att IIS webtjänst inte tilllåter att man laddar upp större bilagor än 4Mb. För att komma runt detta kan man konfigurera om (Exchange Web Services) EWS (på ClientAccess-serverrollen) och öka storleken.
Detta gör man i följande fil:
<Exchange 2007 installation dir>/ClientAccess/exchweb/ews/web.config
Lägg till denna texten:
<system.webServer> <security> <requestFiltering> <requestLimits maxAllowedContentLength="1000000000"/> </requestFiltering> </security> </system.webServer>
direkt efter:
<configuration>
och denna texten:
<httpRuntime executionTimeout="300" maxRequestLength="1000000" />
direkt efter:
<system.web>
Läs mer om problemet på följande sidor eller via medföljande pdf.
MSDN konfiguration av httpRuntime värdet
Web: http://msdn.microsoft.com/en-us/library/e1f13641(VS.71).aspx
PDF:
Allmänt om problemet
Web: http://www.exchange2007.com/2008/10/cant-migrate-accounts-using-transporter.html
PDF:
Web: http://support.microsoft.com/kb/925083/
Web: http://support.microsoft.com/?id=944981
Note: