Essentially, what it does is move the unique-client logic from the server to the client.
As you scale upwards in client numbers, having huge numbers of unique server-side manifests induces significant overhead – potentially 10,000 unique manifests in your Munki server’s manifests directory gets unwieldy.
Because this is a unique manifest, you get the benefits that “real” manifests get.
You can specify items to be installed here that are not provided as optional items in the server-side manifest (as long as they’re in the catalog).
The solution is to determine the serial number of the real Mac by opening About This Mac or running System Information. On my Mac Pro 5,1 it begins with a letter and is 11 characters long.
In Terminal run the following command substituting the name of your Virtual Box virtual machine and your serial number (all one line): Make sure you remove the quotes while entering the above command.
But due to the serial number being “0” the App Store and Server applications will not work.While the basic idea of the local-only manifest is simple, the implementation has some fun details you can take advantage of.Local-only manifests do not have any catalogs of their own.With the uniqueness moved client-side, the server only has to provide the common manifests.There’s a lot of neat things you can do with this idea, so let’s explore some of them!