hello, I actually encounter a huge problem. I created a MDT UDI Deployment task sequence and published it for "all unknow computers" and "all systems". When i start the Task sequence through a full operating system ("run advertised programs") -> no problem : the task sequence runs correctly. When i start the Task sequence through WINPE -> Problem !!. WinPe starts correctly. the welcome screen appears asking me for a password. I type the password and just after i get an error message with the followinf error code : 0x80093102. When I search in the SMSTS.log, it appears that the error code occurs when the client tries to decrypt the message (CRYPDECRYPTMESSAGE). info : i use SCCM in mixed mode. has anynone already encountered this error (and fix it :-) ). by advance thank you. Régis

ok, so found the problem. It's ot a certificate problem as SMSts.log explained but a file problem. i think the task sequence xml file was not correctly formatted : Maybe a bug in the Task Sequence Editor !! I re-created a new task sequence (i didn't duplicate it !!) and published it.

I've had the same issue. I am not sure what happens, but it does appear that something along the line gets corrupted possibly. I've got a case open with Microsoft so I'll let you know what they say. I've built new Task Sequences when this happens, but mine have gotten rather large and it is a pain to rebuild them when an issue occurs. They also seams to corrupt by making the smallest of changes. I wonder if it is due to modifying them to frequently? Not giving the system enough time to push out the changes? Since you cannot see them deploying when modified there is no way to tell when a site is updated or not. Anyone else out there having this issue and if so a resolution? Thank you

Alright, so working with Microsoft Support, I have found the source of the problem. When a Task Sequence is created, a policy (which I believe is only used by PXE...not 100% on this) is created. Each time you modify the TS, a new policy version gets created. There appears to be a limit on how large the resulting policy can be. The max size on this is is 4MB (more specifically 4194304 bytes). The policies themselves exist in the database, so they cannot be viewed like a normal file. So, the Task Sequence I was have issues with has a policy size of 4194354 byters (which is 50 bytes over the limit). This explained why removing a step made it work but adding anything caused it to fail. I am sitting right on the threshold. The magic SQL query to see the size is as follows (This was run against the Central server's Database). Also, it must have an active PXE advertisement to show up: Select PolicyID, datalength(Body) from Policy where PolicyID like ‘%<Task ID for Task Sequence>% If you have multiple advertisements for the same policy, you will get multiple records returned. The first column is the PolicyID and the second is the size of that linked object in bytes. If it is over 4194304 then that is why you are getting the CryptDecdryptMessage. The decrypting mechanism cannot handle the file being larger than 4MB. CryptDecryptMessage ( &DecryptParams, pbEncrypted, nEncryptedSize, 0, &nPlainSize, 0 ), HRESULT=80093102 (e:\nts_sms_fre\sms\framework\smscrypt\windes.cpp,359) Failed to download policy <policy ID> (Code 0x80093102). The REASON this happen is a completely different story. We are using the Dell Client Configuration Toolkit that integrates into SCCM (Version 1.2 as of posting). It has a mechanism for setting the BIOS, but with a config item needed for EACH hardware model we support it takes a total of 16 lines in the task sequence. However, for some reason the policy size resultant from having the configure BIOS steps ballons in size. Creating a NEW task sequence and putting just one line resulted in a policy size of 256kB. I have 15 of them so adding that to my already large and compled Task Sequence adds 3,840kB just for the BIOS settings themselves. Once I removed all of those Dell BIOS line items, but entire policy dropped from just over the 4MB limit to 620kB (little over hald a MB). So, not sure if anyone else will come across this but at least it will be here for the next person to suffer through this issue. I've asked Microsoft to address this issue, but they believe it is a Dell problem which I can understand. What I don't understand is how the policies are generated and why they increase in size so drastically with each line item. The last final note is that my Task Sequence (even when over the size) still ran perfectly fine without issue when launching it via the SCCM client from within the OS. So doing an inplace refresh from Win XP -> 7 or 7 -> 7 ran without issue. The only scenario I had issues with was with PXE booting because PXE requires the use of this policy object. If you have any other questions on this, please respond to this thread and I will be happy to help where I can.