anyweb

well if you feel it's a bug (and I still don't think it is, but I'm happy to be corrected) then you can file a bug on connect here - http://connect.microsoft.com

I don't think it's a bug, what happens is the operating system is now booting into Windows and uses whatever bootloader is now laid down on the hard disk (instead of WinPE which the boot wim containing the logic for F8 has), and there is no logic built into Windows or it's boot loader to press F8, this is temporary though, after the setup windows and configmgr step is done you'll be able to press F8 again, you can however try to press left shift and F10 when it's in this state to see if a command prompt comes up...

you can force a machine policy on those machines at the end of OSD or via another method, this will speed things along as expected. here's a script Eswar created http://eskonr.com/2011/01/script-to-trigger-sccm-machine-policy-or-hardware-inventory-action-agent-on-sccm-clients/

i need more logs, do the below please and attach the logs here The following Log files will also aid in troubleshooting definition updates retrieval. Browse to C:\Windows\Temp and look for the following log files...:- MpCmdRun.Log MpSigStub.Log To get extensive logfiles open an administrative command prompt and CD to the following directory on the client, C:\Program Files\Microsoft Security Client\Antimalware and execute the following command MpCmdRun.exe -getfiles the following will be output the log files are store in C:\ProgramData\Microsoft\Microsoft Antimalware\Support and that directory in turn will contain a CAB file (MPSupportFiles.cab) which has several relevant log files to examine.

well we'll need the logs from a client with the issue, zip them up and attach them to this thread, they'll be in c:\windows\ccm\logs and attach the c:\windows\windowsupdate.log also can you also confirm if normal software distribution is working on these clients or has that stopped also ? and what version of Configuration Manager are you running ?

to do that you need to check auditing as described here http://www.windows-noob.com/forums/index.php?/topic/4037-sccm-console-user-activity-logging/

highest priority always wins so don't worry, if you scroll down the gui even more you might see other policies applied also

can you show us what your Endpoint Protection Update tab gui looks like on a client ? this will show you when it last updated and what version it's running...

attach the smsts.log file so we can take a look please

details, more details, what error do you get ? what environment are you using ? a screenshot perhaps ?

what do your deployment logs reveal ? anything left in the minint folder ?

you get more functionality and flexibility in Configuration Manager as regards to operating system deployment

well go ahead and develop a solution, we'll be happy to test it for you !

I'd recommend you integrate it, and yes time to start learning using virtual labs, a couple of virtual machines (hyperv is great) and you'll be up and running in no time at all.

when debugging stuff like this set your debug level to /v:13 like so http://www.niallbrady.com/2012/01/25/troubleshooting-usmt/ that will give more output in the logs above, in addition, you can simply add a /lac statement like in the following batch file below @set USMT_WORKING_DIR=%~2%\USMTbits\amd64 "%~2\USMTbits\amd64\loadstate.exe" "%~1" /c /lac:Password123 /i:%~2\USMTbits\amd64\miguser.xml /i:%~2\USMTbits\amd64\migapp.xml /i:%~2\USMTbits\amd64\wallpaper.xml /i:%~2\USMTbits\amd64\printers.xml /nocompress /v:13 /l:%~2\Windows\CCM\logs\SMSTSLog\loadstate.log the variables used above (%~1 and %~2 are as follows) if you dont want to use a batch file then modify the statements in your task sequence to match the above (more or less) and you'll be ok, the restore and backup parts of the above are all in the CM12 BitLocker Frontend HTA code available for download here http://www.windows-noob.com/forums/index.php?/topic/7294-the-cm12-bitlocker-frontend-hta/ why reinvent the wheel ;-)

what version (and CU Level) are you running in Configuration Manager ?

well do you want to use MDT only or MDT integrated with Configuration Manager ? if you are working in an enterprise I'd recommend the latter. See below for some guides for same. http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-step-by-step-guides/

as Peter33 says, either remove the computer/user from the collection that the application is deployed to, or adjust the notifications (in custom client settings) for the Client Agent itself.

well have you tried to gollow the advice in the description of each of the Message ID's above ?

while Johans method is great, not every customer is willing to have copies of their apps both in MDT and Configuration Manager,

If you want to re-start the Task Sequence, issue the following command x:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:x:\sms\data

which is not a good sign, are you continuing on error on the Setup Windows and ConfigMgr step ? you should not... the error above means... The keyset is not defined. Source: Windows ----- after a quick search I found this http://support.microsoft.com/kb/840784

shouldn't need to see the comments above up a few posts..

probably missing content on the nearest distribution point, please attach the smsts.log file from a failed install and we can verify.

look at the task sequence it contains restore sections which you can rip out and use to 'restore' your stuff. No need to re-image if that's what you want