Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, June 2, 2017 5:51 PM
This is an issue that just started cropping up this week. I had my OSD PXE boot deployment task sequence working, and all of a sudden it will no longer show up as an option. I've tried multiple computers, virtuals, everything I could think of. SOMETHING changed this week, but for the life of me I can't see what.
I thought it was a corruption in the TS, but I created a new one to test and it doesn't show up either. I've removed/re-added PXE, updated the boot image, done dozens of google searches, nothing has led me to a solution. I honestly don't know what I'm missing-it just won't show any TS from a PXE boot any longer, and the log isn't showing me anything out of the ordinary (I think)
- The machines that I am booting have been deleted from the device list, so it shouldn't know that they ever existed.
- I've tried the procedure at http://www.mrbodean.net/2016/09/18/no-assigned-task-sequence/ without success (no records returned).
- I've checked the BIOS time and it is correct.
Here's the smsts.log from the failures.
Anyone have any further ideas? I'm pretty much at my wit's end with this one.
All replies (10)
Friday, June 2, 2017 9:58 PM ✅Answered
From you logs, it thinks that the client is "unknown."
You need to have a deployment to the unknown machine collection. According to the log, the GUID for the 64-bit unknown machine is 3a5c9350-ce44-45a9-b410-1f9e22e854be. Check that this matches the unknown machine system.
Also, make sure that the deployment is set of "PXE and media", and that the deployment availability time is not far into the future.
Monday, June 5, 2017 10:16 AM ✅Answered
One of the machines that was deployed on friday took unknown computers GUID and thus there were no unknown computers in my environment anymore... Found a solution in this thread:
Best regards,
Rok B
Sunday, June 4, 2017 12:36 PM
Hi,
it also happened to me, same issue, TS works on known machines, PXE boots but for all unknown machines I don't get any TS anymore. Removed DP, MP, WDS, few times now, don't see any errors, anyway still can't get unknown machines see deployment...
After failed attempt ddr creates an unknown sysem in devices, but even if I make (workaround) query that puts those "unknown" machines in collection with deployment it doesn't work...
It works if I import computer (by MAC) and put it in collection with deployment. It seems like the unknown computers collection doesn't work like it should. I will try to find deployment policy in database...
Best regards,
Rok B
Monday, June 5, 2017 8:44 AM
Hi,
>>From your log: "Setting wizard error: There are no task sequences available for this computer."
So you should check if there're any task sequences deployed to the targeted groups which contains the computer you tested.
Regards,
Jimmy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, June 5, 2017 4:15 PM
I have this TS deployed to the unknown computer group, and it is properly set to deploy to PXE:
Now, when a machine boots, it creates an "Unknown" record as it should, but never updates the object with the correct name (because there are no TS to apply). Looking at the Deployments tab, it is empty, I suppose because it doesn't know what to do with it yet. I've never looked at other machines at this stage when it was working properly to see if I should be seeing the deployment of the TS here, so I can't compare.
Here's what properties are currently set on this "Unknown" record, which matches the MAC address of my virtual test machine. It's like the unknown collection doesn't recognize this an an unknown machine, if that makes sense. Even though the "Unknown Computer" property is set to 1, which seems to me should add it to the unknown computer groups.
Monday, June 5, 2017 4:31 PM | 1 vote
Beautiful! I dug around in the database and found a record that matched one of the unknown GUIDs. Strangely, it was the only one that had the GUID without the 'GUID:' prefix.
Verified by deleting it, and was immediately able to see a TS.
Thank you all for the help! This one was really getting my goat!
Monday, June 12, 2017 6:31 AM
There is a hotfix released that should fix this issue: https://support.microsoft.com/en-us/help/4019926/update-rollup-for-system-center-configuration-manager-current-branch-v
You can install it through Updates&Servicing
Monday, June 12, 2017 2:12 PM
This issue occurred two separate times with that hotfix already applied. For some reason, a machine was stealing the "unknown computer" GUID instead of getting it's own.
Monday, June 12, 2017 10:13 PM
After you apply the hotfix, you need to update your boot image packages, update your DPs (including your PXE DPs) and re-create your boot media.
You have to make sure that you don't use old boot media and old PXE boot WIMs. They are causing the unknown system records to be registered as clients.
Tuesday, June 13, 2017 11:19 AM
That is a useful information that I didn't see anywhere else! Thank you Kerwin!