The alternative is to allow the OAB files to be deleted during the ExProfRe activity (no /a command-line qualifier) and to incur the peak in network load as the newly moved users connect to the Exchange 2003 SP1 server for the first time.
With this in mind, if your users have a need for Unicode-mode OABs, you may choose, instead of saturating the network links by performing one action, to retain the ANSI-mode OAB files for a short time and gradually move users to a Unicode-mode OAB by phasing in complete OAB deletes and downloads.
If you wish to upgrade the OAB files to run in Unicode mode, then they must be deleted from the client PC and downloaded from the Exchange 2003 SP1 server. If you do so, the OAB files that you retain will certainly be usable with the new Exchange server, but they, like the old OST file, will remain in ANSI mode, since the previous Exchange 5.5 server can create only ANSI-mode OABs. However, we are concerned here with a cross–administrative group mailbox move accordingly, you may choose to specify the /a command-line qualifier to retain the OAB files. This behavior is obviously desirable if you are carrying out an interorganizational migration where the old OAB files are of no use. Irrespective of the version of Outlook in use, running the ExProfRe tool without the /a command-line qualifier will delete the OAB files held locally on the client PC and request a new set of OAB files from the new Exchange 2003 SP1 server. Kieran McCorry, in Microsoft Exchange Server 2003, Deployment and Migration SP1 and SP2, 2006 9.6.4 Mailbox Moves and OAB Files ▪Īutodiscover Service This service also runs on a CAS server and is the one that makes sure the correct OAB URL is returned to Outlook clients.
OAB Virtual Directory This is an IIS virtual directory on the Client Access Server (CAS).This is where the clients download the OABs from. ▪Įxchange File Distribution Service This runs on a CAS server and is the service responsible for getting the OAB content from the Exchange 2007 Mailbox server (OABGen server). OABGen Service This is the service that is running on the OAB Generation server (Exchange 2007 Server with the Mailbox server role installed) in order for the OABs to be created. (In Exchange Server 2007, OABs are located on the Client Access Server in the site.) The OAB mechanism depends on the following components: ▪ (We'll bet that many of you have had your issues with OABs!) To use the new distribution mechanism, it's required that the clients run Outlook 2007, but there's still support for legacy clients (Outlook 2003 and earlier), since you can choose to have both a Public Folder and a Web-based distribution point. OABs in Exchange Server 2007 use HTTP(S) and the Background Intelligent Transfer Service (BITS), which provides us with several benefits, such as support for more concurrent clients, even more reduced bandwidth usage, and finally, much better control over the distribution points. Exchange Server 2007 introduces a completely new distribution mechanism for OABs, a mechanism that isn't based on Public Folders, as was the case with Exchange Server 20.
When dealing with RDP, and restricting it to specific monitors instead of all monitors, everything I have read indicates you get the monitor numbers by using the MSTSC / command.however I see situations where these numbers change because of changing doc.The OAB functionality has change radically in Exchange Server 2007, so before we dive into the configuration settings for OABs, a little introduction to the new behavior of this type of address book is in order.