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

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

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.   DETECTION status messages take 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 m