Last months I did a lot of ConfigMgr 2012 R2 implementations. Nothing to worry about if you ask me, except for a few things. When doing a lot of OS deployments (on Windows 7 SP1), the Monitoring status is not as it should be. Let me explain what I'm seeing. When doing deployments (task sequence), I recommend to have a look at Monitoring (deployment) status. There you have a good overview of progress on al kind of deployments. More about that can be found here: OS deployment monitoring in ConfigMgr 2012 R2.
Within last months (never seen it before actually) deployments are not Always successful. You will see the following lines in Status Message Viewer (for a specific system):
-11171: The task sequence manager successfully completed execution of the task sequence.
-10804: The ConfigMgr client was reassigned. The previous site code was "". The new site code is "###". (few minutes later)
-10018: Deployment "########" from site "###" was rejected because the client's platform is not supported. (few minutes later)
What happens is that after a successful deployment (which is Message ID 11171) another deployment is starting (?) for it seems, and this is generating a rejected deployment (which is Message ID 10018). So it's succesful, and then it's rejected afterwards? Therefore no successful status message is displayed in ConfigMgr console anymore. At one customer this is the case on ALL (re-)deployments on systems. At another customer this happens to 1 on 10 systems, at both new deployments and re-deployments.
At the moment I have contacted Microsoft support for this. They are still investigating the issue, so hope I have more information soon. When anyone recognizes above issue, I kindly like to hear more about it. Maybe it's a bug, but I don't know at the moment..
Some people saying (Microsoft support included) I must change task sequence properties to support all platforms. When looking at the issue this may be the case. Strang thing is I never change this option, so it's on "Run on any platform" as Always. Hope that anyone can tell me how to solve this! Otherwise MS will tell me soon hopefully ;)
Update 8-9-2014: As mentioned by Microsoft and Robert Kloek in comments, a workaround can be used to get the job done. Just deploy the task sequence to "ConfigMgr clients, Media and PXE" instead of using "Media and PXE only". That way a successful message is showed in the end, and not the "Requirements not met" message. This seems to be a change to me, but it helps for sure!
When re-deploying an already deployed system with ConfigMgr 2012, an error message is sometimes displayed: "Failed to Run task sequence, There are no task sequences available for this computer". This because the system is already available in the ConfigMgr console as a "unknown" system. Because of that the "All Unknown Computers" deployment isn't used and a deployment on a known computers collection isn't used also. This because in system properties: "Unknown Computer = 1" is detected. No way to install this system again!?
As a workaround it's possible to delete the created object in ConfigMgr collections to re-deploy a system again. After deleting the system(s) the error message: "Failed to Run task sequence, There are no task sequences available for this computer" will be gone. Unfortunately after re-deployment the same thing happens again, so it's no real solution to this problem. Another solution to resolve this is mentioned HERE. It says: Add a query rule to the Collection that grabs new computers where the System Resource “Unknown Computer” property = “1”.
I tried that solution myself also, but it don't seems to work either. A "Unknown Computer Bug Update" can be found HERE. It mentions:
"The final response back from Microsoft via Connect was that this would be submitted to the Product Group as a Design Change Request". Hope it will be solved soon! Strange enough I don't have this issue at all ConfigMgr 2012 implementations? Anyone?
Update: For it seems this is only a problem when working with workgroup systems. When working with domain members there isn't any error message. That explaines why I haven't see this problem before.
Update 16-6: Unchecking "Unknown Computer Support" on the DP/PXE in question restarting the executive on the Primary and then reselecting "Unknown Computer Support" on the DP/PXE in question and restarting the executive resolves this issue. The problem you're running into is an corrupt policy on the MP. By Unchecking the option mentioned this will create a new policy and your unknown systems should pick up the TS when in WinPE.
