4 out of 5.0, Reviewed Sep 23, 2016
A Certified staff has been difficult to source.
train your staff before taking on a new platform DEV /OPs approach
have in-house expertise prior to launch
you must purchase premeir services intially
2 out of 5.0, Reviewed Aug 3, 2016
To many vulnerabilities.
It is consistently being updated against hack attacks.
Develop a stronger OS against vulnerabilities.
Use a different virtualization strategy.
5 out of 5.0, Reviewed Jul 14, 2016
Windows Server 2012 R2 has been the easiest, fastest, and most stable Windows Server to date.
Install the desktop experience. Even though this is a server, the desktop experience enables disk cleanup which allows significant space savings.
It's Windows and I do not need to navigate a complex CLI for most tasks!
With so many patches and updates, some directories get very bloated (WinSxS).
Wait for R2. The last two iterations of Windows Server have quickly been followed up with an R2 version. The R2 version has been superior to the original in every way. Watiing for R2 might be worth it.
2 out of 5.0, Reviewed Jul 14, 2016
Not as satisfy as VMware Virtualization. Hyper-V is unstable but has to adopt it due to mgmt.
If cost is not a factor, VMware is a better solution compare to Hyper-V
Make Hyper-V more stable and simplier to manage.
We would stick with VMware if we could.
3 out of 5.0, Reviewed Jun 21, 2016
Easy to implement and user-friendly.
If you are willing to spend extra money on easy infrastructure upgrade, hyper-v is the way to go.
could have implemented for win8 as well.
5 out of 5.0, Reviewed Jun 19, 2016
We had a good experience moving to Hyper-V 3 on Windows Server 2012 R2.
Go on and virtualize with Hyper-V. If you got a good hardware and storage, Virtualization is going to be a great experience.
Easy to build.
Issues with SCVMM.
It's better to wait till first roll-up after the initial launch. That would get most of the bugs fixed.
5 out of 5.0, Reviewed Jun 16, 2016
Top class vendor
5 out of 5.0, Reviewed Jun 9, 2016
Ease of integrating legacy apps into the newer infrastructure without issues.
Do not mirror the old environment. Find the pain points, and learn from the lessons of the older.
Not to rename new environment to match the old environment names once side-by-side testing was done.
4 out of 5.0, Reviewed May 27, 2016
Features in Windows 2012 R2 Server, allows capability for bridging gaps between legacy and target state architectures as it relates to authentication and authorization strategies. The ability to leverage Microsoft ADFS3.0 has opened up the ability to modernize web SSO at a local level that can be standardized across the Enterprise. There is a delicate balance between security and usability when it comes to supporting legacy applications as well as having the ability to use the same identity for SaaS/PaaS solutions that are off-premise. Having a local identity provider that can issue various tokens is bridging the gap for our organization and enables us to support legacy systems while creating modern web applications with modern identity methods.
Focus on realistic target architectures, and leverage readily available capabilities to facilitate achieving that target state.
Ease of use.
Multiforest environments without trust can be cumbersome when adding a XenApp capability.
Other features such as lack of integrated multi-forest directory services would be a nice addition without having to purchase that capability.
Our organization would have done this 24 months ago.
4 out of 5.0, Reviewed May 12, 2016
No problem since we start using Hyper-V and Microsoft has been adding new features with each version.
Virtualization opens the door to other opportunities.
Easy to use. It comes with Windows 2012.
There are a few functions that are only on VMware but Microsoft is catching fast.
No, we would have still selected Hyper-V.
It does what it suppose to do. It is catching up with VMware.
Easy to deploy, particularly with each major version of Windows.