In case if different security groups are imported by separate import rules it causes a problem when membership is overwritten.
For example: GroupA and GroupB contain same object Computer1. Two separate import rules created to import groups. First import rule (GroupA) imports group and correctly assigns Computer1 as a member. Second import rule creates GroupB and assigns Computer1 as a member. However, Computer1 is being removed from GroupA when second import rule runs.
This issue has been reported to the Symantec Development team. A fix is planned for a next release (current release is ITMS 7.1 SP2 MP1 Rollup v3 (see HOWTO81832). Current ETA is for ITMS 7.1 SP2 MP1 Rollup v4
Imported Document Id
This is machine translated content
Login to Subscribe
Please login to set up your
For security reasons, your link to this document has expired. Please click on the attachment link to access this file.
The attachment that you are looking for no longer exists.
There has been an issue retrieving your attachment. Please try again.
Didn't find the article you were looking for? Try these resources.