Worked great on the same machine with Big Sur, and survived the upgrade to Monterey. This is on an M1 Mac, using my Jamf policy that drops the install assets into a temp directory then calls the installbuilder.sh script with -mode unattended. When I tried to apply one of my usual configurations to install the Agent on a machine already running Monterey, the OS throws an error window: Several machines that were upgraded from Big Sur to Monterey and had the Agent already installed were able to keep running the Agent. I'm trying to certify MacOS Monterey for our environment, and while the Solarwinds Discovery Agent runs just fine on Monterey, it does not appear to install on Monterey.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |