![]() ![]() You could use a separate policy for those mailboxes that do require Offline OWA and assign that policy to the mailboxes. Get-OwaMailboxPolicy | Set-OwaMailboxPolicy –AllowOfflineOn NoComputers ![]() To disable Offline OWA for all currently present OWA policies use: Set-OwaMailboxPolicy -Identity Default -AllowOfflineOn NoComputers To disable Offline OWA completely for the mailboxes using the Default OWA Policy use the following: ![]() OWA assumes private as default, you can enable the public computer option), NoComputers, or AllComputers which is default. But checking the TechNet page of the cmdlet, we can find PrivateComputersOnly (offline only available when logged in as private. The parameter is AllowOfflineOn, but the possible values aren’t really intuitive or correspond with those visible EAC. Via the Exchange Management Shell you have to use the Set-OwaMailboxPolicy cmdlet. Navigate in the pop-up window to Offline Access and specify your required setting. It can be turned of via the Exchange Admin Center (EAC) via Permissions>Outlook Web App Policies and then edit the policies by double-clicking them. However, as the browser database in which Exchange OWA stores it’s information isn’t encrypted, it can be a security issue. If the users Outlook profile is configured in Cached Exchange Mode, perform below steps to stop receiving sync log emails and errors: Step 1: Open MS Outlook > click on. Step 2: Once confirming the permissions, provide a new Outlook profile to the user. Although the Offline OWA functionality in Exchange 2013 is a great addition for those that cannot use Outlook (Anywhere with Cached Mode), but are frequently without internet. Step 1: Check whether there are appropriate permissions provided by the user on folder. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |