Feature request - Set Custom fields

0

Can you please look into the option of adding a new deployment step that all it will do is set the value of a custom field for what ever computer it is being deployed to.

Example of how this would be used.

 

Deploying a baseline package to new computers, last step of the baseline package would be to set the "Baseline" custom field to true/yes/1/etc... This way due to the fact that the package got to the final custom field step we know the baseline successfully installed on the computer and its custom field would be set accordingly. PDQ inventory would then know what computers have baseline installed.

Cancel
login to comment
0

This is a very old request, but I know that we can set "Custom Fields" via PowerShell, but if the remote machine has to run the powershell scripts, it can not "set" a Custom Field because PQD Deploy/Inventory is installed on the machine.

If this feature can not be implemented, how can we in a step run a powershell script "locally" on a PDQ Console/Server so that it can take the name of the computer that we are targeting to run the powershell script and pass over the correct information that we need it to do.

Thanks, Shane

Cancel
login to comment

0

I'm very interested to learn how to set custom fields with PowerShell!!!!!

Cancel
login to comment

Reply