When your customer area is created on the MIE, one of the options is to link you to a master MSL (also called the Wiki Master). When you are linked to a master MSL, the following rules apply:
1. You will have your own, independent MSL, however you will inherit all MSL entries from the master to which you have been linked.
2. Any new entries added to the master will appear in your MSL after the next Consolidate run only if the setting SLMLinkedMSLUpdateOnly is set to 0. Generally, new entries will be not be marked as being on your MSL nor will they be marked for watching compliance. In other words, they will show up as new entries in your list of MSL titles on the MIE, but they will not appear in your compliance reporting. You must explicitly set any new entries to be on your MSL and to be watched for compliance.
3. Your linked MSL entries will be updated with any updates to the master each time Consolidate runs. You may exclude certain columns from being updated by adding a list of columns to be excluded to the setting SLMLinkedMSLColsNoUpdate. For example, if you set SLMLinkedMSLColsNoUpdate to "Publisher,Description,Version", then your MSL spellings for Publisher, Title, and Version will be preserved and will not be updated from the master (those columns are normally kept synchronized with the master's spellings.)
4. You are free to add titles to your MSL. Those titles will not be changed nor deleted. Be aware, however, that at some time any titles you add to your MSL may be added by ESI to the master, at which time you may have the same title in your MSL twice (once due to the master and once due to yours). (This will happen if your setting SLMLinkedMSLUpdateOnly is set to 0, which means you inherit any new MSL titles added to the master). You should first ask ESI to add any titles you would like to see to the master to avoid having duplicate titles in your MSL. (Keep in mind that if that happens, the title that comes from the master will initially be set to be ignored by your compliance reporting, so users will still only see one entry for the duplicated title.
5. Your MSL will be updated from the master every time Consolidate runs.
NOTE: Consolidate will now only synchronize MSL titles that are included in the list of Publishers and Families that are configured in the customer record. Publishers are configured in the ‘Restrict WiKi Master synchronization to these publishers’ input. Families are configured in the ‘Restrict WiKi Master synchronization to these families’ input.
6. Software aliases presented by auto-discovery will be copied to the master MSL area for recognition training against the master. They will also be copied to your customer area.
7. Recognition will be performed against both the master MSL and your MSL. This means you inherit the recognition assigned to the master (and therefore the training efforts of whoever is maintaining the master. This also allows you to augment the master with additional training against your MSL.
8. Any downbound equivalent titles defined at the master level will be replicated at your local customer level. For example, if at master level Office 2007 Pro has been set with downbound equivalents of Office 2003 Pro and Office 2000 Pro, then if you also have Office 2003 Pro and Office 2000 Pro on your local MSL and those titles are "opted in" (linked to their equivalent master titles), then your local record for Office 2007 Pro will have your local records for Office 2003 Pro and Office 2000 Pro added as downbound equivalents.
9. Any upgrades defined at the master level that target a title that you have locally and which has been linked to an equivalent master title will by copied (if they don't already exist). For example, if the Wiki Master has Acrobat X Pro Upgrade defined as an upgrade, with the target title set as Acrobat X Pro, if you have Acrobat X Pro defined on your local MSL and that title has been linked to Acrobat X Pro at Wiki Master level, then the upgrade will be copied to your local upgrades. Any current upgrades will not be affected (however, if you already have an upgrade defined for Acrobat X Pro, you will end up with two). In that case, you should remove the locally defined upgrade in favor of the master. Any titles that are defined at master level that are qualifying titles will also be copied to your local upgrade record if you have those same titles defined locally and if those titles are also linked to their equivalent master title. You may add more local qualifying titles and those you added locally will not be affected.
NOTE: If the target MSL title for a master upgrade changes, and you have a local linked copy to that upgrade, your local MSL target will also change and any titles currently defined as qualifying titles - whether added locally or not - will be removed and replaced with qualifying titles defined at the master level (under the same conditions as described above). This will only happen if the target MSL title changes at master level.
10. Any suite components defined at the master level that correspond to a title you have locally will be copied (if they don't already exist). If you have added other titles as components of a suite, those titles will remain - only titles that you have locally that match titles at master level that have been defined, at master level, as components of a suite will be copied down.
