This content has been marked as final. Show 5 replies
Sorry, but you've posted in the old "retail" VirusScan 8 forum.. Because you're using a corporate ENTERPRISE version of McAfee, I'll move your topic to the "Desktop and Server" forum where you should receive more responses.. You can access your thread from either forum location:
In the meantime, why not simply remove the check mark from the Access Protection/Common Standard Protection box that causes the problem?.. We do here.. Many of our programs run from the Temp folder and even when it's set to "warn", it causes problems.
Hope this helps.
or if you still need to keep the rule then....
Disable the block on the rule but leave on report
When you have successfully connected via logmein check back in the access protection log and get the exact name of the files being used to include in you processes to exclude.
Alter rule to reflect this
Basically, I need to block users from changing the hostname on their workstation for it is one of major reasons of high failure rate during agent deployment via epo. Customer send as the list of workstation to be deployed but after investigating, we found out that users already rename their PC's as they logged as the local admin. Moreover, it is tedious to ping them one by one...and this is not totally efficient on how can we verify if the wokrastation name still exist..
I configured user-defined rule to block the registry key (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName\ ComputerName)...but does not taking effect...
hope someone might help on this...:(
We cure such problems here by severely limiting the user rights for ALL our users.. We have a few thousand people which have user rights on our agency computers but VERY few have admin rights, (the rest are power users or less), and only one or two folks have the ability to "Add workstations on a domain" to the network.. Should any user with admin rights inappropriately change a computer name, they lose all network access and stop receiving email, access to network shares, and all other such things. They learn in a hurry what is forbidden.
If you can't adjust the user permissions to limit changes, then given admin privileges to lots of people will continue to cause the problem. Although not necessary here, you might look into creating a Group Policy.
Hope this helps.
yeah, someone already advised me on that but customer is pushy on this..:(