![\"Windows](\"http:\/\/www.heliotropicsystems.com\/blog\/wp-content\/uploads\/SEPM_EventID45.png\" "\\"SEPM_EventID45\\"")
Windows EventID 45<\/p><\/div>\n
Of course, my MSP software is designed to keep trying to get its information back to the data center \u2013 so the Event log just fills up with EventID 45 records as it struggles against Symantec Endpoint Protection.<\/p>\n
There has to be some way of preventing this.
\n
\nThe Symantec documentation (Symantec\u2122 Endpoint Protection Small Business Edition Implementation Guide) describes a process whereby you can create exceptions to eliminate this sort of conflict.\u00a0 Terrific, let\u2019s follow the procedure and update the global Exceptions Policy.<\/p>\n
Creating a Tamper Protection exception<\/p>\n
You can create exceptions for Tamper Protection.\u00a0 You might want to create a Tamper Protection exception if Tamper Protection interferes with a known safe application on your client computers.\u00a0 For example, Tamper Protection might block an assistive technology application, such as a screen reader.\u00a0 You need to know the name of the file that is associated with the assistive technology application.\u00a0 Then you can create an exception to allow the application to run.<\/p>\n
1. On the Exceptions Policy page, click Exceptions.<\/p>\n
2. Click Add > Windows Exceptions > Tamper Protection Exception.<\/p>\n
3. In the Add Tamper Protection Exception dialog box, in the Prefix variable drop-down box, select a common folder.<\/p>\n
When you select a prefix, the exception can be used on different Windows operating systems.<\/p>\n
Select [NONE] if you want to enter the absolute path and file name.<\/p>\n
4. In the File text box, type the name of the file.<\/p>\n
If you selected a prefix, the path should be relative to the prefix.\u00a0 If you selected [NONE] for the prefix, type the full path name.<\/p>\n
5. Click OK.<\/p>\n
6. If you are finished with the configuration for this policy, click OK.<\/p><\/blockquote>\n
So, I added the offending program files, assigned the updated policy to the server, and thought that all would be well.<\/p>\n
Only it wasn\u2019t.\u00a0 Not by a long shot.<\/p>\n
The MSP software continued to generate errors.\u00a0 Symantec continued to block it.<\/p>\n
Open up the documentation again and do some more reading.\u00a0 Aha!\u00a0 I can change the setting for Tamper Protection from \u201cblock\u201d to \u201clog\u201d and assign the updated policy to the server.<\/p>\n
Now that\u2019s better!\u00a0 But only slightly.<\/p>\n
The MSP software is now permitted to run; however, Tamper Protection is still logging the encounter as an error and posts EventID 45.<\/p>\n
Naturally, I opened up a support case with Symantec.\u00a0 Over the past two days, I have spent more than an hour and a half on this, only to find out that \u201cit is known issue and Symantec is working on this.\u201d<\/p>\n
Which is absurd<\/strong>!\u00a0 This product has been on the market for years, and the latest version is supposed to be the best one yet.\u00a0 How can the basic, built-in, functionality of the product not work the way it is supposed to?<\/p>\n
So, I guess I will just have to wait for an update \u2013 after I archive and clear the filled up Event logs from the server.<\/p>\n","protected":false},"excerpt":{"rendered":"
The newly updated Symantec Protection Suite Small Business Edition 4.0 contains Symantec Endpoint Protection 12.1.\u00a0 As part of that offering, there is a module called \u201cTamper Protection,\u201d which is designed to prevent any form of malware from adversely affecting the operation of the Symantec Software. As a managed service provider, I am using a third-party …<\/span> Read More →<\/span><\/a><\/span><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[34,4,32,33,35],"tags":[],"class_list":["post-123","post","type-post","status-publish","format-standard","hentry","category-eventid-45","category-small-business","category-symantec","category-symantec-protection-suite-small-business-edition","category-windows-server-2008-r2"],"_links":{"self":[{"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/123","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=123"}],"version-history":[{"count":10,"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/123\/revisions"}],"predecessor-version":[{"id":187,"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/123\/revisions\/187"}],"wp:attachment":[{"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=123"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=123"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.heliotropicsystems.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=123"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}