Besides being interesting as Hell, we also found a clean resolution that was not available through countless Goog searches.As if all that was not enough, there is a quick lesson on using a SQL Search tool that I was completely unfamiliar with until good friend, Adam Gross (follow this cat on the Twit: AdamGrossTX ), hipped me to what all the cool kids were doing Read On My Friends.
![]() What this hopefully provides are insights and options on how you can dig down and discover what the root cause is in your unique case. We first recognized a challenge existed while reviewing the device progress in our PXE TS Deployment Status. It was not located in the In Progress or Error tabs and ultimately found it in the Requirements Not Met tab. The only real lead this would be providing was that we had a challenge, as Program rejected (wrong platform) had nothing to do with what was causing the TS to fail. It had reached the point of at least verifying the TS contents availability before it suddenly rebooted, returning to the Win7 logon screen. Program Rejected Invalid Policy Sccm Download A SpecificWe worked with the user and obtained the smsts.log while in WinPE and this allowed us to see that the TS was failing to download a specific policy which caused the TS to fail and reboot: Failed to download policy 0EE5B482-390A-48DD-BB47-D5706BAB64599 (Code 0x80004005). ![]() We chatted for a while, bounced ideas back and forth and then Adam found our intersection Using APEX SQLs Text and Object Search tool in his own lab, he narrowed it down to being a Client Setting. For insight on this tool and usage, see How Did He Do That at the tail end of this blog post With the culprit narrowed down to a client setting, we then queried against ClientSettingsAssignments using the PolicyID and Bam Now we had the ClientSettingsID as 16777217. This ensured that whatever the corruption was within the client settings deployment, be it WMI or SQL DB, would be completely cleared and would not cause any additional challenges moving forward. The slash number after a PolicyID is used to distinguish each separate Client Setting Node (not versioning as we previously assumed). Program Rejected Invalid Policy Sccm Plus We AreHes such a nice dood, plus we are both Louisiana natives, so I couldnt pass up a chance to help with some sweet detective work with him. Microsoft MVP Steven Hosking ( OnPremCloudGuy ) recommended it to me several months ago and Ive used it several times to quickly find things in the SCCM DB. In a recent blog post, I mentioned using the View Dependencies function in SQL Server Management Studio (SSMS) to find the SQL objects that related to or depend on other SQL objects, but it only finds objects. Apex SQL Search lets you search for objects AND do full text searching of your entire DB and it does it rather quickly. Its also worth noting that the View Dependencies option function didnt return the correct table for us, so we may have been looking for a while. After blindly trying a few tables with policy in the name, I decided to use Apex SQL Search to search for all instances of the policy text in the db. Within a few minutes, I found the policy in several tables, one of them ended up being ClientSettingsAssignments. I sent the table over to Marc and he immediately confirmed that it contained the missing piece needed to solve the puzzle. If I know Im searching for a numeric value, then I will only check the Numeric columns and Unique identifier columns for my first pass to help speed up the search. If I strike out, then I may check additional options and try again. Program Rejected Invalid Policy Sccm Trial And ErrorFrom here its just a bit of trial and error to find out which tableview is what we need.
0 Comments
Leave a Reply. |