I have alredy disable disk drive , i want to disable mobile devices.
SEPM has four client machines listed as disabled on the home page. I've gotten email notications about them and noticed that. When I checked then, the machine and SEP look fine. Only one of these four is within range for me to check/accessible but it's in use right now.
I can't tell from SEPM what's disabled about them. What does it mean when the home page lists them as disabled?
And is there any way from SEPM to re-eneable them?
Switching views in SEPM, I see two (both Windows) have for SONAR Status, "Component is Malfunctioning." The other two are Macs and don't have that installed.
Simply reinstalling sounds easiest, except the machines aren't easily available.
We have an issue using SEP 14 mp2 with point-of-sale software. For banking transactions to be processed through a credit card machine, IPS has to be disabled. When it is enabled, under the logs the only thing I can see is a sort of hardware address that is allowed to go through from NTP.
Anyone come across this issue? I definitely dont want to disable IPS for obvious reasons but what can I do to get the point-of-sale software to process
the transaction through the workstation connected to the credit card swiping device?
Am new to SEP 14.
Want to find 'system infected' alerts for the past month.
NTP is now replaced with network & host mitigation.
Can someone help me?
Has anyone come accross this problem on Server 2008.
I am running SEP 14.0.2415.0200 and it seems that after a second reboot it no longer disables windows firewall which is stopping our backups from working as well as other things.
Is there any fix around this without having to upgrade to the latest version of SEP as we need the backups to work and other applications ASAP.
Can anyone help as I have been looking at this the pass day.
We have just gone live with a new SEPM server version 14.0.2415.200 and all was working well servers were backing up and all was fine.
However, since then we have discovered that after the servers are rebooted a second time Symantec seems to be blocking Netbackup 7.1 from working with error code 58.
I can connect from a client to the server over ports 13724, 13782, 1556 but cannot connect from the server to the client over the same ports.
As a test I have opened all ports on our firewall settings and still getting the same results.
Randomly though some of the servers are working, they all have the same firewall settings so it seems to be a bit hit and miss.
Upgrading to the latest version currently is not possible as we are going through an audit. Has anyone come across this or any ideas on a fix?
Brand new Mac, High Sierra.
SEPM was 14.0 MP1. That got upgraded to 14.0.1 MP1, the latest. I made a Mac installer from there like normal.
The Mac got 14.0 MP1 on it, and then I realized it wasn't showing up in SEPM, so we upgraded today.
I installed 14.0.1 MP1 over 14.0 MP1 on the Mac. No change.
Then I used a RemoveSymantecMacFiles.zip (from 2015, might be the problem). That ran. SEP was gone that I could tell. Then I installed 14.0.1 MP1. It still isn't showing up in SEPM.
Do I need a newer uninstaller for High Sierra or is somethign else going on?
I just upgraded and I see that.
Is this it?
Is there an option now for SEP on tablets?
When trying to add devce to device groups the tree is cut off by athe gray bar at the bottom. I cannot access the groups hidden behind it
Here is the log:
[AC13-1.3] Block from launching other processes - Caller MD5=9021640543c224ead0152983f446e383 - Target Arguments=""C:\Users\xxxx\AppData\Local\Temp\9\scmhelper_1518711714731.ini" GetDiskSpace "C:\support\SEP 14 Clients\SEP14_Virtual Server""
How do I get past this?
I'm running SEPM out of a Windows 2012 server, trying to push SEP clients to my endpoints. The whole process goes fine until the very end, at the "Deployment Summary" screen, where under "Deployment Status" it says "Failed." The same thing happens when I push communications packages.
There is no error code, or any indication of a problem until the final "Deployment Summary" screen.
This problem persists across endpoint operating systems, and regardless of whether or not the endpoint already has an SEP client. Turning off Windows Firewall did not fix it.
Last summer, we moved all of our machines from the old P1 server onto the new P2 server. But I ran SymDiag on one of the machines, and it indicated that it was communicating with the P1 server. Pushing a communications package from the old P1 did work, but I can't work out why it isn't working with the new server.
Anyone else encountered this issue? Is there a fix, or a workaround?
Symantec has known about the Storage Space drive issue with Surface Laptops for over 6 months. It was reported in July 2017, confirmed again (many times) in November 2017, December 2017 and January 2018 through posts in the forums.
When is there going to be a solution available for the installation of Symantec 14.x onto Storage Space Drives - specifically the ones found in the MS Surface Laptop? And what happens when MS and Dell both start using the Storage Space Drive option in the rest of their laptop systems?
I'm sure as a company Symantec doesn't want to give up any ground in the marketplace but it has been over 6 months and no updates or progress notifications.
Check it out for yourself - all of the new MS Surface systems with 1tb HD's are *only* coming with the storage space drive configured from the factory...
It is possible to disable a computer for a time interval when the Symantec Endpoint is not updated with the latest updates from the management console?
If it is possible how I can do that?
We have made external reporting setup to be able to send log files to splunk.
However we notice that the log file is not updating. The update frequency is set to 30 seconds and we can see .tmp file being updated but not the log file.
Any idea how we can change the settings so it is updating frequently.
I have noticed that the agt_risk.log (and other logs) is not updateing from agt_risk.tmp file.
We need log files to be able to load them into splunk.
Any idea why it is not updating and how can we change the update interval of External Logging?