locked
Windows 10 RSAT WSUS Computers view column changes not copying or persisting RRS feed

  • Question

  • A few weeks ago, I installed the new version of Remote Server Administration Tools on Windows 10. Today I accessed the Windows Server Update Services module for the first time. I selected additional columns from the menu that appeared when I right clicked the column headers in any of the 'Computers' views. I then selected 'Apply to All Views' from the same menu. The columns did not copy to the other computer views. When I restarted the module, the view that I did change had reverted to the default columns. I did see the correct expected behavior in all the 'Updates' views, just not the 'Computers' views.

    I do not see this behavior in the Windows Server Update Services module on the server. I did not see this behavior on my workstation before upgrading to Windows 10 when using RSAT WSUS for Windows 7. It seems this issue is specific to RSAT for Windows 10.

    Has any one else observed this behavior? Is there something I can do to resolve it?

    Thanks,

    Shem

    Friday, September 11, 2015 10:05 PM

Answers

  • I took a hint from Lawrence Garvin's response to this other WSUS issue (https://social.technet.microsoft.com/Forums/en-US/460d631d-9a56-4687-a721-7636ac3cfbdb/how-to-save-columns-customization-and-views-on-wsus-console?forum=winserverwsus) and deleted the %AppData%\Microsoft\MMC\wsus file. The wsus file created when I ran the WSUS snapin again was able to persist the settings.

    One small difference from Lawrence's instructions is that it seems that %AppData% now evaluates to the Roaming folder in Windows 10, so %AppData%\Roaming\Microsoft\MMC evaluates to AppData\Roaming\Roaming\Microsoft\MMC, which does not exist.


    • Marked as answer by ShemSargent Friday, September 11, 2015 10:44 PM
    Friday, September 11, 2015 10:43 PM

All replies

  • I took a hint from Lawrence Garvin's response to this other WSUS issue (https://social.technet.microsoft.com/Forums/en-US/460d631d-9a56-4687-a721-7636ac3cfbdb/how-to-save-columns-customization-and-views-on-wsus-console?forum=winserverwsus) and deleted the %AppData%\Microsoft\MMC\wsus file. The wsus file created when I ran the WSUS snapin again was able to persist the settings.

    One small difference from Lawrence's instructions is that it seems that %AppData% now evaluates to the Roaming folder in Windows 10, so %AppData%\Roaming\Microsoft\MMC evaluates to AppData\Roaming\Roaming\Microsoft\MMC, which does not exist.


    • Marked as answer by ShemSargent Friday, September 11, 2015 10:44 PM
    Friday, September 11, 2015 10:43 PM
  • Hi,

    Glad to hear that your issue has been resolved and thanks for the sharing!

    Your time and efforts are highly appreciated!

    Best Regards.


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, September 17, 2015 2:12 AM
  • Same issue here after upgrading from Windows Server 2012 R2 to Windows Server 2016.

    Thursday, January 19, 2017 1:51 PM
  • I did an in-place upgrade from Win7 with RSAT to Win10. I re-installed the Win10 RSAT tools, but not until I removed the WSUS feature set and added it back - was I able to save/apply the MMC view settings.  No reboot needed.  (and of course, don't forget to upgrade the report viewer with the Report Viewer 2012 Runtime).


    • Edited by AK0000 Thursday, April 20, 2017 3:47 PM more details
    Thursday, April 20, 2017 2:59 PM