GitXplorerGitXplorer
d

puppet-sep

public
2 stars
4 forks
0 issues

Commits

List of commits on branch master.
Unverified
079482878da91930b1ade6e8afe6f716c5ca22fb

micro change for the description

ddigglife committed 7 years ago
Unverified
947f2d9450096ddc56f82b9f53b1cb4e7f9edbe4

fix compatibility issue with SEP12 RU6

ddigglife committed 9 years ago
Unverified
d81de14c4d58355e16f94bf28e177ab070e6e956

add symlink.xml example

ddigglife committed 9 years ago
Unverified
eca7761d6bed0b85259dfc36ef0396b00f33036c

add explantion of sepservice resource

ddigglife committed 9 years ago
Unverified
becc5ae5b82f314ef56886332a5fc3bdccd7f6c8

more consistent status description

ddigglife committed 9 years ago
Unverified
cbe1e462fcfe6b89918dae1cecb47f89367ae755

init

ddigglife committed 9 years ago

README

The README file for this repository.

sep

Puppet module for managing Symantec Endpoint Protection.


How to use

class { 'sep':
  source        => '\\UNCPATH',
  deploy_sylink => true,
  sepm_ip       => 'ip_address_of_sepm_server',
}

Note:

  1. The installer packages of SEP for both 64bit(sep64.exe) and 32bit(sep32.exe) Windows need to be copied to \\UNCPATH.

  2. If deploy_sylink is true, sylink.xml, which is the communication file exported from SEPM Server, is required to be placed under files folder. sepm_ip parameter is also required.

Custom Facts

The client status is collected as sep fact. For example:

{
    "managed": true,
    "service": "enabled",
    "definition": "2015-04-28",
    "sepm ": "127.16.1.111",
    "version": "12.1.4112.4156",
    "path": "C:\\Program Files\\Symantec\\Symantec Endpoint Protection\\12.1.4112.4156.105\\Bin\\",
    "online": true
}