@sgoetz

Shawn,

Let me see if I can explain this better....

Waypoints are triggered by the "Successfully installed..." line in the jamf.log. So if you set a waypoint to, word.app, when it sees "Successfully installed word.app" it triggers that waypoint.

The waypoints sub divide the estimatedCompletion time (this is buildTime in the scripting dictionary). Since the progress bar needs a time set to make forward motion, something needs to be set here. Be default, it's set to 1800 seconds. You could just set a really high number here, and let the waypoints make the jumps.

The waypoint intervals in order are 1/4, 1/2, 3/4, and Terminate. So...when wayPointTwo is triggered, the progressBar will jump to the 1/2 way point.

If you're finding that the waypoints aren't granular enough, you could setup a script or two to adjust the currentTime and buildTime to maneuver the bar anyway you'd like.

Hopefully that helps!

-Jason

Hey @jtratta or anyone that has gotten this to work using way points

So the below AppleScript im running is below. I am running this on the test machine using AppleScript Editor.

tell application "ProgressScreen"

     set useWayPointMethod of every configuration to true

     set buildTime of every configuration to 2000

     set wayPointOne of every configuration to "Parallels Desktop Autodeploy 11.0.2."

     set wayPointTwo of every configuration to "ALL - Adobe Flash Player 21.0.0.213."

     set wayPointThree of every configuration to "Enterprise Connect 1.5.3."

     set wayPointFour of every configuration to "Firefox v44.0.2_IWA.pkg."

end tell

So first I run the above script, than i go to terminal and do sudo jamf policy -id 700, which is my test policy to test progress bar function. It only installs those 4 apps on the machine. However the progress bar is not jumping to 1/4, 1/2, 3/4, Full as they install successfully. I know its reading the log okay cause you can see the messages below the bar.

I tried first building the xCode project as 10.9 in debug mode. Than I tried 10.10 in debug mode. Than I tried just downloading the Scriptable version from the release section on Github. But they all have the same affect. Also Im not sure if this makes a difference, but the test machine is 10.11.4 El Cap.

Im not sure if Im doing the coding above wrong or if Im simply missing something, that probably obvious lmao.

Anyways, at this point Im stuck. Any help would be greatly appreciated.

Thanks All!!

Shawn G

@sgoetz

Shawn,

You've found a bug. I will get that fixed here shortly.

-Jason

Hey @jtratta

Oh yay!! At least I know im not crazy!!

Thank you for all your work Jason on this.

Shawn

@sgoetz

Looks like I found the culprit. I have fixed the mistake in the Configurations.m file and it restored the waypoints on my machine.

You can either pull the code down again or you can just fix the 5 lines of code in your app.

If you check out the commit here you can see the changes in red and green in the Configurations.m file. In your version...just replace the red lines with the green lines and see if that gets you up and running.

The changes in the AppDelegate are to just silence the Swift 3 warnings...nothing to worry about for now.

Thanks for finding this one!

@jtratta

Hey Jason,

That fixed it!!!!! Funny thing I was looking at the file and noticed the PSH didn't match what I was using in Apple Script and was wondering if that was the issue. But Im not experienced enough with creating Apps so I didn't want to make it worse!!

Thank you again!!!!

Shawn G!!!

Hey @jtratta, Thanks so much for this and its working great. Except I do have one issue that I am sure is something related to autolayout but if the jamf log ends up having a long line in it like "the connection to the distribution point failed for package x, retrying on server.pretendco.com/CasperShare" and the feedback label gets big, then it sort of "zooms" in towards the upper left corner and the quit button ends up off screen, etc. I have tried different constraint settings but not finding something that works. Any ideas?

@chriscollins

I think you're right, sounds like the layout just needs some settings. Have you tried the technique I described here?

https://jamfnation.jamfsoftware.com/discussion.html?id=17467#responseChild106999

@jtratta Yeah I tried resetting the contraints and tried every constraint option but it still exhibits the same behavior. Hrmmm.

@jtratta I think I figured it out. I changed the content compression resistance priority for the label to be low so it couldn't "fight" autolayout's attempts to shrink it down to fit the screen when in full screen mode.

This is great! I am playing around with it now, but for some reason the "Quit" button is not clickable when I run it from AppleScript. If I double click the application to run it, the quit button works just fine. Also, is it possible to have the app close after the progress bar gets to the end?

Good work. This gives me a good starting point.

Guys, is it possible to launch ProgressScreen like LoginLog? Means, is it possible to launch ProgressScreen only in LoginWindow without a user being logged in?

@m.entholzner theoretically yes but I am pretty sure that the actual jamf binary/quickadd from the server is not installed either DEP until the initial local user gets to their Desktop the first time (that's been my experience at least) so not sure how you'd install the app or launch it at the login window during the setup assistant.

We don't want to use ProgressScreen in a "classic" DEP scenario, it should be used as a more eye-candy replacement for LoginLog. We used to use LoginLog to display the jamf.log while macOS upgrades for example.

Hows everyone got this looking these days?

What does everyone think about the customize your setup that IBM showed today?

I think I want it.

It's absolutely awesome and I wish they'd open source and release it so I can use it!

I really wish they would open source it as well. This would be awesome for everyone.

Lets ask him today in the session

Don't hold your breath. You have to look at their motivations. They offer a commercial outsourced Mac management service. This is their magic sauce. I don't expect they will give it away.

I'd like to be surprised though!

I think he said it would only be available for (GTS?) customers. I might have the acronym wrong, but as @loceee said, it's their magic sauce.

We'll just have to make our own then!

@jtratta I fully expect this to be complete by the end of your flight home.