Coding Optimization
Those with a developer background will notice that
the code used in the appendix is not the cleanest. While the code
functions and meets the requirements of the project, it could certainly
be optimized. Development projects can always be fine-tuned, optimized
and structured better. This environment is no different. In addition to
optimization, there are several optional functions that could be
implemented:
·
Better Exception code could be handled. In other words,
emails could be sent programmatically to alert the administrator if a
disconnect or delete event is triggered.
·
Exception code could also be added to write log files or
send an email to alert the administrator of coding violations or MIIS
errors.
·
The country code information between AD and Exchange is
much different. Currently, the country code format that must be used in
Exchange is the two-letter designation as specified in the ISO
standards. For example, US for United States and GB for the United
Kingdom. A much more sophisticated lookup table could be converted to
allow for different standards to be used in Exchange (and compatible
with AD) such as United States or U.S.A.
·
The Hide From Address Book flag could be synchronized so
that hidden objects could be replicated in the same hidden state
·
The MAPIRecipient attribute could be replicated to force
rich text between the systems.
·
A much more sophisticated deprovisioning logic could be
put into place to provide “tombstoning” to occur within the MV for
deleted source objects.
·
Logic could be added to the code to block rights to
objects that are not in the target container. In some instances, a
contact in a target system could be “joined” by another object and an
attempted write can occur. This is remedied by setting permissions on
the containers, but it would be cleaner to implement some logic during
the write that verifies the object’s DN matches the folder specified in
the provisioning code
|
