This content has been marked as final. Show 19 replies
Did you add (and sync) to that machine object, $autoboot$ account?
yep, added the acount to 1 specific machine and then synced it.
Is that $autoboot$ account using default password?
Be careful when you create the $autoboot$ account. If you have it set to force password change on next login or force password change if current password is '12345' (and it is) it will also not bypass login.
created new token and changed token password from 12345,
confirmed it is not set to reset password,
cleeared sso details,
resynced with server,
visually confirmed new account data recieved from server in logs.
machine still will not autoboot after 30 seconds preboot screen appears.
you probably have "disable checking for autoboot" ticked in the machine config.
also remember that you have limited protection from data disclosure regulations when you're working in this mode, as you've effectively stored the key alongside the data.
I have follwed the following steps as per administration pdf
The process for creating an $autoboot$ user is:
1. Create the user.
2. Uncheck the Force password change at next logon.
3. Click the Devices tab.
4. Right-click the machine group (or machine, if preferred), and select
5. Ensure the Disable checking for AutoBoot option is unchecked.
6. Ensure the Allow AutoBoot user to be managed locally and Allow
AutoBoot to be cancelled options are checked.
7. Click the Apply button to save these options.
Is there any admin lvl rewquired for the account is is default lvl ok?
you missed out assigning the user to the machine.
No user is added to a specific machine, it is also in the user group for admins on this machine. but as i have said previously it starts to autoboot and then does nothing