In 9.x series, how do your techs know imaging is complete?

Could you just use something like the first boot package from Rich: https://derflounder.wordpress.com/2014/10/19/first-boot-package-install-generator-app/

Or could you just add in a payload free package to be installed at reboot to force the process to work?

Thanks @davidacland

I happened to try this at the end of our last imaging script and it seems to do the job in my so far limited testing. Even better than the reboot maybe

Reloads login window and shows login window text (so tech knows config profiles came down).

launchctl unload /System/Library/LaunchDaemons/com.apple.loginwindow.plist
sleep 15
launchctl load /System/Library/LaunchDaemons/com.apple.loginwindow.plist

You may want to vote up this feature request:

https://jamfnation.jamfsoftware.com/featureRequest.html?id=200

How about trying to use

shutdown -r +1 &

It will shutdown in 1 minute but move it to another task allowing the current script time to finish.
Well at least I think it will :)

@CasperSally We're on 9.63 & our workflow is detailed here.

Techs no a Mac has been imaged as the post flight config policy called has a restart command.

As we edit the login window, techs see the edited login window & know the Macs been imaged.

Not had to changed from 7-9.

+1 on what @bentoms said, plus munki updates start

LK

Unfortunately for us, it looks like we have to add the quickadd package back at reboot for imaging to work, so techs will know imaging complete when out of the adobe account. Thanks for all of the replies, I hope someday the imaging process will work like it should for us and not require the quickadd and I'll try some of the suggestions here.

@CasperSally It may be worth investigation what is failing for you as it's working for others..

You're preaching to the choir @bentoms - been working with support since Dec. Had similar issue in summer 2014, which apparently is same root issue.

Apparently major code changes are needed to address issues with certs/enrollment/etc. Makes it so frustrating to get emails to 'see what we've been working out all winter during the Ice Out' knowing that the issue I reported first week of Dec that needs major code changes to address is still an issue, without a timeline for those code changes taking place.

@CasperSally I'm wondering what differs between your workflow & mine

I'm not sure what makes our environment different, I try to keep things as basic as possible, but we seem to have constantly had issues with cert based communication & enrollment.

We actually had cert issues in 8.x series, but we used MCX back then and it didn't ever cause a pain point in our workflow. I remember support telling me if I ran X command it would be fixed going forward, but I think it never was.

When I upgraded to the 9.x series and started using config profiles instead of MCX, I started seeing "unable to decrypt profile" errors.

Over the summer I got a band aid fix for that and was able to move on with special build of 9.32. Issue came right back in my 9.65 testing. Support had me change a flag in mysql to stop that issue as a test which seemingly worked. The sql change doesn't fix the actual code issue, but allows config profiles to come down as they should.

Then, in further 9.65 testing, I started running across the device signature issue which caused me to have to put quickadd back in the workflow like @loceee. I only see this with Autorun data stored, but autorun is something we depend on.

@CasperSally Ah, auto run data. We don't use it. So that's the differing factor. :(