I do not know why this was changed but it has never been complete. For debugging patching issues, you always want to look at the vulscan log file on the client. You can get to the vulscan log files by running "VULSCAN.EXE e" from Start | Run on the client.
Hi yes we have looked in the vulscan log file but that log file has alot of information based on the compliance scan where as the other log file only concentrated on the definitions your applying.
So it is supposed to report that way then in the console?
We need a way of viewing this log without conneting to the machiine ideally - why would they change this?
Anyone else know?
Well I thought my mind was playing tricks on me. I thought I remebered a more detailed log when I had LD9 SP2 installed. Now i have SP3 installed and having problems all I see is failed in the log and all patches failed in the console. Yet when I right click on the computer go to patch and scan, look at the patch properties it says done no error at the bottom.
I run another scan on the computer and it still says I need this patch.
I ran one patch 5 times over 2 days trying to see why it was failing and the last time I ran it the task finally said successfull. I've run 50 (the maximum 25 at a time) other patches on this computer 3 times and everytime it says failed.
Since this is the first time I've run a patch since upgrading to SP3 are you seeing alot of failures too?