I am trying to apply an Autologin account to a Windows Embedded 7 device that already has the FBWF enabled using a post-operating system deployment task sequence. So, basically I have an OS task sequence that installs the OS, CM and SCEP agents, as well as a couple base applications like Adobe Reader and Flash then enables the FBWF. From there I have this "Autologin Specific" task sequence to apply the specific autologin account as well as a couple applications.
The "Autologin Specific" task sequence applies the autologin registry keys to set it as an autologin user. The task sequence completes, thus enabling the write filter and the computer boots up and logs in as the autologin user, HOWEVER, after any subsequent reboots a balloon message from the task appears that the user has been logged on with the temporary profile - I believe this is because it can not successfully commit any changes to the protected volume because the FBWB was enabled after the task sequence completed. I am unable to log the user into the computer during the task sequence because CM puts the computer is in Service Mode (where only the local Administrator can log on - because the Write Filter is disabled).
I have also attempted to run the script to apply the autologin user in the OSD task sequence before enabling the Write Filter for the first time. This does not work because the computer never exits "sysprep" mode and logs the user in before the script to enable the write filter kicks in.
I do not want my OSD to finish with the Write Filter disabled because if a machine is being imaged at location, there will be a period of time where a user will be able to walk up and log in, before any additional task sequences are run to lock it down.
HP's answer is to use HPDM or basically use command lines to tun the filter off and on. Uh - Not much help here when CM is putting a computer in Service Mode.
Any thoughts?