Hi

I had an issue where after PXE booting and when the TS runs it would not run with "No TS available for this computer"

It was working until i changed the deployment to make available to only PXE and Boot media. Then it stopped working when PXE booting.

The record in the console displayed client no and there were no duplicate UUID's

So the seems the setting was not being honored... I changed the setting back to PXE, CM Clients and Media and it works again..

Can anyone explain why?

Thanks

• Edited by Webbeye Wednesday, February 04, 2015 4:37 PM

When a machine gets removed from AD without the DDNS record being cleared first, the DDNS entry will become an orphan of sorts. It will only be writable by the original AD computer object. This orphaned object can still be discovered by AD System Discovery which can cause duplicate computer devices in SCCM. When I ran into this, I had to have our AD Support folks clear out the entries in the past. If you are not seeing duplicate names, I would rule this scenario out.

What is the status of the SMSTS.log? Have you been able to get it and look through it? Are you the one running the TS or is that someone else? Have you used cmtrace.exe before to analyze the log file? 

In the meantime, try just blowing away the device you imported, re-import it, re-add it to a collection, and re-deploy the task sequence. In other words, just try removing what you had done so far and just start over with re-importing the device again. Having the log would allow us to be more scientific. :-)

Thanks for the replay, Tony.

I am not onsite running the TS hence the delay in getting the log. Yes, i have used CMTrace more time than i want to rememeber :)

I tried removing the objest and reimporting as first steps..

I have setup a test now so they are going to try and image a brand new machine (never been on the network) and get the log if it fails..

I will post it once i receive it

Have you reviewed smspxe.log? smsts.log won't exist yet because you are well before the boot image has even been delivered.

Also, side comment here, AD System Discovery does not query DNS so stale records in DNS will not cause duplicate objects. It does validate that objects it sees in AD during discovery can be resolved via DNS, but that won't cause anyh duplication and only comes into play if an object actually exists in AD.

Good point Jason! I did not even think about that, w/o selecting the Task Sequence there is no log created. 

Thanks for clearing up the AD System Discovery thing. I few months back I had a conversation on here about that with someone and that was what I was told then. I believe... Have to look up that thread again.

thanks Jason, you also reminded me that the DNS record is just part of the requirement for discovering AD objects.

Apologies if i have not described the issue well enough. The boot image downloads and WinPE is initiated, the at the point when searching for the TS policy it replies with "No TS available for this computer" so its not honouring the deployment setting for PXE and media. only When i change this to PXE, CM clients and media it find the policy.

I am testing with a new machine and will get the results tomorrow with smsts.log if it fails..

Ah OK. That does still sound like you've selected hidden.

Start by deleting the deployment and recreating it from scratch and this time don't select the hidden option in the dropdown.

I have created a new deployment (not select hidden) and will get the results of the test tomorrow ;)

For my information, what does the hidden bit actuall

The "hidden" option essentially hides the task sequence from the available list of task sequences where one has to actually specify the deployment ID in order to launch the hidden task sequence. Work's quite well. Good for hiding server related Task Sequences from the desktop team. Check out this blog about it over at Windows-Noob.

Do a search for the machine MAC address and/or Name from the All Systems collection and delete what's returned.

Perform the search from CAS and/or your primary sites if necessary and try again.