You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WAC at first glance seems like a useful tool until one starts needing access to specific settings, a simple example:
Active directory management is not feasible as all the additional options provided by the on prem tool's properties (attributes) are missing.
In the Windows firewall it is not possible to customize certain options such as the origin of the traffic or more advanced options of the rule.
DHCP and DNS years later are still in preview.
WAC also fails to improve the wsus or file server management experience, it just can't be done without native tools.
It does not have support for Linux and although this is out of the question it would add a lot to ease the administration of the infrastructure, after all there are not that many official distributions available and Linux is somehow part of Microsoft thanks to solutions such as containers.
Exchange server, seriously, nothing about this great solution?
In summary, I have installed WAC on many occasions so that it is forgotten for months due to lack of functionality, every time it ends up being removed, it has no practical use.
WAC reminds me of VMWare many years ago when they decided to jump from the local client to the web client, it took "years" because VMWare did not finish adding all the options that did exist in the previous tool then until that did not happen the migration to the new one web management was only partial.
I don't know about the WAC development roadmap but I suggest that for the tool to be viable they migrate each platform completely, eg: active directory that supports all the options available in the current MMC. Once finished continue with the following tool.
If each module is not fully addressed there is no point in WAC existing because it does not solve anything, in the end we all end up using the MMC or powershell.
The text was updated successfully, but these errors were encountered:
Hello @rusomenace, I'm a WAC PM and I would like to have a call to further discuss suggestions on WAC and how we can improve the experience for you and other customers. Would this be ok with you? If yes, please send me an email at [email protected] with 2 or 3 of your preferred times and I can schedule.
WAC at first glance seems like a useful tool until one starts needing access to specific settings, a simple example:
Active directory management is not feasible as all the additional options provided by the on prem tool's properties (attributes) are missing.
In the Windows firewall it is not possible to customize certain options such as the origin of the traffic or more advanced options of the rule.
DHCP and DNS years later are still in preview.
WAC also fails to improve the wsus or file server management experience, it just can't be done without native tools.
It does not have support for Linux and although this is out of the question it would add a lot to ease the administration of the infrastructure, after all there are not that many official distributions available and Linux is somehow part of Microsoft thanks to solutions such as containers.
Exchange server, seriously, nothing about this great solution?
In summary, I have installed WAC on many occasions so that it is forgotten for months due to lack of functionality, every time it ends up being removed, it has no practical use.
WAC reminds me of VMWare many years ago when they decided to jump from the local client to the web client, it took "years" because VMWare did not finish adding all the options that did exist in the previous tool then until that did not happen the migration to the new one web management was only partial.
I don't know about the WAC development roadmap but I suggest that for the tool to be viable they migrate each platform completely, eg: active directory that supports all the options available in the current MMC. Once finished continue with the following tool.
If each module is not fully addressed there is no point in WAC existing because it does not solve anything, in the end we all end up using the MMC or powershell.
The text was updated successfully, but these errors were encountered: