Upgrade Call Manager

Hello All,
our company is planning to upgrade Cisco Call manager 5.0 to version 8. Can you please help me out what the procedure will be. Or also what the steps i need to follow to upgrade from 5 to 8.

Hi ,
For upgrading call manager from version 5 to 8 , u need to consider the following steps:
a. you need to have valid ESW and UCSS contract since this would be a major upgrade.
b. Check for existing Hardware since DRAM and HDD requirements are  different for version 8.0(3) and above.
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
c. you also need to check the software compatibility matrix.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr1.pdf
regds,
aman

Similar Messages

  • Upgrade Call Manager 6.5

    Hello Team,
    Just to get confirmation about the MCS Servers 7800 Series that is it recommanded to upgrade Call Manager 6.5 which is running
    on MCS 7800 Series Server to Call Manager 9. CM-9 us fully unified.
    Thanks,

    Supported Servers for Releases of Cisco Unified Communications Manager (Including Business Edition 3000/5000/6000 and Session Manager Edition) and Cisco Intercompany Media Engine
    http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4f9.html
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • Upgrade Call Manager from 8.6.2 to 10.5

    Hello All,
    We are planning to upgrade a Cisco Call Manager Publisher node from 8.6.2 to 10.5. We want to install a new publisher on a new environment, but we are struggling with some questions.
    If we install the Pub node 10.5 can we migrate the configuration from the 8.6.2 to 10.5? Do we need a special tool for this?
    If above doesn't work, we can still migrate the existing call manager towards the new servers and start the upgrade, the only problem we face there is that we have to change the publisher's IP because we want to use a new ip addressing scheme.
    Kr,
    Yannick Vranckx

    Your best bet is to use the new tool: cisco prime collaboration deployment. This fits perfectly into what you want to do here and can easily help you with all aspect of the migration including the ip address change. You can learn how to use the tool here..
    https://www.youtube.com/watch?v=JzG4kz1_hL4

  • Upgrading call manager from version 8 to 9

    Hi All
    Can anyone please tell me the summary steps on what I need to do to go from call manager version 8 to version 9?
    many thanks
    Carl

    The answer to your question, is that they entirely depend on you exact CUCM versions, asking here and just saying "8 "does not work. You will need to do your due diligence, and read:
    A) Upgrade guide for your target version
    B) Release Notes
    C) New and changed doc, if not included in the RNs already
    They will provide you with ALL you need to perform the upgrade, pre-reqs, procedure, and post-upgrade changes to the VM. All the information is available on cisco.com under the CUCM main documentation site.
    Once you've been thru those, you can come back with any further questions.

  • Upgrade Call Manager from 8.5(1) to 10.5(1) and migrate from MCS to UCS...

    We are upgrading UCM from 8.5(1) to 10.5(1) and migrating from MCS to UCS. We used UCM 8.5 OVA (7500 user) and migrated to UCS.
    Once migrated to UCS we upgraded UCM to 10.5(1). We wanted to use OVA to accommodate 10,000 users, hence took backup of 10.5(1) cluster and installed new servers with new 10.5(1) OVA (10,000 users).
    While doing DRS restore, system we were not able to perform a restore. It seems UCM is not recognizing the XML file. It is strange as we took the back from UCM 10.5(1) and trying to restore same version, only difference is upgrade was done with 7500 user OVA and we are now trying to install 10,000 user OVA.
    Has anyone run into similar issue? any help will be great.
    Thank You.

    This thread is 5 months old but doesn't seem resolved...
    I ran into this same scenario last week. Was using the same SFTP server for backups and restores during migration from 7.1(5) to 10.5 and during final rebuild/restore of the "to-be" production 10.5 Publisher, the DRS server was unresponsive and blamed the Master Agent or SFTP server. I had restarted Master and Local agent repeatedly, and regenerated ipsec certs to no avail.
    TAC suggested I try a different SFTP server (which I already had, with the same files), and try deleting the .xml files that were included with the backup (drfComponent.xml and processhost.xml). I installed TitanFTP, per TAC's recommendation, deleted the processhost.xml file, regenerated the ipsec certificate one last time, restarted DRF Master, and then DRF Agent, and was able to start a DRS Restore.
    Try the above process if you're still having issues.

  • Call Manager 8.0 to 9.1 upgrade

    We are currently running Call Manager 8, UCCE 8, and CVP 8. ICM/CTI 8. 
    We would like to upgrade Call Manager 8 to 9.1 first before upgrading UCCE, CVP, etc., it could be months before these are upgraded.
    Does anyone know or foresee any issues if UCCE, CVP, etc., are not upgraded right away after CM is upgraded?
    Any comment is appreciated.  Thanks.

    Look at the UCCE compatibility matrix as you need the exact versions to find out whether they will work together, of ir you'll need a single window on which to upgrade all.
    HTH
    java
    if this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • What are the essentials needed before upgrading from call manager 9.1.1 to call manager 9.1.2?

    I recently tried to upgrade my call manager in a lab environment from 9.1.1 to 9.1.2 but failed. The error stated that connection had been lost after 2 hours into it. Connect using CLI. Any help would be greatly appreciated.
    Steve

    You mean via GUI??
    What does the upgrade status via CLI says??

  • Call Manager Upgrade????

    I am running Call Manager 6.0. I want to upgrade my Call Manager Software to 6.1.4. Do I have to upgrade the Call Manager Using FTP over the network or can I just use the local DVD drive to upgrade it?

    you cannot directly upgrade from 6.0.1 to
    6.1.3 or 6.1.4 - the best option would be to upgrade to 6.1.2 and from there
    to either 6.1.3 or 6.1.4.
    you should be able to do it via sftp

  • Ringtones and background images not available after call manager upgrade

    Hi,
          We have upgraded our call manager from version 8.5 to 10.5.  Once after the upgrade we lost all the Ringtones and background images except the two default ringtone and background images.  we got 8945 sccp phones(running 9-3-1 firmware) and 9951 sip phones(running 9-4-1 firmware).  Both these phones lost these list.  However the ringlist.xml is available in the tftp server with all the ringtones and the phones are pointed to the right tftp servers.  I tried to restart the tftp servers and tried again, however that didn't help.   we are using call manager 10.5 and h323 voice gateway.  Could anyone please help on this.
    Thanks
    Barry

    Hi Tony,
         I can see the ringtone files in the call manager (osadmin>tftp file mgmt), i have also restarted the tftp services, but it didn't help.  I believe you advised to re-upload the ringlist file (Ringlist.xml) and try again. I will try this and update you.  Please let me know if you have any other suggestions.
    Thanks
    Barry

  • Cisco Call Manager Upgrade from Ver 5.1.3 to Ver 8.6

    Hi ,
    My organization have 4 Subscribers and 1 publisher between 4 different sites. version of all call manager are 5.1.3. all are running on HP Proliant server.
    I looking to upgrade to Version 8.6. Do I need to upgrade server hardware as well for upgrading latest version of call manager or I can use my old server ?
    Thanks
    Amit Sharma

    Hi GP,
    Thanks for your reply.
    Please find below the hardware details of my old server. these details I get from Cisco call manager application.
    Hardware Resources
    Hardware platform type    7835H
    The CPU type    Intel(R) Xeon(TM) CPU 3.40GHz
    Memory    2048 Mbytes
    Detailed Report
    Machine_Type = XXXX
    Model_Number =
    Serial_Number = GB8637LRFE     
    Product_Name = ProLiant DL380 G4
    BIOS_Version =
    BIOS_Build_Level = P51
    BIOS_Date = 04/26/2006
    BIOS_Manufacturer = HP
    BIOS_Language =
    Number_Of_Enclosures =
    Enclosure_Type.0 =
    Processor_Slots = 2
    Active_Processors = 1
    Processor_Family.0 = Xeon
    Processor_Speed_MHz.0 = 3400
    Total_Enabled_Memory_Mb = 2048
    ROM_Diagnostics_Build_Level =
    Thanks
    Amit

  • What is the procedure of Call Manager upgrade from version CUCM 7.1 (MCS Server) to version CUCM 10.2 (on UCS server)

    Hi
    What is the procedure of Call Manager upgrade from version CUCM 7.1 (MCS Server)  to version CUCM 10.2 (on UCS server) , please let me know the steps to what would be the backup procedures and upgrades.
    Regards
    Gaurav

    I'd suggest reading this guide to make sure you have prepared your environment to support 10.x first. The link below also contains the upgrade path to 10.0(1).
    One of the ways you can do this is:
    1/ Apply refresh upgrade cop file on all servers in cluster.
    2/ Upgrade the cluster to 8.6(2). Take a backup of the cluster.
    3/ Build a cluster of 8.6(2) servers on VMs, and assign them the same hostnames and IP address as the hardware cluster. (You may need to keep these on a separate network until switching off the hardware machines)
    4/ Restore the backup taken from the hardware cluster on to the VM cluster.
    5/ Upgrade VM cluster to 10.0(1).
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100_chapter_010.html#CUCM_RF_UA60AFAB_00

  • OMServer.msi returns error 1603 when trying to upgrade first management server from Operations Manager 2012 SP1 to Operations Manager 2012 R2

    Hi All, looking for some assistance with the following issue.
    We are attempting to upgrade our Operations Manager 2012 SP1 environment to Operations Manager 2012 R2.
    We have completed all the pre-upgrade tasks detailed here
    http://technet.microsoft.com/en-us/library/dn249704.aspx
    We are then following the guidance detailed here regarding upgrading distributed management groups
    http://technet.microsoft.com/en-us/library/dn249721.aspx. The upgrade fails on the first management server with the following screen being displayed.
    OMServer.log file is as follows.
    === Verbose logging started: 22/01/2014 10:21:27 Build type: SHIP UNICODE 5.00.9200.00 Calling process: C:\Users\scomaction\AppData\Local\SCOM\Setup\SetupChainerUI.exe ===
    MSI (c) (78:34) [10:21:27:040]: Resetting cached policy values
    MSI (c) (78:34) [10:21:27:040]: Machine policy value 'Debug' is 0
    MSI (c) (78:34) [10:21:27:040]: ******* RunEngine:
    ******* Product: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    ******* Action:
    ******* CommandLine: **********
    MSI (c) (78:34) [10:21:27:040]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (78:34) [10:21:27:040]: Grabbed execution mutex.
    MSI (c) (78:34) [10:21:27:071]: Cloaking enabled.
    MSI (c) (78:34) [10:21:27:071]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (78:34) [10:21:27:071]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (D4:30) [10:21:27:082]: Running installation inside multi-package transaction F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    MSI (s) (D4:30) [10:21:27:082]: Grabbed execution mutex.
    MSI (s) (D4:A0) [10:21:27:086]: Resetting cached policy values
    MSI (s) (D4:A0) [10:21:27:086]: Machine policy value 'Debug' is 0
    MSI (s) (D4:A0) [10:21:27:086]: ******* RunEngine:
    ******* Product: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    ******* Action:
    ******* CommandLine: **********
    MSI (s) (D4:A0) [10:21:27:175]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (D4:A0) [10:21:27:181]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:190]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (D4:A0) [10:21:27:192]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
    MSI (s) (D4:A0) [10:21:27:200]: File will have security applied from OpCode.
    MSI (s) (D4:A0) [10:21:27:234]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi' against software restriction policy
    MSI (s) (D4:A0) [10:21:27:234]: SOFTWARE RESTRICTION POLICY: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi has a digital signature
    MSI (s) (D4:A0) [10:21:27:354]: SOFTWARE RESTRICTION POLICY: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (D4:A0) [10:21:27:354]: MSCOREE not loaded loading copy from system32
    MSI (s) (D4:A0) [10:21:27:360]: End dialog not enabled
    MSI (s) (D4:A0) [10:21:27:360]: Original package ==> F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    MSI (s) (D4:A0) [10:21:27:360]: Package we're running from ==> C:\Windows\Installer\4b8344.msi
    MSI (s) (D4:A0) [10:21:27:371]: APPCOMPAT: Compatibility mode property overrides found.
    MSI (s) (D4:A0) [10:21:27:372]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'.
    MSI (s) (D4:A0) [10:21:27:372]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (D4:A0) [10:21:27:378]: Machine policy value 'TransformsSecure' is 1
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisablePatch' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (D4:A0) [10:21:27:380]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'.
    MSI (s) (D4:A0) [10:21:27:380]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (D4:A0) [10:21:27:380]: Transforms are not secure.
    MSI (s) (D4:A0) [10:21:27:380]: Note: 1: 2205 2: 3: Control
    MSI (s) (D4:A0) [10:21:27:380]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\scomaction\AppData\Local\SCOM\Logs\OMServer.log'.
    MSI (s) (D4:A0) [10:21:27:380]: Command Line: OM_INSTALLDIR=F:\Program Files\Microsoft System Center 2012 R2\Operations Manager SEND_CEIP_REPORTS=0 MU_SETTING=0 ROOT_MANAGEMENT_SERVER_PORT=5723 SC_DB_SERVER=SCOM-XXX-AG SCDATABASENAME=OperationsManager DW_DB_SERVER=SCOM-XXX-AG DWDATABASENAME=OperationsManagerDW REBOOT=ReallySuppress CURRENTDIRECTORY=C:\Users\scomaction\AppData\Local\SCOM\Setup CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=4472
    MSI (s) (D4:A0) [10:21:27:380]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{58EFE971-58C1-4DBD-A400-A7607A745475}'.
    MSI (s) (D4:A0) [10:21:27:380]: Product Code passed to Engine.Initialize: ''
    MSI (s) (D4:A0) [10:21:27:380]: Product Code from property table before transforms: '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'
    MSI (s) (D4:A0) [10:21:27:380]: Product Code from property table after transforms: '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'
    MSI (s) (D4:A0) [10:21:27:380]: Product not registered: beginning first-time install
    MSI (s) (D4:A0) [10:21:27:380]: Product {C92727BE-BD12-4140-96A6-276BA4F60AC1} is not managed.
    MSI (s) (D4:A0) [10:21:27:380]: MSI_LUA: Credential prompt not required, user is an admin
    MSI (s) (D4:A0) [10:21:27:381]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
    MSI (s) (D4:A0) [10:21:27:381]: Entering CMsiConfigurationManager::SetLastUsedSource.
    MSI (s) (D4:A0) [10:21:27:381]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (D4:A0) [10:21:27:381]: Adding new sources is allowed.
    MSI (s) (D4:A0) [10:21:27:381]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:381]: Package name extracted from package path: 'OMServer.msi'
    MSI (s) (D4:A0) [10:21:27:381]: Package to be registered: 'OMServer.msi'
    MSI (s) (D4:A0) [10:21:27:383]: Note: 1: 2262 2: AdminProperties 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'DisableMsi' is 1
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (D4:A0) [10:21:27:383]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (D4:A0) [10:21:27:383]: Product installation will be elevated because user is admin and product is being installed per-machine.
    MSI (s) (D4:A0) [10:21:27:383]: Running product '{C92727BE-BD12-4140-96A6-276BA4F60AC1}' with elevated privileges: Product is assigned.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding OM_INSTALLDIR property. Its value is 'F:\Program Files\Microsoft System Center 2012 R2\Operations Manager'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding ROOT_MANAGEMENT_SERVER_PORT property. Its value is '5723'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Modifying SC_DB_SERVER property. Its current value is 'OperationsManager'. Its new value: 'SCOM-XXX-AG'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding DW_DB_SERVER property. Its value is 'SCOM-XXX-AG'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding DWDATABASENAME property. Its value is 'OperationsManagerDW'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Users\scomaction\AppData\Local\SCOM\Setup'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '4472'.
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
    MSI (s) (D4:A0) [10:21:27:383]: RESTART MANAGER: Disabled by MSIRESTARTMANAGERCONTROL property; Windows Installer will use the built-in FilesInUse functionality.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:383]: TRANSFORMS property is now:
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
    MSI (s) (D4:A0) [10:21:27:395]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming
    MSI (s) (D4:A0) [10:21:27:396]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Favorites
    MSI (s) (D4:A0) [10:21:27:398]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Network Shortcuts
    MSI (s) (D4:A0) [10:21:27:399]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Documents
    MSI (s) (D4:A0) [10:21:27:401]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
    MSI (s) (D4:A0) [10:21:27:402]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Recent
    MSI (s) (D4:A0) [10:21:27:404]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\SendTo
    MSI (s) (D4:A0) [10:21:27:405]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Templates
    MSI (s) (D4:A0) [10:21:27:405]: SHELL32::SHGetFolderPath returned: C:\ProgramData
    MSI (s) (D4:A0) [10:21:27:406]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Local
    MSI (s) (D4:A0) [10:21:27:408]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Pictures
    MSI (s) (D4:A0) [10:21:27:411]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (D4:A0) [10:21:27:413]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (D4:A0) [10:21:27:414]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
    MSI (s) (D4:A0) [10:21:27:415]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
    MSI (s) (D4:A0) [10:21:27:417]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
    MSI (s) (D4:A0) [10:21:27:420]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (D4:A0) [10:21:27:421]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (D4:A0) [10:21:27:423]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
    MSI (s) (D4:A0) [10:21:27:424]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu
    MSI (s) (D4:A0) [10:21:27:426]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Desktop
    MSI (s) (D4:A0) [10:21:27:427]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
    MSI (s) (D4:A0) [10:21:27:428]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
    MSI (s) (D4:A0) [10:21:27:428]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
    MSI (s) (D4:A0) [10:21:27:433]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\4b8344.msi'.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi'.
    MSI (s) (D4:A0) [10:21:27:434]: Machine policy value 'MsiDisableEmbeddedUI' is 0
    MSI (s) (D4:A0) [10:21:27:434]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
    MSI (s) (D4:A0) [10:21:27:434]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 2205 2: 3: PatchPackage
    MSI (s) (D4:A0) [10:21:27:434]: Machine policy value 'DisableRollback' is 0
    MSI (s) (D4:A0) [10:21:27:434]: User policy value 'DisableRollback' is 0
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
    === Logging started: 22/01/2014 10:21:27 ===
    MSI (s) (D4:A0) [10:21:27:435]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:436]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
    MSI (s) (D4:A0) [10:21:27:438]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
    MSI (s) (D4:A0) [10:21:27:438]: Doing action: INSTALL
    Action start 10:21:27: INSTALL.
    MSI (s) (D4:A0) [10:21:27:444]: Running ExecuteSequence
    MSI (s) (D4:A0) [10:21:27:444]: Doing action: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76
    MSI (s) (D4:A0) [10:21:27:447]: PROPERTY CHANGE: Adding SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76 property. Its value is 'C:\Windows\SysWOW64\'.
    Action start 10:21:27: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76.
    MSI (s) (D4:A0) [10:21:27:448]: Doing action: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76
    Action ended 10:21:27: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76. Return value 1.
    MSI (s) (D4:A0) [10:21:27:450]: PROPERTY CHANGE: Adding System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76.
    MSI (s) (D4:A0) [10:21:27:450]: Doing action: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6
    Action ended 10:21:27: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76. Return value 1.
    MSI (s) (D4:A0) [10:21:27:452]: PROPERTY CHANGE: Adding WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6.
    MSI (s) (D4:A0) [10:21:27:453]: Doing action: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522
    Action ended 10:21:27: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6. Return value 1.
    MSI (s) (D4:A0) [10:21:27:455]: PROPERTY CHANGE: Adding System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522.
    MSI (s) (D4:A0) [10:21:27:456]: Doing action: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
    Action ended 10:21:27: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522. Return value 1.
    MSI (s) (D4:A0) [10:21:27:458]: PROPERTY CHANGE: Adding WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C.
    MSI (s) (D4:A0) [10:21:27:458]: Doing action: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
    Action ended 10:21:27: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C. Return value 1.
    MSI (s) (D4:A0) [10:21:27:461]: PROPERTY CHANGE: Adding SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C property. Its value is 'C:\Windows\SysWOW64\'.
    Action start 10:21:27: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C.
    MSI (s) (D4:A0) [10:21:27:461]: Doing action: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7
    Action ended 10:21:27: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C. Return value 1.
    MSI (s) (D4:A0) [10:21:27:463]: PROPERTY CHANGE: Adding WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7.
    MSI (s) (D4:A0) [10:21:27:463]: Doing action: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7
    Action ended 10:21:27: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7. Return value 1.
    MSI (s) (D4:A0) [10:21:27:466]: PROPERTY CHANGE: Adding System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7.
    MSI (s) (D4:A0) [10:21:27:467]: Doing action: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8
    Action ended 10:21:27: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7. Return value 1.
    MSI (s) (D4:A0) [10:21:27:468]: PROPERTY CHANGE: Adding WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8.
    MSI (s) (D4:A0) [10:21:27:469]: Doing action: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9
    Action ended 10:21:27: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8. Return value 1.
    MSI (s) (D4:A0) [10:21:27:471]: PROPERTY CHANGE: Adding WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
    MSI (s) (D4:A0) [10:21:27:472]: Doing action: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE
    Action ended 10:21:27: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9. Return value 1.
    MSI (s) (D4:A0) [10:21:27:474]: PROPERTY CHANGE: Adding WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE.
    MSI (s) (D4:A0) [10:21:27:475]: Doing action: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0
    Action ended 10:21:27: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE. Return value 1.
    MSI (s) (D4:A0) [10:21:27:477]: PROPERTY CHANGE: Adding ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0 property. Its value is 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\'.
    Action start 10:21:27: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
    MSI (s) (D4:A0) [10:21:27:477]: Doing action: FindRelatedProducts
    Action ended 10:21:27: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 1.
    Action start 10:21:27: FindRelatedProducts.
    MSI (s) (D4:A0) [10:21:27:481]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT_AGENT property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _SearchOpsMgrShellPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Doing action: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0
    Action ended 10:21:27: FindRelatedProducts. Return value 1.
    MSI (s) (D4:08) [10:21:27:501]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI847C.tmp, Entrypoint: SetMonadFilePath
    MSI (s) (D4:B0) [10:21:27:502]: Generating random cookie.
    MSI (s) (D4:B0) [10:21:27:505]: Created Custom Action Server with PID 4964 (0x1364).
    MSI (s) (D4:34) [10:21:27:527]: Running as a service.
    MSI (s) (D4:34) [10:21:27:529]: Hello, I'm your 64bit Impersonated custom action server.
    Action start 10:21:27: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
    MSI (s) (D4!DC) [10:21:27:638]: PROPERTY CHANGE: Modifying MONAD_SHELL_PATH property. Its current value is 'Error: Value Never Set. Check the CACore:SetMonadFilePath CA'. Its new value: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'.
    GetRegistyStringValue: Registy key value found.. C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    MSI (s) (D4:A0) [10:21:27:640]: Doing action: _Set_CORECOMPONENTPRESENT
    Action ended 10:21:27: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 1.
    MSI (s) (D4:A0) [10:21:27:643]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
    Action start 10:21:27: _Set_CORECOMPONENTPRESENT.
    MSI (s) (D4:A0) [10:21:27:644]: Skipping action: _AbortDowngradeProductAttempt (condition is false)
    MSI (s) (D4:A0) [10:21:27:644]: Doing action: _AbortIncompatibleComponents
    Action ended 10:21:27: _Set_CORECOMPONENTPRESENT. Return value 1.
    Action start 10:21:27: _AbortIncompatibleComponents.
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5044 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 1580 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5512 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 4268 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5024 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 6064 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 3396 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 2704 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5568 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5940 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 1968 could not be cancelled. Error: 1168
    MSI (s) (D4:A0) [10:21:27:652]: Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service Manager is already installed. These must be uninstalled to proceed.
    The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service Manager is already installed. These must be uninstalled to proceed.
    Action ended 10:21:27: _AbortIncompatibleComponents. Return value 3.
    Action ended 10:21:27: INSTALL. Return value 3.
    Property(S): DiskPrompt = Please Insert Disk 1
    Property(S): UpgradeCode = {17058653-A628-4C03-8F80-5E2B179ECD55}
    Property(S): SCDATABASENAME = OperationsManager
    Property(S): SC_DB_SERVER = SCOM-XXX-AG
    Property(S): SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): CORECOMPONENTPRESENT = {8B21425D-02F3-4B80-88CE-8F79B320D330}
    Property(S): OM_INSTALLDIR = F:\Program Files\Microsoft System Center 2012 R2\Operations Manager
    Property(S): ProgramFiles64Folder = C:\Program Files\
    Property(S): Privileged = 1
    Property(S): ARPSYSTEMCOMPONENT = 1
    Property(S): DONOTSKIPDELETESERVICES = 0
    Property(S): DONOTSKIPINSTALLSERVICES = 0
    Property(S): OM_COMMON_PRODUCT_REGISTRY_PATH = SOFTWARE\Microsoft\System Center Operations Manager
    Property(S): OM_COMMON_PRODUCT_RELEASE_REGISTRY_KEY = 12
    Property(S): OM_COMMON_PRODUCT_DEFAULT_INSTALL_DIR = System Center Operations Manager
    Property(S): NetFxVersion = v2.0.50727
    Property(S): IS_OM_SERVER = 1
    Property(S): InstallAPMAgent = 1
    Property(S): INSTALLLEVEL = 100
    Property(S): ALLUSERS = 1
    Property(S): ARPNOREPAIR = 0
    Property(S): ARPURLINFOABOUT = http://www.microsoft.com/mom
    Property(S): ARPURLUPDATEINFO = http://www.microsoft.com/mom
    Property(S): ARPHELPLINK = http://support.microsoft.com
    Property(S): MSIRESTARTMANAGERCONTROL = Disable
    Property(S): SQL_PORT = 1433
    Property(S): DbSizeGood = 1
    Property(S): DbFileOptionsGood = 1
    Property(S): DbFilesSpaceGood = 1
    Property(S): DbNameGood = 1
    Property(S): SqlServicesStarted = 1
    Property(S): _SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): _SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): DialogWizardTitle = System Center 2012 R2 Operations Manager Setup
    Property(S): MinimumOSMsg = This product must be installed on Windows Server 2008 R2 or higher.
    Property(S): MOMSDKPortDesc = Operations Manager SDK.
    Property(S): MOMConnectorPortDesc = Operations Manager Connector Framework.
    Property(S): MOMAEMPortDesc = Operations Manager Application Error Monitoring.
    Property(S): MOMSQMPortDesc = Operations Manager Customer Experience Improvement Program.
    Property(S): MOMHSPortDesc = System Center Management Health Service
    Property(S): SCOMV3SP1ProgramName = System Center 2012 R2 Operations Manager
    Property(S): FWRulePingRequestName = Operations Manager Ping Request (Echo Request - ICMPv4 OUT)
    Property(S): FWRulePingRequestDesc = Operations Manager network monitoring ping request
    Property(S): FWRulePingResponseName = Operations Manager Ping Response (Echo Response - ICMPv4 IN)
    Property(S): FWRulePingResponseDesc = Operations Manager network monitoring ping response
    Property(S): FWRuleSnmpRequestName = Operations Manager SNMP Request
    Property(S): FWRuleSnmpRequestDesc = Operations Manager network monitoring SNMP request
    Property(S): FWRuleSnmpResponseName = Operations Manager SNMP Response
    Property(S): FWRuleSnmpResponseDesc = Operations Manager network monitoring SNMP response
    Property(S): FWRuleSnmpTrapListenerName = Operations Manager SNMP Trap Listener
    Property(S): FWRuleSnmpTrapListenerDesc = Operations Manager network monitoring SNMP trap listener
    Property(S): Manufacturer = Microsoft Corporation
    Property(S): ProductCode = {C92727BE-BD12-4140-96A6-276BA4F60AC1}
    Property(S): ProductLanguage = 1033
    Property(S): ProductName = System Center Operations Manager 2012 Server
    Property(S): ProductVersion = 7.1.10226.0
    Property(S): SecureCustomProperties = ACTIONSPASSWORD;CORECOMPONENTPRESENT_AGENT;CORECOMPONENTPRESENT_GW;CORECOMPONENTPRESENT_RC;CORECOMPONENTPRESENT_SCE;CORECOMPONENTPRESENT_SMB2;CORECOMPONENTPRESENT_SMRTM;IS_AVICODE_AGENT_INSTALLED;IS_MOMASPAGENT_INSTALLED;MOM_DB_SERVER;MOMDATABASENAME_OLD;OM_NEWER_PRODUCT_FOUND;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650;SQL_PORT
    Property(S): MsiHiddenProperties = _SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;_SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;ACTIONSPASSWORD;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650
    Property(S): WixPdbPath = d:\btvsts\20867\private\product\setup\wix\msi\server\om\obj\amd64\OMServer.wixpdb
    Property(S): CORECOMPONENTPRESENT_AGENT = {8B21425D-02F3-4B80-88CE-8F79B320D330}
    Property(S): ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): MONAD_SHELL_PATH = C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Property(S): EnableEV.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = 1
    Property(S): AddInstallPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = add
    Property(S): RemoveInstallPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = remove
    Property(S): WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE = C:\Windows\
    Property(S): VersionNT = 602
    Property(S): DW_DB_SERVER = SCOM-XXX-AG
    Property(S): DWDATABASENAME = OperationsManagerDW
    Property(S): OMDATABASENAME = OperationsManger
    Property(S): MaximumDataAgeMinutes = 10080
    Property(S): MaximumQueueSizeKB = 102400
    Property(S): MOMSDKPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 5724
    Property(S): MOMConnectorPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51905
    Property(S): MOMAEMPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51906
    Property(S): MOMSQMPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51907
    Property(S): SDK_SERVICE_TYPE = 4
    Property(S): ROOT_MANAGEMENT_SERVER_PORT = 5723
    Property(S): SERVER_MANAGEMENT_GROUP_TYPE.C6F00077_9737_419B_A8B6_B309BA6F8FC8 = 1
    Property(S): MaximumForwardedVirtualQueuePercentage = 8
    Property(S): QueueSendDataSinglePriority = 0
    Property(S): ADMIN_ROLE_GROUP.C6F00077_9737_419B_A8B6_B309BA6F8FC8 = Administrators
    Property(S): USE_MANUALLY_SPECIFIED_SETTINGS = 1
    Property(S): WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 = C:\Windows\
    Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
    Property(S): CAN_REGISTER_FOR_MU = 0
    Property(S): MU_SETTING = 0
    Property(S): IS_ROOT_HEALTH_SERVICE = 0
    Property(S): IS_MOM_SERVER = 0
    Property(S): IS_MOM_GATEWAY = 0
    Property(S): WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8 = C:\Windows\
    Property(S): WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 = C:\Windows\
    Property(S): System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 = C:\Windows\system32\
    Property(S): DirectoryTable100_amd64.1C11561A_11CB_36A7_8A47_D7A042055FA7 = DirectoryTable
    Property(S): WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = C:\Windows\
    Property(S): SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = C:\Windows\SysWOW64\
    Property(S): DirectoryTable100_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = DirectoryTable
    Property(S): SEND_CEIP_REPORTS = 0
    Property(S): System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 = C:\Windows\system32\
    Property(S): ACS_AGENT_ACCOUNT.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 =
    Property(S): WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6 = C:\Windows\
    Property(S): SC_COMMON_REGISTRY_PATH = SOFTWARE\Microsoft\System Center\2010\Common
    Property(S): DISCOVERY_DATA_AUTHORIZATION_ENABLED = 0
    Property(S): IcmpProtocol.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 1
    Property(S): IcmpRequestType.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 8:*
    Property(S): IcmpResponseType.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 0:*
    Property(S): SnmpProtocol.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 17
    Property(S): SnmpPort.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 161
    Property(S): SnmpTrapPort.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 162
    Property(S): DirectionIn.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 0
    Property(S): DirectionOut.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 1
    Property(S): SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76 = C:\Windows\SysWOW64\
    Property(S): System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76 = C:\Windows\system32\
    Property(S): ADVISOR_UPLOADFREQUENCY_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1
    Property(S): ADVISOR_UPLOADDAY_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_UPLOADTIMEHOUR_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_UPLOADTIMEMIN_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_MAXCACHESIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1024
    Property(S): ADVISOR_MAXMAILBOXSIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1024
    Property(S): ADVISOR_ARCHIVEPERIOD_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #5
    Property(S): ADVISOR_LOGLEVEL_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #3
    Property(S): ADVISOR_NEEDMPINITIALIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1
    Property(S): ADVISOR_LYNC_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #0
    Property(S): ADVISOR_SHAREPOINT_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #0
    Property(S): MsiLogFileLocation = C:\Users\scomaction\AppData\Local\SCOM\Logs\OMServer.log
    Property(S): PackageCode = {58EFE971-58C1-4DBD-A400-A7607A745475}
    Property(S): ProductState = -1
    Property(S): PackagecodeChanging = 1
    Property(S): REBOOT = ReallySuppress
    Property(S): CURRENTDIRECTORY = C:\Users\scomaction\AppData\Local\SCOM\Setup
    Property(S): CLIENTUILEVEL = 3
    Property(S): MSICLIENTUSESEXTERNALUI = 1
    Property(S): CLIENTPROCESSID = 4472
    Property(S): MsiSystemRebootPending = 1
    Property(S): VersionDatabase = 300
    Property(S): VersionMsi = 5.00
    Property(S): VersionNT64 = 602
    Property(S): WindowsBuild = 9200
    Property(S): ServicePackLevel = 0
    Property(S): ServicePackLevelMinor = 0
    Property(S): MsiNTProductType = 3
    Property(S): WindowsFolder = C:\Windows\
    Property(S): WindowsVolume = C:\
    Property(S): System64Folder = C:\Windows\system32\
    Property(S): SystemFolder = C:\Windows\SysWOW64\
    Property(S): RemoteAdminTS = 1
    Property(S): TempFolder = C:\Users\SCOMAC~1\AppData\Local\Temp\
    Property(S): ProgramFilesFolder = C:\Program Files (x86)\
    Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
    Property(S): AppDataFolder = C:\Users\scomaction\AppData\Roaming\
    Property(S): FavoritesFolder = C:\Users\scomaction\Favorites\
    Property(S): NetHoodFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
    Property(S): PersonalFolder = C:\Users\scomaction\Documents\
    Property(S): PrintHoodFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
    Property(S): RecentFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Recent\
    Property(S): SendToFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\SendTo\
    Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
    Property(S): CommonAppDataFolder = C:\ProgramData\
    Property(S): LocalAppDataFolder = C:\Users\scomaction\AppData\Local\
    Property(S): MyPicturesFolder = C:\Users\scomaction\Pictures\
    Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
    Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
    Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
    Property(S): DesktopFolder = C:\Users\Public\Desktop\
    Property(S): FontsFolder = C:\Windows\Fonts\
    Property(S): GPTSupport = 1
    Property(S): OLEAdvtSupport = 1
    Property(S): ShellAdvtSupport = 1
    Property(S): MsiAMD64 = 6
    Property(S): Msix64 = 6
    Property(S): Intel = 6
    Property(S): PhysicalMemory = 8192
    Property(S): VirtualMemory = 7854
    Property(S): AdminUser = 1
    Property(S): MsiTrueAdminUser = 1
    Property(S): LogonUser = scomaction
    Property(S): UserSID = S-1-5-21-607126847-70518424-489426498-210484
    Property(S): UserLanguageID = 2057
    Property(S): ComputerName = SCOMMS1-VM
    Property(S): SystemLanguageID = 2057
    Property(S): ScreenX = 1024
    Property(S): ScreenY = 768
    Property(S): CaptionHeight = 23
    Property(S): BorderTop = 1
    Property(S): BorderSide = 1
    Property(S): TextHeight = 16
    Property(S): TextInternalLeading = 3
    Property(S): ColorBits = 32
    Property(S): TTCSupport = 1
    Property(S): Time = 10:21:27
    Property(S): Date = 22/01/2014
    Property(S): MsiNetAssemblySupport = 4.0.30319.17929
    Property(S): MsiWin32AssemblySupport = 6.2.9200.16384
    Property(S): RedirectedDllSupport = 2
    Property(S): MsiRunningElevated = 1
    Property(S): USERNAME = Windows User
    Property(S): DATABASE = C:\Windows\Installer\4b8344.msi
    Property(S): OriginalDatabase = F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    Property(S): UILevel = 2
    Property(S): ACTION = INSTALL
    MSI (s) (D4:A0) [10:21:27:697]: Note: 1: 1708
    MSI (s) (D4:A0) [10:21:27:698]: Product: System Center Operations Manager 2012 Server -- Installation operation failed.
    MSI (s) (D4:A0) [10:21:27:698]: Windows Installer installed the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.1.10226.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
    MSI (s) (D4:A0) [10:21:27:744]: Deferring clean up of packages/files, if any exist
    MSI (s) (D4:A0) [10:21:27:744]: MainEngineThread is returning 1603
    MSI (s) (D4:30) [10:21:27:744]: No System Restore sequence number for this installation.
    === Logging stopped: 22/01/2014 10:21:27 ===
    MSI (s) (D4:30) [10:21:27:746]: User policy value 'DisableRollback' is 0
    MSI (s) (D4:30) [10:21:27:746]: Machine policy value 'DisableRollback' is 0
    MSI (s) (D4:30) [10:21:27:746]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (D4:30) [10:21:27:746]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (D4:30) [10:21:27:746]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (D4:30) [10:21:27:746]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (s) (D4:30) [10:21:27:747]: Destroying RemoteAPI object.
    MSI (s) (D4:B0) [10:21:27:747]: Custom Action Manager thread ending.
    MSI (c) (78:34) [10:21:27:748]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (c) (78:34) [10:21:27:749]: MainEngineThread is returning 1603
    === Verbose logging stopped: 22/01/2014 10:21:27 ===
    Any assistance anyone can provide will be greatly appreciated.

    Verify from permission of user that you use it in upgrade, make sure that scom machine and user that you use it in upgrade in sysadmin group in database of operationsManager and OperationsManagerDW
    Also Verify from Prerequisites of Upgrade SCOM 2012 sp1 as below link
    http://technet.microsoft.com/en-us/library/jj656654.aspx
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

  • Call Manager Migration 7.1.5 to 9.1 / Trunking : ICT vs. SIP

    Hello All,
         Currently studying for CCNA Voice and have been asked by my current employer to upgrade CUCM 7.1.5 to 9.1.1. There has been a time frame put on the deployment however I want to dig pretty deep into the deployment to learn as much as possible. I am going to start by configuring a trunk between the 2 call manager clusters. from there I will add users to the new call manager and try to convert slowly to the new call manager instead of one big cutover. I will place a route pattern over the trunk so that cucm 9.1 will route through cucm 7.1 while I slowly convert users to the new system. I will then deploy directory numbers in a Staging partition that is not associated with any CSS. Once I have all users and phones configured on the new 9.1 call manager I want to use the bulk admin tool to change the staging partition to the working internal_PT production partition. The users will be imported from LDAP.  My questions are, does this sound like a feasible plan?  Is there any other difference between a SIP trunk and ICT besides the SIP and H.323 protocol? ( I prefer SIP from what I have read) and will having the same users on both boxes interfere with call processing, if these users and phones are not active yet?

    Just for the record. I found the solution to my problem. Checking more logs I read this:
    The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.
    "/usr/local/cm/script/cm-dbl-ontape_backup-install RU PostInstall 9.1.2.11900-12 7.1.5.30000-1 /usr/local/cm/ /common/component/database /common/log/install/capture.txt " terminated. Exceeded max time (240)
    The system will now halt.
    So I accessed the Dissaster Recovery Section on CUCM and deleted the tape backup device that was configured there. After deleting it the upgrade went well.

  • Do I get full conference call management options on iPhone 6 model A1549 if using it with GSM carriers?

    I have iPhone 6 model A1549, bought from and currently using with Verizon. You all must be aware that we can use the same phone for GSM carriers like at&t as well. Now we all know that some of the features related to conference calling are not available on CDMA carriers, like we cant have more than 2 callers, and we can't manage conference calls by making the conversation with one party private for some time and again switching back to conference mode, disconnecting a particular party instead of having to end the entire call etc. reference link- iPhone: Understanding phone features - Apple Support These features are available on GSM models and carriers, I just wanted to ask if I use a GSM SIM from a GSM carrier on this model, do I get these additional conference call management options or I am restricted to Verizon like experience while being on at&t (and while using the at&t SIM in this model)

    Yes, I am dealing with this right now on at&t with a 6 plus. I've been down the same road as you. I got it to work with a windows phone yesterday but not my 6 plus when I switched back to the iPhone. My wifes 6 works fine. I believe it is an at&t issue and not an 8.3 issue. After dealing through several levels of support at at&t, they are telling me it has to do with their transition to hd voice. Some people are having this issue because they are updating their system and some peoples phone profile, on phones that have hd voice capabilities, are not getting added to their line and call forwarding will not work without it. I have a trouble ticket open to their engineering dept and they promise it will work for me on or before the 24th of april. Engineering has to build my phones profile so call forwarding will work with my iPhone.
    This is frustrating because like you, I need to forward my calls because I have no signal in my office and need to forward to another phone so I can get my calls. If at&t would quit dragging their feet and enable wifi calling, this wouldn't be an issue for me. I would suggest you put more pressure on at&t and escalate this until it gets resolved. Or put your sim in a phone that does not have hd voice capability and see if it works then.
    Good luck. I'm keeping my fingers crossed this will be fixed for me on or before the 24th. We'll see.
    EDIT: I see you did put it in another phone and it worked. That backs up that the issue is at&t and their hd voice upgrades. They had no explanation as to why some work and some don't, but have them make sure a profile for your phone is on the line. If not, they'll need to build one for the phone so that it''l work. At least that's the story for now. Like I said, I'll know more in a day or two.

  • Is it possible to take the CDR data from a v4.2 Call Manager and copy it to a separate server where it would be made available for reporting?

    Is it possible to take the CDR data from a v4.2 Call Manager and copy it to a separate server where it would be made available for reporting? We are not interested in migrating the CDR data to v6 because of the concerns it introduces to the upgrade process. Is it possible to get the raw data and somehow serve it from a different machine? (knowing it would be 'old' data that stops as of a certain date). If so, what would be the complexity involved in doing so?
    It seems like the CDR data lives within MSSQL and the reporting interface is within the web server portion of the Call Manager... that's as far as we've dug so far.

    Hi
    It is absolutely possible to get the data - anyone you have in your org with basic SQL skills can move the data off to a standalone SQL server. This could be done most simply by backing up and restoring the DB using SQL Enterprise Manager.
    Moving the CAR/ART reporting tool would be more difficult... if you do actually use that for reporting (most people find it doesn't do what they need and don't use it for anything but basic troubleshooting, and get a third party package) then the best option may be to keep your publisher (possibly assigning it a new IP) and leave it running for as long as you need reporting.
    You would then need a new server to run your upgraded V6 CCM; you may find you need this anyway.
    Regards
    Aaron
    Please rate helpful posts...

Maybe you are looking for

  • MOVEMENT TYPES IN SD

    HI SAP GURUS, Movement types used in these activities and also STO ( PLANT TO DEPO), (DEPO TO PLANT )  WIT AND WITHIN  1 COMPANY CODES AT  PGI AT BILLING AT RETURNS all possible ways OR any short cuts points are to be rewarded for best relevent answe

  • List of all Weblogic versions

    I am looking for a list of the all the Weblogic server versions e.g. 8.1.3, 8.1.5, 8.1.6, then is the next version 9.1.

  • GP Action Assignment to a role

    I have a create <> approve request process Need to understand following scenario 1. I have assigned approval step to the a Role/Group rather than an individual user. The whole group has a common inbox that they would be able to open from their respec

  • Performance cfif vs cfswitch

    With cfswitch code is more readable so no dought it should be used. But I am wondering if using cfswitch improves/affects performance of website or no? thanks

  • Iphoto deletes my facebook albums

    I'm having a serious issue with my iphoto program! Whenever I use the tool in iphoto to 'share' an album from my iphoto to facebook, I click on share, facebook, new album... & automatically, a pop up appears saying that one of my facebook albums (a d