Example: The values in the above screenshot mean OAB is generated once every day.
The Exchange Server 2013 CAS role proxies the OAB download request to an appropriate Mailbox role server.
The CAS role maintains log of each request it handles in the log files, present in folder %Exchange Install Path%\Logging\Http Proxy\OAB\ These log files are an excellent tool to identify which mailbox server the CAS chose to serve the request.
Information of some important fields from the log file: The log file can be imported in Excel for better readability.
Command to enable View Entire Forest: Set-ADServer Settings -View Entire Forest $true Creating a new OAB in Exchange 2013 no longer uses the -Server parameter.
In order to create a new OAB, you should only specify the address lists to be required.
The Exchange team blog article OAB in Exchange Server 2013 introduced the new Offline Address Book (OAB) generation and distribution architecture in Exchange Server 2013.
Take a few moments to visit the article if you haven’t seen it yet or re-visit it for a quick refresher.
Prior to CU5, this will result in frequent full OAB downloads and is therefore, not recommended.The management and administration is different in Exchange 2013 because of architecture changes.Additionally, the new Exchange Admin Center does not currently have options for managing OABs.You might see a “Schedule” defined when viewing properties of Exchange 2013 OAB.But, the Exchange Server 2013 OAB generation take place according to the “Schedule” defined on OAB properties: Instead, Exchange Server 2013 OAB Generation takes place according to OABGenerator Work Cycle and OABGenerator Work Cycle Checkpoint properties configured at the Mailbox Server.