view targeted computers wrong in patch management 7.1 sp1
Hi,
we have cms and are running patch management 7.1 sp1.
We have apporved a bulletin and created a policy to apply to a filter with a 5 test machines. This works ok and I can check the policy is applying to the correct machines,by viewing the policy and checking the computer and seeing the policy applied to it.We have tested the rollout and it is only rolling out to the right machines so the filters are definately working.
If I look in the delivery summary it shows the bulletin and the targeted computers is showing 43 which is the number of machines the need the update.
The installation complete column shows the correct total e.g. 5, but the installation incomplete shows all the remainign machines (43). Right click and choosing view complete or uncomplete installations both give no results which is not very helpful considering i know it patched 5 machines.
According to the manual the 'view targeted computers' "displays the computers that the software update policy containing this bulletin is targeting" which it is clearly not.
I could cope with this as just a bug, but how do i see what computers that I have applied a software update policy to have actually succeeded or failed given that the complete/incomplete reports do not work and the delivery summary report is wrong?
any help is appreciated
cheers
Comments
Reboots?
Have the computers rebooted after installing the patch, thus completing the install? Have they performed a new Windows Vulnerability Assessment Scan, which has been processed by the NS?
Mike Clemson, Senior Systems Engineer
Intuitive Technology Group -- Symantec Platinum Partner
sorted it
found out the problem. It was the alternative dns name that I used. Although this is set correctly and resolved on all host (that address is what all the clients use to connect) it stops the task server binding to 50121.
I changed the reg key on the NS server HKLM\Software\Altiris\Altiris Agent\Servers to point to the FQDN of my NS server rather than the alternative name and it worked. Found someone else with the same problem.
After this the task server bound to 50121 and tickle now works.
cheers
can you please elaborate on
can you please elaborate on that Task Server issue? You created an alias and registered all the agents via that alias, is that correct?
Daniel Lopes de Oliveira
Endpoint Management Architect & Consultant
-----------------------------------------------
MCITP: EA
Would you like to reply?
Login or Register to post your comment.