Sign in
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Reviews from AWS customer

4 AWS reviews

External reviews

38 reviews
from

External reviews are not included in the AWS star rating for the product.


3-star reviews ( Show all reviews )

    Harry Murdani

Provides good support, and is quite reliable but has high costs

  • November 08, 2024
  • Review provided by PeerSpot

What is our primary use case?

I use Windows Server primarily as an Infra Server and Active Directory domain controller. It acts as a domain controller, chain email server, application server, and file server.

How has it helped my organization?

Windows Server offers good operational benefits. It is quite sustained, provides good support, and is quite reliable.

What is most valuable?

All features are required for managing my data center. The domain controller is for Active Directory, and if you need to include an email server, you can't ask about features individually since all features are necessary.

What needs improvement?

The price is very expensive. It would be excellent if Microsoft could reduce the price. Also, the support team is getting worse in terms of expertise. No cost-saving benefits have been observed.

For how long have I used the solution?

I have been working with Windows Server for almost 20 years.

What do I think about the stability of the solution?

For stability, I rate Windows Server seven out of ten.

What do I think about the scalability of the solution?

Scalability is rated eight out of ten.

How are customer service and support?

The customer support team is not satisfactory. Their expertise has diminished. I rate them two out of ten.

How would you rate customer service and support?

Negative

How was the initial setup?

The setup is easy. I would rate it a nine out of ten. Deployment takes about five minutes per server.

What about the implementation team?

You need at least a team of two people for deployment to manage and support, especially when one person is unavailable.

What was our ROI?

There is no cost saving. I have not observed any cost-saving benefits.

What's my experience with pricing, setup cost, and licensing?

The price of Windows Server is very expensive. On a scale of one to ten, with ten being the most expensive, I rate it ten out of ten.

What other advice do I have?

It's better to have your own internal server capabilities. Do not rely on the support; you need your team to manage and support the server.

I'd rate the solution seven out of ten.


    Parimal Sardar

Helpful to share authentication, user access, and rollback but needs improvement in integration features

  • March 12, 2024
  • Review provided by PeerSpot

What is our primary use case?

Even though there were changes in my job role or company, I continued to use Windows Server.

What needs improvement?

In recent times, improvements are required since everything is going to be very granular. If you give access to a particular group or particular user in a particular product line and if you want someone to be a part of that group which has different rights from another team, like an SME, who has more rights compared to an ordinary person, and if a new person or novice person comes in, he will have lesser rights.

Nowadays, everybody wants a user-friendly dashboard and interface. People don't want to know about complex commands and want everything to be available in just a few clicks on the dashboard, where they can see the top trends, what commands are being used, how many logins, and other such related information. The integration process should be smooth if I have Microsoft Active Directory deployed on an on-premises model and I want to connect it to a Microsoft Active Directory on the cloud. Even if you are involved in complex things on the back end, from the front end, the tool should be made easier for users to understand so that they can identify the credentials or keys they use.

If you want to integrate or connect with multiple integration points or ecosystems, then such a process should be something that is easily doable for users. Whether the tool is connected to an API, on-premises model, or cloud, it should be made a process that is easy for users.

For how long have I used the solution?

I have experience with Windows Server. I have used Windows 95, Windows 98, Windows 2000, and Windows NT.

What do I think about the stability of the solution?

When it comes to volume, the performance decreases. I have seen a lot of companies claim that their tools can support a certain amount of capacity, but when we, as users, come near the prescribed capacity limit and are unable to use the product, the company claims that the capacity limit details were given to them by their engineering team. I feel that the engineering team hardly tested the product at the required level to see if the product could support it when the actual production load came to the level they figured out earlier. If a particular product claims to be able to support 1,000 units or users, I see the performance decreasing after the tool is used by 800 or 900 users. If you go for a storage tool, the company claims that its product will support one petabyte, but when users actually have that much capacity, they realize that the product doesn't offer much support.

What do I think about the scalability of the solution?

Around seven people in my company use the product.

How are customer service and support?

My company uses the solution's technical support if we are not able to solve a problem related to the product.

Which solution did I use previously and why did I switch?

Since migrating to the product from another solution, my company faces challenges in using complex security support when there is a high volume.

How was the initial setup?

If an architecture is complex, the setup phase takes time. If you need to integrate multiple touchpoints, then the setup process takes time.

What about the implementation team?

The deployment process can be done with the help of our company's in-house team.

What other advice do I have?

Speaking about how the product enhances our company's data management capabilities, I would say that based on my long experience with the product, I feel that presently, the solution is totally different. Nowadays, users get Version 21H2 (OS build 22000)​​ Windows 11, which is totally different from its past offerings. Previously, Windows Server fell under a totally different domain or technology, but currently, it's a totally different tool.

I would say that I have stopped using the product at an individual level and have started working with the team in my company that takes care of its deployment and manages the virtual environments.

The tool has been beneficial for our company's IT infrastructure since I feel that Windows is preferred by many for the domain controller and for using SSO authentication along with Active Directory services. With SSO authentication and Active Directory services, users' contact domains and everything are available. It can help users benefit from the tool while sharing authentication, user access, rollback, and other areas.

In terms of security features, users need more in areas like authentication and location.

There is no multi-vendor support to help deal with the area of integration.

I rate the product a seven out of ten.


    SHUBHAM BHINGARDE

Has an easy-to-use graphical user interface (GUI), but its deployment is a bit difficult

  • February 08, 2024
  • Review provided by PeerSpot

What is our primary use case?

We use Windows Server for Active Directory (AD). We use the solution to manage user data and access through Active Directory. We use Windows Server to host and configure the mail servers.

What is most valuable?

Since Windows Server has a graphical user interface (GUI), it is easy to use and implement the services that we are using.

What needs improvement?

Compared to Linux, the solution is a bit difficult to deploy. The solution should have a faster deployment.

For how long have I used the solution?

I have been using Windows Server for more than five to six years.

What do I think about the stability of the solution?

The solution has good stability.

I rate the solution an eight out of ten for stability.

What do I think about the scalability of the solution?

Around 50 employees are using the solution in our organization. The solution is used extensively in our organization, and we have plans to increase the usage.

How was the initial setup?

The solution’s initial setup is straightforward.

What about the implementation team?

The solution's installation process is a bit lengthy and hectic. It took more time than the Linux operating system used to take. Our in-house team follows the documentation part, and we do the deployment ourselves from scratch.

What's my experience with pricing, setup cost, and licensing?

We use only the license versions of Windows Server.

What other advice do I have?

We currently have our own data center where we host the services. Since we are a government-based R&D organization, we do not trust any cloud platform services like Azure, Google, and AWS.

We had to configure all the services and features that were available. We had to look for additional plugins that we could create and integrate for the security of our organization. I would recommend Windows Server for an organization dependent on the GUI part. Otherwise, I recommend using Linux servers.

The hardware requirement for Windows Server is very large compared to Linux. For that, we need to use or deploy the maximum hardware that is necessary.

Overall, I rate the solution a seven out of ten.

Which deployment model are you using for this solution?

On-premises


    Abey Varghese

Good for tasks that are closely related to Windows environments

  • January 31, 2024
  • Review provided by PeerSpot

What is our primary use case?

We mainly worked with Windows Server 2003, 2008, 2012, and 2016 as they were the go-to operating systems for applications like Excel Server and various other software. We occasionally used Linux servers, especially for databases and specific applications, but most of our work was on Windows servers.

What is most valuable?

When we deploy this operating system, we're primarily focused on managing virtual environments. There are different parts like the directory, data storage, and CPU usage which are really useful. We also compare it to other parts like group policy, all of which are related to users. Currently, I find that users are very involved when it comes to these applications or servers on the two other links.

What needs improvement?

I believe that Windows Server can be somewhat vulnerable compared to other options, but its security can be improved. I also think that the setup process can be somewhat complex, depending on the applications involved.

Regarding the security features of Windows Server, while it offers some built-in security measures, it's not sufficient to solely rely on them. Additional external devices such as firewalls may be needed for comprehensive protection. Deploying antivirus and firewall software on the server is advisable, but having an external firewall adds an extra layer of security.

When migrating to Windows Server from previous versions or other platforms, noticeable improvements were observed, particularly in the utilization of graphical interfaces. Windows offers robust graphical guidance, especially compared to Linux or other systems like Acronis, making it easier to navigate and manage various functionalities.

For how long have I used the solution?

I have used Windows Server for a couple of months.

How are customer service and support?

I found it somewhat lacking in responsiveness at times.

How was the initial setup?


Maintenance also requires a team to handle day-to-day activities.When it comes to deploying Windows Server for managing virtual environments, we use VMware. Deployment can require involvement from managers, administrators, and technicians, and it may involve consulting external experts.
When it comes to deploying Windows Server, there's a policy in place for CR (change request) management. Typically, consulting with experts is necessary to design the system, taking into account factors like the number of users, required robustness, and specific functionalities such as messaging or email systems.

What other advice do I have?

On a scale of 1 to 10, I rate Windows Server around a 5 or 6.

When it comes to recommending Windows Server to others, it depends on the critical applications being used. If you're installing an Oracle database, for example, I wouldn't recommend Windows Server. In such cases, Linux or similar platforms might be more suitable. However, for tasks closely related to Windows environments, like utilizing Microsoft products extensively, Windows Server could be a faster and more compatible option, especially when it comes to firewall capabilities.


    WilyonTjahyadi

Effective but lacks scalability in certain aspects

  • January 19, 2024
  • Review provided by PeerSpot

What is most valuable?

What I like about Windows Server is that it is an effective and useful solution for my needs.

What needs improvement?

Windows Server could improve its integration with cloud and hybrid environments to better adapt to modern computing needs.

For how long have I used the solution?

I have been using Windows Server for over 20 years.

What do I think about the stability of the solution?

I would rate the stability of the solution as a six out of ten.

What do I think about the scalability of the solution?

I would rate the scalability of Windows Server at five out of ten. It is okay for basic upgrades, but it lacks the flexibility needed for more advanced scaling, especially in cloud or hybrid environments. It is not quite ready for those kinds of setups yet.

How are customer service and support?

I would rate technical support directly from Windows at around three out of ten—it is not the best. However, if you go through a partner who sells or supports Windows, the support could be around seven out of ten, because Windows relies on these partners for assistance.

How would you rate customer service and support?

Neutral

How was the initial setup?

I would rate the easiness of the initial setup as a seven out of ten. Deployment took a few hours.

What's my experience with pricing, setup cost, and licensing?

I would rate the costliness of Windows Server as an eight out of ten. It is quite expensive.

What other advice do I have?

Overall, I would rate Windows Server as a seven out of ten.


    Aqib Khan

The product is secure, and it performs well, but the stability could be improved

  • January 15, 2024
  • Review provided by PeerSpot

What is our primary use case?

We use the solution for all the applications and Active Directory. We use it for enterprise management. We have different departments.

How has it helped my organization?

The product is secure.

What is most valuable?

The product’s performance is good. We have a good infrastructure.

What needs improvement?

The stability could be improved.

For how long have I used the solution?

I have been using the solution for eight to ten years. I am using the latest version.

What do I think about the stability of the solution?

The tool is stable. I rate the stability an eight out of ten.

What do I think about the scalability of the solution?

We have more than 5000 users. The usage keeps increasing in our organization.

How are customer service and support?

Whenever we face any issue, we contact our Windows team, and they improve it. The technical support is fine.

How was the initial setup?

The initial setup is straightforward.

What about the implementation team?

The deployment was done in-house. We have a big team to deploy and maintain the product, including project and system managers.

What other advice do I have?

I will recommend the tool to others. Overall, I rate the solution a seven or eight out of ten.

Which deployment model are you using for this solution?

On-premises


    Virimai Mare

Easy to setup, stable and caters to my wide range of use cases but lacks user-friendly interface

  • January 15, 2024
  • Review provided by PeerSpot

What is our primary use case?

It's used for a variety of things, like Active Directory, DNS, cloud shares, and application hosting. We also have some third-party applications running on it and web services.

What needs improvement?

It would be nice if it was more user-friendly, especially for migrating applications.

For how long have I used the solution?

I've been working with Microsoft for about 12 years now, since December 2004.

What do I think about the stability of the solution?

It's quite stable, probably an eight out of ten. It really depends on the specific business needs and applications running on it.

What do I think about the scalability of the solution?

It can be scalable to a certain extent, but it depends on the resources you have available and the applications you're running. We have around a thousand end users using this solution.

Which solution did I use previously and why did I switch?

I've worked with Unix and Linux before, but it was a long time ago.

How was the initial setup?

The initial setup is quite easy for me, especially since I've been using it for so long. It usually takes just a few steps, depending on whether it's deployed in the cloud or on-premises.

What about the implementation team?

We handle it in-house, no need for external help.

What was our ROI?

We've seen value in Windows Server because the systems work smoothly without any problems. And the additional benefit is the support we receive.

What other advice do I have?

My main advice is to understand the business first. Then, see if the solution will work on that platform. Also, check which applications it supports. If they're using data and Microsoft, in some cases, we use applications verified by Microsoft. You can be sure they're compatible with Windows and find support from both ends. So, understand the business in terms of its goals, turnaround time, risk factors, and skill requirements. Consider if they have enough skilled people to support it, both for daily use and when issues arise. You need to know these things before making a decision.

Not every time is Microsoft the right choice. Some systems or platforms they want to run may not be supported by Microsoft. So, it's crucial to understand the business requirements first; then you know which platform or solution works best for you.

Overall, I would rate the solution a seven out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud


    WaleedKhan

Provides ease of access to databases, but its firewall services need improvement

  • October 25, 2023
  • Review provided by PeerSpot

What is our primary use case?

We use the product to manage databases for various projects.

What is most valuable?

The product offers in-house servers. It helps us update them and check any technical issues easily.

What needs improvement?

The product's user interface upgrades and firewall services need improvement.

For how long have I used the solution?

We have been using Windows Server for seven to eight years.

What do I think about the stability of the solution?

The platform provides ease of access to databases in terms of migration.

What do I think about the scalability of the solution?

It is a scalable product. We have more than 200 Windows Server users in our organization. We might increase usage in some of our departments, like support administration, in case the business expands.

How are customer service and support?

We have an in-house technical support team.

How was the initial setup?

The initial setup is easy if you have a basic knowledge of the process. We can deploy it on-premise or on the cloud, depending on the project requirements.

What's my experience with pricing, setup cost, and licensing?

There could be a one-time cost for Windows Server and not every month. It is a huge amount for the companies to pay yearly.

What other advice do I have?

I recommend Windows Server to users working on multiple projects and have an in-house team with enough resources. I rate it a seven out of ten.


    Sven Missorten

Transparent and easy-to-learn, but the product is not stable

  • May 22, 2023
  • Review provided by PeerSpot

What is our primary use case?

We use the solution for mass storage and application storage.

What is most valuable?

DFS is the most valuable feature of the product. The product is very transparent. Any changes to the underlying file servers are not visible to users. It is a huge benefit for us. 

The GUI is familiar. Anyone who doesn't know how to use a file server can be taught to use the product in a few minutes.

What needs improvement?

The solution should improve its stability. After some updates, one of the KBs faced issues while booting. On boot, it started boot looping randomly.

The solution is very rigid. Whenever we want to make changes that are slightly out of the ordinary, we have to do them manually.

For how long have I used the solution?

I have been using the solution for four and a half years.

What do I think about the scalability of the solution?

The solution is definitely scalable. Around 1,500 people are currently using the solution in our organization.

What about the implementation team?

It is quite easy to maintain the product. We have deployed the solution across the whole company.

What other advice do I have?

I have used all the versions from 2003 to 2022. You can change the host and IPs and switch on the whole configuration. The users do not notice anything as long as DFS is active and the file system is the same. The product is a good choice for small-scale environments. Overall, I rate the product a seven out of ten.

Which deployment model are you using for this solution?

On-premises


    ferricoxide

Not the "homerun" I was hoping for.

  • December 03, 2021
  • Review from a verified AWS customer

Organization is wanting to use Inspector to validate that launched EC2s are adequately hardened. Further, they wanted to evaluate against Inspector's CIS benchmarks. Figured, "if I start from an official AMI, it ought to be a homerun to get a clean output from Inspector". Launch an EC2 from the AMI. Discover that the AMI is missing the AWS agent. Correct this gap. Run Inspector. Wait for report. Report comes back with nearly 40 "High" findings (nearly 30 if you ignore the DC-only and NG-only findings).

Notice, "oh, *this* AMI is built using the 1.3.0.2 benchmarks and Inspector is using the 1.1.0 benchmarks. Go back to AWSMP and click on the "view older versions" link under the AMI. Am simply taken back to the AMI's normal information page with no indication of availability of back-rev AMIs that I might need.

Report back issues to my organization. They note, "but those findings are all HIGH findings".

Not the "homerun" I was hoping for.


showing 1 - 10