- Buy windows server 2012 r2 standard upgrade install#
- Buy windows server 2012 r2 standard upgrade update#
This issue can be easily fixed by uninstalling the role, rebooting your server, and reinstalling the server. The generic error message received will usually be “MMC could not create the snap-in”. This has happened to me on occasion for the File Server Resource Manager MMC snap-in, and the Network Policy Server MMC snap-in (Figure 1). In some unexplained cases, certain MMC snap-ins will be broken post-upgrade. I learned that one the hard way on my first upgrade. The only known resolution is to format the drive and reinstall the operating system from scratch. If you do not, your WSUS installation will be completely broken afterwards and there is no known fix from Microsoft.
Buy windows server 2012 r2 standard upgrade update#
If the server you’re planning on doing an in-place upgrade directly to Windows Server 2012 R2, and the server is currently running the WSUS (Windows Server Update Service) role version 3.2 (Windows 2008 R2 and earlier), you MUST uninstall the WSUS role before upgrading. However, if you believe your server is still a good candidate for an in-place upgrade, here are some important things you should know about BEFORE doing an in-place upgrade in hopes of making your life as an IT administrator easier. …then I’d strongly advise against doing an in-place server upgrade on that server.
![buy windows server 2012 r2 standard upgrade buy windows server 2012 r2 standard upgrade](https://cwrak.net/wp-content/uploads/2018/02/window2.png)
![buy windows server 2012 r2 standard upgrade buy windows server 2012 r2 standard upgrade](https://i0.wp.com/www.ntweekly.com/wp-content/uploads/2010/08/082010_0601_QuestionHow4.png)
So far, the vast majority of them are completed with little headache and virtually no post-troubleshooting required. I’ve probably done about 20 of these in-place upgrades over the last year or two.
![buy windows server 2012 r2 standard upgrade buy windows server 2012 r2 standard upgrade](https://i.ytimg.com/vi/QenswufMqnY/maxresdefault.jpg)
Today, we’re going to focus on some of the pesky things that might cause you some grief when doing an in-place upgrade from Windows 2008 R2 to Windows 2012 R2. The alternative of creating a new server and migrating over the applications/data, is typically going to take FAR longer to accomplish (but in some cases, may still be the wisest choice!).
Buy windows server 2012 r2 standard upgrade install#
Perhaps the biggest advantage of doing an in-place server upgrade is that most upgrades can be completed in a mere two hours or less which includes not only the upgrade itself but also the time necessary to install all applicable Windows Updates, post-upgrade. While some administrators are adamant that proper server upgrades –must- be done this way, or that way, truthfully, both approaches come with their own share of advantages and disadvantages.