Inplace Upgrade client OS from 2008R2 to 2012

I have several machines still on 2008 R2 that we want to inplace upgrade to Server 2012. I've tried looking for information on this and I am not having any luck.
I'm assuming I could use my updated/captured 2012 .wim file and a task sequence to do so, but I haven't really found any information/articles/guides discussing this exact scenario.

What do you want to upgrade exactly? Site servers or site systems? If so: that's not supported.
Or whatever OS? If so: ConfigMgr cannot perform inplaces upgrades - only wipe and load (with capturing and restoring the user state).
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

  • Upgrade from 2008R2 to 2012 or 2014?

    Hi, 
    Have to start planning/testing a upgrade of SQL 2008R2 in the next month or so.  I was planning on going to 2012 but I'm wondering if I should jump straight to 2014.  Anyone done this all in one go, any problems/issues? 
    I will upgrade one instance to start with, however I will still need to backup/restore from 2008R2 to this 2012 server, mostly using RedGate SQL Backup, however there are occasions when vanilla backup/restore are used.
    No replication or log shipping (as yet).
    The server is a development environment for SSIS & SSRS, basically it's a BI server.
    Thanks in advance. 
    Dave

    Hello,
    On SQL Server 2008 R2 you have Business Intelligence Development Studio for BI, SSIS. SQL Server 2012 and 2014 offer SQL
    Server Data Tools. You won’t be able to use SSIS designers in VS 2008 to target SSIS 2012, you will have to use VS 2010 or VS2012, and if you upgrade to SQL 2014 to will have to use VS 2013.
    http://blogs.msdn.com/b/analysisservices/archive/2014/04/02/sql-server-data-tools-business-intelligence-for-visual-studio-2013-ssdt-bi.aspx
    Use SSIS package upgrade wizard to upgrade SSIS packages.
    http://msdn.microsoft.com/en-us/library/cc280547.aspx
    Since SQL Server 2012, a new project deployment model exists. Read about it on the following document.
    http://msdn.microsoft.com/en-us/library/hh667275.aspx
    If you choose to upgrade to SSIS 2014 instead of SSIS 2012, you will have to provide users access to integration services service using the following procedure. You do not have to do this procedure for SSIS 2012.
    http://msdn.microsoft.com/en-us/library/hh213130.aspx
    Please use Upgrade Advisor to detect any possible blocking points.
    http://msdn.microsoft.com/en-us/library/d85b0833-ddeb-42e3-9397-97ea60d521b7(v=sql.120)
    The following technical guides may be useful.
    http://download.microsoft.com/download/9/5/3/9533501A-6F3E-4D03-A6A3-359AF6A79877/SQL_Server_2012_Upgrade_Technical_Reference_Guide_White_Paper.pdf
    http://blogs.technet.com/b/sqlman/archive/2014/12/17/sql-server-2014-upgrade-technical-guide-now-available.aspx
    Questions:
    (1)  
    Are you planning an in-place upgrade or a side-by-side upgrade? Backup SSRS encryption keys and restore them on the new environment on a side-by-side
    upgrade.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Upgrading SQL Server from 2008 to 2012 doesn't respect existing install / instance paths

    Basic Information : Running Microsoft Windows Server 2008 with MS SQL Server 2008 (version 10.0.5869), trying to upgrade to SQL Server 2012. Currently working in a cloned
    VM of our production server (so I can try things and not worry about affecting our production system).
    Current server setup:
    C Drive: Operating System (About 7 GB of 50 GB free)
    J Drive: Program Files (About 65 GB of 78 GB free)
    F Drive: SQL Databases (About 120 GB of 195 GB free)
    Issue: I am trying to do an upgrade of our existing MS SQL Server 2008 install. I am using the GUI method, and choosing "Upgrade from SQL Server, 2005, SQL Server
    2008, or SQL Server 2008 R2" in the Setup GUI:
    All the checks & rules run with no issues. When I get to the "Instance Configuration" screen in the setup GUI, it is not respecting where my SQL Server instance is already installed (which is on the J drive). Instead it wants to install EVERYTHING
    (including Instance Directory, which should be on the F drive, and the install folder, which should be on the J drive) on the C drive under C:\Program Files\ and there is no option in the GUI to change that, as it's grayed out.
    I tried using a Configuration File to do the upgrade, but when I tried to specify the specific paths, it says those variables are not allowed to be used in an upgrade. If I allow the install to go through, it seems to install fine, but only leaves me with about
    1.5 GB free on the OS drive (Drive C) and all of SQL Server is now installed on Drive C, which is not what I want or need.
    Looking in the Registry Editor, I can see that under HKLM\SOFTWARE\Microsoft\Microsoft
    SQL Server\MSQL11.MSSQLSERVER\ that the SqlProgramDir key
    has changed from "F:\" to "C:\Program Files\Microsoft SQL Server\" and that the SQLPath and SQLDataRoot have
    changed from "F:\MSSQL10.MSSQLSERVER\MSSQL" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL". SQLBinRoot has
    also been changed "F:\MSSQL10.MSSQLSERVER\MSSQL\Binn" to "C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn".
    It doesn't seem to want to follow where the existing Install and Instance Directories are. Am I missing something here? I've done a decent amount of research, but can't find anything that talks about this. So I'm at a loss as to what to do from here.

    I haven't touched the registry. Here is the ConfigurationFile.ini from the original install (I've scrubbed sensitive info out of it) showing the paths:
    ;SQLSERVER2008 Configuration File
    [SQLSERVER2008]
    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.
    INSTANCEID="MSSQLSERVER"
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
    ACTION="Install"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.
    FEATURES=SQLENGINE,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
    ; Displays the command line parameters usage
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console.
    INDICATEPROGRESS="False"
    ; Setup will not display any user interface.
    QUIET="False"
    ; Setup will display progress only without any user interaction.
    QUIETSIMPLE="False"
    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
    X86="False"
    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
    ERRORREPORTING="False"
    ; Specify the root installation directory for native shared components.
    INSTALLSHAREDDIR="J:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.
    INSTALLSHAREDWOWDIR="J:\Program Files (x86)\Microsoft SQL Server"
    ; Specify the installation directory.
    INSTANCEDIR="F:"
    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
    SQMREPORTING="False"
    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).
    INSTANCENAME="MSSQLSERVER"
    ; Agent account name
    AGTSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; Auto-start service after installation.
    AGTSVCSTARTUPTYPE="Automatic"
    ; Startup type for Integration Services.
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account.
    ISSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; The name of the account that the Analysis Services service runs under.
    ASSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; Controls the service startup type setting after the service has been created.
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services.
    ASCOLLATION="Latin1_General_CI_AS"
    ; The location for the Analysis Services data files.
    ASDATADIR="F:\MSAS10.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files.
    ASLOGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files.
    ASBACKUPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files.
    ASTEMPDIR="F:\MSAS10.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files.
    ASCONFIGDIR="F:\MSAS10.MSSQLSERVER\OLAP\Config"
    ; Specifies whether or not the MSOLAP provider is allowed to run in process.
    ASPROVIDERMSOLAP="1"
    ; Specifies the list of administrator accounts that need to be provisioned.
    ASSYSADMINACCOUNTS=""
    ; Startup type for the SQL Server service.
    SQLSVCSTARTUPTYPE="Automatic"
    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
    FILESTREAMLEVEL="0"
    ; Set to "1" to enable RANU for SQL Server Express.
    ENABLERANU="False"
    ; Specifies a Windows collation or an SQL collation to use for the Database Engine.
    SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"
    ; Account for SQL Server service: Domain\User or system account.
    SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; Windows account(s) to provision as SQL Server system administrators.
    SQLSYSADMINACCOUNTS=""
    ; The default is Windows Authentication. Use "SQL" for Mixed Mode Authentication.
    SECURITYMODE="SQL"
    ; Provision current user as a Database Engine system administrator for SQL Server 2008 Express.
    ADDCURRENTUSERASSQLADMIN="False"
    ; Specify 0 to disable or 1 to enable the TCP/IP protocol.
    TCPENABLED="1"
    ; Specify 0 to disable or 1 to enable the Named Pipes protocol.
    NPENABLED="0"
    ; Startup type for Browser Service.
    BROWSERSVCSTARTUPTYPE="Disabled"
    ; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
    RSSVCACCOUNT="NT AUTHORITY\SYSTEM"
    ; Specifies how the startup mode of the report server NT service. When
    ; Manual - Service startup is manual mode (default).
    ; Automatic - Service startup is automatic mode.
    ; Disabled - Service is disabled
    RSSVCSTARTUPTYPE="Automatic"
    ; Specifies which mode report server is installed in.
    ; Default value: “FilesOnly”
    RSINSTALLMODE="DefaultNativeMode"

  • SCCM - Client migration from 2007 to 2012

    Hi All,
    Can someone share the information what will be the impact in case , if we install CM2012 R2 client on the exisiting 2007 R2 client machine
    Regards,

    Hi,
    In addition, information from the source hierarchy about any advertisements or deployments that have not yet run, Compliance data and inventory are not retained.
    For more information, please check the article below.
    Planning a Client Migration Strategy in System Center 2012 Configuration Manager
    http://technet.microsoft.com/en-us/library/gg712283.aspx
    Best Regards,
    Joyce
    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.

  • Upgrade packages from 2008R2 to 2014/SSDT2013

    We are going to upgrade our environment from 2008R2 to 2014. This means both database engine and packages will be upgraded to 2014 and SSDT2013 respectively.
    Has anyone experienced this scenario? Can you give me some advise or checklist before upgrading packages or if possible TSQL/store proc changes/testing. 
    How do you have done testing after upgrading packages for result scan (output comparison with 2008R2 packages)?
    Any recommendation besides running upgrade advisor?
    Thanks in advance! :)
    ZK

    Hi ZK,
    Based on my research, some custom SSIS Tasks can always throw error after upgrading packages from SQL Server 2008 R2 to SQL Server 2014. After going thru the upgrade wizard you need to do several things:
    Change your custom tasks and components to target the .NET 4.0 Framework in each of the project properties, in the Application Tab, under Target framework.
    Update the assembly references in each of your projects to point to the appropriate SqlServer dlls.
    Build and copy your project dlls to the appropriate directory, depending on what kind of components you are updating, i.e. Program Files (x86)\Microsoft SQL Server\120\DTS\PiplelineComponents
    Register your components in the GAC.
    Close Visual Studio and then reopen; open your SSIS packages and refresh the SSIS Toolbox, by right clicking in the tool box and selected Refresh Toolbox.
    Besides, if some of your script task throw errors to you, we can open the script task in VSTA, insert Breakpoint to debug the scripts, then find the root cause. For more details, please see:
    Debug a Script by Setting Breakpoints in a Script Task and Script Component
    The following similar thread is for your reference:
    http://nobrainerlab.com/2013/02/19/ssis-script-task-upgrade-to-ssis-2012/
    Thanks,
    Katherine Xiong
    If you have any feedback on our support, please click
    here.
    Katherine Xiong
    TechNet Community Support

  • Mdx queries work different on 2008R2 and 2012

    Hi all,
    we have migrated our SSAS database from 2008R2 to 2012 recently. And I found strange thing. The mdx query below (generated by Cognos) worked quite fine on 2008R2
    WITH
      MEMBER [Territory].[Territories].[XQE_MDF_CM0] AS IIF(COUNT(INTERSECT(DESCENDANTS([Product].[Products].CURRENTMEMBER, [Product].[Products].[Product]), XQE_NS0) AS [XQE_SA0] , IncludeEmpty) > 0, AGGREGATE([XQE_SA0], ([Territory].[Territories].DEFAULTMEMBER)),
    NULL)
      SET XQE_NS0 AS FILTER([Product].[Products].[Product].MEMBERS, [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "713077" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "857127" OR
    [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "857128" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "713080" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY")
    = "717113" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "856597" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY") = "857129" OR [Product].[Products].CURRENTMEMBER.PROPERTIES("MEMBER_KEY")
    = "713083")
    SELECT
      CROSSJOIN({[Date].[Time].[Month].&[201409]}, CROSSJOIN(HIERARCHIZE(GENERATE(XQE_NS0, ANCESTORS([Product].[Products].CURRENTMEMBER, [Product].[Products].[Brand]))), {[Measures].[QTD Sales Revenue]})) DIMENSION PROPERTIES PARENT_UNIQUE_NAME,  PARENT_LEVEL
    ON AXIS(0)
    FROM [Nemesis]
    WHERE ([Territory].[Territories].[XQE_MDF_CM0]) CELL PROPERTIES VALUE,  CELL_ORDINAL,  LANGUAGE,  FORMAT_STRING
    But on 2012 version there was an interesting thing
    Result from (2008R2)
     2014/09 2014/09
    GALVUS GALVUSMET
    QTD Sales Revenue QTD Sales Revenue
    2346360.3062295 5550927.34167495
    Result from (2012)
     2014/09 2014/09
    GALVUS GALVUSMET
    QTD Sales Revenue QTD Sales Revenue
    5550927.34167495 5550927.34167495
    both results have been duplicated. Finding out a reason it looks like the where Clause which should filter products across first calc member works wrong. So when comment out where clause outcome looks right (I put all products from both brands by the way).
    But clients have to choose products to filter.
    I am just wondering if anyone encountered a similar issue, or 
    even if somebody have the solution.
    Many thanks,
    Denis.
    Denis

    In other words filter by set in WHERE clause is not working via calc member and aggregate function.
    Any ideas guys?
    Denis

  • Inplace upgrade SCCM 2012 R2 server OS from 2008 R2 to 2012R2 and SQL 2008R2 to 2012

    Hi
    Is it possible to do inplace upgrade?
    I have Windows Server 2008 R2, SCCM 2012 R2 CU1, SQL 2008 R2, WSUS and MDT 2013.
    Can I upgrade to Windows server 2012 R2 and SQL server 2012?
    Are there any catches which I must know before upgrade?
    Do I start upgrade with OS and then SQL?

    The in-place upgrade of the operating system is not supported...
    For a complete list see:
    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_UpgradeInfrastructure
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • CLIENT NOT UPGRADING FROM 2007 TO 2012

    I HAVE ONE PRIMARY SITE, 1200+ CLINETS
    SOME CLIENTS UPGRADED FROM 2007 TO 2012 NO PROBLEM. OTHERS HAVE A MESSAGE IN THEIR LOG FILES .

    Hi,
    Have you reviewed the ccmsetup.log and client.msi.log?
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Upgrading Sharepoint Content Database from 2008R2 sql server to SQL Server 2012

    I am doing an upgrade of SharePoint 2010 to 2013.
    What is the best way for the SharePoint database in 2008 to upgrade to 2012.
    attaching just the backup of content database should work or there is some other considerations as well along with.
    Are there any  known issues while upgrading the SharePoint database from 2008 to 2012.
    this is not an in place upgrade.
    kukdai

    If I may continue this question. I am upgrading MSSQL 2008 to MSSQL 2012. This box contains all of the DBs for our Sharepoint installation.  I am not a Sharepoint admin, I am a DBA.  So let me get this straight , from what I read up above all I
    have to do is just go through the standard procedure of upgrading SQL server 2008 to 2012 and the sharepoint DBs will upgrade with it w/o an issue.  Are there any gotchas with SSRS?  
    My SQL box runs WIN 2008 and has all necessary MSoft updates.
    Ianaa

  • Best practice for client migration from SMS 2003 to SCCM 2012 R2?

    Can anyone advise what the most recommended method is for migrating SMS 2003 clients (Windows 7) to SCCM 2012 R2?
    Options are:
    1. SMS package to deploy ccmclean.exe to uninstall SMS 2003 client. Deploy SCCM 2012 R2 client via SCCM console push.
    2. Simply push SCCM client from console installing over existing SMS 2003 client.
    I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
    3. Use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean and then install the SCCM client.
    Appreciate any feedback. Thank you.

    Hi,
    >>I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
    I haven't seen any official document records the option 2 method. There is only upgrading from SCCM 2007 to SCCM 2012 directly.
    I think you could use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean.exe. Then use SCCM 2012 to discover these computers and push clients to them.
    Best Regards,
    Joyce

  • Inplace upgrade Windows 2012 DC to Windows 2012 R2

    Hi
    We plan to upgrade some of our DCs from Windows 2012 to Windows 2012 R2.
    Theese DCs is on a DMZ holding our virtual machines management servers so they are not the most critical DCs but they are critical enough to not working for a longer time.
    Normally we dont do inplace upgrade but this is more of quick solution to raise the servers to the same OS level
    So has anyone done an inplace upgrade from 2012 to 2012 R2 on domain controllers? Any problems?
    We have two DCs, in differents locations.
    BR

    Yes, we've upgraded some of our DC's from Server 2012 to Server 2012 R2 without any issues at all. Obviously you want to do them one at a time, but we found it completely straight forward.
    In fact, if it wasn't for some unrelated legacy issues at one site (old servers preventing us upgrading that sites DPM install as DPM 2012 R2 doesn't support them, but DPM 2012 doesn't support Server 2012 R2) we'd have upgraded all our DCs by now.

  • Issues with upgrading client from 1.2 to 3.0

    I've upgraded a bunch of Mac's ARD client from 1.2 to 3.0 using ARD 3 admin's upgrade client feature. On some, I can't Observe or Control. So far I can copy files, run reports, and see current status. I can also ssh into machines with no problems. I've run the updater a second time and no go.
    All of these Macs were on 10.3.6. So sshed into them and ran all updaters and repaired permissions. Then upgraded ARD client.
    Any thoughts on whats the cause of this problem and how to remedy it?
    Any suggestions is appreciated.

    More info after some testing.
    Noticed machines that started out with base OS 10.3.1 with subsequent updates are the ones having observe/control issue. Most update progressions: 10.3.2, 10.3.3, 10.3.6 combo, 10.3.9 combo.
    Machines that started out with base OS 10.3.5 are not effected after upgrading to 10.3.9.
    Repaired permissions, updated binding, re-applied 10.3.9 combo update to one machine with no change.
    Removed client by taking following steps - KB 108021
    $ sudo rm -rf /System/Library/CoreServices/Menu\ Extras/RemoteDesktop.menu
    $ sudo rm -rf /System/Library/CoreServices/RemoteManagement/
    $ sudo rm -rf /System/Library/PreferencePanes/ARDPref.prefPane
    $ sudo rm -rf /System/Library/StartupItems/RemoteDesktopAgent/
    $ sudo rm /Library/Preferences/com.apple.ARDAgent.plist not applicable in any of my configs
    $ sudo rm /Library/Preferences/com.apple.RemoteManagement.plist
    Built an client installer package using ARD 3 admin and still can't Observe/Control but most other items seem to function.
    I'm suspecting this has to do with base OS these machines were built on. Running out of ideas. I would like to find out whats preventing me to control machine instead of rebuilding a bunch of machine. Any input is appreciated.

  • Upgrade to R2 from SCOM 2012 SP 1 UR 4 - Final configuration failed to install

    I was upgrading our test SCOM 2012 SP1 UR 4 sever to R2 and ran into the following issue:
    Setup cannot be completed…  Final configuration failed to install.
    Everything else upgraded fine.
    There was no rollback performed…. The log states “Skipping rollback for install item Final Configuration as it was not successfully installed”
    Looking in OpsManagerSetupWizard.log in the section for Final Configuration I see the following:
    [16:00:43]:           Always: :!***** Installing: POSTINSTALL ***
    [16:00:43]:           Info:      :SetProgressScreen: StartMinorStep.
    [16:00:43]:           Warn:    :ApplyUpdates: Unable to load QFE file.
    [16:00:43]:           Always: :Doing Preinstall task for POSTINSTALL
    [16:00:43]:           Warn:    :CheckAndLoadUpdateFiles: Unable to load QFE file.
    [16:00:43]:           Always: :Doing Install task for POSTINSTALL
    [16:00:44]:           Debug: :DoInstallTask: Found Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall;PostInstallProcessor as type and method.
    [16:00:44]:           Info:      :Type: Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall  Method: PostInstallProcessor
    [16:00:44]:           Info:      :SetProgressScreen: Init Exe Install progress.
    [16:00:44]:           Info:      :AddUninstallChangeEntry: Cleaning out existing files at the ARP file cache location D:\Program Files\System Center 2012\Operations
    Manager\Setup
    [16:00:44]:           Error:     :InstallActionProcessor.DoInstallTask: method PostInstallProcessor threw exception.  We will return installSuccessful = false.:
    Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
    [16:00:44]:           Error:     :StackTrace:   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at Microsoft.SystemCenter.Essentials.SetupFramework.InstallActionProcessor.DoInstallTask(InstallItemsInstallDataItem itemToInstall)
    [16:00:44]:           Error:     :Inner Exception.Type: System.UnauthorizedAccessException, Exception Error Code: 0x80131604, Exception.Message: Access to the path 'EULA_EN_EVAL.RTF'
    is denied.
    [16:00:44]:           Error:     :InnerException.StackTrace:   at System.IO.Directory.DeleteHelper(String fullPath, String userPath, Boolean recursive, Boolean
    throwOnTopLevelDirectoryNotFound)
       at System.IO.Directory.Delete(String fullPath, String userPath, Boolean recursive, Boolean checkHost)
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.ARPFileCache()
       at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupHelpers.AddUninstallChangeEntry()
       at Microsoft.SystemCenter.Essentials.SetupFramework.InstallItemsDelegates.PostInstall.PostInstallProcessor(Func`3 setProgressScreen)
    [16:00:44]:           Error:     :ProcessInstalls: Install Item Final Configuration failed to install.  We did not launch the post process delegate.
    [16:00:44]:           Always: :SetErrorType: Setting VitalFailure. currentInstallItem: Final Configuration
    [16:00:44]:           Info:      :SetProgressScreen: FinishMinorStep.
    [16:00:44]:           Always: :****************************************************************
    [16:00:44]:           Always: :****Starting*RollBack*******************************************
    [16:00:44]:           Always: :****************************************************************
    [16:00:44]:           Info:      :SetProgressScreen: StartMinorStep.
    [16:00:44]:           Always: :ProcessRollback: Skipping rollback for install item Final Configuration as it was not successfully installed.
    [16:00:44]:           Always: :****************************************************************
    [16:00:44]:           Always: :****Ended*RollBack**********************************************
    [16:00:44]:           Always: :****************************************************************
    [16:00:44]:           Always: :Entering Page: FinishPage
    The log states “Access to the path 'EULA_EN_EVAL.RTF' is denied.”  I was able to find this file in D:\Program Files\System Center 2012\Operations Manager\SetupTemp\EN, but when viewing its contents I see it
    was from the SP 1 upgrade as it starts off with “MICROSOFT EVALUATION SOFTWARE LICENSE TERMS MICROSOFT SYSTEM CENTER 2012 STANDARD SERVICE PACK 1.”  Based on everything else referenced in the log file previously, it seems like it was trying to locate
    this file in D:\Program Files\System Center 2012\Operations Manager\Setup.  Also, I applied the product key after installing SP1 previously, so it was not running with an evaluation license.
    Running Get-SCOMManagementGroup | ft skuforlicense, version, timeofexpiration –a
    gives me:
    SkuForLicense Version     TimeOfExpiration
           Retail 7.1.10226.0 12/31/9999 11:59:59 PM
    The version (7.1.10226.0) is that of SCOM 2012 R2 (as I noted before, there was no rollback.)  Everything seems to be functioning fine (Console, Web Console, Reporting Services.)
    Is there a way to get it to re-run only the Final Configuration steps (which will probably fail again as the EULA file does not exist where it expects it)?  I am not sure if there were supposed to be any further
    configuration steps that did not get completed, so i dont know how stable SCOM is now.  Should I re-run the R2 installer?  Or is it OK as is?  The only info online about a SCOM Install where the final configuration failed to install dealt with
    an error upgrading the SCOM Console, which is not relevant to my situation.  This is my test SCOM environment, running on a VM.  I could revert to the pre-upgrade snapshot and see if another upgrade attempt completes successfully, but if that does
    work I am concerned that something like this may happen in my prod environment, which is not running on a VM, so has no ability to revert to a snapshot.

    Hi,
    Please refer to the following links:
    Do I need a specific Cumulative Update Release (UR) in order to upgrade to SCOM 2012 or 2012 SP1 or 2012 R2?
    http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx
    Upgrading Operations Manager from 2012 SP1 to 2012 R2 step by step
    http://www.systemcentercentral.com/upgrading-operations-manager-from-2012-sp1-to-2012-r2-step-by-step-upgrading-to-2012-r2-series/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+systemcenterforum+%28System+Center+Central+Rollup%29
    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.

  • Upgrade from Windows Server 2012 Active Directory to Windows Server 2012 R2 Active Directory

    We are currently running Windows Server 2012 Active Directory and would like to upgrade to Windows Server 2012 R2 AD. Is it OK to just do an in-place upgrade, or is it advisable to build new domain controllers on R2? Are there any guides or articles anyone
    can recommend?

    Hi Ginandtonic,
    To upgrade DC(Domain Controller) from windows server 2012 to windows server 2012 r2, please refer to these articles:
    Upgrade from windows Server 2012 to 2012 R2                                 
    Upgrade Active Directory from 2012 to 2012 R2
    I hope this helps.
    Best Regards,
    Anna

  • Upgrade Client from 11.2.0.1 to 11.2.0.3  on Windows 7 / INS-30071

    Hi,
    I want to upgrade the client (Administrator) on my system from 11.2.0.1 to 11.2.0.3. Is this not directly possible due the new Update mechanism in 11.2.0.2? I can choose "Upgrade client", but it fails with INS-30071, and I can't find any logs to analyze this error further. OS is Windows 7.

    Pl identify which version of Win 7 - you will need Professional or higher - http://docs.oracle.com/cd/E11882_01/install.112/e24187/pre_install.htm#CIHIAGFG
    All you need to do is to install 11.2.0.3 into a new ORACLE_HOME, then uninstall 11.2.0.1
    "INS-30071" Error During Upgrade Oracle Client or Server From 11.2.0.2 To 11.2.0.3 [ID 1483670.1]
    HTH
    Srini

Maybe you are looking for