Hi Sri – I would really love to know the reason why you want to use a BAT file to run a PS script. I keep seeing this a lot, I feel the need to understand the rational behind it; personally it feels very wrong or at the least unnecessary.
Hi Eric – CMTrace (or trace32 for 2007) can definitely tell you what you want. The log to look at is still SMSTS.Log. All you need to do is use the filter feature and enter criteria “installed successfully”. This will give a list of only the items that installed. If you know what is meant to be there you can check them off. Perhaps a nicer/quicker way is to use PowerShell to do the same thing – hunt for those words.Finally, whilst status messages are useful, I don’t like using them for OSD checking. I either look at Monitoring and find the deployment and look at the status log in the console, or, even better use CMtrace and connect through to the remote machine and look at the logs directly. Note you can redirect the logs to a central share too, which can also help with auditing.Mike
Hi,Patching ironically uses the same logs as always: C:WindowsWindowsupdate.log being the main one.There is also eventlogs galore in eventviewer (source c:windowslogsWindowsupdate).In the CCM folder there are a few more to check: c:windowsccmlogsUpdatesHandler.log, WUAHandler.log and PolicyEvaluator.log as the most useful.for a full list see here: https://technet.microsoft.com/en-us/library/hh427342.aspx#BKMK_WSUSLogMike
A PowerShell alias is a shortcut to a command that can save you some keystrokes and help you remember commands. In this guide, you will learn how to create a PowerShell alias and what to keep in mind when working with aliases.