The goal of this wiki page is to provide the necessary steps it takes to go through and set the TargetAddress attribute of a mail-enabled Contact object in a GalSync Solution to something specific using the mailNickName attribute and the msExchOriginatingForest attribute.
By the end of this document, you should be able to implement this into a test environment, and test this scenario and then implement it into production. *NOTE: This wiki page is meant as a guide to illustrate how to customize the GalSync solution. You do not have to utilize the same attributes documented here. Your business rules may require that you utilize different attributes, or want the export to look differently.
This section will cover items to backup. Backing up your configuration before you make a change like this is a best practice and/or a good habit. It will allow you the ability to roll back a change if you it does not work for you. Here our focus will be to backup:
Essentially, you will be making a code change to the GalSync.DLL. This is a DLL that is delivered with the product. It is very possible that in an hotfix update, or service pack install that we could overwrite the default GalSync.DLL file. This is why we recommend to backup the source code, as well as rename the default GalSync Solution. The steps below will guide you through backing up and renaming the default GalSync Solution.
Now that we have backed up our management agent, and source code, we are ready to proceed with making the modifications. This part of the wiki document will display the steps to make the modifications in the Target Management Agent to Export Attribute Flow ( EAF ). The reason we are making the change in Export Attribute Flow ( EAF ) is because we want to leave the original value in the metaverse, and only change the value on export.
The GUI modifications are complete, and now we are ready to modify the source code. This section of the wiki will cover the necessary steps to make the source code modifications. It will be beneficial if you have some knowledge of working with Microsoft Visual Basic .NET, as the GalSync solution is written using Microsoft Visual Basic .NET. We will be focusing on the GalMA.vb file, which is the Management Agent Extension for GalSync. We will be working in the MapAttributesForExport Sub Routine.
The build update path is where the compiled version of the DLL is written too. By default, it will be referencing the Extensions folder under:
We want to ensure that we do not overwrite the DLL without making a backup copy of it first. We also do not want to overwrite the GalSync.XML file. If by chance you do overwrite the GalSync.XML file, follow the information found in the Microsoft Knowledge Base Article 948167. The steps below will guide you through updating the build output path.
*NOTE: A few things to note here:
Case
"_MyNewTargetAddress"
Try
csentry(
"targetAddress"
).Value =
"smtp:"
& _
mventry(
"mailNickName"
).Value &
"@"
"msExchOriginatingForest"
).Value
Catch
ex
As
Exception
Throw
New
Exception(
"Exception Occurred"
& vbCrLf & _
ex.Message.ToString() & _
vbCrLf & ex.InnerException.Message.ToString())
End
"givenName"
"."
"sn"
It is very important to test your new source code prior to allowing it to run in your production environment. We strongly urge you to have a development/test environment. If you do not have a test environment, ensure that you backup your existing GalSync.DLL.
FIM LANDING PAGE: Resource Wiki and Troubleshooter Wiki Index