What is our primary use case?
As a Microsoft partner, I integrate Windows servers based on what companies need, focusing on
Windows Server 2019 combined with Citrix for virtual desktops and applications.
We are currently in a transition phase, introducing Windows Server 2025 (Windows Server 2025) | Support by SupportedImages in a Citrix environment because Windows Server 2019 is no longer supported for some required software. We upgraded to Windows Server 2025 (Windows Server 2025) | Support by SupportedImages because certain applications demand at least Windows Server 2022, and moving forward, all new projects will use Windows Server 2025 (Windows Server 2025) | Support by SupportedImages.
Although identity management is a consideration, we are not currently using it on a larger scale in our projects with Citrix, such as in a banking environment, where we rely on other products for identity management due to the partial hybrid connectivity of our servers.
Containerization and virtualization are areas to explore, but we are not using them actively at the moment. Virtualization layers are often different, and clusters of systems such as VMware handle that adequately.
For disaster recovery regarding Windows Server, we typically rely on storage-level recovery rather than Windows Server backups. Many of our similar scenarios involve using virtual abstraction layers beneath.
What is most valuable?
A significant benefit of Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is its smoother integration with
Windows 11, particularly in network environments. However, the new features are not immensely groundbreaking, as we were satisfied with Windows Server 2019 for most scenarios. In Citrix environments, moving to Windows Server 2025 (Windows Server 2025) | Support by SupportedImages resolves compatibility issues since it pairs well with
Windows 11 clients.
What needs improvement?
The changes that Microsoft made with the introduction of Windows Server 2025 (Windows Server 2025) | Support by SupportedImages did not enhance our security; rather, they made it harder due to uncommunicated security features being activated. We encountered scenarios where processes that previously functioned became problematic, especially for third-party software vendors.
The main issues arise from recently introduced security features that were implemented without adequate notice, complicating the use of third-party software. Moreover, Microsoft has altered the update schedule, cramping our release cycles in environments with 180 servers serving around 1,000 users due to unexpected updates.
For how long have I used the solution?
I have been working with Windows Server since Windows NT 4.0 in the 90s, transitioning from UNIX systems to Windows. My experience includes being a Microsoft Certified Trainer for Windows Server 2000 up to 2008. Although I stopped giving those lectures, I still work heavily with Windows Server.
What do I think about the stability of the solution?
The stability of our systems is not 99.9%, as network problems and driver issues sometimes lead to glitches. For instance, I must occasionally take machines offline for reinstallation or other corrective measures.
What do I think about the scalability of the solution?
I have not encountered issues with scalability while using Windows Server 2025 (Windows Server 2025) | Support by SupportedImages, but redundancy can be a concern when creating cluster environments, which require ample resources.
How are customer service and support?
Support experiences often vary. It takes patience and time to engage with Microsoft support, and I have found that engineers are sometimes hesitant to proceed with support tickets due to lengthy processes. I find that consulting alternative AI resources can often yield quicker answers.
How was the initial setup?
My experience shows that installing Windows Server is relatively straightforward. The procedure remains consistent between versions such as Windows Server 2019 and Windows Server 2025 (Windows Server 2025) | Support by SupportedImages, taking roughly 5 to 10 minutes.
What was our ROI?
I do not perceive a significant monetary relief from the upgrade from Windows Server 2019 to Windows Server 2025 (Windows Server 2025) | Support by SupportedImages, as licensing contracts usually remain independent of the installed versions, meaning the overall costs are somewhat static.
What's my experience with pricing, setup cost, and licensing?
License costs in the banking environment are typically not a main concern, as other IT costs tend to overshadow them. I find that server licenses are not excessively burdensome compared to costs such as memory, which can be significantly higher.
Which other solutions did I evaluate?
The ongoing debate around the security comparisons between Windows and Linux has persisted for decades, with Windows being seen as a more closed system. Recently, some issues have arisen predominantly affecting Linux systems, challenging previous notions of safety.
What other advice do I have?
In Switzerland, my clients, particularly in the banking sector, are cautious about moving data to the cloud due to legal concerns about US access. Therefore, some companies prefer keeping their data on premises to avoid compromising security.
Currently, I primarily work on-premises, operating exclusively within shared hardware data centers and not utilizing cloud services such as Azure or AWS.
We have experimented with Azure for some testing installations, but the overall costs associated with cloud services raise concerns. While we employ cloud solutions for backup, our infrastructure remains on-premises.
For the product itself, Windows Server 2025 (Windows Server 2025) | Support by SupportedImages earns a solid rating of seven or eight from me because it is user-friendly to work with. My main frustration lies in the mandatory updates and newly introduced security features that complicate third-party software operations.
Which deployment model are you using for this solution?
On-premises
