Windows Server 2025 (Windows Server 2025) Hardened
Centralized identity and file management has streamlined daily operations and reduced downtime
What is our primary use case?
Our main use case for Windows Server 2025 (Windows Server 2025) | Support by Supported Images was Active Directory via Windows Server for our organization. Our secondary main use case was providing a file server for the company.
For day-to-day identity management and file access, we created identity-based home drives for users. Whenever users log in, their home drive is mapped to their Active Directory user profile. That is how we managed user requests regarding file and identity services.
Handling Active Directory and a file server for a large company is a pretty big use case, and I believe that covers our main use cases.
How has it helped my organization?
Windows Server 2025 (Windows Server 2025) | Support by Supported Images has positively impacted our organization, since Windows Server is basically the mainstream choice for managing large enterprises because of Active Directory, which is the obvious use case of Windows Server. We have a multi-directory environment, and we handle it very well because of the Windows Server Active Directory environment. We have different child domains, we used a DHCP server in the past, and we also used a file server. We handle everything via Windows Server.
We have seen specific outcomes, such as reduced downtime. Because we can configure an additional domain controller, if there is an issue on the primary domain, we can easily turn on the secondary domain and promote it as the primary domain until we fix the issue with the other server. When we faced such an issue, we resolved it within one or two minutes because of the Windows Server PowerShell features, which helped us speed up the resolution.
What is most valuable?
Among the best features Windows Server 2025 (Windows Server 2025) | Support by Supported Images offers, the main one is the user interface. I am talking about the Active Directory interface, which has improved a lot. Specifically, they changed the back-end file system and processing, so I can access it pretty fast without any lag. That was the main feature we liked about the newer release of Windows Server. I have used Windows Server 2008 and Windows Server 2019, so I can easily see the difference.
In terms of administration time, we used PowerShell in the back end to make changes faster. We process users in no time with PowerShell by connecting it directly to Active Directory. We use PowerShell scripting and Task Scheduler on the server itself. Whenever there is a need, we run Task Scheduler or sometimes automate it, so we can easily fix certain attribute issues, password resets, or other group issues with PowerShell because of this newer Windows Server environment.
What needs improvement?
I do not see much room for improvement in Windows Server 2025 (Windows Server 2025) | Support by Supported Images. All the required features are there in the latest release, so it is pretty good.
If I could change one small thing, it would be updates, because sometimes an update can fail and break Windows Server. We faced that issue in the earlier days, when a Windows update broke the server.
Everything is good.
For how long have I used the solution?
I have been using Windows Server 2025 (Windows Server 2025) | Support by Supported Images for more than a decade. I have used Windows Server for almost more than a decade in my existing environment.
What do I think about the stability of the solution?
Windows Server 2025 (Windows Server 2025) | Support by Supported Images is definitely stable.
What do I think about the scalability of the solution?
The scalability of Windows Server 2025 (Windows Server 2025) | Support by Supported Images is pretty good. You can definitely scale it up to a large level. That is what I can say.
How are customer service and support?
We have never faced any issue with the customer support for Windows Server 2025 (Windows Server 2025) | Support by Supported Images.
I rate the customer support 10 out of 10 on a scale of 1 to 10.
Which solution did I use previously and why did I switch?
We did not use another solution previously. We were using Windows Server 2008, and then we upgraded to a new release of Windows Server for its features.
What was our ROI?
We have seen a return on investment. We were successfully able to manage a large organization because of Windows Server and its environment via Active Directory.
We have managed around 5,000 users with Windows Server 2025 (Windows Server 2025) | Support by Supported Images and Windows Server Active Directory.
What's my experience with pricing, setup cost, and licensing?
The pricing, setup cost, and licensing for Windows Server 2025 (Windows Server 2025) | Support by Supported Images were pretty reasonable. It was not expensive, and it was fair enough.
Which other solutions did I evaluate?
We did not evaluate other options before choosing Windows Server 2025 (Windows Server 2025) | Support by Supported Images.
What other advice do I have?
On a scale of 1 to 10, I rate Windows Server 2025 (Windows Server 2025) | Support by Supported Images 10 out of 10 because of the use case. If you understand the needs of your organization, Windows Server can definitely help you with them.
I give it a 10 out of 10 because Windows Server has all the capabilities to manage small or large organizations. If you know what your organization needs, you can definitely handle that requirement without complicating the situation.
For others looking into Windows Server 2025 (Windows Server 2025) | Support by Supported Images, you should definitely take a look at Windows Server. If your organization needs Active Directory user management, file services, or DHCP services, this is the one, because you will get everything under one roof. It is a pretty reliable solution.
Modern security and ai features have transformed financial virtualization and analytics work
What is our primary use case?
For our security and compliance needs, Windows Server 2025 (Windows Server 2025) | Support by SupportedImages has extensively modernized Active Directory. Active Directory provides better security control, improved scalability, and identity management. All of these features help us maintain very strong security protocols and a secure environment as we work in the financial domain.
How has it helped my organization?
As I mentioned, Windows Server 2025 (Windows Server 2025) | Support by SupportedImages has the best security capability compared to any previous Windows Server release. It has very good support for Azure and other clouds, including hybrid cloud integration. The AI capability is very good. It has very good Active Directory capabilities. The hot-patching capabilities have reduced our downtime. It also has very long-term enterprise support, which deserves to be applauded.
What is most valuable?
In the day-to-day work of our development teams, the integration with GitHub and analytics has improved our working capabilities inside Windows Server 2025 (Windows Server 2025) | Support by SupportedImages. It has been a great addition because, compared to the previous operating system, it provides out-of-the-box capabilities.
The governance and security in the AI capabilities of Windows Server 2025 (Windows Server 2025) | Support by SupportedImages are among the best provided, compared to its predecessors or its competitors.
The accuracy and reliability of its AI output in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is also very good, in the sense that you can trust the outcome produced by it to an extent.
What needs improvement?
Certain hybrid features in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages may also require additional administrator retraining, which can be improved as well.
I rate it a 9 rather than a 10 because of the licensing cost, which is the one point I am deducting. It is still on the higher side, and that is one aspect that can be improved. Other than that, its features and capabilities are top-notch.
For how long have I used the solution?
Which solution did I use previously and why did I switch?
What was our ROI?
As a ballpark number, it has saved at least 30% of our time since we migrated from the previous version, basically from Windows Server 2019 to Windows Server 2025.
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
Centralized identity management has strengthened hybrid access control and simplified container deployment
What is our primary use case?
We are working with the identity management part of Windows Server 2025 (Windows Server 2025) | Support by SupportedImages.
We are using containerization for application deployment on Windows.
What is most valuable?
Identity management for access control is definitely an important aspect for us.
We use identity management to address security risks in our Windows Server 2025 (Windows Server 2025) | Support by SupportedImages environment. As of now, we have a hybrid environment that is also connected through Azure. For central management, since we have many locations and sites, I believe Microsoft AD is the best solution I know of in identity management.
For how long have I used the solution?
What other advice do I have?
Modern desktop delivery has become smoother and integration with current clients works reliably
What is our primary use case?
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?
What needs improvement?
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?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
How was the initial setup?
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
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.
Hybrid servers have simplified service delivery but still need stronger security controls
What is our primary use case?
I use Windows Server 2025 (Windows Server 2025) | Support by SupportedImages mainly for configuring different servers and offering services to clients, including DHCP, DNS, Active Directory (AD DS), Active Directory certificate services (AD CS), and group policies.
I did not configure identity management in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages, but many members of my team are configuring it. Identity management and access management are mainly configured in the firewall.
How has it helped my organization?
We are integrating cloud capabilities in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages daily, gradually becoming meaningful, and in the coming days, it will certainly improve operational efficiency significantly.
It definitely minimizes downtime during disaster recovery.
Downtime and latency will be reduced significantly, though I do not have a clear quantification of the exact improvements.
What is most valuable?
The biggest advantage I find in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is that it is very user-friendly.
Most of the features make troubleshooting very easy in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages. However, in Linux, if you want to configure servers and troubleshoot, you should have a sound knowledge of core Linux and Unix operating systems, particularly good command line control. For users not very familiar with command lines, Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is the best option.
Identity management is helpful for access control; we can divide users in our domain into groups and provide different access to them for different resources.
Containerization in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages helps with application deployment as it allows us to run separate applications in isolated containers, maximizing resource utilization for CPU and memory.
What needs improvement?
Regarding security, I do not agree with Windows Server 2025 (Windows Server 2025) | Support by SupportedImages because I believe Linux is the best for securing servers.
Windows Server 2025 (Windows Server 2025) | Support by SupportedImages has become a very good, sound operating system, and I do not find any issue.
Looking to the future, I see Windows Server 2025 (Windows Server 2025) | Support by SupportedImages having a very bright future, but it needs to improve security integrations and command line functionalities to help administrators have better control.
Regarding security, we should ensure that our servers accessible from the public network are not exposed, aiming to minimize the attack surface as much as possible.
We have a granular level of control in Linux through command lines, which is something we lack in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages. If more shells, such as Bash, are implemented alongside command line and GUI, it will provide a better mix for users and administrators.
For how long have I used the solution?
I had started using Windows Server a long time back, having begun with Windows NT Server 4.0 in 1998.
More than 20 to 25 years have passed since then.
What do I think about the stability of the solution?
Windows Server 2025 (Windows Server 2025) | Support by SupportedImages has become much more stable compared to earlier versions; as long as sufficient hardware resources are allocated, it operates effectively.
What do I think about the scalability of the solution?
I find scalability in Windows Server 2025 (Windows Server 2025) | Support by SupportedImages much easier compared to earlier versions, but some improvements are still needed.
I see no limitations in scalability per se, but for effective use, high-end hardware requirements, such as more memory and CPU, are essential, which are less of an issue in Linux.
How are customer service and support?
Microsoft technical support is good; their response is timely and prompt.
I would rate Microsoft support as eight out of ten.
How was the initial setup?
Installing Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is very easy; anyone can do it.
What was our ROI?
I see value for money with Windows Server 2025 (Windows Server 2025) | Support by SupportedImages; we can save time and money through automation, which we are gradually implementing.
The savings may be around 50% when automation is fully implemented.
What's my experience with pricing, setup cost, and licensing?
I believe the pricing of Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is okay and perfect compared to what other industry products and vendors are charging.
What other advice do I have?
I was part of the Microsoft service provider network as an Action Pack member, but right now we have membership with Amazon AWS and Microsoft Azure, deploying most things in the cloud.
I have it in a hybrid environment; it is both on cloud and on-premises.
I work with both Azure and AWS for Windows Server 2025 (Windows Server 2025) | Support by SupportedImages.
I have purchased licenses for various products, including Palo Alto, Fortinet, Cisco SD-WAN, Cisco Catalyst SD-WAN, and Nexus ACI; these two Cisco products are very good and hold substantial market share.
If I had to rate Windows Server 2025 (Windows Server 2025) | Support by SupportedImages, I would give it a seven out of ten.
Cloud hosting has improved security and flexibility but licensing costs need better options
What is our primary use case?
Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is mainly used by our client for application hosting.
I don't work extensively with the identity management part, but I do occasionally engage with it.
We work with Entra, which is the main use case we are using for the Active Directory part.
We are not currently using Windows Server 2025 (Windows Server 2025) | Support by SupportedImages for containerization support.
How has it helped my organization?
The impact of cloud integration on operational efficiency is significant, as many servers are now virtual servers or cloud servers, unlike previous days when we ran Microsoft Server editions on bare-metal servers. Currently, almost 100 percent is deployed on either virtualized platforms or cloud platforms such as Azure.
We have not calculated metrics for minimizing downtime, but with cloud platforms such as Azure, there are sometimes regional inaccessibilities, though availability is better compared to having bare-metal servers.
What is most valuable?
The biggest advantage of Windows Server 2025 (Windows Server 2025) | Support by SupportedImages depends on the application stack, because some customers use Microsoft stack, while others use Linux operating systems. However, customers who develop their applications on Microsoft stack choose Microsoft, and I think the majority is doing so.
What I appreciate about Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is the full solution Microsoft provides, especially when it comes to the cloud part and security, with their Microsoft total solutions.
The security protocols that Windows Server 2025 (Windows Server 2025) | Support by SupportedImages has are a full stack. When it comes to the Microsoft full stack, they have Active Directory, the Defender part, and it can extend into Microsoft Sentinel, which represents the benefit Microsoft has.
What needs improvement?
The main disadvantage of Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is pricing, as customers choose some Linux versions, which are open-source editions. There are some customers moving to open-source Linux editions because of the pricing, which is the main disadvantage, especially when it comes to SQL databases, as SQL is quite costly.
I think Microsoft might bring new licensing models to support different customer segments, such as enterprise and SMEs, primarily focused on cost. Bringing additional products in the operating system versions with current features would be beneficial.
The only drawback I see is connected with the license model and price. That is the only disadvantage, but everything else is acceptable.
For how long have I used the solution?
I have been working with Windows Server 2025 (Windows Server 2025) | Support by SupportedImages since 2010.
What do I think about the stability of the solution?
If Windows Server 2025 (Windows Server 2025) | Support by SupportedImages is hardened perfectly, it is stable, but if it is not updated properly, then it will not be.
What do I think about the scalability of the solution?
As for the scalability of Windows Server 2025 (Windows Server 2025) | Support by SupportedImages, I do not see any limitation. It all depends on what to host on these servers and whether to deploy on a single instance, multi-instance, or a scalable Kubernetes architecture.
How are customer service and support?
Technical support from Microsoft is adequate, and there is a lot of documentation available. There is nothing to complain about.
If I had to rate support from zero to ten points, I would give them an eight.
How was the initial setup?
For Windows Server 2025 (Windows Server 2025) | Support by SupportedImages, I find installation to be easy.
What was our ROI?
Windows Server 2025 (Windows Server 2025) | Support by SupportedImages has a market presence, and I do not disagree, especially since many applications are developed on Linux and are moving towards the cloud such as Azure. Therefore, Windows will maintain a good market share, but cost-sensitive customers often move towards Linux versions.
Which other solutions did I evaluate?
From a technical perspective, Linux may take much more use, and while a beginner might look for Windows due to lack of exposure, my reading shows that Linux users utilize its capabilities more than with Windows Server 2025 (Windows Server 2025) | Support by SupportedImages.
What other advice do I have?
We are working as a partner with Microsoft.
We have different customers with various deployment styles, but our focus is mainly on the cloud.
We work in majority with enterprise customers as well as small and medium enterprises.
The majority of deployments are on our cloud platforms, which are built on products such as VMware, but we also have some workloads on Azure. Previously, we had Azure Stack, which is now discontinued, so we are moving others to local cloud platforms such as VMware and Nutanix.
My team has purchased products from cloud providers for storage services and some platform as a service kind of requirements.
Overall, I would rate Windows Server 2025 (Windows Server 2025) | Support by SupportedImages at seven points.
Server 2012 R2 is fine tuned version of 2012 with many improvements - can be deployed different ways
Can check your system with Best Practice Analyser to see if its optimised
easy to add extra roles to your server
extremely scalable for small or big requirements
Can be deployed by premade images using Azure or other providers if you are using it on the cloud
About to be end of life this (2022) year.