+13Has anyone been able to package and deploy DeepFreeze Cloud clients? The only DeepFreeze discussions and papers I see are pretty dated (2011).
I can successfully export a .pkg from the DF Cloud console, it is a zip file containing the .pkg and a plist. Nothing I normally do using either Composer (snapshot) or dragging and dropping into Admin works and will install correctly.
TIA,
/randy
Best answer by Randydid
I figured it out just before they got back to me. Here is what I did:
Some time during steps 8 or 9, you will get a DeepFreeze will reboot in x minutes message and that is why it is important to finish the snapshot process quickly and drop into the Admin tool as your test Mac will start the Deepfreeze process and you will lose your work!
My mistake was not having the .plist file in place prior to running the CloudAgent.pkg AND not actually waiting for the install/freeze/reboot process to completely finish. I have tested it by making a policy and making available in Self Service and by adding it to my image config as priority 20. Both work perfectly.
I counted at lest 3 reboots before DF was configured and booted up frozen.
Hope this helps!
/randy
+7Hey Randy,
I haven't been able to successfully deploy it any way except for taking the pkg that's created from the Deep Freeze installer and manually installing it. I've tried making it a policy that will run on enrollment, tried installing it post imaging (as suggested in the dated white papers), and even tried running it as a remote policy with a custom trigger well after imaging and enrollment. Still nothing. Would love to hear about a successful deployment.
-Thomas
+13That has been my finding too, so far.
I am going to open a support request this week with them. If I find anything, I will let you know.
/randy
+13I am still waiting on a support call from them. I just requested it today-things are busy here with the start of the new school year. I will let you know @jross and everyone know what they say.
/randy
+13I figured it out just before they got back to me. Here is what I did:
Some time during steps 8 or 9, you will get a DeepFreeze will reboot in x minutes message and that is why it is important to finish the snapshot process quickly and drop into the Admin tool as your test Mac will start the Deepfreeze process and you will lose your work!
My mistake was not having the .plist file in place prior to running the CloudAgent.pkg AND not actually waiting for the install/freeze/reboot process to completely finish. I have tested it by making a policy and making available in Self Service and by adding it to my image config as priority 20. Both work perfectly.
I counted at lest 3 reboots before DF was configured and booted up frozen.
Hope this helps!
/randy
DeepFreeze on-prem deployment setup is on my to do list for this week. Any reason this workflow shouldn't work for me as well?
+1I wasn't able to get the above solution to work for me. I did find an alternative though incase anyone else, like me, was still having trouble. Big thank you to @Randydid because I wouldn't have thought about moving the .plist either. This will result in a .pkg instead of a .dmg, which was fine for my needs though it may not be for yours.
installer -pkg /private/tmp/CloudAgent.pkg -target /
Packaging this up seemed to work well for my needs. After about sixty seconds, I receive the prompt from DF Cloud that my machine will reboot in two minutes. If anyone sees any glaring flaws, please let me know! Thanks
+3I wasn't able to get the above solution to work for me. I did find an alternative though incase anyone else, like me, was still having trouble. Big thank you to @Randydid because I wouldn't have thought about moving the .plist either. This will result in a .pkg instead of a .dmg, which was fine for my needs though it may not be for yours.
installer -pkg /private/tmp/CloudAgent.pkg -target /
Packaging this up seemed to work well for my needs. After about sixty seconds, I receive the prompt from DF Cloud that my machine will reboot in two minutes. If anyone sees any glaring flaws, please let me know! Thanks
Just coming in to say that this method still works flawlessly in 2022. Thank you so much!
+5I have a policy that deploys just the .pkg. I did nothing with the .plist
This executs without error, but doesn't "actually" work – much like what others have experienced.
I duplicated this policy, removed the triggers, set to "Ongoing" execution frequency, and made it available in Self Service. This also worked without error, but this time the machine in question showed up in the Deep Freeze Cloud console just a minute or two after.
I don't get what's different when both of these policies are basically the same.
I will try @dclary's method of making a new Composer package with the plist and the post-install command and report back.
+5I have a policy that deploys just the .pkg. I did nothing with the .plist
This executs without error, but doesn't "actually" work – much like what others have experienced.
I duplicated this policy, removed the triggers, set to "Ongoing" execution frequency, and made it available in Self Service. This also worked without error, but this time the machine in question showed up in the Deep Freeze Cloud console just a minute or two after.
I don't get what's different when both of these policies are basically the same.
I will try @dclary's method of making a new Composer package with the plist and the post-install command and report back.
No dice. And yes, I set the path to where the CloudAgent.pkg and the .plist were.
I've tried a million different ways to do this with Jamf or just through Terminal, and the only thing that worked was manually running the installer. Jamf would "successfully" run the "installer -pkg" command but nothing would happen, I presume because it was looking for the .plist and there doesn't seem to be a way to call the installer AND the .plist without executing the .pkg manually in Finder (or with an "open" command in Terminal).
At the very least, I could push the .pkg and .plist out to 30 some-odd machines with ARD. This way, I was able to get into a "rhythm" of going from computer to computer and running the installer. All the machines are visible + controllable in the DFC console now. Kind of annoying, but it is what it is.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
