According to the below article, this is a known issue without a specific resolution, which prompted the creation of the Autologon Utiliy instead (essentially an MSI version of the Autologon policy).
http://www.symantec.com/docs/TECH151916
http://www.symantec.com/docs/TECH151755
So for your "danger-close" scenarios, generate a new Autologon Utility MSI (instead of making GPO changes) for your specific event, and run it on the endpoints prior to the reboot.
Don't forget, there is also the option of using the SEE Reboot Utility too, but this is less secure and not recommended for mass use (as it would require passing out the creds of a registered user or client administrator via a clear-text script):
http://www.symantec.com/docs/TECH178365