I want to set the OWA parameters for a user back toblank. I cannot get the Set-CASMailbox to accept $null. Problem: I thought I'd get fancy and set the OWAJunkEmailEnabled parameter to True in the EMS. When I did this, I noticed I only got the Light version of OWA. Inventigating further, I discovered that after I used the above command, that all the OWA... parameters (OWACalendarEnabled, OWASContactsEnabled, etc.) were set to False (as seen in the Get-CASMailbox cmdlet) Looking at other users on other mailboxes that I didn't muck with, I noticed that the users had blanks defined. How do I reset these back to blank? Using Null, 0, $Null.... all told me I was not permitted to do so, (I attempted to set -OWAJunkEmailEnabled $null Error: "Set-CASMailbox : "OWAJunkEmailEnabled" cannot be set to an empty value (null) in Exchange 2007 virtual directories." Edit: Adding insult to injury... I just figured out this doesn't set the setting.... but determines whether or not OWA sees it... uggg. Anyway, any help would be much obliged.

Hi, Thank you for postingon the forum firstly. The current problem as I understood is like below ===================================== while setting any attribute\flag about CASMAILBOX, other flags including OWAPremiumClientEnabled become false. Thus OWA premium appearance not be available, it only can show the legacy light appearance, correct? I would like to say that I also have reproduced the symptom. Based on my research till now, it seems that cannot change them back to the blank. It seems that these flags type has been changed from system.Nullable to System.Boolean. it only allow $true or $false this time, we can manually set these flags value. I am not sure if it is a designed issue. I will do efforts to consult and give you a update if I get the correct answer. Thanks you for your understanding. Currently, let us set OWAPremiumClientEnabled flag to $true, this should make the premium appearance back from light. Set-CASMailbox -identity adam@contoso.com OWAPremiumClientEnabledtrue Note: for above adam@contoso.com mentioned, It is just a sample. More information: ============= Set-CASMailbox http://technet.microsoft.com/en-us/library/bb125264(EXCHG.80).aspx Regard, Jason

Hi Has a fix been released for this issue? It is very annoying to change one attribute in a users OWA config and for it then knock out all the other features. Is there a way to reset the settings in an OWA config. Would be nice for these segmenation options to be provided "Per user" in the ESM GUI. Regards Anthony

Hello, Sorry for delay response to this thread. Actually during this time, I also sent a internal discussion regarding this question. According to our discussion feedbacks, Those OWA flags (e.g. OWAPremiumClientEnabled) is stored in Mailbox Folder Set in Exchange 2007. We have performed intensive tests for it. We confirm that this result, When setting a single OWA parameter using the set-casmailbox cmdlet to true sets all other OWA features to False. Its indeed not a desired result, but I am not sure whether any RU(rollup update) can fix it. Good news is that it looks like those flags are not in the next generation of exchange product so this problem never happen again. Here is an workaround of this problem. Cause ====== When setting a single OWA parameter using the set-casmailbox cmdlet to true sets all other OWA features to False which is not a desired result. Note: Disabling or enabling any of these features on a user object override the settings stored on the OWA virtual directory. Resolution ======== When setting any OWA parameter, we update bits on the msExchMailboxFolderSet attribute for each user object. If you want to set only one feature to FALSE, you have to set all of the other parameters to TRUE. For example, if you want to disable the OWA premium client for users, you would set -OWAPremiumClientEnabled to false, but also set all other features to TRUE so that users do not lose any other functionality. Here would be the command syntax. Code Snippet set-casmailbox -identity "DOMAIN\USER" -OWAChangePasswordEnabled:$true -OWAPremiumClientEnabled:$false -OWACalendarEnabled:$true -OWAContactsEnabled:$true -OWATasksEnabled:$true -OWAJournalEnabled:$true -OWANotesEnabled:$true -OWARemindersAndNotificationsEnabled:$true -OWASpellCheckerEnabled:$true -OWASearchFoldersEnabled:$true -OWASignaturesEnabled:$true -OWAThemeSelectionEnabled:$true -OWAJunkEmailEnabled:$true -OWAUMIntegrationEnabled:$true -OWAWSSAccessOnPublicComputersEnabled:$true -OWAWSSAccessOnPrivateComputersEnabled:$true -OWAUNCAccessOnPublicComputersEnabled:$true -OWAUNCAccessOnPrivateComputersEnabled:$true -OWAActiveSyncIntegrationEnabled:$true -OWAAllAddressListsEnabled:$true To enable all features, you can run the following command changing the user that you want to modify. Code Snippet set-casmailbox -identity "DOMAIN\USER" -OWAChangePasswordEnabled:$true -OWAPremiumClientEnabled:$true -OWACalendarEnabled:$true -OWAContactsEnabled:$true -OWATasksEnabled:$true -OWAJournalEnabled:$true -OWANotesEnabled:$true -OWARemindersAndNotificationsEnabled:$true -OWASpellCheckerEnabled:$true -OWASearchFoldersEnabled:$true -OWASignaturesEnabled:$true -OWAThemeSelectionEnabled:$true -OWAJunkEmailEnabled:$true -OWAUMIntegrationEnabled:$true -OWAWSSAccessOnPublicComputersEnabled:$true -OWAWSSAccessOnPrivateComputersEnabled:$true -OWAUNCAccessOnPublicComputersEnabled:$true -OWAUNCAccessOnPrivateComputersEnabled:$true -OWAActiveSyncIntegrationEnabled:$true -OWAAllAddressListsEnabled:$true If you would like to set this back to the default where msExchMailboxFolderSet is not set on your users, you can use ADModify to do this following the below steps. - Run ADModify, and click Modify Attributes. - Select the domain and domain controller from the drop-down list. - Add the users, and click Next. - Click the Custom tab. In Attribute Name, enter msExchMailboxFolderSet, and under Attribute Value, type null or set it to 2147483647 to enable all OWA features. - Click Go. To verify if this was set correct, run get-casmailbox username | fl to verify that there are no values for any of the OWA features or all values are set to true if you set MSExchMailboxFolderSet to 2147483647 . Keep in mind that OWAEnabled is not part of OWA segmentation and is controlled by the ProtocolSettings attribute which by default is set to Null which means that OWA is enabled. Thanks for your attention. -Jason