msExchMailboxFolderSet<\/em> attribute of one or more users, which actually stores the segmentation settings for a mailbox-enabled user in AD. Depending on the features that are enabled and disabled, this attribute will have a different value. But these are the two which may help you out to reset the value of all OWA* properties for a user to True or to the default value of <not set>.<\/p>\nTo reset the value of the parameter to the default <not set>, just run the following line:<\/p>\n
Set-QADUser ‘<domainname>\/<OU>\/username’ -objectattributes @{msExchMailboxFolderSet=$Null}<\/em><\/p>\nTo set the value of all properties (starting with OWA) to $True, just run the following:<\/p>\n
Set-QADUser ‘<domainname>\/<OU>\/username’ -objectattributes @{msExchMailboxFolderSet=2147483647}<\/em><\/p>\nSo, for example, if you want to disable the ability of user A\u00a0to change\u00a0its passwords using OWA, I would run:<\/p>\n
Get-QADUser<\/em> ‘<domainname>\/<OU>\/user A’ <\/em>| Set-QADUser -objectattributes @{msExchMailboxFolderSet=2147483647}<\/em><\/p>\nSet-CASMailbox\u00a0 UserA -OWAChangePasswordEnabled:$False<\/em><\/p>\nFor other settings, create or use a test user, and see what the value is of the attribute msExchMailboxFolderSet, and you’re ready to change the setting for any amount of users at once \ud83d\ude42<\/p>\n
$testuser = Get-QADUser UserA<\/em><\/p>\n$testuser.msExchMailboxFolderSet<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"When you use the EMS cmdlet Set-CASMailbox to configure user-based segmentation for Outlook Web Access, you may already have noticed that even though you set the value of just one property to $False, by running a simple line like<\/p>\n
Set-CASMailbox UserA -OWAChangePasswordEnabled:$False<\/p>\n
Exchange will set the value of all properties starting with OWA to $False, thereby disabling almost every feature of Outlook Web Access for that user or the users you selected to change. Exchange will enable the ability to change the password using OWA, but will disable all other features that weren’t explicitly enabled or disabled prior to running the cmdlet. There are quite a few easy ways to reset or undo the changes.<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[160,25],"tags":[50,88,998,267,265,28,158,264,266],"class_list":["post-579","post","type-post","status-publish","format-standard","hentry","category-exchange-management-shell","category-windows-powershell","tag-exchange","tag-exchange-2007","tag-exchange-management-shell","tag-get-qaduser","tag-owa","tag-powershell","tag-quest","tag-set-casmailbox","tag-set-qaduser"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t