Service Manager 2012 SP1 consoles hanging or slow performance issue in Virtual Environment

Hii,
We are facing SCSM SP1 console performance issue which is utilizing high CPU and working deadly.
For information, our SCSM is in Virtual environment via Hyper-V.
When running the console over an RDP session to a Hyper-V virtual machine, we have to be careful not to maximize the console so that it will remain fast. If we maximize on the VM, the console is so slow as for it to be unusable.
Can someone share his experience, please?
Regards, Syed Fahad Ali

Hi Sayed,
This is a bug and hopefully Microsoft team will solve it soon. if you can to vote for this bug here
https://connect.microsoft.com/WindowsServer/feedback/details/810667/scsm-console-consumes-a-lot-of-cpu-when-opened-maximized-on-work-item-view-like-all-incidents
Mohamed Fawzi | http://fawzi.wordpress.com

Similar Messages

Service Manager 2012R2 - Hotfix for Service Manager 2012 SP1 secondary Management server

Can the hotfix for the issue described here -
http://blogs.technet.com/b/servicemanager/archive/2013/04/22/service-manager-2012-sp1-secondary-management-server-cannot-set-availability-on-a-health-service-that-doesn-t-exist.aspx
, be applied to a 2012R2 Service Manager environment?
My dilemma; In a Service Manager 2012 SP1 environment, I installed a secondary mgmt server, promoted it, then upgraded to R2. This R2 Primary mgmt server has the error described in the TechNet blog.
The reason this was done, the original primary mgmt server (2012 SP1) resided on the same server as the Portal. This original primary is still at 2012 SP1 with the System Center services disabled.
Again, can the hotfix for Service Manager 2012 SP1 secondary mgmt servers be applied to a Primary mgmt server (or environment, however the hotfix is run) server Service Manager 2012 R2?
Thank you,
Brian VanDam
BVAN in SoCol

Hi,
Hmm, you should probably log a case for this, but my first thought here would be to install a new SCSM 2012 R2 server and promote that one to the new Primary server, then remove the old ones.
Regards
//Anders
Anders Asp | Lumagate | www.lumagate.com | Sweden | My blog: www.scsm.se

System Center Service Manager 2012 SP1 upgrade install error

I am trying to upgrade my SCSM 2012 front end app server to SP1 and am getting these failures in the log when it fails with the error "Service Manager is not in a valid state"
09:07:58:Could not find WCS portal web site in IIS metabase!
09:08:02:***ERROR*** Microsoft System Center 2012 - Service Manager: Microsoft System Center 2012 - Service Manager is not in a valid state.
09:08:02:Application Ended
09:08:02:-222
Can someone tell me how to get this rectified? The WCS portal is installed and running and has been for months. The DW is upgraded but I cannot get the SharePoint self service portal or the App server to upgrade due to this error.

Hello
One question you have the website installed on the same
server on which you have the Server Management
Server, so if you can
not make your upgrade to
SP1, this changed because
a prerequisite of System Center Service
Manager 2012 SP1 in which you can not have
the server Mangement and
website on the same server they have to be
separate.

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.

SCCM 2012 connector not working roperly in Service Manager 2012 Sp1

I'm using SCSM 2012 Sp1 and I've SCCM 2012 in my environment. I already configured the SCCM connector in SCSM. But it not showing the software inventory on the software tab. Reather then software inventory it showing every things.
Please any one help me to solve this issue.
Mithun Dey Web: http://cloudmithun.wordpress.com If this may give your necessary resolution please mark it as Answre.

Hi
It can be the
Asset Intelligence that you have to enable in SCCM.
Look here how you do it:
http://www.windows-noob.com/forums/index.php?/topic/1225-what-is-asset-intelligence-and-how-can-i-use-it-in-sccm/
Remy BOVI

Service manager 2012 sp1 notifications

I get trouble with SCSM notifications. One day I created notifications for incidents and request, and off them, but at next day, when I ON they I have a trouble: after ON notifications I get email's for incidents and request for older
month. Why SCSM send me an old notifications?
P. S.
1. Notific-s configure - when object is created send email to affected user
2. When object status change to resolve - also send email to affected user

Are you the affected user in Incident and Service Request Work items that you are getting notications for, or are you getting these notifcations regardless?

Service Manager 2012 R2 is not in a valid state.

I currently have Service Manager 2012 SP1 with update roll up 4 installed on our server. I also installed the web portal on the same server. later I installed the web portal on a separate server(I could not remove the web portal as we had already
started using the server and I can not just uninstall the web portal. I stopped the data warehouse jobs and updated the Data warehouse to 2012 R2 with no problems and started the update for the service manager server and I get an error when the setup
splash shows up " Microsoft System Center 2012 R2 Service Manager is not in a valid state". this is now a production server. I have backuped the DB and the management packs. for worst case. I have tried to run the update from all
user accounts I can think of I even detached the date warehouse thinking that some of the jobs had not stopped. I found a few links online regaurding the removal of the web portal with out removing the management server but I don't want to do
this on a production server. I am now stuck with a 2012 R2 data ware house( I can't use) and a 2012 SP1 management server and web portal. please help!!

here is the SCSM setup wizard log (part of it)
this is what I have found "Could not find WCS portal web site name in setup registry!"
the web portal was installed and sharepoint was never installed then moved to a different server..
how do I remove the self-service portal and web parts of service manager with out removing the management server. (having to back up MPs and DBs and restoring them)
05:59:45:All vital setup files found.
05:59:45:Upgrading Service Manager 7.5.2905 with 7.5.3079
05:59:45:Checking dependencies for Server upgrade...
05:59:47:Getting Management Group information from PMR-SC-SM:ServiceManager
05:59:47:[GetManagementGroupPropertiesFromDB]: Opened the DB connection using Data Source=PMR-SC-SM;Initial Catalog=ServiceManager;Integrated Security=True;Persist Security Info=False.
05:59:47:[GetManagementGroupPropertiesFromDB]: Found Management Group information.
05:59:47:[GetManagementGroupPropertiesFromDB]: Found Primary SDK server:PMR-SC-SM.adi.local.
05:59:47:Validating SmAdminRoleGroup
05:59:47:Checking dependencies for WCS Portal upgrade...
05:59:47:Could not find WCS portal web site name in setup registry!
05:59:48:***ERROR*** Microsoft System Center 2012 R2 Service Manager: Microsoft System Center 2012 R2 Service Manager is not in a valid state.

How to create drop down option in service manager 2012 incident portal

Hii,,
Please assist how to create drop down option in service manager 2012 SP1 default incident portal. We would like to provide the drop down option in "Please enter the title for the Issue" to our users.
Regards, Syed Fahad Ali

As was already referenced, you could use a Simple List for the prompt, however if you are referring to the default General Incident that is available out-of-the-box, you might be limited in what you can modify.
I did some work for a client, that wanted to have a list and other options for the General Incident through the Portal. So, I ended up having to create a custom General Incident instead of using the default one, which will then allow you to add any type
of prompts, and configure them as you want (i.e. with a simple list).

High Watermark issue with monitoring Service Manager 2012 R2

Hi,
Our customer has a Service Manager / Operations Manager 2012 R2 environment where SCOM will regularly generate an alarm related to High Watermark monitoring on the Service Manager data warehouse - not every day though. The alarm looks like this:
Value of 3559 is not higher than 3559
This value hasn't changed for weeks.
Having done a lot of searching we have found nothing but reference to the same recurring flow of information where people keep mentioning different values but there is no conclusion of what this might be caused by and how to solve it. The solutions
have become outdated anyway. Here is one example:
http://social.technet.microsoft.com/forums/systemcenter/en-US/889af8f3-cdf8-4d88-ae99-5dbe18d529ef/service-manager-2012-data-warehouse-high-watermark-monitor
The Service Manager Database Account in SCOM is our service account that has sysadmin in SQL. Basically, with regards to the security configuration, our customer should be covered.
To my knowledge agent-based and agentless monitoring have both been supported since SCSM 2012 SP1. Also, we have the latest management pack for Service Manager monitoring in SCOM, at the moment this should be
7.5.3079.0.
As mentioned above the value has not been changing for quite some time and nor has it in the database.
My questions are the following:
- Is there anyone that has found a solution in the meantime, especially with regards to R2?
- What is the purpose of High Watermark monitoring for the data warehouse? Why does this need to be monitored?
- We would like to understand the nature of this value better. Should it be higher each day compared to the day before?
- Could it just be overriden in SCOM?
Many thanks in advance!

Rather unexpectedly, the SCOM alarm disappeared overnight and when checking the workflow in the incident that was generated from the alarm, the incident got a Resolved status right before midnight at 23:59:58. We have a ConfigMgr connector that is scheduled
to run at 23:00 which we had disabled a day ago to check something else. But I don't think it had anything to do with this. As the alarm has disappeared from the SCOM console, we have also checked the registry values. Now, instead of "3559 3559 3559"
it says "3559 3559 3585". We have had the 3559 value since 18th July, and out of a sudden something must have been triggered, causing the value to increase. What was triggered and how, no idea... Not sure either what it means that only one of the
Three numbers have been updated with a new value. When talking about the DW jobs, using the SMlets we can see every day that, MPSync, DWMaintenance and the ETL jobs are working well. What we have had though for a longer time is that the cube processing
tends to have issues once a week, where processing won't finish and the cubes get hanging in a running state. We can fix that manually every time and often we don't even have to touch DWMaintenance or the ETL jobs, we don't need to go beyond manually
working with the cube processing jobs themselves. So it might not have an impact on the ETL jobs themselves. Occasionally we do find ourselves in a situation where we we need to play around in the SQL database and manually set the required value (can't
recall if it's 3, 6 or 7) cause we get an error in the DWMaintenance batch, but even though that's an occasional issue it's not constant and also something we can solve, and furthermore it's another known issue outside of the high watermark issue. So
we are a bit uncertain but can at least see that something works sometimes that sometimes increases the high watermark value :). In our case.

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"

RU2 install fails for Service Manager 2012 R2

Rollup Update 2 for Service Manager 2012 R2 is crashing during install on my prod management server...it installed fine on my test server. It happens very quickly after I click "install", just after agreeing to the license terms. I've ran
the .Net repair tool, but did not fix it. I've pasted the SCSMPatcherSetupWizard01.log file contents below, but the log seems to have just stopped abruptly.
Description:
Stopped working
Problem signature:
Problem Event Name:   CLR20r3
Problem Signature 01:   scsm2012_amd64_patchwizard.exe
Problem Signature 02:   7.5.3079.61
Problem Signature 03:   534468e0
Problem Signature 04:   mscorlib
Problem Signature 05:   2.0.0.0
Problem Signature 06:   5265c965
Problem Signature 07:   34a9
Problem Signature 08:   1c5
Problem Signature 09:   System.IO.IOException
OS Version:   6.1.7601.2.1.0.272.7
Locale ID:   1033
SCSMPatcherSetupWizard01.log:
2014-05-01T12:58:49.2025363-05:00   Always:   Trace Session Started
12:58:49:
12:58:49:Application Started
12:58:49:This is 64-bit application.
12:58:49:LoadQuickFixEngineeringDetails: Loading entries from the xml file C:\Users\serviceman\AppData\Local\Temp\3\WZSE0.TMP\SCSMPatcher\QFEList.xml
12:58:49:LoadQuickFixEngineeringDetails: Found data for POSTINSTALL
12:58:49:LoadQuickFixEngineeringDetails: Found entry SCSM2012R2_KB2904710_AMD64
12:58:49:LoadQuickFixEngineeringDetails: Done loading QuickFixEngineering File
12:58:49:Start adding DataItems
12:58:49:Final Install Tasks
12:58:49:Done adding DataItems
12:58:49:Current UI culture (en-US) is not supported. Using Parent culture.
12:58:49:Found C:\Users\serviceman\AppData\Local\Temp\3\WZSE0.TMP\SCSMPatcher\en\EULA_QFEKB2904710.rtf.
12:58:49:Found C:\Users\serviceman\AppData\Local\Temp\3\WZSE0.TMP\SCSMPatcher\SCSM2012R2_CU_KB2904710_AMD64_7.5.3079.61.msp.
12:58:49:All vital setup files found.
12:58:54:ProcessInstalls: MSI is not in silent mode. Setting the external UI.

More info:  This thread suggested that fully patching their server resolved their issue, but I can confirm my server was fully up to date with all critical, security, and updates for Server 2008 R2 SP1 through 04/2014. I have .Net Framework
4 Client profile and Extended installed with their patches current. I wonder if upgrading to .Net 4.5 would have prevent this?
http://social.technet.microsoft.com/Forums/en-US/b4dea854-3191-4b9a-9aa1-1fbf8b37c077/system-center-service-manager-sp1-update-rollup-2-error?forum=systemcenterservicemanager
I also found a this article that talks about deploying the .MSP without the Patchwizard.exe wrapper, so sounds like I should be good.
The *Patchwizard.exe file is just a wrapper, so if you have a tool like Configuration Manager you can use the .MSP file directly for deployment and skip deploying the executable. This is a fully supported scenario so if that better suites your needs
then feel free to deploy the update using this method instead.
http://blogs.technet.com/b/servicemanager/archive/2013/07/16/deploying-the-msp-file-from-a-service-manager-update-rollup-using-configuration-manager.aspx

Service Manager 2012 R2 report libraries don't deploy

So I've got a fresh install of Service Manager 2012 R2 with SQL Server '08 R2 in the 4 server layout, everything on Hyper-V. My issue is this: after registering the data warehouse, everything appears to function normally, the MPSyncJob completes its first
pass and other jobs show up in the list but the reports section of the management console is never populated. All of the management packs deploy just fine except for the report libraries and there is no indication/logs of issues on any of the servers. I've
gone through the manual setup setups for SSRS several times with no change in results. This is the 4th full reinstall of Service Manager with the same result.
Any thoughts? Is there any way to tell whether or not SSRS is actually functioning as intended? Are there any special database permissions that need to be configured for the DW reports service account (I have read all set)?

here is the SCSM setup wizard log (part of it)
this is what I have found "Could not find WCS portal web site name in setup registry!"
the web portal was installed and sharepoint was never installed then moved to a different server..
how do I remove the self-service portal and web parts of service manager with out removing the management server. (having to back up MPs and DBs and restoring them)
05:59:45:All vital setup files found.
05:59:45:Upgrading Service Manager 7.5.2905 with 7.5.3079
05:59:45:Checking dependencies for Server upgrade...
05:59:47:Getting Management Group information from PMR-SC-SM:ServiceManager
05:59:47:[GetManagementGroupPropertiesFromDB]: Opened the DB connection using Data Source=PMR-SC-SM;Initial Catalog=ServiceManager;Integrated Security=True;Persist Security Info=False.
05:59:47:[GetManagementGroupPropertiesFromDB]: Found Management Group information.
05:59:47:[GetManagementGroupPropertiesFromDB]: Found Primary SDK server:PMR-SC-SM.adi.local.
05:59:47:Validating SmAdminRoleGroup
05:59:47:Checking dependencies for WCS Portal upgrade...
05:59:47:Could not find WCS portal web site name in setup registry!
05:59:48:***ERROR*** Microsoft System Center 2012 R2 Service Manager: Microsoft System Center 2012 R2 Service Manager is not in a valid state.

VMM 2012 SP1 Console Fail Installation With Error 1603

Dear Sir,
I am trying to install VMM 2012 SP1 console on my management Windows 8 Enterprise machine, but it's failing:
[Installing C:\Users\XXXXX\Desktop\VMM 2012 SP1\amd64\setup\msi\Client\AdminConsole.msi failed with Windows Installer error 1603.
See C:\ProgramData\VMMLogs\AdminConsole.log for more information. After resolving the problem, retry setup.]
I am admin with full permission, and the machine is joined to the domain.
Please find below VMMlogs for more information:
Property(S): CountComponentClients = DAFEE2F2-CF16-47f5-94A7-725D0795BCB9
Property(S): RegisterCmdlets = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installUtil.exe" /LogFile= /LogToConsole=false "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Microsoft.SystemCenter.VirtualMachineManager.dll"
Property(S): RollbackCmdlets = "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installUtil.exe" /u /LogFile= /LogToConsole=false "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Microsoft.SystemCenter.VirtualMachineManager.dll"
Property(S): TRANSLATE_SID = S-1-5-11
Property(S): TRANSLATE_SID_PROPERTYNAME = AUTHENTICATEDUSERS
Property(S): AUTHENTICATEDUSERS = Authenticated Users
Property(S): DeleteAddInsOldFolder = "C:\Windows\SysWOW64\cmd.exe" /C rmdir "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\AddInPipeline\AddIns.old" /S /Q
Property(S): RenameAddInsFolder = "C:\Windows\SysWOW64\cmd.exe" /Q /C ren "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\AddInPipeline\AddIns" "AddIns.old"
Property(S): ProgramFiles64Folder = C:\Program Files\
Property(S): TARGETDIR = F:\
Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(S): SourceDir = C:\Users\supercharo\Desktop\VMM 2012 SP1\amd64\setup\msi\Client\
Property(S): HelpDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\help\
Property(S): psModulesDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\psModules\
Property(S): INDIGOPORT = 8100
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {CDFB453F-5FA4-4884-B282-F46BDFC06051}
Property(S): ProductLanguage = 1033
Property(S): ProductName = Microsoft System Center Virtual Machine Manager Administrator Console (x64)
Property(S): ProductVersion = 3.1.6011.0
Property(S): INSTALLLEVEL = 100
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): ALLUSERS = 1
Property(S): BOOTSTRAPPED = 0
Property(S): REREGBINDIR = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\wwwroot\bin\
Property(S): SecureCustomProperties = ANYVERSION
Property(S): Trace.3812768D_658A_4BB6_9A68_F288BE3E9CF5 = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\
Property(S): RegisterEventManifest = "wevtutil.exe" im "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\VmmEtwEvents.Man"
Property(S): RollbackRegisterEventManifest = "wevtutil.exe" um "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\VmmEtwEvents.Man"
Property(S): ExecXmlFile = 2€0€C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\VmmEtwEvents.Man€7€1€/*/*/*/*[@messageFileName]€messageFileName€C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\Microsoft.VirtualManager.EtwResources.dll€2€0€C:\Program
Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\VmmEtwEvents.Man€7€1€/*/*/*/*[@resourceFileName]€resourceFileName€C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\Microsoft.VirtualManager.EtwResources.dll
Property(S): MsiLogFileLocation = C:\ProgramData\VMMLogs\AdminConsole.log
Property(S): PackageCode = {A96E8FEC-A027-4FF8-A395-1ECC0C460677}
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): INSTALLINGLANGUAGE = 1033
Property(S): REBOOT = ReallySuppress
Property(S): CURRENTDIRECTORY = C:\Users\supercharo\AppData\Local\Temp\VMB790.tmp\Setup
Property(S): CLIENTUILEVEL = 3
Property(S): MSICLIENTUSESEXTERNALUI = 1
Property(S): CLIENTPROCESSID = 968
Property(S): VersionDatabase = 301
Property(S): VersionMsi = 5.00
Property(S): VersionNT = 602
Property(S): VersionNT64 = 602
Property(S): WindowsBuild = 9200
Property(S): ServicePackLevel = 0
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
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\SUPERC~1\AppData\Local\Temp\
Property(S): ProgramFilesFolder = C:\Program Files (x86)\
Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Users\supercharo\AppData\Roaming\
Property(S): FavoritesFolder = C:\Users\supercharo\Favorites\
Property(S): NetHoodFolder = C:\Users\supercharo\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(S): PersonalFolder = C:\Users\supercharo\Documents\
Property(S): PrintHoodFolder = C:\Users\supercharo\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(S): RecentFolder = C:\Users\supercharo\AppData\Roaming\Microsoft\Windows\Recent\
Property(S): SendToFolder = C:\Users\supercharo\AppData\Roaming\Microsoft\Windows\SendTo\
Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(S): CommonAppDataFolder = C:\ProgramData\
Property(S): LocalAppDataFolder = C:\Users\supercharo\AppData\Local\
Property(S): MyPicturesFolder = C:\Users\supercharo\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): 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 = 32695
Property(S): VirtualMemory = 58675
Property(S): AdminUser = 1
Property(S): MsiTrueAdminUser = 1
Property(S): LogonUser = supercharo
Property(S): UserSID = S-1-5-21-3202008507-3906799607-3053210984-500
Property(S): UserLanguageID = 1033
Property(S): ComputerName = CHARO-Z1
Property(S): SystemLanguageID = 1033
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 = 23:20:44
Property(S): Date = 2/17/2013
Property(S): MsiNetAssemblySupport = 4.0.30319.17929
Property(S): MsiWin32AssemblySupport = 6.2.9200.16384
Property(S): RedirectedDllSupport = 2
Property(S): MsiRunningElevated = 1
Property(S): Privileged = 1
Property(S): USERNAME = CHARO
Property(S): DATABASE = C:\Windows\Installer\113cc0a.msi
Property(S): OriginalDatabase = C:\Users\supercharo\Desktop\VMM 2012 SP1\amd64\setup\msi\Client\AdminConsole.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): ComponentCount = 0
Property(S): ROOTDRIVE = F:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SOURCEDIR = C:\Users\supercharo\Desktop\VMM 2012 SP1\amd64\setup\msi\Client\
Property(S): SourcedirProduct = {CDFB453F-5FA4-4884-B282-F46BDFC06051}
Property(S): ProductToBeRegistered = 1
MSI (s) (DC:2C) [23:20:44:051]: Note: 1: 1708
MSI (s) (DC:2C) [23:20:44:051]: Product: Microsoft System Center Virtual Machine Manager Administrator Console (x64) -- Installation failed.
MSI (s) (DC:2C) [23:20:44:052]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager Administrator Console (x64). Product Version: 3.1.6011.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation
success or error status: 1603.
MSI (s) (DC:2C) [23:20:44:067]: Deferring clean up of packages/files, if any exist
MSI (s) (DC:2C) [23:20:44:068]: MainEngineThread is returning 1603
MSI (s) (DC:A4) [23:20:44:072]: RESTART MANAGER: Session closed.
MSI (s) (DC:A4) [23:20:44:072]: No System Restore sequence number for this installation.
=== Logging stopped: 02/17/2013 23:20:44 ===
MSI (s) (DC:A4) [23:20:44:076]: User policy value 'DisableRollback' is 0
MSI (s) (DC:A4) [23:20:44:076]: Machine policy value 'DisableRollback' is 0
MSI (s) (DC:A4) [23:20:44:076]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (DC:A4) [23:20:44:076]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (DC:A4) [23:20:44:077]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (DC:A4) [23:20:44:078]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (DC:A4) [23:20:44:084]: Destroying RemoteAPI object.
MSI (s) (DC:A4) [23:20:44:084]: Custom Action Manager thread ending.
MSI (c) (C8:18) [23:20:44:086]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (C8:18) [23:20:44:086]: MainEngineThread is returning 1603
=== Verbose logging stopped: 02/17/2013 23:20:44 ===
Your help is highly appreciated.
Thank you.
Regards,

Mine is solved.
Was because I removed VMM 2012 R2 on the same host (again, because R2 doesn't do P2V conversions) but the uninstall failed to remove "Microsoft Web Deploy 3.5". When VMM 2012 SP1 installs uses Web Deploy 3.0 and was blocked by the newer version. uninstalled
3.5 and then the console install worked.
hopes this helps someone out there.
Jae

Service Manager 2012 Remote Control

Hello
Is there a way to integrate ConfigMgr 2012 Remote Control to Service Manager 2012 task? I have configured Remote desktop and remote assistance but, my customer specifically looking ConfigMgr 2012 Remote Control.

Hi Manoj,
Yes, when you create a new task under Library > tasks, fill in the general information such as the Task Name, Target Class, and Management Pack. Optionally, you may select categories to add the task to be displayed in certain places in the console. When
you fill in the full path to the command line, ensure that the machines that are running the service manager console have access to this path. If Configuration Manager is installed on the computer(s) running the Service Manager Console, you may fill in the
path as C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\i386\CmRcViewer.exe. You also have to option to insert a parameter or working directory as well if you choose to. For example, if you would like the parameter to be the Windows
Computer IP address, you may enter the following:
$Context/Path[Relationship='CustomSystem_WorkItem_Library!System.WorkItemAboutConfigItem' TypeConstraint='CustomMicrosoft_Windows_Library!Microsoft.Windows.Computer']/Property[Type='CustomMicrosoft_Windows_Library!Microsoft.Windows.Computer']/IPAddress$
Another way to set this parameter would be by selecting Insert and selecting the property for IP Address.
Once the task has been created, you can verify it is working properly by navigating to the class/categories you have chosen and it should be listed by the Task Name you entered.
Katie Dyer | [email protected] | San Diego, CA
Check out our System Center App Store: www.cireson.com/app-store

Configuration Manager 2012 SP1 updates

Hi,
Are there any updates to Config Manager 2012 sp1 other than the Cumulative updates?
I see there are 3 cumulative updates but each say to not install unless a specific fix is needed.
I am not sure if any of the fixes might fix some problem that we might not have today but could later.
Should we just not upgrade or should we apply the CU1, 2 and 3 even though we dont have any specific problems?
Thanks Lance

Lance,
There are actually 4 Cumulative updates. The patches are cumulative so you only apply the latest.
http://sccmentor.wordpress.com/2014/01/29/cumulative-update-4-for-system-center-2012-configuration-manager-service-pack-1-is-now-available/
As to installing, it depends if you have any currently issues that are addressed by the patches or need to support Windows 8.1 in anyway, in which case you would have to go with CU3 and above.
Personally I like to keep the system up to date but with any update fix there's always the chance of it introducing a new issue,
Cheers
Paul | sccmentor.wordpress.com

Service Manager 2012 SP1 consoles hanging or slow performance issue in Virtual Environment

Similar Messages

Maybe you are looking for