Passed 70-238 with a 908

This test was just weird. 70-236 and 70-237 were right on with the MS objectives, however this one was just all over the place. I obviously can't say much about it, but like any other test, if you have real world experience and know your stuff, you'll pass. At the time of this post, neither 237 nor 238 have books released so I just took the tests blind (but with 2nd shot) and passed easily from being in the trenches with exchange 07.

Passed 70-237 with a breeze

That was a little too easy I think, I got a 921, again the exam objectives on the MS site are all covered, know your AD infrastructure or don't even try this one.

Passed 70-236 today, taking 237 friday

Obviously I can't say much about it, but the exam objectives listed on MS's site were dead on. The test did make me wonder who really backs up the queue databases on their hub transport servers?

There is no book out for 237, so I'm taking blind (thank goodness for 2nd shot). Wish me luck.

Public Folders and Exchange 07

So SP1 gave us some GUI management, but still no way to set permissions with the gui other than 'send as'. The 2 most common resolutions to this problem are 1. Leave PF's on Exchange 2003, and 2. Suck it up, and deal with it in powershell; here is how:

To modify the permissions of a top level folder to give the user "sally" editor rights and have this permission apply to all sub-folders, execute this command:

get-publicfolder -"\top level folder name" -recurse PIPE add-publicfolderclientpermission -accessrights "editor" -user "sally"

Use the pipe symbol, not the word, for some reason the symbol doesn't show up on blogger.

editing the default recipient policy

For most of us, using the cmdlet

set-emailaddresspolicy "default policy" -includedrecipients allrecipients

will work fine, however some will get an error stating:

Unable to edit the specified E-mail address policy. E-mail address policies created with legacy versions of Exchange must be upgraded using the 'Set-EmailAddressPolicy' task, with the Exchange 2007 Recipient Filter specified.

This is generally because of a mailbox manager setting applied to your default policy, and exchange 2007 doesn't do mailbox manager. Remove the mailbox manager settings and re-run the command.

Creating Exchange 07 mailboxes with ADUC

If you use active directory users and computers to mail enable a user account with an exchange 07 mailbox, it'll probably work and seem fine in outlook until the user tries to hit OWA. Then they'll get the error below. Also, EMC will list their mailbox as 'legacy mailbox'. To resolve, execute this cmdlet: Set-Mailbox username -ApplyMandatoryProperties


RequestUrl: https://webmail.company.com/owa/lang.owa host address: 192.168.10.10
ExceptionException type: Microsoft.Exchange.Data.Storage.StoragePermanentExceptionException message: There was a problem accessing Active Directory.Call stack
Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostLocally(OwaContext owaContext, OwaIdentity logonIdentity, CultureInfo culture, String timeZoneKeyName, Boolean isOptimized)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Inner ExceptionException type: Microsoft.Exchange.Data.Directory.InvalidADObjectOperationExceptionException message: Property Languages cannot be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. Current version of the object is 0.0 (6.5.6500.0).Call stack
Microsoft.Exchange.Data.Directory.PropertyBag.set_Item(PropertyDefinition key, Object value)
Microsoft.Exchange.Data.Directory.ADObject.set_Item(PropertyDefinition propertyDefinition, Object value)
Microsoft.Exchange.Data.Directory.ADObject.StampCachedCaculatedProperties(Boolean retireCachedValue)
Microsoft.Exchange.Data.Directory.ADObject.ValidateWrite(List`1 errors)
Microsoft.Exchange.Data.Directory.Recipient.ADRecipient.ValidateWrite(List`1 errors)
Microsoft.Exchange.Data.Directory.Recipient.ADUser.ValidateWrite(List`1 errors)
Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties)
Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()

Exchange 2007 SP1 rollup 1

Its got a lot fixes listed here: http://support.microsoft.com/?kbid=945684

All went fine for me in lab testing and in production rollout, however it did not start any of the exchange services upon completition, nor did it start IIS on the CAS server or ask for a reboot, so be prepared to either reboot or manually start all services.