
Opmantek How-To: Automate your configuration backup with opConfig
Join Paul McClendon, an Opmantek Support Engineer, as he demonstrates how to quickly automate configuration back up using opConfig.
Join Paul McClendon, an Opmantek Support Engineer, as he demonstrates how to quickly automate configuration back up using opConfig.
Join Paul McClendon, Opmantek Support Engineer, as he outlines how to get the Opmantek VM up and running using VirtualBox.
It is possible to import one or many devices using a CSV file, Audit Script Result or an NMIS Nodes file.
Go to menu: Manage -> Devices -> Import Devices from CSV (you can also choose Audit Script Result or NMIS Nodes file.)
Below is an example of the required CSV format:
The minimum required attributes for attributes are ‘name’ and ‘org_id’.
You should not include the edited_by and edited_date fields. These will be automatically set.
If you include the “id” field and set it with a number, that item will be updated rather than created.
You should use a header line containing the names of the columns you wish to populate, then your data lines below that.
"name","org_id","type","ip"
"mail","1","computer","192.168.1.110"
"router","1","router","192.168.1.1"
"laser","1","printer","192.10"
Join Paul McClendon, an Opmantek Support Engineer, as he demonstrates how to create organizations to be used in Open-AudIT.
Orgs (Organisations) in Open-AudIT are a key item. A user has a primary Org as well as a list of Orgs they can access. A user combines this with a list of assigned ‘Roles’ that define what actions they can take on items assigned to the Orgs they have access to. The combination of a users ‘Orgs’ and ‘Roles’ define what they can and cannot do within Open-AudIT.
Most items in Open-AudIT are assigned to an Org, Devices, Locations, Networks, etc, etc.
Orgs can have child Orgs. Think of an organisational chart (tree) structure. If a user has access to a specific Org, they also have access to that Orgs descendants.
Recent Comments