Become a Columnist Microsoft Exchange Site Microsoft Support SiteMSDN Exchange Site

   

Subscribe to OutlookExchange
Anderson Patricio
Ann Mc Donough
Bob Spurzem
Brian Veal
Catherine Creary
Cherry Beado
Colin Janssen
Collins Timothy Mutesaria
Drew Nicholson
Fred Volking
Glen Scales
Goran Husman
Guy Thomas
Henrik Walther
Jason Sherry
Jayme Bowers
John Young
Joyce Tang
Justin Braun
Konstantin Zheludev
Kristina Waters
Kuang Zhang
Mahmoud Magdy
Martin Tuip
Michael Dong
Michele Deo
Mitch Tulloch
Nicolas Blank
Pavel Nagaev
Ragnar Harper
Ricardo Silva
Richard Wakeman
Russ Iuliano
Santhosh Hanumanthappa
Steve Bryant
Steve Craig
Todd Walker
Tracey J. Rosenblath
 
 

MIIS Deployment for Exchange 5.5

Configure Deprovisioning

When a source item is deleted, a process called Deprovisioning is used to remove the object from the metaverse and from the target directories. As you can imagine, considerable time and energy can be spent in developing the appropriate business logic to follow when deprovisioning items.

At this time, we did not create a specialized rules extension to control how items are removed. We feel that the standard deletion on export rule can be used to remove the target entry is the source is deleted. Because of the granular rights assignment and specific containers used for exports, we do not believe additional coding will be required. If additional coding work is required, this is the screen that you would use to specify the change.

 

Configure Extensions

This last configuration screen is used to specify which DLL is used to control the logic for this MA. Currently, there is a single extension DLL used for this MIIS environment. While this basic design works, it is not considered best-practice. Each MA should use its own extension.DLL when possible. To learn more about this concept, see the Developer Reference help file on the MIIS server or search for “Creating a Rules Extension from Multiple Sources.”

 


Business Unit MA

Just as with the Exchange MA, this page shows us the base Management Agent (Active Directory) and the name we have provided to identify the Agent. This name is used within the source code to identify the Connector Space.

 

 

 

 

Connection to Active Directory Forest

In this page, we identify the Active Directory Forest we will connect to as well as the credentials we will use. You can see that we have specified the MIIS user account in order to restrict our permissions to the AD environment.

 


Configure Directory Partitions

It is from this screen that we identify the directory partitions that contain the objects we want to synchronize (copy to) with the Metaverse. From this screen, we can identify any other credentials we want to use (for other partitions for example) as well as the containers we want to choose.

Note: It is important that you select both the source containers and target containers from the Containers window. Deselected containers will not be used for either reading or writing with MIIS.

Select Object Types

We need to expose several different types of information from the Active Directory environment. You will probably need to use the Show All checkbox to select each of these object types.

 



MIIS Deployment for Exchange 5.5


Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008