Not heard / seen that one before. First up:
... go through the Core-side files first of all, to check / make sure that the policy/task you've created works & goes active (I'm assuming this works, but pays to be careful).
On the client, you may want to enable debug-logging across the board for more info once you know that's where the problem is (information on how to do so is linked above) - that's an "if needed". Chances are you'll have something in your logs already.
Stumbling blocks on the client would usually be:
Step 1 - Does the policy check work? Check the PolicySync-log for that. Also this may help - Error: "Signature Verification Failed" from PolicySync.exe - if that's the problem you run into.
Step 2 - Assuming the policy check works - does the task get downloaded properly? Does the task start properly ?
Step 3 - What's the detail on the task actually running? If something fails, it'll tell you in the task-specific log (that'd be something like "sdclient_task###.log" where ### is the ID number of the task that you see in the console). These task-ID specific logs are here on the client => "C:\Program Files (x86)\LANDesk\LDClient\Data\".
... that should be enough to get you stared. Not sure how you don't have those packages on a new install ... but since it's "just a VB-script with 2 extra files" you can happily create them manually ... shy of having fat-fingered something (or the client not being able to reach those files), you should find something in the logs I've described / that are linked in the articles to get you on the right track .
I experienced the same issue and the support desk has not really helped. What I have done is use the osdrep.msi with vbs script to install PXE. It appears that part of the install portion is missing on 2016... not sure why. I am using the msi from a previous 9.6 core, all I have to do after that is replace the boot.wim files.
I have seen the issue before. Never figured out why it happens, but they basically were missing after install.
I have exported a copy of both packages from my 2016 core and attached them here.
You should be able to follow this doc to import them into your core.
It will also have my core's name as the source, so open the package up, and change that to reflect your core/core's IP.
This will at least allow you to know your working with the same package as a 2016 core should be, and then if the package still fails to install, then it becomes a troubleshooting issue of why the pxe rep won't install.
PXE_SWD_Files.zip 3.7 K
Outstanding Nick many thanks. I have imported and will test this morning.
Bizarrely your core has the same name as mine, domain different obviously
1 of 1 people found this helpful
I want to point out that this community article is now specific to the version of LDMS 2016 that you're running. If you are running 2016.3, the disappearance of the PXE installation and removal packages is completely normal as they now have the new "Self electing services" feature. PXE service is now handled in a very different way. I'm posting this, since folks could get a bit confused, if they're reading this article and have the newer version of the product.