I would like more server hardware in the cloud. Deploying more into the Azure ( /products/microsoft-azure-reviews ) architecture would be beneficial, and maintaining support for legacy applications would facilitate easier deployments onto new operating systems like Windows 11 ( /products/windows-11-reviews ).
The process was streamlined but didn't make our work simple. We encountered an issue with the person responsible for designing the website. They installed a plugin that disrupted the services and made the website inaccessible. We resolved the problem using the automatic backup preconfigured on the platform. The website was restored quickly, making it easy to address the user-created issue.
Microsoft has announced that it is going to discontinue the solution. I wish the vendor would not discontinue the tool. The reporting features could be improved. We use our in-house tools for reporting.
The downside is that Microsoft bought this product and they are going to discontinue it in 2026. This is worrisome for us. I would like to see them continue to maintain the product. From my point of view, it reached a maturity where we can consider it to be perfect. If we wanted to be picky, Microsoft could improve the synchronization of the client. We were forced to put our own PowerShell script, which mimics the built-in functionality of the syncing. It would avoid errors. Another feature that has not been implemented, but would be nice to have is the possibility to publish different shortcuts within the same package, to different groups. There is a solution in place, but it's not really working. If you have two different groups on two different shortcuts, everything works fine, as long as you don't have a common set of users in those groups. As soon as you have one user in both groups, then the client won't know which one to publish, and it is not able to do a merge between those two settings. I would like the synchronization improved and to have the possibility to publish different shortcuts to different groups within the same package.
Microsoft Application Virtualization (App-V) enables you to make applications available to end users without installing the applications directly on end user computers. App-V transforms applications into centrally managed services that are never installed and don't conflict with other applications.
There is definitely room for improvement with Microsoft App-V, especially in terms of enhancing troubleshooting resources and user guidance.
I would like more server hardware in the cloud. Deploying more into the Azure ( /products/microsoft-azure-reviews ) architecture would be beneficial, and maintaining support for legacy applications would facilitate easier deployments onto new operating systems like Windows 11 ( /products/windows-11-reviews ).
The process was streamlined but didn't make our work simple. We encountered an issue with the person responsible for designing the website. They installed a plugin that disrupted the services and made the website inaccessible. We resolved the problem using the automatic backup preconfigured on the platform. The website was restored quickly, making it easy to address the user-created issue.
Microsoft has announced that it is going to discontinue the solution. I wish the vendor would not discontinue the tool. The reporting features could be improved. We use our in-house tools for reporting.
The downside is that Microsoft bought this product and they are going to discontinue it in 2026. This is worrisome for us. I would like to see them continue to maintain the product. From my point of view, it reached a maturity where we can consider it to be perfect. If we wanted to be picky, Microsoft could improve the synchronization of the client. We were forced to put our own PowerShell script, which mimics the built-in functionality of the syncing. It would avoid errors. Another feature that has not been implemented, but would be nice to have is the possibility to publish different shortcuts within the same package, to different groups. There is a solution in place, but it's not really working. If you have two different groups on two different shortcuts, everything works fine, as long as you don't have a common set of users in those groups. As soon as you have one user in both groups, then the client won't know which one to publish, and it is not able to do a merge between those two settings. I would like the synchronization improved and to have the possibility to publish different shortcuts to different groups within the same package.
If it were possible to integrate App-V with a cybersecurity solution then we could implement a documentation registry, which would be useful.