Endpoint Services, Munki, What are the details of the CSV file used for adding endpoints to Multi-tenant Munki?
Describe the Multi-tenant Munki CSV input file.
Munki Mac Endpoint Management
University of Illinois IT Pros leveraging Technology Services Endpoint Service Munki Mac Endpoint Management
Enrolling multiple MacOS endpoints in Multi-tenant Munki is accomplished via a comma-separated values (CSV) file. Each row in the CSV represents what to do with that endpoint. Each endpoint should be uniquely described by the MacOS serial number.
- The columns in the file can appear in any order but the first line (row 1) of the CSV file must contain headers with specific names indicating the data expected in that column.
- Tick the checkbox for any column you are providing in your CSV file. Unchecked columns won't be processed and don't need to be supplied in your CSV. Columns provided in your CSV that aren't checked or additional columns beyond those checked in the submission webpage will be ignored.
- Your CSV should be in UTF8 and can use either CRLF or LF line endings.
If you don't describe whether to add or delete an endpoint, any endpoint with an unknown serial number is added to Multi-tenant Munki when the "Add" checkbox is selected in the portal. Multi-tenant Munki will ignore an endpoint if you specify a serial number Multi-tenant Munki doesn't already know about and do not select "Add" in your checked series of columns on the portal.
If you check both "Add" and "DELETE" on the webpage, and supply an unknown serial number in your CSV where the "DELETE" column is set to
1, Multi-tenant Munki will produce an error because you're asking for Multi-tenant Munki to both add and remove the same unknown serial number.
Multi-tenant Munki preprocesses as much as possible and verifies as many potential issues with the CSV before starting processing. So, if two rows have the same name or serial number, the entire CSV errors out with a message giving the offending serial number or name.
If you download a CSV from the system, all the columns that can be processed are represented. There are a few attributes for the "Window" or "status" that are listed as (ro) as they will be ignored upon reupload.
Example CSV download:
Repository,Name,Serial Number,Client Identifier,Use Template,Force Retemplate,Rename on Install,Window,Status(ro),Window Start(ro),Window Close(ro),Delete /global/UofI/UIUC/test,swan-childrss-sierra-vm,VMh9nfsiEBHn,everything_raw,0,1,1,0,ungenerated,2017-06-06 16:45:24,2017-06-11 16:45:24,0
The columns you can check in the submission webpage and provide in your CSV are as follows:
|Name||Specifying a name, for example
Best practice: set this name to fit the format dept-serialnumber where "dept" is the same department or unit prefix used in Active Directory for naming objects followed by a hyphen and the serial number of the endpoint.
|Repository||The full path hierarchy of the repository, for example
|Serial Number||Required field—Serial number of the machine; this is used as the key for uploads.|
|Client identifier||This field name is case sensitive. This field will set the manifest name, known as
|Rename on Install||
|Window||The default window length is 0 minutes if this field is left blank. Specifying a window length will reopen the window on any computer with a non-zero window time.|
|Use Template||Setting this field will force the the
|Force Retemplate||will force any endpoint with "Use Template" set to
|Repository||Should the repository for the endpoints in this CSV be changed to match the repository listed for this CSV?|
|DELETE||Setting this field to