The decision to upgrade to server 2012 isn't an easy one. But here are six reasons you might want to make it a priority:
VDI extends internal infrastructure services to remote workers by provisioning low-latency virtualized workspaces. With Server 2008 and below, support for USB redirection was limited and performance significantly degraded for users that were assigned to pooled virtual machines, since most if not all locally saved preferences and settings were lost on logout due to the static nature of the pooled image.
Display rendering was also performed by the GPU physically installed on the VDI server, which also impacted performance. With Server 2012, these disadvantages are eliminated, which results in a speedier VDI performance. User preferences are more easily made persistent. RemoteFX, with its virtualized display adapter, achieves much higher rendering performance, and USB device output is redirected seamlessly to the client without the need for custom drivers.
Extending asset life
Microsoft revisited some common management challenges with a series of useful, built-in solutions for Server 2012. IP Address management (IPAM) is a new feature of Server 2012 that addresses not only IP management but IP discovery and auditing, DNS, and DHCP even if these services do not sit on the server. Also new to Server 2012 is data de-duplication and Server Message Blocks, which is now a true SAN protocol that achieves 6 GB per second. Deploying Server 2012 might lower your footprint, and at the very least it won't mean new servers.
Automation and scripting
Powershell was always capable of managing many aspects of Windows Server, but it is now a major emphasis. Server 2012 focuses on the use of commandlets, which increased from around 230 in Server 2008 R2 to over 2,300. Couple this enhanced automation framework with Microsoft's increased emphasis on centralized management, and the upgrade to Server 2012 starts to make a lot of sense from a scripted management perspective alone.
NTFS isn't good enough
Server 2012 addresses concerns about limitations associated with NTFS with the new file system aptly named Resilient File System (ReFS). If file system limitations are preventing you from upgrading, ReFS is completely backward compatible so the new features won't break a file migration that started on an NTFS structure. When an integrity check is desired, CHKDSK is now dual-phased and takes significantly less time to complete even though using it isn't typically necessary anymore.
The new file system has increased reliability with the use of B+ trees; volumes can expand up to 1 Yottabyte; individual files can grow up to 16 Exabytes; independently-stored checksums are built-in; and ReFS leverages something called integrity streams, which facilitate a new layer of resiliency. This area could be a subject unto itself, but suffice it to say, Windows-based file servers can be worthy contenders where enterprise data is concerned.
Disk and storage management
Disk management received a major overhaul in Server 2012. Storage spaces and pools provide different types of disk abstractions that make storage management easier for admins. And they represent now-native storage concepts that have been previously achieved only with third-party plug-ins. This development is huge for the Windows world and with a lessened dependence on third-party plug-ins, the cost of upgrading almost pays for itself on this point alone.
There are a host of smaller but possibly very important features that might make the decision to upgrade easier. Hyper-V replicas, shared nothing live migrations, Dynamic Access Control, and Direct Access are all examples of specialized technologies new to Server 2012.
While they may not be particularly applicable to smaller IT shops, quite commonly they are of eminent concern to enterprise-class infrastructures. If your organization has special security or operational requirements, or has an immediate use case for ReFS, data de-duplication, and even the ability to install Server 2012 Core and add a GUI later, one or several of these features could be exactly what justifies an upgrade.
Like everything in IT, Server 2012 obviously isn't appropriate for every situation and every solution. So upgrading doesn't make sense if your priorities and requirements just don't line up. With all things Microsoft, upgrading will become necessary eventually to keep support. But in the meantime, take the time to look closely at both your business and the OS and deploy if and when it truly makes sense.