10,039 Views
4 Replies
Last post:
May 8, 2009 2:28 AM by
dEcSup 
0 |
|
votes |
|
Grabbed from NAI:
You may have Group Policy Objects (GPO's) running in the environment where McShield is placed in the System Services policies, or you may be running in an Active Directory domain where Alert Manager has been published to the Object container.
Determining if GPO's are running in the environment where McShield is placed in the System Services policies
You can verify this by retrieving the computer and user policies. These can be obtained by following the below steps:
Go to Start | Run
Type MMC.
When the console appears go to "console" at the top of the window, choose from the drop down "Add/Remove Snap-in".
Choose "add".
Add the component piece "Group Policy"
A window will appear, choose "finish".
Choose "Ok"
Click the plus sign next to Computer Configuration.
Right click "Software Settings", choose export list, and save this as COMPUTER.TXT.
Repeat steps 8 and 9 for User configuration, but label the saved file as USER.TXT.
Search these files for "McShield". If found, this is the cause of the error and McShield needs to be removed from the Group Policy.
Determining if an Active Directory domain exists where Alert Manager is published to the Object container
To determine if AM is published to the Object container you can look at NAI21546: Locating Alert Manager in the Active Directory. This issue will persist after you move one server out of this domain into another or Alert Manager is moved from the Object container. To easily determine if this is the issue, you can rename ADSLOKUU.DLL to ADSLOKUU.OLD. If McShield starts without error then this was the cause of the error.
You may have Group Policy Objects (GPO's) running in the environment where McShield is placed in the System Services policies, or you may be running in an Active Directory domain where Alert Manager has been published to the Object container.
Determining if GPO's are running in the environment where McShield is placed in the System Services policies
You can verify this by retrieving the computer and user policies. These can be obtained by following the below steps:
Go to Start | Run
Type MMC.
When the console appears go to "console" at the top of the window, choose from the drop down "Add/Remove Snap-in".
Choose "add".
Add the component piece "Group Policy"
A window will appear, choose "finish".
Choose "Ok"
Click the plus sign next to Computer Configuration.
Right click "Software Settings", choose export list, and save this as COMPUTER.TXT.
Repeat steps 8 and 9 for User configuration, but label the saved file as USER.TXT.
Search these files for "McShield". If found, this is the cause of the error and McShield needs to be removed from the Group Policy.
Determining if an Active Directory domain exists where Alert Manager is published to the Object container
To determine if AM is published to the Object container you can look at NAI21546: Locating Alert Manager in the Active Directory. This issue will persist after you move one server out of this domain into another or Alert Manager is moved from the Object container. To easily determine if this is the issue, you can rename ADSLOKUU.DLL to ADSLOKUU.OLD. If McShield starts without error then this was the cause of the error.
Yoda 
"Always two there are, a master and an apprentice."
