It has to be called $autoboot$ in the first place - autoboot won't work - that's not the user name the system needs to find?
For an OFFLINE system, if I created my$autoboot$, once I restart, the workstation will bypass PBA and go to Windows? There's no need to run the command:disablesecurity?
create $autoboot$ where?
the disablesecurity command creates a local psudo-$autoboot$ user only locally, it won't survive a sync though.
Again, this is for a stand alone offline system. If I create an eepc 5.2 machine --> under the general tab, select the neccesary options for autoboot --> create my$autoboot$ user and add it to the machine --> create an install set --> run the install set on the offline machine --> the machine encrypts --> encryption is complete --> update software --> reboot the machine and EE will be bypassed because i've added my$autoboot$ ? How does EE know when you want to bypass PBA?
it "knows" because the $autoboot$ user exists on the machine?
If you added operational $autoboot$ account to machine group, from which you have created offline installation set, bypassing pre-boot will work.
No additional operations are needed.
It works, because EEPC client communicates with transfer database file, that has been created and added to offline install set.
Check clients SDMCFG.INI file to see configuration details.
Your offline machine object will be added to transfer database (local to client machine).
You can later import transfer database SDB to your online database. That will stop object not found messages in your client communication log.