Startup Security Utility - No administrator was found.

Hi Simon,

here is a link that explains these steps (thanks to Mike Bombich):

https://bombich.com/kb/ccc5/preparing-your-backup-disk-backup-os-x#erase_apfs_co ntainer

Please scroll up in this post to my October 6 post for more details.

Good luck!

Best regards

Mirko

Hi Simon, you're absolutely right - this is it.

For performing step #2 and #3, you would use Apple's built in Disk Utility

Here is a guide, of how to make sure, that you leave no trace of the old APFS container, because if you would, then step #7 would not work: Preparing your backup disk for a backup of macOS | Carbon Copy Cloner | Bombich Software

Best regards, Mirko

Thanks Mirko (italian name, isn't it?).

Just a personal thought: I would perform a "zerodisk" from terminal before creating APFS from disk utility if it was precedently formatted in APFS. Just to be "more" sure although I do not love zeroing SSDs neither the continuous action of TRIMming. I believe an SSD should be erased as rather as possible.

Tnx Again

Simon

tried again with this result:

2018-11-05 22:34:54.068 sysadminctl[2710:87553] setSecureTokenAuthorizationEnabled error Error Domain=com.apple.OpenDirectory Code=5101 "Authentication server refused operation because the current credentials are not authorized for the requested operation." UserInfo={NSLocalizedDescription=Authentication server refused operation because the current credentials are not authorized for the requested operation., NSLocalizedFailureReason=Authentication server refused operation because the current credentials are not authorized for the requested operation.}

Strange. This happened to me only, when I did sysadminctl interactive -secureTokenOn <user name> -password <user password> *before* I completely removed the old APFS container.

Did you try to add sudo before the command, something like

sudo sysadminctl interactive -secureTokenOn <user name> -password <user password>

?

Yes I did as I also did remove “interactive” as looks obsolete in some sites but nothing changes.

I’m now doing a fresh install and will import through Migration Assistant as I don’t have time to waste in tests.

Thanks anyway, Mirko_

I am having this issue of no admin acct in recovery, and only used TM backup during setup of my imac pro. No CCC etc. But the terminal command to get a token doesn't work and I have no interest in reinstalling just to get into startup security utility. Is there any other way that doesn't involve a new install procedure?

in terminal it says:

Secure token is DISABLED for user "me". Any way to enable secure token for me?

What is the exact error message you are getting when you run

sudo sysadminctl interactive -secureTokenOn <user name> -password <user password>

(and of course replace the terms in < > by the correct values)?

Don't remember the exact message I received for that terminal command above, but The solution is to toggle filevault on and then back off. Then the secure ticket or whatever it is called is created and the log in recovery environment into security utility works. I now have turned off everything in there as well. The problem was, often upon boot up the imac pro shuts itself down and powers off half way through a cold startup. (The next boot goes on normally) The error report that comes up on the next normal boot shows "bridge os" as the problem. I am certain that whatever issues that people had with the T2 chip early on, have not entirely been fixed since this is a brand new imac pro and the latest mojavi. I don't need the secure stuff and am hoping that disabling the stuff if recovery helps to keep these bridge os panics down to a minimum. If the issue is with the chip and not software or firmware updates, then I guess we are stuck with it.

This is one of the three solution that can work but not necessarily. In fact it didn’t work with me.

I had the also the third suggested by mr. Bombich (the first should be in this post if I’not wrong) but unfirtunately the email is lost. I’ll check if I can recover it and post it here. In any case if you contact mr. Bombich he’ll reply you for the three solution. In my experience neither will be ever used. Better a fresh install and migration from CCC (admin included).

Cheers. Simon

Very nice, I replied to myself in the post above but was for you. Sorry Simon

Hi Simon - Zerodisk is absolutely not necessary. I'd advise not to put this strain onto your SSD. Best, Mirko

I’ll perform a zerodisk only on the first and last 100 sectors.

Tnx Simon

What happened? What was the result of the procedure?

I’m not with my Mac. I’ll reply you tomorrow although wat’s really boring me is the inability to do a clean install via Internet Recovery. Tomorrow I’ll try via ethernet from different routers.

Thanks