Inplace upgread Windows 2008 R2 to Windows 2012

Hello,
I am  testing inplace upgrade from Windows 2008 R2 to Windows 2012 R2. My test server is Windows 2008 R2 Enterprise, Evaluation and is a domain controller. I tried to perform an inplace upgrade, however it failed. The compatibility report says that
Windows Server 2008 R2 Enterprise cannot be upgraded to Windows Server 2012 R2 Datacenter Evaluation (Server with GUI).
I also update the schema first. It went fain and it was completed without error.
Thank you.

Hi,
Based on my experience, it is not supported to upgrade
from a Windows server evaluation version to another Windows server evaluation version. If you want to use Windows server 2012 R2 Datacenter evaluation version, you need to delete the previous operate system and perform a clean installation. Or
you can convert the evaluation version of Windows Server 2008 R2 to a full retail version and then upgrade it to Windows server 2012 R2 Datacenter version.
For more detailed information, please refer to the link below:
Upgrade Options for Windows Server 2012 R2
Best regards,
Susie

Similar Messages

  • SharePoint 2013 Server OS upgrade from Windows 2008 R2 to Windows 2012 R2

    Is it possible to have SharePoint 2013 farm to have mixed version of OS (Windows 2008 R2 and Windows 2012 R2). 
    We have a request to upgrade our farm servers from WIN 2008 R2 to Win 2012 R2. We have 5 servers in farm - 
    2 App servers - running with Central Admin, Service Applications, User Profile
    3 Web Front End Servers- running web application, search and workflow manager
    the database layer is separate on sql 2012 R2
    We want to upgrade OS from windows 2008 R2 to windows 2012 R2 and SQL to SQL 2014. 
    What will be right approach to do OS upgrade in above scenario to minimize the impact of downtime.
    May be add windows 2012 based servers in farm one by one and replace the windows 2008 R2 based servers from server.
    Regards,
    Kunal Abrol

    Its possible, but I wouldn't recommend it.  The problem is that you can only install SharePoint 20103 on Windows Server 2012 r2 using the slipstreamed SP1 version.  I assume that you used the regular version to install on you Server 2008 r2 versions.
     Even if you upgrade those servers to SP1 there are some minor differences in the builds between slipstreamed SP1 and upgraded SP1.  So although it will work it isn't recommended.
    Also, you should be aware the upgrade of inplace SharePoint servers running Windows 2008 r2 to Windows 2012 r2 is not supported.  
    To upgrade to server 2012 you'll need to add 2012 servers to your environment using the slipstreamed version os SharePoint and then remove the old server 2008 r2 servers as soon as possible.  For the period of the upgrade you should be able to get away
    with running the farm in a mixed state.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Error while deploying Windows 2008 R2 using SCCM 2012 R2

    I am trying to deploy Window 2008 R2 image (captured from a  reference machine) using SCCM 2012 R2. I have integrated MDT 2013 with SCCM 2012 R2 and created an MDT task sequence. During deployment, towards the end of Applying image.wim, it gives me
    an error that task sequence failed with the error code 0x80070002. And then the system reboots. After reboot, I am able to login to the Windows Server. It seems to work fine, but there are no applications etc installed. Also the _SMSTS log folder is still
    present in  the C drive. And in the smsts.log file, i can see errors like failed to copy unattend.xml file. Please help me.

    Hi,
    Error code 0x80070002, it means the system cannot find file specified.
    For more information, please review the link below:
    Task Sequence Failed with the Error Code 0x80070002
    http://prajwaldesai.com/task-sequence-failed-error-code-0x80070002/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Migration of DNS from Windows 2008 R2 to Windows 2012

    Hello,
    We have a pair of Windows 2008 R2 servers running authoritative DNS services (they are not AD controllers, neither used as resolvers). There are ~20 domains + 10 DNSSEC domains hosted on those servers. We're considering to migrate them to Windows 2012
    servers and retain IP addresses.
    I'd greatly appreciate if somebody could advise the basic steps for such migration (particularly the DNSSEC part).
    Many thanks.

    Hi,
    It worked for me with a test zone but my example only had a single A record. You should test this first by adding the zone and testing resolution on the 2012 server before deleting it from the 2003 server.
    The bug for secondary zones that you describe in Server 2008 is news to me. However, 2012 and 2012 R2 has many advantages over 2008 R2 for DNSSEC signed zones so I would recommend you migrate even if you weren't having problems on 2008 R2.
    If you've been following the thread you mentioned above, you know that I've been doing a lot of testing with signed zones being updated on secondary servers. The signed zone is *always* updated on a secondary server but if the change on the primary was only
    a signature refresh then as of right now there is still a bug where the newest RRSIGs are not transferred to the secondary server. This happens because the zone transfer occurs just before the new RRSIG is generated on the primary. This causes it to be left
    behind on the primary server unless there is another zone transfer afterward. Note that a zone transfer still happens, it just happens too soon. The zone transfer that happens is an incremental zone transfer.
    If the previous RRSIG expires before another zone transfer occurs then the zone can have validation problems on the secondary. There is a hotfix for this that will be distributed soon. I am checking now on the date.
    If you increment the serial # on the primary, the secondary should get a full zone transfer.
    -Greg

  • In-place upgrade from windows 2008 R2 to windows 2012

    Hi all,
    we are currently running SAP ERP EHP7 (Netweaver 7.40 ) on Windows 2008 R2 server, MS SQL 2012 database.
    Is it possible to do in-place upgrade to Windows Server 2012?
    We want to do upgrade without buying new hardware  and perform system copy.
    Regards

    Hi,
    the only note where we discussed our findings about in-place upgrades of the Windows operating system is SAP Note 1494740.
    Even though the upgrade to Windows Server 2012 is not discussed explicitly, the note is also valid for Windows Server 2012.
    The only thing you have to take care is: upgrade your system components (database, other 3rd party software) to versions supported on Windows Server 2012 before you are performing the in-place upgrade.
    Regards
    Peter

  • Domain Controller upgrade windows 2008 r2 to windows 2012

    I currently have 3 windows 2008 r2 domain controllers. 1 physical and 2 virtual. I am looking to see what the best upgrade path would be. the physical is the primary and has dhcp and dns services
    Stonecold31666

    See this,
    http://social.technet.microsoft.com/wiki/contents/articles/16797.upgrade-to-active-directory-2012.aspx
    Regards
    Biswajit Biswas
    My
    Blogs|TechnetWiki
    Ninja
    Best regards Biswajit Biswas Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin

  • VM windows 2008 Cluster on Hyperv 2012 Server FC Disk error after Live Migration of the active VM Cluster Node

    Deployed a 2 nodes Windows 2008 R2 SP1 Failover Cluster on a HyperV 2012 Server cluster deployed on IBM HS23 blade.
    Disk susbsystem is IBM Storwize V7000. MPIO driver installed plus IBM DDSM.
    Lun presented to the VM are connected with Virtual FC Adapter and everything works fine in the cluster until we start a live migration of the VM which hold the cluster disks online.
    After migration complete positively, at the moment the MPIO of the migrated VM goes crazy with a lot of errors (source: mpio eventID 16 ) and warnings (source: mpio EventID: 17) in the system event log. After that the disks becomes unavailable.
    Consequently everything hangs until power off the migrated vm, so the services on the cluster switchs on the second node.
    I try to set the registry key HKLM\CurrentControlSet\Services\Disk\TimeOutValue to 190 as i found on various articles but nothing seems to change....
    Any idea?
    vannig

    Hello,
    I've just been through the IBM interoperability matrix and came across this statement:
    Hyper-V on x64 based systems is supported with the following guest OS: Windows 2003 32bit, Windows 2003 64bit, Windows 2008 32bit, Windows 2008 64bit.
    Clustering of guest OS is not supported at this time. When using Emulex HBAs with Hyper-V please select the settings mentioned in the Host Attachment section of SVC Info Center
    http://publib.boulder.ibm.com/infocenter/svc/ic/index.jsp
    Thanks

  • How to Upgrade Service Manager 2012 SP1 with Windows 2008 R2 to SCSM 2012 R2 with Windows 2012 R2

    Hi,
    We are using Service Manager 2012 SP1 UR2 with Windows 2008 R2.
    I am planning to upgrade Service Manager to R2 with Windows 2012 R2. I found the steps to upgrade SCSM 2012 Sp1 to R2 but need assistance to upgrade with 2012 R2 OS.
    Please suggest how to achieve the above mentioned objective.
    Regards, Syed Fahad Ali

    Virtualization solves this problem handily, by allowing you to create a new server to run the new program on the same hardware. it also solves the related problem of moving off unsupported hardware without changing OS or application. VMware is my personal
    favorite, but Hyper-V, Xen, and VirtualBox all have similar capabilities.
    Compare the cost of work and confidence in success of a upgrade, where any of thousands or millions of uncontrolled settings could cause an issue, to the cost of work and confidence in success of installing a new OS instance and configuring a known state
    for the new environment.
    In short, upgrades should no longer be a thing. there are just too many ways they can go wrong, and it's far too easy to create a new OS with minimal expense and effort.

  • Upgrade from windows 2008 R2 to windows 2012 and Quorum

    Dear Sir.
    I am going to upgrade hyper-v cluster of 4 nodes 2008 r2 to windows 2012 hyper-v cluster.
    i am going to evict tow node and build new cluster.
    should I configure new quorum for new cluster or can i use the the quorum from old system ?
    thanks

    Hi,
    Base on my experience, you need create a new cluster when you choose migrate the cluster, so you need the new witness disk.
    The
     related article:
    Best practices for migration of cluster windows 2008 R2 / 2012 - As melhores Praticas para migrar um Cluster de Windows 2008 para Windows 2012
    http://blogs.technet.com/b/hugofe/archive/2012/12/06/best-practices-for-migration-of-cluster-windows-2008-r2-2012-as-melhores-praticas-para-migrar-um-cluster-de-windows-2008-para-windows-2012.aspx
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Moving farm from Windows 2008 R2 to Windows 2012 (R2?)

    I've been asked to move our current small SP2010 Server farm (WFE, App, and SQL) from Windows 2008 R2 servers to new Windows 2012 servers.
    Any limitations that would prevent this from happening? Any major differences? Installation through the GUI won't be a problem? Any benefits to tout? I've installed 2012 R2 on a HyperV but haven't messed around with it much beyond that.
    Thanks,
    Scott

    For SharePoint 2010, I would suggest sticking to 2008 R2. It is the most well tested operating system for SharePoint 2010. There may be some unknown gotchas that the community is unaware of with Server 2012 or 2012 R2.
    Otherwise, everything should 'just work' with SP2 media.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Windows 2008 Server and Windows 8 clients

    Hey Guys,
    I have had this problem for sometime now and really need a solution. I have Windows 2008 Enterprise Server running about 200+ terminal services clients. All Windows XP clients are fine, Windows 7 clients have issues when they get an updated version of
    remote desktop client(to solve the issue we simply rollback the update), Windows 8 clients cannot connect and use out remote app. The issue stems from the newer version of remote desktop client (on windows 7 and embedded in windows 8) cannot connect to our
    terminal server and generates an error and immediately disconnects. The error says "
    Your computer can't connect to the remote computer because an error occurred on the remote computer that you want
    to connect to
    So my questions are, how can i update my Windows 2008 Terminal server version to support these clients, or do u have migrate to Windows 2012? Or is there a solution to my current problem which will allow my client to connect and use the remoteapps?

    Hi,
    Thank you for posting in Windows Server Forum.
    Please follow the below steps and verify result.
    LAN manager authentication level settings (Local security policy->Local Policies->Security Options->Network Security: LAN Manager Authentication level). 
    Try to change it to "Send NTLMv2 response only" 
    Snap:
    If still face the issue please install this Hotfix.
    RDS client computer cannot connect to the RDS server by using a remote desktop connection in Windows
    http://support.microsoft.com/kb/2752618/
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Windows 2008 Server R2 Windows Explorer Refresh Issue

    I work on a Windows 2008 R2 server that I connect to through remote desktop. Recently the automatic refresh in Windows Explorer stopped working. If I create, delete, copy, move, rename etc., I do not see the changes unless I refresh (F5). I tried the three
    solutions below which was for Windows 7, but they have not fixed the problem. Can anyone please help me.
    http://www.julianevansblog.com/2011/06/windows-7-file-and-folder-refresh-problem.html
    Ray Pietrzak

    You can unmark no problem.
    You tried with 0x0 ? In my first post I did a error to write down 0x1. From there, if it does not work we will continue.
    They are other key too that might work;
    NoRemoteChangeNotify = 1 (DWORD) in the same location as thee other.
    and NoSimpleNetIDList = 1 (DWORD) from HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
    Thanks
    Regards, Philippe
    Don't forget to mark as answer or vote as
    helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
    Answer an interesting question ? Create a
    wiki article about it!

  • Restore Exchange 2007 SP3 to Windows 2008 R2 from Windows 2003

    Perhaps I'm being dense, but I had Exchange 2007 SP3 installed on a Windows 2003 Server, and I've used "setup /mode:recoverserver" to restore it to a Windows 2008 R2 server... how do I restore the databases which I backed up with the Windows backup tool
    on 2003?
    I installed KB974674, the restore tool onto the 2008 R2 server but when I try and restore the backup it comes up with "this feature is no longer supported".  Something I'm missing here?

    These things marked as answers are not answers.
    I have now thoroughly tested using setup /mode:recoverserver and it works fine going from Windows 2003 to Windows 2008 R2 with Exchange 2007 SP3, done several installations now without a problem.
    "Setup /m:RecoverServer cannot be used across operating systems. A server that was originally running Windows Server 2003 can be recovered only on Windows Server 2003, and a server that was originally running Windows Server 2008 can
    be recovered only on Windows Server 2008."
    This appears to be wrong, unless someone can tell me why it's right (I haven't tried moving Unified Messaging yet).  I've done it to 2008 R2 several times now and also in the other direction, from 2008 R2 to 2003, I can't find anything that didn't work
    afterward, although I haven't really thoroughly tested OWA yet, I admit (but it does appear to be working).
    I think that documentation is out-of-date as it doesn't mention R2 plus I think it was written before SP3 came out and that paragraph is just wrong.
    Basically how I do it is like this:
    Dismount databases from the 2003 server and copy the storage group folders to a network location or removable media.
    Install the Windows 2008 R2 server using the same machine account that was being used by the 2003 server.  Install the prerequisites needed for Exchange 2007 SP3 installation on 2008 R2 (note in addition to the IIS components and RPC over HTTP this
    also requires the AD tools in RSAT, which I haven't found mentioned in technical documentation).  Install the relevant windows updates.
    Install Exchange 2007 SP3 using setup /mode:recoverserver  Install the update rollup.
    Copy the storage groups into the relevant folders on the new server and mount them.  Migrate any relevant certificates (e.g. for ActiveSync).
    Obviously then check it all over with the diagnostic tools and check it with EXBPA.  The backups are obviously totally different, but really I think you should be using DPM anyway.
    To me that was pretty easy to do, to be honest.  About 1.5 on a scale of one to ten.  Basically install it, recover it, copy over some files and mount them.
    Seriously on a halfway decent server I've done it in under an hour.

  • Windows 2008 R2 SP1 Windows update not applicable

    HELP!!! We have 3 Windows 2008 R2 servers that were updated with SP1 back in March. Last month we noticed on our Retina audit that the three servers were missing several Windows critical patches that were released after SP1 was applied. WSUS did not report
    any missing patches for those three servers. When we tried to manually apply those missing patches we get the error message "This update is not applicable to your computer". After some troubleshooting we found that KB976932 (Service Pact 1) is not listed in
    installed updates. However, system property shows Windows 2008 R2 SP1 Enterprise Edition. We are certain that SP1 did NOT come pre-installed. Microsoft Baseline Security Analyzer detected no missing patches. Microsoft System Readiness Tool CBA logs show no
    errors. Ran SFC /SCANNOW and found no error also. Force install of the patches with command switch /wuforce, did not work we still get the same message patch not applicable. We compared our servers that are fully patched running Windows 2008 R2 SP1 against
    the three unpatched servers and found several dll and sys file's version to be different. Those dll and sys files are also the files that would have been updated by the critical patches. The only thing different between the fully patched Windows 2008 R2 SP1
    servers and the unpatch are the unpatch have no public internet access. We confirmed patches that were required prior to SP1 push are installed: KB2454826 KB2534366 KB2533552 KB976902 Confirmed: Partition with Windows 2008 R2 SP1 installed is set to "ACTIVE"
    Windows Event Collector service is started Windows Modules Installer is started Uninstalling SP1 is not possible because the KB976932 is not listed and verified "not hidden" in installed updates list. Rebuilding the three servers are the very last option,
    since they are critical. Other than the missing patches.... the servers are running great, we have no reported issues with the three servers. Attempt to reinstall SP1 failed after reboot, error 0X800F0826. If anyone has experience this problem and know of
    a solution please help.

    Hi,
    I would like to confirm that what updates are not applicable for your three Windows Server 2008 R2 SP1 servers?
    Based on the current situation, please run the System Update Readiness Tool as Meinolf Weber mentioned and check the CheckSUR.persist.log for the corrupted
    files. After that, please refer to the following Microsoft TechNet article for how to repair them.
    Advanced guidelines for diagnosing and fixing servicing corruption
    http://technet.microsoft.com/en-us/library/ee619779(WS.10).aspx
    Regards,
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • In Place Upgrade WSUS windows 2008 R2 into windows server 2012

    Hi Team,
    i had question. I have windows server 2008 R2 and installed WSUS role at that server.
    Can I do inplace upgrade into windows server 2012 std edition?
    is there any impact into wsus services?
    thanks

    If it is not a DC, upgrade should be easy. And there shouldn’t be any problems.
    The question was about upgrading a WSUS server, and regardless of whether it's a DC or not, it most emphatically will not be problem free. In fact, it's flat out not possible! On WS2012 the upgrade will be blocked if WSUS v3 is present,
    and on WS2012R2 it will corrupt the WSUS installation beyond repair requiring a reinstallation of the operating system.
    Please review the
    WSUS v6 documentation regarding upgrade requirements.
    Warning
    Upgrade from any version of Windows Server that supports WSUS 3.2 to Windows Server® 2012 R2 requires that you first uninstall WSUS 3.2.
    In Windows Server 2012, upgrading from any version of Windows Server with WSUS 3.2 installed is blocked during the installation process if WSUS 3.2 is detected, and you are prompted to first uninstall Windows Server Update Services prior to upgrading Windows
    Server 2012.
    However, because of changes in Windows Server 2012 R2, when upgrading from any version of Windows Server and WSUS 3.2 to Windows Server 2012 R2, the installation is not blocked. Failure to uninstall WSUS 3.2 prior to performing a Windows Server 2012 R2 upgrade
    will cause the post installation tasks for WSUS in Windows Server 2012 R2 to fail. In this case, the only known corrective measure is to format the hard drive and reinstall Windows Server 2012 R2.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Maybe you are looking for