Nested manifest in munki-enroll

[tansharma]

Hi, I've just started using munki-enroll and works quite well. I do have a question about the manifest creation though.

Using the script as is for testing, when munki-enroll runs on a new client machine it creates a manifest as clients/host name. However, when i look at the manifest in Munki Admin, under the 'included manifests' tab there appears to be a blank manifest.

So far, I've only been testing on a small batch of machines and have manually removed the blank manifest. I can't work out why this is happening. Is it something you've come across before?

thanks Tan

[edingc]

Tan,

Are these clients set with a default manifest before the munki-enroll script fires? If they are not, that could explain the blank manifest key.

The original intent of the script is to create a client-specific manifest after a "default" manifest has already been specified. So the clients should be set to use site_default or some other all-encompassing manifest before munki-enroll is executed.

The point of having it setup this way is that a large number of machines can be targeted with the general manifest while the individual machines can be targeted using the specific manifests.

Thanks!

Cody

[tansharma]

Hi Cody, Thanks for that. At the moment the client machines do not point to a specific manifest, and i was primarily using munki-enroll to create a specific manifest for each machine. I'll get the machines to point to a common manifest and run enrol again.

Thank you for your help. As someone just staring out with Munki, i've found munki-enroll extremely useful.

regards Tan

[edingc]

Tan,

Glad to help. I highly recommend creating a site_default manifest. It will be very helpful when you need to install an application on every Mac. Inside of editing each client manifest you will only need to modify a single, site-wide manifest.

Thanks.

Cody

[tansharma]

Cody, Thanks for that. I'm in the process of doing that now. regards Tan