Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

If some of the application failed during enrollment, SB quit button greyed out #70

Open
ssnak3 opened this issue Mar 12, 2018 · 4 comments
Labels

Comments

@ssnak3
Copy link

ssnak3 commented Mar 12, 2018

Hi Team,

As I have been describing on slack, there seems to be an issue when one of the applications from enrollment failed, it says that "application failed, support is notified" but the user cannot quit SB.

A little background on our environment:
We have offices all over the world and a lot of Distribution points and we are using User initiated enrollment that is performed by "admins" that do not have access to JAMF Pro console.
They are just there to enroll the device and if something is wrong they report that back to us, which is why it is important that SB windows with failed policies stay open so they can visually see what application/configuration failed and then they can report to us and quit the installer.

We currently have most of the Applications install from DMG files and scripts which means we are using ghostpkg scripts.
Status during installation is working perfectly (Installing, Error, Done) but we had to make some adjustments in the ghostpkg script (maybe take a look at that) because we could not see package in progress untill we replaced:

echo "$forceDate $forceUser: $forceStatus $forcePackage-1.2.3.pkg..." >> /var/log/jamf.log
with
echo "$forceDate $forceUser: $forceStatus $forcePackage..." >> /var/log/jamf.log

But since changing the above code we don't have the status issue, the main issue is that if we:

  1. Set canContinue to YES on all packages in .plist file, the user can quit SB during enrollment at any time.
  2. If we set canContinue to NO on all packages, after the enrollment is complete and if some applications failed to install user cannot quit the SB, it just stands there without progress bar saying "Some software failed installation. Support has been notified"

We even added the extra line in enrollment script which will touch the .SplashBuddyDone file but it is all the same.
Don't know if there is any workaround, can we modify any files at the end of enrollment to set quit button available to the user?

I would gladly test any scenario you can advise and let you know with some feedback.
If there are any additional question just shoot!

Thank you!

@ssnak3
Copy link
Author

ssnak3 commented Mar 12, 2018

Addition:
Just tested if all applications successfully install, then quit button is not greyed out and everything is working as expected.
In that scenario canContinue for all applications is set to NO

@ssnak3
Copy link
Author

ssnak3 commented Mar 16, 2018

Found a workaround:
Set all policies before as canContinue to YES, but put last one to NO.
I set the last policy that basically is just runing recon but could be anything with ghostpkg script.

@dinero1010
Copy link

Hello - perhaps on a somewhat unrelated note - what is the easiest way to set Continue as the default button regardless of the package installation status?

@cybertunnel cybertunnel added the bug label Aug 6, 2018
@cubandave
Copy link

Thank you @ssnak3!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants