Skip to main content

is it possible to manually install the opsmgr (scom) agent with patches?

the answer is yes and no.  the bottom line is, you can’t do it from a single command line execution as you can generally with other MSI installations.

for example, if you wanted to run the momagent.msi and use the patch switch as shown in this example, it simply will not work.

msiexec /i MOMAgent.msi PATCH=Q954049-x86.msp;Q954903-x86.msp;Q956689-x86.msp USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=mytestgroup MANAGEMENT_SERVER_DNS=mytestserver.mydomain.com SECURE_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=1 /l opsmgr_install.log

 

instead, you’d have to run the previous installation without specifying the PATCH= switch.  once completed, then you can roll in the additional patches by running msiexec in update mode.  it would look something like this:

msiexec /update Q954049-x86.msp;Q954903-x86.msp;Q956689-x86.msp REINSTALL=ALL REINSTALLMODE=omus /L*v opsmgr_install.log /qn

 

thanks clive!

Comments

  1. I didn't count the characters, but are you exceeding the command line maximum (255, right?)? Maybe if you could move some of the other parameters off the command line and into a config file or elsewhere, it would work?

    ReplyDelete
  2. it's a limitation of this particular msi.

    ReplyDelete
  3. Marcus, you could try creating an administrative installation for the SCOM Agent. And then patch the administrative install.

    This could be interesting if there would be like 20 patches for the latest SCOM RTM version Agent. Maybe I'll give this a shot when i find some spare time ;)

    http://michielw.blogspot.com

    ReplyDelete
  4. i'm not sure what kind of semi-supported position that would put me in. :| sorry for the late response!

    ReplyDelete
  5. We are looking into doing an Administrative Install Point for this. Right it would include the base agent for SCOMR2 plus CU1. Ever consider this option?

    ReplyDelete

Post a Comment

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …