InstaUp2Date + DeployStudio + Symbolic Links – On behalf of Melmaninga

[Allister Banks]

Melmaninga wrote to me asking to post the following:

With the older versions (1.5 I think) I used InstaUp2date in
conjunction with DeployStudio. Basically I used symlinks for the
InstaUp2DatePackages and the OutputFiles folders that pointed
respectively to the Packages and Masters/HFS folders in my
DeployStudio Repository. This meant the exact same packages and
images were used in both tools.

[Allister Banks]

Hey Melmaninga,

I have heard confirmation that conversely, DS doesn’t mind being symlinked to a package store, so that might be worth giving a shot. And to extend it even further, modifying your instaUp2Date catalog files to instead make reference to the URL’s in your munki repository can save you concerns about which is the authoritative source, since instaDMG would conceivably be used less frequently and just cache whats being distributed by munki. Hope that helps,

Allister

[Tim Sutton]

Allister wrote:

Melmaninga wrote to me asking to post the following:

With the older versions (1.5 I think) I used InstaUp2date in
conjunction with DeployStudio. Basically I used symlinks for the
InstaUp2DatePackages and the OutputFiles folders that pointed
respectively to the Packages and Masters/HFS folders in my
DeployStudio Repository. This meant the exact same packages and
images were used in both tools.

FWIW, Karl mentioned in his macsysadmin talk this past October that he does this for the OutputFiles destination for instadmg, when he wants to output straight to DS.

[Author]

Posts