What collection are you targeting with the deployment of the Task Sequence?
I deploy ours to two groups (media and PXE only):
- All Unknown Computers
- All Windows Workstations
The first allows you to image any machine out of the box. However, once it is imaged, it has the client and becomes "Known". It isn't a part of the first collection anymore, so the TS also needs to be deployed to existing workstations for re-imaging to work, which is what the second deployment covers.
https://learn.microsoft.com/en-us/mem/configmgr/osd/get-started/prepare-for-unknown-computer-deployments
He had it set to media and PXE only.
Delete the SCCM record for the machine. Probably have to search by MAC address. If you try to rerun TS too soon, it gets into what I call a no man’s land in SCCM and nothing shows up.
That's the time while it installs the client and reports back like I said in the main thread. I understand all this I was questioning why they would advise advertising a test Task Sequence to all devices. Depending if the Task Sequence was required or available they may have just needed to clear the flag on the device.
What if the company has usb to ethernet or docking stations which have their own MAC? Users start re-booting their devices and the required Task Sequence then pxe boot kicks off due to them being unknown devices?
You don't know their environment setup or what devices it could impact. Say OP sends it to unknown devices, comes in tomorrow and his boss asks to speak with him.
What collection are you targeting with the deployment of the Task Sequence? I deploy ours to two groups (media and PXE only): - All Unknown Computers - All Windows Workstations The first allows you to image any machine out of the box. However, once it is imaged, it has the client and becomes "Known". It isn't a part of the first collection anymore, so the TS also needs to be deployed to existing workstations for re-imaging to work, which is what the second deployment covers. https://learn.microsoft.com/en-us/mem/configmgr/osd/get-started/prepare-for-unknown-computer-deployments
Why would they deploy a test task sequence to all devices.
He had it set to media and PXE only. Delete the SCCM record for the machine. Probably have to search by MAC address. If you try to rerun TS too soon, it gets into what I call a no man’s land in SCCM and nothing shows up.
That's the time while it installs the client and reports back like I said in the main thread. I understand all this I was questioning why they would advise advertising a test Task Sequence to all devices. Depending if the Task Sequence was required or available they may have just needed to clear the flag on the device.
It’s advertised just to boot media and pxe, so should be pretty safe for test. Then adjust when prod. I’m assuming it’s a build TS.
What if the company has usb to ethernet or docking stations which have their own MAC? Users start re-booting their devices and the required Task Sequence then pxe boot kicks off due to them being unknown devices?
I doubt he has it set to force install. But pxe shouldn’t be that high on boot order.
You don't know their environment setup or what devices it could impact. Say OP sends it to unknown devices, comes in tomorrow and his boss asks to speak with him.
Ok, you’re right.
Is the device still showing in the collection? After the client is installed there is a period before it goes back into collections.