The most valuable feature is its stability. We have had no problems with Windows Server and we plan to continue using it in the future.
This product has very good features.
The most valuable feature is its stability. We have had no problems with Windows Server and we plan to continue using it in the future.
This product has very good features.
I would like to see better integration with other operating systems. For example, when I migrate from services from Linux or Unix to Windows Server, it's hard to do. I expect it to be easier.
We began using Windows Server between 10 and 12 years ago.
This is a scalable product. We have more than 150 people in 20 different groups who use it. In my personal group, we have four people.
We have not faced any problems that we couldn't solve, so we have not needed to contact technical support.
I have worked with other operating systems such as Linux and Unix, and I find that they are more complicated.
The initial setup is straightforward. It takes between two and four hours to deploy, depending on the type of service.
We installed it ourselves and we have an IT staff of about six people that use it regularly.
We have a corporate deal with Microsoft and pay licensing fees annually. It is an expensive product.
Overall, this is a good product that is easy to use, it has very good features, and I can recommend it.
I would rate this solution a seven out of ten.
It's a platform, so it brings on a system for the servers themselves. I have multiple services running over Microsoft Servers, for example.SAP, Exchange . All of my services already running are running over this platform.
I also using it occasionally for application access.
The most valuable aspect of the solution is its operating system. It's just like Linux or UNIX.
I'm using all the features within it and find them all quite helpful.
I love using it for the DHCP server, DNS services, and using a computer to map sites on our domain.
The security should be improved, specifically from port security & Allowed protocols,The improvement should retire all marked ports & protocols as a security breach to enhance platform risks & stability .
Overall, from a security perspective, Microsoft needs to improve.
The Server platform GUI seems to take up a lot of resources unnecessarily.
I've been using the solution for twenty plus years for now.
While the solution hasn't always been stable, starting from the 2012 version, it's increasingly gotten more stable.
Since the 2012 version, we find it to be quite stable. The OS between the resources, between applicators, technical support, etc., is all very easy to handle. We don't have issues with it; it seems to be quite reliable.
The company here is using this solution. Sometimes it's for remote access, however, even if they don't use it for that, they already using is as it's implemented over the Windows Server.
I'm not sure if we'll be scaling any more as everyone is using it.
Registration is very easy, so we didn't need technical support for that aspect of the solution. However, it still requires continual study in order to use everything properly. In terms of speaking with someone directly, I don't have any information about that, and therefore can't comment on the quality of their service.
The initial implementation was not complex. I'd describe the setup as straightforward.
You have to sign off the approach of the planned service, make a timeline, and start to implement a POC. Once you're done with that, you can apply for it online.
For Microsoft platforms, we have not needed any outside assistance. For the other services, like ERP, we are already using consultants for implementation.
We're just a customers. We've been using multiple versions of the solution up to the 2016 version.
I would recommend the Microsoft platform and Windows Servers in particular. It's great for implementation into any environment and is easy to use. They have enhanced some security, however, there needs more done in that respect.
That said, from an efficiency, performance, business continuity, and integration standpoint, I'd highly recommend the Microsoft platform. While Linux has a better security layer, if that is your concern, be aware it will require investment in a lot of resources, training.
I'd rate the solution seven out of ten. To get higher marks, the solution really needs to do something about the GUI & its security, which currently consumes a lot of resources & allowing breaching.
We use the product as an application and SQL server.
The platform’s most valuable features are performance and centralization of operating systems. We can use one standardized system to host all applications.
The product's pricing needs improvement.
We have been using Windows Server for more than 20 years.
We have more than 100 Windows Server users in our organization. It is a scalable product.
We contact the technical support team for a few queries.
We used Linux before. In some cases, it works better than Windows in terms of administration tools, especially for small companies.
From a centralization standpoint, Windows Server is a good technology that allows IT staff to consolidate their expertise on a single product, avoiding the need to manage different sources for Linux and Windows.
Windows Server is highly priced. They offer bundled licenses to be purchased yearly. Also, we need to pay extra for support services while utilizing different sources such as Linux.
Windows Server’s integration with Active Directory enabled a single technology to manage multiple applications. Additionally, the feature for centralized management has proven beneficial in enhancing overall efficiency and meeting evolving requirements compared to Linux.
It is primarily suitable for enterprises as the cost would be a concern for smaller organizations.
It is a user-friendly platform. I rate it a nine out of ten.
I use the solution to manage file servers.
The tool is easy to access and manage. You don't have to take any backups.
Windows Server needs to improve its speed and stability.
I have been working with the product for 20 years.
I rate the product's stability an eight out of ten.
Windows Server is scalable, and my company has 2000 users. It is used extensively.
I haven't contacted Microsoft support.
The tool's deployment is straightforward and takes six months to complete. The product is overseen by a technical team of ten resources.
Our consulting company helped with the deployment.
The tool's licensing costs are yearly.
I rate the overall product an eight out of ten.
We use Windows Servers to manage user logins through Active Directory and facilitate VPN connections, supporting our researchers who are architecturally building on DSP DNS for enhanced security and access control.
I find Windows Server valuable for its flexibility and user-friendly interface.
In terms of improvement, performance could be enhanced.
I have been using Windows Server for 13 years.
Windows Server is very stable.
We have not had any issues with the scalability of Windows Server.
In large-scale environments with numerous simultaneous logins, Windows Server may not match the performance power of Linux. Linux tends to excel in handling extensive user loads, while Windows Server remains user-friendly for various tasks.
The initial setup is quite straightforward and the deployment only takes about 30 minutes.
We handled the deployment in-house without the need for a consultant or integrator. We manage it ourselves, and our subscription with Microsoft includes support, so whenever we have questions or issues, we contact Microsoft, and they assist us.
I would recommend Windows Server to others but the choice depends on the specific technology and applications you plan to use. It is essential to consider compatibility and performance factors, as some applications may work better or be recommended for installation on Linux. Overall, I would rate Windows Server as an eight out of ten.
We are using this solution for all of our on-premise application servers. The latest version is Windows Server 2019, but we are using Windows Server 2016. We haven't felt the need to upgrade it.
It is easy to use, and its performance is good.
When it comes to virtualization, VMware is a bit more advanced in terms of security. Hyper-V does provide facilities, but it probably has to do a bit more work in terms of encryption. People will normally go for VMware because of the features that it has as a server, particularly the virtualization feature.
I have been using this solution since 2012.
It is stable.
It is scalable. In terms of its usage, the license that we currently have is good enough for us. We will increase its usage, but we don't need to purchase anything in the foreseeable future. We have enough.
We are also doing a PoC for moving the server that we have at each location to the cloud. After that is done, we will look at the cost and think about migrating to the cloud.
Its initial setup is very straightforward. The duration depends on how big the installation is in terms of the database and the domain you want to use. It can vary from about an hour to a couple of hours with updates, etc. It could be anywhere from 60 minutes to 3 hours.
All of our people are adept at handling its installation.
I would recommend this solution to others. I would rate Windows Server an eight out of ten.
We use it to implement and configure Active Directory environments for organizations. Projects can be related to running WS systems as well as implementing and performing System Center Configuration Manager, assisting the OM, Operation Manager, and monitoring.
The biggest and the most important services used in most of the organizations in the world is the Active Directory. The policy management feature is a great option for managing different policies in the domain environment.
Also, integration with other Microsoft solutions like Exchange and System Center Configuration Manager has the great ability to manage all of the different features on system support, like upgrading, securing, and troubleshooting different Windows systems for clients.
I think integration with Linux operating systems would be a great idea, as well as focusing on the simplicity of running containers in the Linux environments. I think this would be a requirement for the next generation of applications running in .NET and Microsoft programming languages.
Microsoft should expand to integrate the Windows Server with Azure and Linux distribution to provide a simple container environment for running dockerized applications.
I've been using it for around 10 years.
It is scalable. We currently have around 30 engineers using the Windows Server, but we hope to increase this number.
The initial setup is very simple.
I implemented it myself.
One of the problems with Microsoft is the price of licensing, and volume licensing for educational systems is a great option to bequeath licensing for small businesses.
On a scale from one to ten, I would rate it at nine.
For authentication and identity management, without a doubt, I would suggest using the Active Directory with Microsoft Windows Servers.
I primarily use the solution for college assignments.
We are using it just to learn how to configure all the options that Windows Server provides for the active directory and basically all the necessary configurations. It's for enterprise infrastructure, so to speak. We are mainly focusing on group policy and remote authentication, the main controller, and all the functionalities that a Windows server provides through the access directory.
The solution, in general, is quite straightforward. A beginner could probably use it with ease. It's always more or less simple to understand how this works.
Configuring a group policy has shown to be not very straightforward. For example, one of our assignments was to create a GPO that should block any user of opening and/or downloading an MP3/WAV file, and the same for video files. It was very confusing to find a solution that would do just that, we had to test different approches, or ven combining policies to achieve something that resambles what was asked to do. The default template in the File Server Resouce Manager isn't enough.
I've only been using the solution for about two months or so. It's relatively new to me.
The solution is quite stable. It doesn't have bugs or glitches, nor does it crash. It's reliable.
The solution is scalable. A company shouldn't have any troubles expanding it if they need to.
There may be 50 or 60 users on the solution currently. They're all students.
I'm not sure if I will continue using the solution of expanding usage in the future.
We've never really reached out to technical support. Typically, we'll look to the internet to search for answers. We'll google and find what we need.
I didn't previously use a different solution.
The solution is not too complex. It's quite simple to install the components, and not very difficult to configure for the most part. We're just to start using it, and it's not so complex so far. Still, it has a learning curve. You have to get to know some basic concepts before you can really understand what you're configuring. Otherwise, you get a little bit lost.
The installation itself only takes about ten minutes or so. It's rather quick. You don't really need to deploy it, per se, as it's on a virtual machine. It's not a professional environment. Of course, it would probably take longer if you have to configure all of the necessary requirements for professional applications.
My colleagues and I handled the installation as a group.
I'm not really a customer. I'm just a student learning the ins and outs of the product itself.
We are using in virtual machines the Windows Server 2019.
I'd recommend this solution. It's quite complete. For a company that wants all the necessary components to administer their infrastructure and so forth, it's quite good.
Overall, I would rate the solution eight out of ten. If they offered better documentation that wasn't as dated I might rate it higher.