Open for Voting

Save view layout after a program upgrade

I was wondering if it could be possible to save view layout after a program upgrade.

A recent program upgrade reminded me to suggest this. I recently upgraded to 1.73.221.4 patch to prepare for the upcoming 1024 byte certificate changes coming from Microsoft this month.

I had to go into each of my views and add a column so it was really no big deal, but I was wondering if larger organizations with more complex WSUS setups would need to save particlar settings in certain views.

Thanks again for all your hard work on this product. It really does the trick for 3rd party software.

  • Thanks for info. Should I delete this idea since it has not happened in a while?

  • FormerMember
    FormerMember

    We’ve reproduced the issue in our environment. The reason is that Patch Manager 1.85 MMC snap-in in use different file to store the custom view layouts

    The issue may occur in following upgrade scenarios:

    1.7x -> 1.85

    1.7x -> 1.80 -> 1.85

    And here is a workaround:

    1. Close Patch manager MMC console

    2. Go to the folder:

    C:\Documents and Settings\<user_name>\Application Data\Microsoft\MMC\ (Windows 2003)

    C:\Users\<user_name>\AppData\Roaming\Microsoft\MMC\ (Win 2008 and higher)

    3. Create a backup of files in the folder

    4. Remove file “SolarWinds” if present.

    5. Rename file “EminentWare” to “SolarWinds”

    6. Restart the console

    Sorry for the inconvenience.

  • Yes Mark, this has been the case in most updates of Patch Manager. Luckily, I do not have too many custom views, I just set the views I like one by one till they get done. I just figured it was part of the job of managing the Patch Manager server. Usually it only takes me a couple of hours to correct the saved views.

  • I just updated to 1.85 and found all my custom views to be reset!  This really sucks as i had put in a significant amount of time customizing those views.  Including following the recent article which now have to be redone!  Please bump this feature request!  Thanks!  -mark