Skip to main content
Question

Compiling using an external HDD as the DP for both source and destination


Forum|alt.badge.img+16
  • Valued Contributor
  • 1002 replies

As the title said I am investigating whether it is possible to create compiled configurations using a local replication as both the source and destination.
Currently it always seems to try and read and compile back to the primary distribution point, which I understand from a Casper operational point of view.
We however currently do not use the compiled configurations within Casper, they are exported out to Deploy Studio and I was interested in how fast these would happen using a local SSD for everything.
I have successfully created the local drive using Casper Admin to replicate to it.
Has anybody else done anything similar, it's partly a bit of playing around, partly a might be useful type exercise.

3 replies

Chris_Hafner
Forum|alt.badge.img+23
  • Jamf Heroes
  • 1718 replies
  • November 7, 2014

That would be interesting. I believe that it will always compile to the master DP. You could, temporarily switch the 'Master' and compile locally. Then replicate and swap the master back. I've done that before while investigating replication issues. There are potential side effects of course depending on how your clients look for DPs.


bentoms
Forum|alt.badge.img+35
  • Legendary Contributor
  • 4331 replies
  • January 4, 2015

@Look, or use AutoDMG to create your OS.dmg. https://github.com/MagerValp/AutoDMG


Chris_Hafner
Forum|alt.badge.img+23
  • Jamf Heroes
  • 1718 replies
  • January 5, 2015

You certainly could. You'd have to pull your packages out of one of your DPs if you haven't kept copies elsewhere. However, it's an option. That said, it may be a worthy feature request. I quite like using Casper Imaging but I can understand where you're coming from.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings