Scheduling Operations Manager Maintenance mode?
I'm trying to schedule Stephan Stranger's SCOM Maintenance mode script. The issue is that I don't see a good way to pass the parameters the scripts
is looking for via the Scheduled Task.
Is there a good way to pass the scripts needed parameters like group name and maintenance mode duration? Maybe I need to write a batch file and call the .ps1 and arguments from the .BAT - I've been playing with the .BAT for over an hour and can't that
to work either.
Currently when I create a scheduled task with these settings:
Program/script:
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add Aurguments (optional):
-noexit C:\Scripts\MaintMode\Start-SCOMMaintenanceModeForGroups.ps1 "TestingDSRGroup" -endtime 5 -reason "unplannedother" -comment "Testing DSR Group" -Verbose
It seems to just run in the background with out popping up a powershell window and will eventually end with a (0x1) Last Run Result.
Here is the syntax that works great from with in powershell with Stephan's script but I can't seem to work from a scheduled task:
C:\Scripts\MaintMode\Start-SCOMMaintenanceModeForGroups.ps1 "Testing DSR Group" -endtime 5 -reason "unplannedother" -comment "Testing DSR Group" -Verbose
Any assistance appreciated.
Hi,
An easy way around this is to use the -File parameter. Write up a quick oneliner that calls your script and save it as a .ps1 file. As soon as you have a working caller script, you can use -File C:\path\to\script.ps1 as the arguments and the scheduler will
just run your script instead of trying to specify all of your parameters directly.
Don't retire TechNet! -
(Don't give up yet - 12,830+ strong and growing)
Thanks Mike. That did the trick. I tried the -FILE argument previously with no luck, I should have mentioned that in my original post.
Once I created a .PS1 with the arguments I needed and then called that with the scheduled task it went off with out a hitch. Thanks a milion. I never would have thought of that.
Similar Messages
-
How to schedule Maintenance Mode in SCOM 2012?
Hi
How do I schedule Maintenance Mode in SCOM 2012? Do we have any tool for 2012 like we had with 2007?
Regards,
Akhilesh
Thanks, AkhileshYep - to add a calendar takes some extra steps:
E.g.
1) Create a database which includes a table to store information such as:
- target for maintenance mode
- scheduled time for maintenance mode
- Comments
- Duration
- Reason
2) The Service Request fires off an Orchestrator runbook that stores this information in the database
3) Another Runbook that runs frequently that checks the database to see if it should kick off maintenance mode.
It isn't any easy solution for maintenance mode. It works better for more simplistic scheduling e.g. we do implement this kind of logic for environment refreshes and backups where we use the SM Portal and Orchestrator to log a date and then have another
runbook that runs at 2am every day to check if it should execute a backup \ refresh.
Cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/ -
Hi,
We planning to go one level higher to automat and have more dynamic Software Update Management for Windows Servers. We have SCCM 2012 R2, SCOM 2012 R2 and SCO 2012 R2.
Our plan is to pur server in an AD-Group to get Update Schedule, from the servers will be importet to an Collection for Automatic Update and reboot. If I understand Everything right SCOM can't read AD-Group and put then in an Schedule maintenance mode. SCOM
can read reg value as exempel.
IS there any smar way to make the SCOM Maintenance Mode Schedule dynamic?
I found this
http://www.scom2k7.com/scom-2012-maintenance-mode-scheduler/?
/SaiTechYou could use Orchestrator to put the servers from a specific collection, or AD group, in maintenance mode in SCOM. For an example see:
http://www.systemcentercentral.com/orchestrator-how-to-scom-maintenance-mode-for-windows-computers-in-an-sccm-collection/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
Create alert when management server is in maintenance mode
has anyone setup alerting, such that, an alert is generated when a gateway or a management server is put into maintenance mode? (we are assuming there are multiple management servers and gateways)
if so, how did you achieve this?1) You may create a time script monitor to get any server in maintenance mode. Using powershell script get-scommaintenancemode to get server in maintenance mode information.
2) How to create a powershell script monitor
http://scug.be/dieter/2014/04/24/scom-creating-a-powershell-script-monitor-with-silect-mpauthor/
http://www.code4ward.net/main/Blog/tabid/70/EntryId/51/How-to-create-a-Two-State-PowerShell-Script-Monitor-using-the-Authoring-Console-Part-1.aspx
3) For powershell get-scommaintenancemode, pls refer to
http://technet.microsoft.com/en-us/library/hh920235(v=sc.20).aspx
Roger -
Powershell script for put the particular service in to Maintenance mode
Hi Everyone,
I have requinquent to schedule the Maintenance mode for service. If anyone help with script to put the service into maintenance mode, then i can schedule the same through Task Scheduler.
Thanks in advance.
Regards
KarthickHi,
Please have a look on:
http://technet.microsoft.com/en-us/library/hh918505(v=sc.20).aspx
http://blog.coretech.dk/msk/operations-manager-2012-maintenance-mode/
Cheers
Christoph Maresch | My blogs: blog.cmaresch.at | XING:
Christoph Maresch
| Linkedin:
Christoph Maresch -
Maintenance Mode For One Monitor
Is it possible to place one monitor in maintenance mode? Not the entire computer or object, but just that one monitor? I don't want other monitors for that object to be silenced though.
Hi,
A Windows Schedule task,
http://technet.microsoft.com/en-us/library/cc748993.aspx
Please read this one:
Management Pack for the SCOM 2012 Maintenance Mode Scheduler
http://blog.tyang.org/2014/05/22/management-pack-scom-2012-maintenance-mode-scheduler/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
Failed to get Monitor - Start Maintenance Mode
Hi,
Am struggling with a problem with Orchestrator R2 apparently not recognising output from a Monitor alert step in a run book. I have Orchestrator 2012R2 and SCOM 2012R2 configured. Orchestrator is co-located with VMM2012R2.
Operating system for all is Windows server 2012
I have installed and deployed the Orchestrator R2 Integration packs which in deployment manager state version 7.2
I have checked to ensure that both Orchestrator, SCOM and VMM are all R2 (They are)
I am looking to create a runbook that will start services as per the link here: (Thanks to Jakob for this)
http://blog.coretech.dk/jgs/sco-2012-scom-2012-best-practice-monitor-alert-and-restart-a-service/
I can test the connection to the SCOM server - fine
I create the monitor alert step and test - fine
I create the start maintenance mode step and get the following error:
Filed to get Monitor. The exception was "An object of class MonitoringObject with ID 00000000-0000-0000-0000-000000000000 was not found.".
I have used the runbook tester and the monitoringobjectfullname is present in the output for the start maintenance mode step.
However irrespective of the variable that I attempt to use in start maintenance mode step I continue to get the same error as above.
The monitor alert step completes with no issues, but everytime on the start maint mode step it fails.
I have validated the SCOM connection account has all the appropriate SCOM permissions. I have also provided it with full domain admin rights, but with no success.
Any ideas on how to troubleshoot this would be welcomed
Thanks in advanceHi Stefan,
A little extension of your approach as this is only usable if you want to set a Windows Server into Maintenance Mode - but not e.g. for Distributed Apps
I just required the "Start Maintenance Mode" Activity to set a distributed app and a websphere application server instance (which is not linked with the server itself). And I did not find any documentation how to fill the field - only for Windows
Computer.
So I'll post my result on how to get the value which needs to be entered within the "Monitor" field:
(PowerShell - Use "Activities > System > Run .Net Script > Type: Powershell)
Import-Module OperationsManager
$object= Get-SCOMMonitoringObject -displayname "<desired object displayname";
# or use the ID instead:
# $object = Get-SCOMMonitoringObject -ID "<ID of object>";
$name = $object.displayname;
$fullname = $object.fullname;
$monitor = $name + " : " + $fullname
Then put $monitor within "published data" and you can use it directly in the "Start Maintenance Mode" Activity.
This only works if the runbook is running on a SCOM management server as it requires the SCOM Powershell Module. But at least it somehow shows the syntax.
Best Regards
Klaus
Austria -
I want to put a scom gruop into Maintenance. The Management Server is not member of it.
When I use the following Powershell Script with SCOM 2012....
Import-Module OperationsManager
$Instance = Get-SCOMGroup -displayname "<Group>"
$Time = ((Get-Date).AddMinutes(90))
Start-SCOMMaintenanceMode -Instance $Instance -EndTime $Time -Comment "Automatic WSUS Updates" -Reason "PlannedOperatingSystemReconfiguration"
....the Maintenance mode never ends. I have to stop the mode manually. When I use the SCOM Console everything is fine.In my environment, it works but may be in some delay. Moreover, you can use get-scommaintenancemode to watch whether the maintenace mode and schedule end time is correct.
You may be refer to Pete Zerge blog "r OpsMgr 2012: Group Maintenance Mode via PowerShell"
http://www.systemcentercentral.com/opsmgr-2012-group-maintenance-mode-via-powershell-the-way-it-should-be/
Roger -
SCOM 2012 Maintenance Mode PowerShell Script Problems
I've seen other questions about this topic before, but none of them seem to address my specific problem, so I am starting a new thread.
I am writing a script to put a single server (not a group) into maintenance mode. Here is the command that it ultimately tries to call:
Start-SCOMMaintenanceMode-Instance$Instance-EndTime$EndTime-Reason$Reason-Comment$Comment
So an exmaple would look like this:
Start-SCOMMaintenanceMode -Instance "$Instance -EndTime "02/03/2014 15:26:00" -Reason "PlannedOther" -Comment "Testing Maintenance Mode"
When my script tries to run this command, this is the error message that I get:
Start-SCOMMaintenanceMode : Start time must be before end time for maintenance mode.
Parameter name: startTime
At C:\users\x036036\Desktop\Start-SCOMMaintenanceModeForServer.ps1:143 char:21
+ Start-SCOMMaintenanceMode -Instance $Instance -EndTime $EndT ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Microsoft.Syste...anceModeCommand:StartSCMaintenanceModeCommand) [Start-SCOMMaintenance
Mode], ArgumentOutOfRangeException
+ FullyQualifiedErrorId : ExecutionError,Microsoft.SystemCenter.OperationsManagerV10.Commands.StartSCMaintenanceModeCommand
I've tried to look at Start-SCOMMaintenanceMode help online, but I don't see that "startTime" is a parameter. So what is this error message talking about? What am I missing?Thanks for your help. I didn't see your response until just now, but I have been playing around with this all since my last response. I got it to work. I wish I could pinpoint what exactly I changed to get it to work, but I
feel like I've been changing so much stuff that I'm not sure any more.
Just in case anyone finds it useful, here is the code.
[CmdletBinding(SupportsShouldProcess=$true)]
param
[Parameter(Mandatory=$True,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='What is the server you want to put in Maintenance Mode?')]
[Alias("Server")]
[string[]]$ServerName,
[Parameter(Mandatory=$True,
ValueFromPipeline=$false,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Specifies the time the maintenance will end. The minimum amount of time a resource can be in maintenance mode is 5 minutes. This is a required parameter. Format is 1/29/2014 8:59:26 AM')]
[Datetime]$end,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='PlannedOther, UnplannedOther, PlannedHardwareMaintenance, UnplannedHardwareMaintenance, PlannedHardwareInstallation, UnplannedHardwareInstallation, PlannedOperatingSystemReconfiguration, UnplannedOperatingSystemReconfiguration, PlannedApplicationMaintenance, ApplicationInstallation, ApplicationUnresponsive, ApplicationUnstable, SecurityIssue, LossOfNetworkConnectivity')]
[string]$Reason,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Allows you to type a comment about the maintenance activity.')]
[string]$Comment,
[switch]$EventLog
set-strictmode -version latest
#$start=Get-Date
#$currentlog = $start.ToString()
Write-Verbose "Starting $($myinvocation.mycommand)"
Write-Verbose "Ready to put ServerName $ServerName in Maintenance Mode"
Function Start-SCOMMaintenanceModeForServer
[CmdletBinding(SupportsShouldProcess=$true)]
param
[Parameter(Mandatory=$True,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='What is the server you want to put in Maintenance Mode?')]
[Alias("Server")]
[string[]]$ServerName,
[Parameter(Mandatory=$True,
ValueFromPipeline=$false,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Specifies the time the maintenance will end. The minimum amount of time a resource can be in maintenance mode is 5 minutes. This is a required parameter. Format is 1/29/2014 8:59:26 AM')]
[Datetime]$end,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='PlannedOther, UnplannedOther, PlannedHardwareMaintenance, UnplannedHardwareMaintenance, PlannedHardwareInstallation, UnplannedHardwareInstallation, PlannedOperatingSystemReconfiguration, UnplannedOperatingSystemReconfiguration, PlannedApplicationMaintenance, ApplicationInstallation, ApplicationUnresponsive, ApplicationUnstable, SecurityIssue, LossOfNetworkConnectivity')]
[string]$Reason,
[Parameter(Mandatory=$False,
ValueFromPipeline=$True,
ValueFromPipelineByPropertyName=$True,
HelpMessage='Allows you to type a comment about the maintenance activity.')]
[string]$Comment,
[switch]$EventLog
Begin
Write-Verbose "Starting Function Start-SCOMMaintenanceModeForServer"
#Check for minumum Maintenance mode period of 5 mins.
$start = Get-Date
$5MinFromNowTime = $start.AddMinutes(5)
#$end = [datetime]$end
$end = $end.AddSeconds(5)
if($end -lt $5MinFromNowTime)
Write-Error "The time span for the maintenance mode should be at least 5 minutes." -ErrorAction Stop
Write-Verbose "Following server will be put in Maintenance Mode: $ServerName"
$MSs = Get-SCOMManagementServer
} #End Begin
Process
Write-Verbose "Checking if server $ServerName is a Management Server"
#Write-Verbose ($MSs | Select DisplayName)
if(($MSs | Select DisplayName) -eq $ServerName)
Write-Verbose "We don't want to put a Management Server in Maintenance Mode. Skipping"
else
Write-Verbose "Let's put server $ServerName in Maintenance Mode"
$Instance = Get-SCOMClassInstance -Name $ServerName
if ($PSCmdlet.ShouldProcess("Putting $ServerName in Maintenance Mode until $($end).") )
Write-Verbose ("Start-SCOMMaintenanceMode -Instance " + $Instance + " -EndTime " + $end + " -Reason " + $Reason + " -Comment " + $Comment)
Start-SCOMMaintenanceMode -Instance $Instance -end $end -Reason $Reason -Comment $Comment
}#End of whatif
}#End of else
if ($PSBoundParameters['EventLog'])
write-eventlog -LogName "Operations Manager" -Source "OpsMgr SDK Service" -EventID 999 -message "The following Objects are put into in Maintenance Mode until $($end) : $($ServerName)"
}#End if
} #End Process
End
Write-Verbose "Finished Function Start-SCOMMaintenanceModeForServer Function"
#Main
try
if ($PSBoundParameters['EventLog'])
write-eventlog -LogName "Operations Manager" -Source "OpsMgr SDK Service" -EventID 998 -message "The $($myinvocation.mycommand) is used to put Objects in Maintenance Mode"
Write-Verbose "Checking if OperationsManager Module is loaded"
#Check if OperationsManager Module is loaded.
if(!(Get-Module OperationsManager))
Write-Verbose "Importing OperationsManager Module"
Import-Module OperationsManager -ErrorAction Stop
Write-Verbose "Checking for OM2012 environment"
#Check if OM2012 is being used.
if(!(Get-Module OperationsManager).Description -eq "Operations Manager OperationsManagerV10 Module")
Write-Error "This script is only for OM2012"
#Call Function
if ($PSBoundParameters['EventLog'])
Start-SCOMMaintenanceModeForServer -ServerName $ServerName -end $end -Reason $Reason -Comment $Comment -EventLog
else
Start-SCOMMaintenanceModeForServer -ServerName $ServerName -end $end -Reason $Reason -Comment $Comment
} #End Try
catch [System.IO.FileNotFoundException]
"OperationsManager Module not found"
$_.Exception.Message
catch
Write-Warning "Oops something went wrong"
$_.Exception.Message
$end=Get-Date
Write-Debug ("Total processing time {0}" -f ($end-$start).ToString())
Write-Verbose "Ending $($myinvocation.mycommand)"
There is one remaining problem with this script. It does not correctly check to see if something is a management server. We have two management servers. These are the applicable lines, which I still haven't gotten to work yet. First, this retrieves
the list of my Management servers:
$MSs=Get-SCOMManagementServer
Next, these lines are supposed to check if the server I specified is a management server:
if(($MSs | Select DisplayName) -eq $ServerName)
Write-Verbose "We don't want to put a Management Server in Maintenance Mode. Skipping"
Thanks to the Intellisense pop-up deal, I can see that $MSs does get my two management servers. And I can clearly see that there is a DisplayName column. And I can also see that the $ServerName does match what I put in my command line. But it doesn't
seem to catch them if they are actually equal to each other. I don't know if it's because there's two Management Servers, and it doesn't know how to compare like that? Any idea? Is there some sort of loop I need to write so that it compares is to the DisplayName
for EACH Management Server it finds? Any help would be greatly appreciated. -
FWSM maintenance mode - vlan 1
Hi,
A client has had their FWSM fail, when you try to start the module the switch eventually disables the power to that slot (%C6KPWR-SP-4-DISABLED: power to module in slot 4 set off (Module Failed SCP dnld)). I have turned off diagnostics with 'no diagnostic boot level' and then use 'boot device module 4 cf:1' to bring the FWSM up into maintenance mode. I can then session up from the switch and log in to the FWSM as root.
After inputting all the necessary IP info I can't ping anything on vlan 1 as I would expect, I have set the FWSM as 192.168.1.2 and a FTP/TFTP server as 192.168.1.1
I have removed the firewall vlan groups and tried to put them back with just vlan 1 but this isn't accepted (the reasons are covered in other posts on the forum). What am I doing wrong as the instruction say that vlan 1 is the only vlan that is accessable whilst the FWSM is in maintenance mode.
I can create an int vlan 1 in the switch and ping my ftp server so know that the switchport is set up correctly, I can also see that Po308 is formed and when the module boots I can see the Gi4/xx interfaces come up (FWSM is in slot 4).
Any ideas of what to try next?
............and they aren't covered by maintenance agreements
FWSM
Maintenance image version: 2.1(4)
[email protected]#show images
Device name Partition# Image name
Compact flash(cf) 4 c6svc-fwm-k9.3-1-4-0.bin
Switch
SWITCH# sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXI7, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Mon 18-Jul-11 05:49 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)
Regards
MelRecently i met the same problem.
When installing FWSM board on the Catalyst 6509 there is not communication access via vlan1 in the maintenance partition.
Moreover, the FWSM works properly in the aplication partition(cf:4).
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXH8, RELEASE SOFTWARE (fc1)
System Bootstrap, Version 12.2(17r)SX5, RELEASE SOFTWARE (fc1)
Mod Ports Card Type Model
1 48 48-port 10/100/1000 RJ45 EtherModule WS-X6148A-GE-TX
4 6 Firewall Module WS-SVC-FWM-1
5 2 Supervisor Engine 720 (Active) WS-SUP720-3BXL
8 5 Communication Media Module WS-SVC-CMM
Mod MAC addresses Hw Fw Sw Status
1 001b.d41a.8360 to 001b.d41a.838f 1.5 8.4(1) 8.7(0.22)BUB Ok
4 0003.fead.962e to 0003.fead.9635 3.0 7.2(1) 4.1(14) Ok
5 0017.9444.c3ec to 0017.9444.c3ef 5.4 8.5(2) 12.2(33)SXH8 Ok
8 0017.0ee2.13cc to 0017.0ee2.13d5 2.8 12.4(25c), 12.4(25c), Ok
FWSM versions
FWSM Firewall Version 3.2(20)
Device Manager Version 5.0(3)F
Not possible to verify the switch is in the service.
I guess the reason is likely next.
FWSM supports only untagged packets on the vlan1. By default catalyst 6500 not tagged native vlan1.
In my case globally enabled tagging in the native vlan.
#sh vlan dot1q tag native
dot1q native vlan tagging is enabled globally
sh vlan dot1q tag native
dot1q native vlan tagging is enabled globally
Per Port Native Vlan Tagging State:
Port Operational Native VLAN
Mode Tagging State
Gi1/2 trunk enabled
Gi1/8 trunk enabled
Gi1/13 trunk enabled
Gi1/14 trunk enabled
Gi1/17 trunk enabled
Gi1/18 trunk enabled
Gi1/21 trunk enabled
Gi1/27 trunk enabled
Gi1/30 trunk enabled
Gi1/32 trunk enabled
Gi1/38 trunk enabled
Gi1/42 trunk enabled
Gi1/43 trunk enabled
Gi1/44 trunk enabled
Gi1/46 trunk enabled
Gi5/2 trunk enabled
Po2 trunk enabled
Po308 trunk enabled -
Maintenance Mode Switch for APEX
Is there any way that I can throw an switch in APEX and have it allow users who are currently logged in to finish their sessions (maybe displaying an alert message at the top of their pages asking them to finish what they are doing quickly and logout) but display a message denying new users the ability to login and use APEX. What I am after is a way to gracefully clear users off of my app server so I can take it down without giving a grand maul das boot to active users. Kind of the "The store is now closing, please take your final purchases to the registers at this time." type of announcement. Lock the front doors but let people who are already inside finish their business type of result. If this does not exist, it would be a nice feature to have at the internal workspace control level.
Hi,
A Windows Schedule task,
http://technet.microsoft.com/en-us/library/cc748993.aspx
Please read this one:
Management Pack for the SCOM 2012 Maintenance Mode Scheduler
http://blog.tyang.org/2014/05/22/management-pack-scom-2012-maintenance-mode-scheduler/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
Automatic Maintenance Mode SCOM 2012
What I'm trying to do is get an alert based on a shutdown event to trigger a script that then puts the server into maintenance mode. I've seen a few solutions to this for 2007, but this is the only one I've seen for 2012.
https://overcast.azurewebsites.net/2013/11/auto-maintenance-mode-with-scom-2012/
Basically, an alert is set up to watch for the shutdown event, which then uses a command channel to execute the script. The main significant part of that is the use of the ManagedEntityDisplayName parameter in the command channel to pass the server
name to the script. If I run the script from a command prompt and pass the FQDN of the server to it as a parameter, it works like a charm. But when I use SCOM to run it through the command channel, the server never gets put into
mm. For troubleshooting, I had it write a couple things to a log file.
When I run it from the command prompt, the log file contains the hostname I'm passing it for the ManagedEntity parameter in line 4, and the Instance that is returned from line 6 and it all works.
When I run it with the command channel in SCOM, it again writes out the ManagedEntity parameter as the hostname, so that part seems to work the same. But the Instance is returned to the log file as an empty line and then of course the server doesn't
go into MM. So it seems like something is different between me passing the FQDN as a parameter from the command line, and the command channel passing the ManagedEntity parameter from SCOM. Even though they both get written to the log file as the
hostname of the server. Any idea what I'm missing?
Param($ManagedEntityDisplayName)
$startTime = [DateTime]::Now
$endTime = $startTime.AddMinutes(15)
"Managed Entity is $managedentitydisplayname" |out-file log.txt
import-module OperationsManager
$Instance = Get-SCOMClassInstance -Name $ManagedEntityDisplayName
"Instance is $Instance" | Out-File log.txt -Append
Start-SCOMMaintenanceMode -Instance $Instance -EndTime $endTimeHi
What version of Power shell are you using on your management server? The I suspect the issue might be that when you run it doesn't actually load "import-module
OperationsManager" when scom runs it. So when you execute any scom command and save it into a variable it will always be empty.
To test if this is the issue run this
Param($ManagedEntityDisplayName)
$startTime = [DateTime]::Now
$endTime = $startTime.AddMinutes(15)
"Managed Entity is $managedentitydisplayname" |out-file log.txt
import-module OperationsManager
$SCOMConnection = Get-SCOMManagementGroupConnection
"Connection is $SCOMConnection" | Out-File log.txt -Append
$SCOMAgent = Get-SCOMAgent -name $ManagedEntityDisplayName
"SCOMAgent is $SCOMAgent" | Out-File log.txt -Append
If you don't get anything for these variables looks like the Import module is the issue.
I suggest the following:
Adding the full file path location to the module (might just not be registered correctly)
see: http://msdn.microsoft.com/en-us/library/dd878350(v=vs.85).aspx
If the above doesn't fix the issue re installing the console might be needed
see: http://thoughtsonopsmgr.blogspot.com.au/2013/02/om12-sp1-operations-manager-shell-fails.html
What version of Power shell are you also running on your Management server/s? If you are running v4 you might also need to include credentials when making a connection to the management server:
see: http://blogs.technet.com/b/robcost/archive/2008/05/01/powershell-tip-storing-and-using-password-credentials.aspx
So your after you import the Operations manager module you need
New-SCOMManagementGroupConnection -ComputerName "localhost" -Credential (Get-Credential WOODGROVE\Administrator)
see: http://technet.microsoft.com/en-us/library/hh920188(v=sc.20).aspx
Also how many management servers do you have? If you have more that 1 don't forget to place a copy of the script in the same location on each MS.
Thanks Martin
sustaslog.wordpress.com -
Found all the Servers that were restart without the maintenance mode were actived ?
Hi all
I was wondering if I can find a query about this request:
- Found all the Servers that were restart without the maintenance mode were actived ?
It's to make a Report To include in Reporting Services.
sorry for my English :)
Thank you very much and have a good dayHi, first if the maintenance mode is activated no events are collected, then, as example, in default rules you can see the following
Collection Rule for Windows Restarted Events that collects eventid=6005
with eventsourcename=eventlog from System
log which is enabled by default.
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=6005&EvtSrc=EventLog&LCID=1033
So you can check Data warehouse DB for presence such event
select ComputerName, DateTime from Event.vEvent ev
inner join Event.vEventDetail evd on ev.eventoriginid = evd.eventoriginid
inner join Event.vEventParameter evp on ev.eventoriginid = evp.eventoriginid
inner join vEventLoggingComputer elc on elc.eventloggingcomputerrowid = ev.loggingcomputerrowid
where eventdisplaynumber = '6005' Order by ComputerName, Datetime
http://blogs.technet.com/b/kevinholman/archive/2007/10/18/useful-operations-manager-2007-sql-queries.aspx
So if you see this event it means the server was restarted and the maintenance mode was not activated.
Also keep in mind that there can be other event ids when computer is restarted, as example see the rule
Collection Rule for Windows Restart Events (restarted from bugcheck) -
ConfigMgr Backup puts SCCM Server into Maintenance Mode (SCOM)
Hi all,
I have a strange issue.
We have a SCOM-Server (2012 SP1 - 7.0.9538.1068) which Monitors several servers. We also have an SCCM-Server (2012 R2 - 5.0.7958.100) for Client/Software Deployment. This SCCM-Server is also a SCOM-Gateway...
Now we have the issue, that i get strange Events in the Operations Manager Eventlog on the SCCM-Server (SCOM-Gateway):
Source: Health Service
Event ID: 1217
Level: Information
Description: The System Center 2012 - Operations Manager Agent running on Computer "SCCM-Server HOSTNAME" is suspended for the following reason: "ConfigMgr 4.00.7958.0000 - Starting - Backup".
There are several strange things with this message:
1. The Version is completely wrong... should probably be 5.00.7958.0000???
2. We have the SCCM-Backup (in Administration -> Overview -> Site Configuration -> Sites -> Site Maintenance -> Backup Site Server) NOT enabled!!!
3. The main issue now is, that the SCCM-Server (SCOM-Gateway) everyday changes to mantenance mode (for some hours over night!), and therefore all SCOM-Agents behind the SCOM-Gateway are alerting Heartbeat failures!
Example Times/Dates when the issue occurs:
Do you have any clues about this message?
Thank you for your help.
PatrikHi,
Have you checked Smsbkup.log as Torsten said?
You could also check the status messages for SMS_SITE_BACKUP in the Component Status node in the
Monitoring workspace.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
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"
Maybe you are looking for
-
Memory leaks and multi threading issues in managed client.
In our company we use a lot of Oracle, and after the release of the managed provider we migrated all applications to it. First the things were very impressive : the new client was faster, but after some days applications that uses 100MB with old cli
-
I can't open apps in my iPhone after synced to iTunes.
I'm having problem with iTunes, seems like everytime i sync my iPhone after it finish synced, I can't open some of the apps. I even try to find my apps (new) in iTunes, but it's not in the library. But if I started install any new app, the apps that
-
3D tryout: Do I need to UNinstall Acrobat Pro V7.x.x first?
I tried to install the Acrobat 3D tryout but it didn't work. I already have Acrobat Pro V7.0.5 on my machine. When I run the 3D installer I get this message: " Setup has detected that you already have a more functional product installed. Setup will n
-
Any FM / BAPI to Convert UOM (PLPO-MEINH) from ST to PC
Dear Friends, I am searching for a FM or Bapi to convert the Unit of Measure PLPO-MEINH, from ST to PC(Piece). Your Feed Back would be highly appreciated. Best Regards, Azam.
-
Usuability of materialized views
Hi , How can i exactly tell whether a Mview can really be used ? i.e the compile_state --> VALID/INVALID staleness--> FRESH, STALE, UNUSABLE, UNKNOWN, or UNDEFINED should i be checking the compile_state or the staleness and if it's staleness column t