Rollup 2 for Exchange Server 2010 Service Pack 1

Today the Team released Rollup 2 for Server 2010 Service Pack 1 (KB2425179). This update raises version number to 14.1.270.1.

If your upgrading from you need to implement this rollup because the bug Exchange 2007 OWA redirect bug with Exchange 2010 sp1 is fixed check: kb2458419

The List with Fixes:

983186 The mailbox alias of a user contains the "?" character unexpectedly after you run the "Enable-Mailbox" cmdlet to create a mailbox for the user in an Exchange Server 2010 environment

2295902 An excepted occurrence is not excluded from a recurring iCalendar message for an Exchange Server 2010 mailbox user

2385017 You cannot edit public folder items even though you are the owner of the items in an Exchange Server 2010 environment

2385194 You cannot connect to an Exchange Server 2010 mailbox by using a MAPI application when a Mailbox server and a Client Access server are installed on different computers

2397171 You cannot reply or forward a large email message on an Exchange Server 2010 mailbox

2403783 An incorrect label is displayed in the date field in a public folder item when you open the item by using OWA in an Exchange Server 2010 environment

2408924 The subject of an item is deleted when you use the "UploadItems" operation together with the "Update" action or the "UpdateOrCreate" action in an Exchange Server 2010 environment

2409597 You cannot open a public folder item when the default public folder database for the mailbox database is unavailable in an Exchange Server 2010 environment

2423776 The Exchange Information Store service crashes frequently during a public folder replication process on an Exchange Server 2010 public folder

2431500 You cannot connect to an Exchange Server 2010 mailbox simultaneously by using Anywhere from several -based computers

2433642 The "FETCH (BODYSTRUCTURE)" command returns a corrupted file name of an email message attachment on an Exchange Server 2010 computer

2452075 You cannot connect to mailboxes in a recovery database on a server after you install Exchange Server 2010 SP1

2458005  The Exchange Mailbox Replication service crashes when you use the "New-MailboxImportRequest" command to import a PST file to an Exchange Server 2010 mailbox

2458419 "A temporary change has occurred that requires you to connect to a different server" error message when Exchange Server 2007 mailbox users try to access their mailboxes by using an Exchange Server 2010 Client Access server

2322161 The replay queue length on passive copies of mailbox databases in Database Availability Group continues to increase in an Exchange Server 2010 environment

982004 Exchange Server 2010 users cannot access the public folder

983492 You cannot updated content of an Exchange Server 2010 public folder

983549 Exchange Server 2010 removes the sender’s email address from the recipient list in a redirected email message

Download the Hotfix HERE

Post to Twitter

Rollup 2 for Exchange Server 2007 Service Pack 3


Today the Team released Rollup 2 for Server 2007 Service Pack 3 KB2407025. This update raises version number to 8.3.137.3.

The List with fixes:
972186 Some functions do not work if you install Security Configuration Wizard on a Server 2008 SP2-based Exchange Server 2007

979046 Attachments are empty when you save them by using OWA after you have applied the update of KB 958881 on an Exchange Server 2007

980038 The Exchange System Attendant service crashes intermittently in the Oabgen.dll module on an Exchange Server 2007 server

981602 Event ID: 4999 is frequently generated in a mixed Exchange Server 2007 and Exchange Server 2003 environment

982476 The Imap4.exe process crashes intermittently on an Exchange Server 2007 server

982478 Notes URL links in a plain text message are not clickable when you open this message by using OWA in an Exchange Server 2007 environment

2028675 The MSExchangeFDS.exe process occupies lots of memory if there are thousands of OABs created on an Exchange Server 2007 server

2029086 Some characters of an email message are displayed in an incorrect text size when you access your mailbox by using OWA in Exchange Server 2007

2032216 The Microsoft Exchange Information Store service crashes on an Exchange Server 2007 server when you start it or try to mount certain databases

2121536 Exchange Server 2007 cannot index a message

2201236 The "All Day" field is marked with "No" when you access a meeting request that has a duration time that is more than 24 hours by using a mobile client through ActiveSync in an Exchange Server 2007 environment

2203212 Certain mailboxes cannot be moved from an Exchange Server 2007 server to an Exchange Server 2010 server

2210042 A sub contact folder is still visible after you set the "PR_ATTR_HIDDEN" attribute to "True" in an Exchange Server 2007 environment

2230824 The Microsoft.Exchange.POP3.exe process or the Microsoft.Exchange.Imap4.exe process may crash after you enable protocol logging for POP3 or IMAP4 on an Exchange Server 2007 server

2249814 You receive misleading information when you run the "New-TestCasConnectivityUser.ps1" script on an Exchange Server 2007 server

2263342 "The operation failed" error message in client when a user sends a recurring meeting request with an email message attachment in an Exchange Server 2007 SP2 environment

2276439 (http://support.microsoft.com/kb/2276439/ ) The Microsoft.Exchange.IMAP4.exe process crashes when an IMAP4 client retrieves a meeting request that includes exception attachments in an Exchange Server 2007 environment

2280234 "Your POP3 server has not responded in 60 seconds." error message when a POP3 client connects to an Exchange Server 2007 Client Access server to access an Exchange Server 2003 mailbox

2282570 "550 5.1.3" NDR message when an Exchange Server 2007 user sends an email message to a recipient

2265306 The Exchange Information Store service stops responding when you perform a search operation on an Exchange Server 2007 mailbox in Outlook

2282746 The "Private" sensitivity status of an occurrence of a recurring meeting request is lost when you edit the occurrence in OWA in an Exchange Server 2007 environment

2286782 The response details are still included in the response email message when you set the "EnableResponseDetails" property to "False" in an Exchange Server 2007 environment

2290105 A shared document cannot be open by using OWA after you install Exchange Server 2007 SP3 on an Exchange Server 2007 server

2290159 The POP3 service crashes on an Exchange Server 2007 server

2344372  You cannot move mailboxes to an Exchange Server 2007 server

2362371 You receive a "Success" response when using the Test-Mailflow command on an invalid or nonexistent external email address in an Exchange Server 2007 environment

2384754 "Unable to identify local server row in Replication state table for this FID" error message when you run the Information Store Integrity Checker tool on an Exchange Server 2007 server

2387915 The ESEBack component does not support ETL tracing on an Exchange Server 2007 server

2388057 The Exchange Transport service crashes on Exchange Server 2007 servers in a mixed Exchange Server 2007 and Exchange Server 2010 environment

2394731 An HTML attachment of a shared mailbox cannot be saved when you set the "BypassOwaHTMLAttachmentFiltering" setting to "True" in an Exchange Server 2007 environment

2424499 Exchange Server 2007 does not support to assign a mailbox with the "Send on behalf" permission of a security group in the EMC or in the EMS

2427297 The created time and the modified time of an attachment are incorrect when you save an email message on an Exchange Server 2007 mailbox

2430674 The "Leave message intact" method in a Folder Assistant rule does not work when you post an item by using OWA in an Exchange Server 2007 environment

Download the hotfix HERE

Post to Twitter

After installing Rollup 1 for Exchange 2007 SP3 IMAP is now serving most text/plain parts as text/html

After installing Rollup 1 for 2007 SP3 IMAP is now serving most text/plain parts as text/html instead. I had some issue with a simple mail import tool that now imported all mail with html codes.

Before the rollup 1 they were previously multipart/alternative messages with both text/plain and text/html subparts.

Solution:
You can set in through in the GUI or using to set the value to 0 text only

ImapMessagesRetrievalMimeFormat:
0:Text Only
1:HTML Only
2:HTML and Alternative Text
3:Enriched Text Only
4:Enriched Text and Alternative Text
5:Best Body Format

Exchange Management Console:

  1. In the console tree, expand Server Configuration, and then click Client Access.

  2. In the work pane, click the POP3 and IMAP4 tab.

  3. In the work pane, select IMAP4 and then, in the result pane, click Properties.

  4. On the IMAP4 Properties page, click the Retrieval Settings tab.

  5. In the Message Retrieval pane, select a message format from the drop-down list under Message MIME format. I choies for 0

  6. Click Apply, and then click OK to save your changes.

Powershell:

Set-CASMailbox -Identity yourcasserverhere -PopMessagesRetrievalMimeFormat 0

Post to Twitter

Migrating to Exchange 2010 & PDA Sync Issues

Some day’s ago I was testing some PDA’s Mobile and Nokia’s for a Migration to .

I created a little procure to test it.

1. PDA sync at first with ISA 2006 against .

2. Shutdown the ISA 2006 Server

3. Starting the TMG Server

4. Checking if the PDA would sync. (The PDA should be sync with legacy.wardvissers.nl automatically )

5. Move the Mailbox to Exchange 2010 and check again if the PDA sync works.

 

Windows Mobile PDA (6.1).

1. Works fine

2.

3.

4. The PDA will be redirected to legacy.wardvissers.nl and pda sync works great. The User had nothing to do.

5. Moving the Mailbox to Exchange 2010 there is no problem. The user will automatically redirected from legacy.wardvissers.nl to webmail.wardvissers.nl with out any problems.

Nokia E71/E72 (Mail for Exchange Client 3.0.73)

1. Works fine

2.

3.

4. PDA don’t sync anymore. The user must change the sync url manual to legacy.wardvissers.nl than it works again.

5. Moving the Mailbox to Exchange 2010 there is no problem. If you change the url to legacy.wardvissers.nl you must change it manually back.

Nokia E71/E72 With (Road Sync 4.0/5.0)

1. Works fine

2.

3.

4. PDA don’t sync anymore. The user must change the sync url manual to legacy.wardvissers.nl than it works again.

5. Moving the Mailbox to Exchange 2010 there is no problem. If you change the url to legacy.wardvissers.nl you must change it manually back.

Conclusion

Moving PDA users to Exchange 2010 can be a pain in the ass. Best practice is create a list of all PDA users and move them first to Exchange 2010 and than all other users.

Post to Twitter

Exchange 2010 & Outlook 2010 Automatically Shared Mailboxes

When you set full access permissions with the management console on a mailbox,the user which has be giving full access right now there will filed a new property.
image

The property is MSExchDelegateListLink. You can check it with adsiedit.
image

When you open now 2010 you can now see that Wardtest is automatilly Added

image

And additional mailboxes is empty
image

When you migrating from to 2010 and upgraded the Clients to Outlook 2010
Use dis script to set the MSExchDelegateListLink object automatically. Test I first. It’s your own risk.

$a=get-MailboxPermission * | where {$_.IsInherited –eq $False –and $_.accessrights –eq “FullAccess”}
$a | remove-MailboxPermission –confirm:$false
$a | add-MailboxPermission

Save the scripts to MSExchDelegateListLink.ps1

It works great Open-mouthed smile
Source

Post to Twitter

The security certificate on the server is invalid. Contact your Exchange Server administrator or ISP to install a valid certificate on the server. Support Code: 80072F0D or 0x80072f0d

I had some Mobile device that did not sync anymore. I changed the Certificates on and ISA 2006 Servers.

After some investing. The problem was I was missing the GlobalSign Domain Validation CA certificate

image 

After creating the cer file and installed on my PDA active sync works again.

Source:
http://support.microsoft.com/kb/927465

http://support.microsoft.com/kb/915438

Post to Twitter

Exchange 2007 OWA Redirect Bug Introduced with Exchange 2010 SP1

The Customer where I now work has a mix of and 2010 users.  It seems that SP1 has introduced a obvious bug.  Before I get into that, I’ll give some background on how 2010 coexists with previous versions of .
When you have a mix of and older versions in your environment, you have to do a bit of work to make the two work together for your external users.  In a nutshell, you use Client Access Server (CAS) as your primary entry point for all external users. 
Say you use webmail.wardvissers.nl as your externally accessible URL.  If an Exchange 2010 user logs in from the Internet, the Exchange 2010 CAS will do its thing and the user will get a nice Web App screen.
If an Exchange 2007 user logs in using webmail.wardvissers.nl, the Exchange 2010 CAS will redirect the user to an externally accessible Exchange 2007 CAS using a different URL (like legacy.wardvissers.nl).  The redirection is silent, but the user may notice their browser changed to legacy.wardvissers.nl
How the redirect is handled is managed by the LegacyRedirectType setting in the Exchange 2010 OWA virtual directory.  In most cases, LegacyRedirectType is set to Silent.  To see what the setting is in your environment, run:Get-OWAVirtualDirectory -Server <CASservername> | FL Identity, LegacyRedirectType

In SP1, this redirection is no longer silent.  When your Exchange 2007 user logs in via webmail.wardvissers.nl, they are presented with this screen:

The text reads:

A temporary change has occurred that requires you to connect to a different server.  To connect, click the button below.  For security reasons, you’ll be asked to enter your user name and password again.

Sure enough, when you click Connect, you are redirected to legacy.wardvissers.nl, where you have to re-enter your user information.
Thankfully, the same sort of thing doesn’t seem to happen with Outlook Anywhere or ActiveSync clients.
I checked the LegacyRedirectType value on my 2010 SP1 CAS boxes and they are all still set to Silent.  The issue occurs because the OWA virtual directory value for LegacyRedirectType is being ignored.  This is an extraordinarily unfortunate thing to have been introduced with SP1.   If you have a mixed Exchange 2007/2010 environment, I suggest you wait until the rollup 2 is out before deploying SP1. 

Update 15 December 2010

Update 2 for Exchange 2010 and the fix is there described 2458419 "A temporary change has occurred that requires you to connect to a different server" error message when Exchange Server 2007 mailbox users try to access their mailboxes by using an Exchange Server 2010 Client Access server

You can download the rollup HERE

Post to Twitter

Exchange SP1 2010 Setting rights with Public Folder Management Console

For 2007 you had PFDAVAdmin to set rights on the Public Folder store.

For (RTM & SP1) you have the tool ExFolder to set rights on the public Folder store.

But the Exchange Team did a great job to add Public Folder Rights to the Public Folder Management Console.

When you right click on the a public folder you can set permission on two ways.

1. Right click on the public folder and choose Manage Settings

I give my self Owner rights for this little demo.

image image
imageimage
imageimage
image

2. Select Properties from the public folder and then select the Permissions tab.
image

Post to Twitter

Passed the 70-663 Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010 Exam

Last Friday I passed the 70-663 Designing and Deploying Messaging Solutions with Server 2010 Exam with 981 points.

So I am very pleased with it. Last month’s I’m working a lot with . I love the product. Last Friday evening I updated a customer DAG cluster to SP1. Next moth starting moving the 2000 mailboxes from tot Exchange 2010.
image_thumb

Post to Twitter

Exchange 2007/2010 Performance settings on vSphere.

When install a 2007 or 2010 Server on there are some settings that will increase de performance.

- Use de VMXNET 3 Adapter
- Use per Disk a SCSI Controller
- Store the Log & Database files on physical Lun on a SAN
- Use the LSI LOGIC SAS controller for 2008 &
- Use the VMware Paravirtual SCSI (PVSCSI) Controller for Every physical Raw Device Mapping (RDM).

Another TIP.  & needs a lots of Memory. When choosing the size for the OS partition, swap file need also al lot of space.

Post to Twitter