Feature Request (WSUS Group)

[Travis R]

Hey I wanted to request a feature or two 🙂

Getting WSUS Group membership info from the registry key SoftwarePoliciesMicrosoftWindowsWindowsUpdate(TargetGroup) would be useful to me. There are also other keys in there that could be useful although it could get to be complex to display.

Second, I use CMTrace as a log file viewer. I do this so that the windows update log isn’t static and I can watch it move as it’s doing things.. Really REALLY useful over closing and opening the log several times. Anyway, is it possible that you have an option somewhere to open the WindowsUpdate.log file with the ‘default’ log file viewer that would be in use on the system. (If you didn’t use a log file viewer I guess it’d just open with Notepad.)

You’ve made a really cool app. I absolutely hate how you can’t manipulate the Windows Update COM object remotely, and you have an interesting way of getting around that restriction.

My company purchased an enterprise license a while back, and every admin that sees your tool loves it. Keep up the good work!

[doug]

Travis – I’m really glad the app is working for you. We are considering hardcoding some reg query capabilities in a future release. However, in the meantime you can actually already get at this information quite easily with BatchPatch in a couple of different ways. Try “Remote Command 3[or 4] Logged Output” with REG QUERY (http://technet.microsoft.com/en-us/library/cc742028.aspx). Or you can also hardcode this into BatchPatch yourself into the “Get Information > Create/modify user-defined commands” section, or in the “Remote Process/Command > Create/modify user-defined commands” section. Once you decide which commands you want, add them and they will appear in the BatchPatch menu and stay there until/unless you decide to delete them at a later date. We added this functionality specifically to address the fact that all of our customers have different needs, and we are not able to hardcode everything into BP for everyone. This option enables everyone to completely customize BP for their own needs.

Use the following syntax examples to create your commands:

List all subkeys in a specified subkey:

REG QUERY “HKLMSoftwareMicrosoft”

List specific value in a specified subkey:

REG QUERY “HKLMSoftwareMicrosoft.NETFramework” /v InstallRoot

We will look into your other request about providing an option to use the default log file viewer. To be clear, is your CMTrace simply setup such that it’s associated with all *.log files ? So you doubleclick any .log file and it launches in CMTrace?

Thanks,

Doug

[Travis R]

Sorry for the late reply Doug! And thanks for the information.. I’ve played a little with remote commands and will definitely have to look at it more.

As far as the other thing goes.. CMTrace is set up as the default log file viewer on my system. If you don’t set it that way of course it’ll open in notepad. 🙁

But I love the ability to watch log files scroll by instead of viewing/closing/opening/viewing/closing….

[doug]

Travis – the build that was published two days ago (11/11/2013) has an option in Tools > Settings to use the system default log viewer instead of the built-in BatchPatch viewer. Hopefully that should do the trick for you. If not, let me know.

Thanks,

Doug

[Travis R]

It works beautifully! Thank you so much!

And I built the remote command. It works great too. I used: reg query “hklmSoftwarePoliciesMicrosoftWindowsWindowsUpdate” /v “targetgroup” to find the WSUS group membership.

Knowing that I can basically program this thing to grab registry keys as I need is good enough for me!

Again thanks so much for your responsiveness, and I really like your program.

[doug]

Thanks for confirming, Travis. I’m really glad it’s working well for you.

Take care,

Doug

[doug]

There is now direct support for retrieving registry keys under Actions > Get Information > Get registry key/value

[Author]

Posts