ConfigMgr 2012 and McAfee
Back to ConfigMgr main menu
ConfigMgr 2012 and McAfee VirusScan do not play nicely together. The main reason is that McAfee cannot handle DISM. This is well documented and available on the McAfee website.
https://kc.mcafee.com/corporate/index?page=content&id=KB76867&actp=LIST
So what problems can this cause
1. Boot images are not created during ConfigMgr installation. This is a real pain.
2. You cannot use DISM to manually create the boot images - you get access denied error.
3. You cannot add drivers to the boot image. The process fails as it uses DISM.
The solution is to disable both Access Protection and On-Access Scanner before you carry out any of these tasks. You can enable them again afterwards.
This is the official guidance from McAfee - see the link above.
ConfigMgr 2012 and McAfee VirusScan do not play nicely together. The main reason is that McAfee cannot handle DISM. This is well documented and available on the McAfee website.
https://kc.mcafee.com/corporate/index?page=content&id=KB76867&actp=LIST
So what problems can this cause
1. Boot images are not created during ConfigMgr installation. This is a real pain.
2. You cannot use DISM to manually create the boot images - you get access denied error.
3. You cannot add drivers to the boot image. The process fails as it uses DISM.
The solution is to disable both Access Protection and On-Access Scanner before you carry out any of these tasks. You can enable them again afterwards.
This is the official guidance from McAfee - see the link above.
No comments:
Post a Comment