Administrators and advanced users of Integration Manager can store registration keys in the Microsoft.Dynamics.GP.IntegrationManager.ini file, which, if it exists, overrides the Registry’s license key information. This allows administrators to set licensing information at the user level, and it is helpful when more than one customer is sharing a Terminal Services server or Microsoft SQL Server® in a data center environment.
The first time a user starts Integration Manager, the software looks for a file named Microsoft.Dynamics.GP.IntegrationManager.ini in the folder where Integration Manager is installed. If it finds an Microsoft.Dynamics.GP.IntegrationManager.ini file, then it uses the settings that are stored there to override some of the default behaviors in Integration Manager.
To use the Microsoft.Dynamics.GP.IntegrationManager.ini in a Terminal Services environment, Terminal Services users need to use separate Microsoft.Dynamics.GP.IntegrationManager.ini files. These separate files store different Integration Manager registration keys that are unique to the user. To do this, Terminal Services users need to modify their Integration Manager shortcut on their desktop with a switch that designates the location of the Microsoft.Dynamics.GP.IntegrationManager.ini file. Append the Integration Manager switch with “/ini=C:\home\TSUser1\Microsoft.Dynamics.GP.IntegrationManager.ini” on the end of the shortcuts target string.
C:\Program Files\Microsoft Dynamics\Integration Manager\Microsoft.Dynamics.GP.IntegrationManager.exe / ini=C:\home\TSUser1\Microsoft.Dynamics.GP.IntegrationManager.ini
Registry information in the Microsoft.Dynamics.GP.IntegrationManager.ini file would appear as follows:
[IMRegistration] SiteName=Fabrikam, Inc. Key1=H94KDFJ9009SDF Key2=J90DF75KDLK0 Key3=LSDKJAF92348UL Key4=F98
Microsoft.Dynamics.GP.IntegrationManager.exe first looks in the Microsoft.Dynamics.GP.IntegrationManager.ini file and checks for the existence of the value SiteName. If SiteName exists, it assumes registration data to be contained in the Microsoft.Dynamics.GP.IntegrationManager.ini file and reads all the keys from the Microsoft.Dynamics.GP.IntegrationManager.ini file. Any missing keys are defaulted to a blank string (as if there were no value for that key). In the above example, Key 5 would be read in as a blank value.
If no registration information exists in the Microsoft.Dynamics.GP.IntegrationManager.ini file, then Microsoft.Dynamics.GP.IntegrationManager.exe checks for licensing information in the Registry.
If you use the Microsoft.Dynamics.GP.IntegrationManager.ini file to store registration keys, the registration dialog box continues to open. To hide this window, under the [IMReg] setting in the Microsoft.Dynamics.GP.IntegrationManager.ini file, add HideMsgBox=True.
If you are using only the Microsoft.Dynamics.GP.IntegrationManager.ini file and no valid registration keys exist in the Registry, the Integration Manager Not Registered window still opens every time you launch Integration Manager. To hide it, select Do not show this window again.