MicrosoftI hear your point Artem Pronichkin. In fact there are few but certain usecases to use sconfig remotely.
- Windows Update via WAC is rather slow and still unreliable compared to sconfig, also sconfig WU does not show the same updates as settings app would (this can be a benefit, especially to skip prefetched updates, again especially for circumvent the Server 2016 update issues we are still suffering - not long for me until I have killed them all at our customers)
If you have a SMB customer that has 80+ Servers some of them still need manual patching and a remote sconfig would be amazing. I think we could even disable RDP then.
- you might want to check or configure telemetry
- you might want to check configure RDP, Network Ping response (for troubleshooting, for MTU handshake) etc.
I would like to stay away from legacy MMC and RDP and personally treat them as they do not exist anymore - if possible.
Sure many things can be managed via PowerShell, GPO or WAC (if not in DMZ), but it is easier for some other folks than me.
Later this week I'll add a bunch of feedback regarding WAC 2012 preview soon in uservoice, including ideas for sconfig.
sidenote: Often enough I wished sconfig would be also available on Windows 10 clients :). At the end it is just a script.
