![]() The SymptomsĪs stated before, our deployment package was made via the Official Symantec procedure, in which you export the Installation App from the SEPM with the Additional Resources Folder containing your server and license configuration pointing to your SEPM. I am going to share this information so that you can avoid the heartache and pain that I went through in hunting this problem down and patching it. After doing some digging, I was able to find and patch the problem. ![]() What was worse, was that the deployment package was reporting that it was installing correctly with no errors reported and the Application seemed to be running fine. This, coupled with problem report tickets for SEP and Mac that came in, showed us an alarming trend…Our Macs running 10.11 were not linking back to our server despite having all of the information to do so. With all the fun news from the end of last month with Symantec, we have been closely examining our SEP deployments and their linking back to the SEPM. These installations are then linked and managed by a Server with Symantec Endpoint Protection Manager (SEPM) installed on it. Without going into great detail about our environment for obvious reasons, we use the latest version of the Symantec Endpoint Protection (SEP) that we deploy through our MDM Server. ![]() ![]() Here is a fun little issues that I came across in my work’s Mac Environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |