SCOM 2019 is HERE! - Kevin Holman's Blog

Unlike SCOM 1801 we do not find “Webhost” folder under “C:\Program Files\Microsoft System Center\Operations Manager\WebConsole”. Please advise ... Skiptocontent Menu Close SCOM2019isHERE! Download: https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-2019 Documentation: https://docs.microsoft.com/en-us/system-center/scom/whats-new-in-om?view=sc-om-2019 QuickStartGuide: https://kevinholman.com/2019/03/14/scom-2019-quickstart-deployment-guide/ Officialannouncement: https://cloudblogs.microsoft.com/windowsserver/2019/03/07/coming-soon-microsoft-system-center-2019/ SCOM2019wentGAonMarch14th2019. TheSemi-AnnualChannel(1801/1807)willnotbecontinued. NewfeaturesandfixeswillcomeinUpdateRollupsevery6months. Sonowwegetthebestofbothworlds…. newfeaturesaddedevery6monthsjustlikeSAC,butLongTermServicing(5yearsofmainstreamsupportand5yearsofExtendedSupport)withoutthelimited18monthsupportofeachreleaseinSemi-AnnualChannel. Onlyonebranchtodealwithsupporting,patching,etc. I’mreallyhappyaboutthisdirection…..anditmakesalotofsenseforMicrosoftandforcustomers. SCOM2016,SCOM1801,orSCOM1807canallbedirectlyupgradedtoSCOM2019. DirectIn-placeupgradepaths: Q&A: Q: WhatOSversionsaresupportedforSCOM2019Serverroles? A: WindowsServer2016and2019. LINK Q: WhatversionsofSQLserveraresupportedforSCOM2019OpsDB,Warehouse,andReportingServerroles? A: SQL2016,SQL2017,andSQL2019CU8aresupported. LINK Q: WhatWindowsOSversionsaresupportedasamonitoredAgentforSCOM2019? A: WindowsServer2019,2016,2012R2,2012,andWindows10. Note: theSCOM2019agentdoesnotsupportWindowsServer2008norWindowsServer2008R2. LINK Q: WhatpreviousSCOMVersionscanbeupgradedinplacetoSCOM2019? A: SCOM2016,1801,and1807only. LINK Q: InasidebysidemigrationtoanewSCOM2019managementgroup,whatSCOMversionscancoexistinasupportedfashion? (i.e…agentsofoneversioncommunicatingwithmanagementserversofanotherversion?) A: SCOM2016,1801,and1807cancoexistwithSCOM2019deployments. (ItispossiblethatolderversionsofSCOMwillcommunicatewithSCOM2019,butitisn’tatestedandsupportedscenariooutsideofwhatisdocumented) LINK Q: AreanycapacityandscalechangescominginSCOM2019? A: No,theseareconsistentwithSCOM2016. LINK Q: ShouldIupgradeinplacefromSCOM2016/1801/1807,ordoasidebysidemigrationtoanewmanagementgroupandnewVM’s? A: Thisdependsonyourcurrentsituationandyourgoals. ThefirstandmostimportantdecisionfactorisareallyourSCOMinfrastructureserverroles(includingSQLservers)runningonWindowsServer2016ataminimum,andSQL2016ataminimum? Ifnot–youcannotin-placeupgradeuntilyoumeettheminimumsupportedrequirements. Ifyoudo,theinplaceupgradewillbethesimplestsolution. IfyouarerunningonpreviousOSorSQLversions,youwillhavetoevaluatehowmuchworkthiswillbetomigrateallyourserversroles,versusdeployinganewmanagementgroupand“startingover”. Q:CanSCOM2012R2bein-placeupgradeddirectlytoSCOM2019? A: No. YouwouldneedtofirstupgradetoSCOM2016asaninterimstep,per: LINK Q: DoIneednewmanagementpacksforSCOM2019? A: No,anyMPthatworkedinSCOM2012orSCOM2016shouldworkfineinSCOM2019. However,youshouldregularlydoareviewofyourMP’sinuseandupdatethemtocurrentversions.  IfyouhaveANYfeedbackonthisrelease,PLEASEopenaUserVoicesubmissionathttp://aka.ms/SCOM   KnownissuesinSCOM2019GA Thefollowingaresomeissuesbroughttomyattentionfromthecommunity: 1. ManagementServerinstallationfailswhenTLS1.0isdisabled,andprerequisitesforTLS1.2aremissing. Onthefirstmanagementserverbeinginstalled,theUIwillreturnafailure,andintheOpsMgrSetupWizard.log(foundatC:\Users\\AppData\Local\SCOM\LOGS),youseethefollowing: [09:41:56]:   Info:   :Info:GetLocalizedAdminGroupName:AdministratorsGroupNameis:BUILTIN\Administrators [09:42:12]:   Error:   :PopulateUserRoles:failed:ThrewException.Type:System.ArgumentException,ExceptionErrorCode:0x80070057 Ontheanyadditionalmanagementserversbeinginstalled,thiswillshowupbyhangingon“RegisteringManagementServer”andnevercompleting. ThisiscausedbyhavingTLS1.0disabledontheSCOMmanagementserverorSQLserver.IfTLS1.2isenforcedorTLS1.0disabled,youmustFIRSTinstallthesoftwareprerequisitesforTLS1.2forSCOM. 2. WhenusinganolderversionofSSRS2017forSCOMreporting,youareunabletobrowsedirectlytohttp://yourreportserver.yourdomain.com/Reports Thisreturnsa500error. ThisisanissueinSQL2017ReportingServicesandisresolvedusingbuild14.0.600.1274orlaterathttps://www.microsoft.com/en-us/download/details.aspx?id=55252 3. WhenusingSSRS2017,youmightseeerrorsonamanagementserverforeventID31567withdescription“FailedtodeployreportingcomponenttotheSQLServerReportingServicesserver”and“extensionisnotallowed”. ThisisapparentlybecauseofanewsecurityrestrictioninlaterbuildsofSSRS2017. TheworkaroundistoopenSQLManagementStudio,connecttoyourReportingServicesinstance,openthePropertiesoftheinstance,Advanced,andadd*.*tothelistfor“AllowedResourceExtensionsForUpload” 4. Whenusingascopeduserprofile,youmightseea“500–Internalservererror”whenusingastateviewintheWebConsole. YoualsowillseethesamebugthatwasinSCOM2016UR6wherestateviewsmaythrowanerror:Incorrectsyntaxnearthekeyword‘CREATE’. ThisbugwasfixedinSCOM2016UR7andisresolvedinSCOM2019UR1. Postnavigation PreviousPreviouspost:MPAuthoringwithfragments–IntroducingcombofragmentsNextNextpost:SCOM2016SecurityAccountMatrix 119Comments LookingatthatroadmapdoesnotmakemefeelveryhappyKevin🙂 Talkabouthavingsecondthoughts! What’snottolike?Ilikeeverythingaboutthis! Wellifyouthinkaboutitthe1801upgradewaslikeareinstall.1807wasalittlebetterbutitsisstillnowherenearaseasyasSCCM.Thisdoeskindofmakesensefromasupportpointofview CanweupgradeSCOM2012R2toSCOM2019? No,notdirectly.YouwouldneedtoupgradetoSCOM2016first,orjustdoasidebysidemigration.UpgradeswouldbeapainastheOSandSQLversionupgradeswouldbealotofwork Readingthisagainandnotmuchischangingtheyjustmovedthebranchreleasetobeingincludedinrollups OhYes,thisistherightwaytogo. Thisisgreatnewsandit’sgoodtoknowthatMicrosofthaveactuallylistenedtotheircustomersforonce.I’mjustabouttodesignaSCOMupgradeforacustomerandremovingSACsavesmefromhavingabigheadacheonbeingforcedtogoinonedirectionoranother.HavingthisLTSC/SACsplitjustdidn’tmakeanysenseforthekindsofbusinessclientsIhave. WillSCOM2019stillworkwithcurrentlyinstalledagentsonWS2008/2008R2/2012?Orwillallofthoseagentsstopworking/reportinguptothemanagementservers/DB? Thanks! –Michael Technically–youcouldleavethose2008/2008R2agentsrunningaSCOM2012R2orSCOM2016agent,andtheywillconnectandcommunicatejustfinetoaSCOM2019managementserver.Itjustwon’tbe“supported”byMicrosoft.However,manycustomersdidthiswithServer2003agentsreportingtoSCOM2016managementservers. hiievenhaveaserver2003with2012agentrunningintest-SCOM2019worksfine.SotheagumentofnotupgradingtoSCOM2019shoodnotbebecausofAgentsupport. Youarecorrectinthatitworksfine.However,thatconfigurationisnotsupportedbyMicrosoft.Soitisaquestionofvendorsupport,notoneof“doesitworkornot”. WindowsServer2012supporthasbeenadded/clarified.OnlyWindowsServer2008/2008R2remainunsupportedastheirEOLisapproachingsoon. Seemsalittlesoontonotsupporttheagentonawindow2008R2environmentithasnotgotEOLyet.Imayhavetorethinkgoingto2019forawhilesinceIstillhavealotof2008R2outthere. WindowsServer2008andWindowsServer2008R2bothfalloutofExtendedSupportin10shortmonths,byJan/2020.ThiswilllikelynothindermanycustomersasmostareorshouldbedeepintoprojectsremovingthisOSfromtheirinfrastructurethisyear. Toosoon?Youdorealize2008isa12yearoldoperatingsystemright?Wow,youwouldnevermakeitinmyshop.WearefullCI/CR/CUandupgrafeourOSbefore3yearsisup.Bitmyappsdontsupportnewoperatingsystems🙁FINDNEWAPPSITS2020,GOCLOUD.Thisoldwayofhowthelineneedstodie.Ivebeendoingthisfor21yearsnowandSCOMfor10andtherearenoothermonitoringsolutionswiththismuchpoweratsuchlowcostperiod.Getwiththetimesman Nosupportformonitoring2012?.LookslikeIwon’tbeupgradingforawhile. WindowsServer2012supporthasbeenadded/clarified.OnlyWindowsServer2008/2008R2remainunsupportedastheirEOLisapproachingsoon. IopenedasupportticketandconfirmedthatMicrosoftwillnotbesupportingmonitoringServer2012withSCOM2019. IgothalfwaythroughimplementingSCOM2016SACbeforehavingtostoptherolloutduetotheAPMbug.IworkforanaccountingfirmwithaheavyrelianceonSharePointandcan’ttakeanychanceswithsystemstability.Mostpeoplehavereportedgoodresultsusingtheoldagent/NOAPMworkaroundbut,again,thereisnoguarantee. Atthispoint,IamunabletocontinueimplementingSCOM2016SACduetotheAPMbugandiamunabletoimplementSCOM2019duetothelackofsupportforServer2012.WhatdoyourrecommendtoyourcustomersthatneedtosupportmonitoringServer2012+usingasupportedconfiguration?MybossisabigNaggiosfanandisrecommendingthatIlookatit.Arethereothersolutionsyouwouldrecommend? TheAPMbugisanon-issuewhenyouinstallwithNo-APM.Thereareotherworkaroundsthathavebeenpostedaswell. Forcustomerswhoneeda“MicrosoftSupported”pathtomonitorWindowsServer2012–youmightconsiderusingtheLogAnalyticsagent(MMA).ThisagentcurrentlysupportsWindowsServer2008R2andlater,andsupportsconnectingawidearrayofSCOMmanagementgroupversions. IfyouareconsideringNagios,whichisopensourced,whywouldhavingofficialsupportbeashowstopperforSCOM?TheSCOM2019agentworksfinewithnoknownissuesonWindowsServer2012,itjustwasn’tpartofthesupportedconfigurationtestingforSCOM2019,andveryfewcustomershavealotofinvestmentsinWS2012,asmostmovedquicklytoWS2012R2.Or,youcouldleavetheSCOM2016agentonWS2012,andjustconnectittoyourSCOM2019deployment,ifyouwanta“supported”agentversion. theagentthatisinstalledwhenconnectedtoazureautomationworkspacedoesnothonortheNOAPMsetting,andMicrosoftcanpushanupdateofthatagentoutanytimetheywish.Thisshoulddefinitelybechangedtoatleasthonorthesettingthatweretherepreviously. Thiswillworkasatemporaryworkaround–https://techcommunity.microsoft.com/t5/Core-Infrastructure-and-Security/SCOM-and-APM-the-simplest-workaround/ba-p/323740 YoushouldhavefullyreadthedocumentationbecausetheAPMissueisamutepoint,isnotabugandhasafullysupportedworkaround. “TheAPMbugisanon-issuewhenyouinstallwithNo-APM.Thereareotherworkaroundsthathavebeenpostedaswell.” IhavereadreportsofpeoplehavingproblemsevenafterinstallingwithNo-APM.Callmegunshy. “Forcustomerswhoneeda“MicrosoftSupported”pathtomonitorWindowsServer2012–youmightconsiderusingtheLogAnalyticsagent(MMA)” IreadthatMicrosofthaddiscontinuedtheuseofSCOMinternallyinfavourofthisapproach.Isthiswhatyourecommend? “IreadthatMicrosofthaddiscontinuedtheuseofSCOMinternallyinfavourofthisapproach.Isthiswhatyourecommend?” Notatall.TherewasonedivisioninMicrosoftITthatpublishedthatarticle.SCOMisstillthebestsolutionforOn-premandHybridscenarios–fortheabilitytomonitorheterogeneous,multi-vendorOS,hardware,3rdpartyapplications,inhousedevelopedapps,storage,networkdevices,etc–allinoneplace–inmyopinion. IrecommendopeningasupportcasewithMicrosoftand/orfilingarequestathttp://aka.ms/SCOM–pushingbackonthenomonitoringofWS2012withSCOM2019.Ifenoughcustomersraisethisasaconcern–thePGmightrevisitthis. WhataboutRHEL6westillhavealotofthat.Wedohaveanongoingprojecttoupgradebutneedtoknowwhatouroptionsarenow.Wewerepartwaythroughgoingto2016andplannedtojustdoaninplaceupgradetogoto2019assoonasitreleased.NoRHEL6couldimpactthat.For2008R2wehaveleftIcouldjustdeployoutthe2016AgentwithSCCMandmoveonuntiltheserverisretired.AnyworkaroundforRHEL6. Hello,ithinkonlysupportfrommswillnotbeavailablefor2008Server.YesterdayiinstalledenviromentwithScom2019andwasabletopushagentsto2008R2Serverandallworksproperly. 2019AgentMultihomewithSCOM2019andSCOM2012R2worksalsoperfekt. Read.The.Documentationpeople IsusingSCOM2019incombinationwithanoldagentversionsupported?ThiswouldenablemetomonitorWindows2008R2byusinganoldagentversion. Doesitwork?Yes.Isitsupported?No–asthisscenarioreceivednotesting. Hello,youcanusenewagentsthisworks.Butonly64bitsystems. I’llbereplacingmynetwork’sSCOM2012R2withthisversion.Wehave300endpointsthatwe’llbemonitoring.About40%servers,and60%networkdevices.20%ofthedevicesareataremotesitewitha200Mbpsbandwidthconnection.IhaveusedtheSCOMsizingtool,butMicrosoft’slowestrecommendationsarebasedon500serversand100networkdevices.Iwillbeusingvirtualservers,andiamtryingtoscaledownthedeploymenttosomethingmorereasonabletofitmynetwork.ThepreviousdeploymentconsistedofasingleManagementServerwithaSQLServerhostingtheOperationsManagement,theDataWarehouse,andtheReportingServerdatabases.IamplanningoninstallingtheWebConsole,whichwasn’tinstalledbefore.WhenattemptingtoinstalltheWebConsoleonthe2012R2ManagementServerweranintoissueswithalertsnotbeingsentout.Iwasthinkingaboutdoingasimilarimplementationthistimearound,butwith8coresand32GBramforeachserverthistimearound.Whatwouldyourecommend? Ialwaysrecommend2MSforanyproductiondeployment,toprovidehigheravailability.Forsomethingofyoursize,2MSonVM’s,eachwith4CPUand8GBofmemoryshouldbesufficient.Anythingmorethan16GBmemoryontheMSwillbeawasteinyoursize.FortheSQLserver,withallofthemcombinedtogether(whichisfineforthissizing)I’dwant8CPUand32GBRAM. Thanks.DocumentationrecommendsinstallingthewebconsoleontheserverthathosttheReportingdatabase,butwithallthedbsononeserver,woulditmakemoresensetoputthewebconsoleononeofthemanagementservers? Thatrecommendationispoor,andoutdated,IMHO.ItisanoldcontinuationfromwhenwehadtoinstallIISonSSRSforthereportingwebsite.ThatendedaroundSQL2008butthemodelsneverchanged.IinstallthewebconsoleonthefirsttwomanagementserversIdeploytoacustomer,asastandard.Thatgivestheopportunityforhighavailabilitytothewebconsole,andreducesauthenticationissuescausedbyauthenticationdelegation. WhatdoyouthinkabouttherecommendationtohosttheSCOMdbsontheirownserver?WoulditbestillbeunwisetohostthemonaserverwithSCCMdbsevenifmoreresourcesareallocated? TherecommendationtonotsharewithotherDB’sissolid–butitdependsonthesizeoftheenvironment.Ifonedatabaseisreallybusyandtransactional,itcanrobperformancefromotherDB’ssharingtheinstance.InsmallercompaniesatsmallerscaleitwillbeOK,butyou’dneedtoensureyouareaddingalotofresourcestoSQL.Ingeneral,Iadviseagainstit.SQLstandardlicenseisincludedinSystemCenterlicensingforthisveryreason….youcandeployasmanySQLstandardeditioninstancesasneeded,aslongastheyarededicatedonlytoSystemCenter. AmIcorrectinassumingthisappliestoinstancesandnotservers?CouldweputtheSCOMdbsontheirowninstance,buthostthemonaclusterthathousestheSCCMdbinstance? DoestheWebapplicationtransactionmonitorretrycountworksnowonthisnewversion? 80%ofourmonitoringisofthosemonitorsandthebugoftheretrycountbeingignoredisamajorpainoftheproduct… Bythewaywecurrentlyhave1807andhavethisproblem. Itisntreallyabug,asitworksexactlyasdesigned.Itisaretrycountofthemodule,notoftheworkflow.Customersdesirearetrycountoftheentireworkflowafter“x”numberofretries–butthatwasneverintheoriginaldesign.Iunderstandwhereyouarecomingfrom,however.Mostcustomershavemigratedawayfromthetransactionmonitors,totheWebAppavailabilitysolution(whichismuchsimpler)orusingacustomsolutionwhichgivesthiscapabilitytoURL’s.IfyouwanttoseethisspecificenhancementtotheWebTransactionmonitor,Irecommendformallyrequestingithere:http://aka.ms/SCOM Neverknewthiswasworkingasintended,honestlythoughtitwasabug,butevenso,whatdoyoumeanit’saretrycountofthemoduleandnotoftheworkflow?Ifeelitisn’tretryingagainonanything,wehaveeventestedwithwiresharkandneverseeitretryafterafailure,itjusttriggersanalertonfirsttry. HiJohn, ThemoduleattemptsaconnectiontotheURL,andwaitsforaresponse.Iftherequesttimedout/fails,itwillimmediatelyretry,uptothenumberoftimesinyourconfiguration.However,customerslookingattheUIassumedthiswasaretryoftheworkflow,meaning,checktheURLevery2minutes,butonlygenerateanalertafter3attemptsoftheworkflow(6minutes)havepassed.Itdoesn’tworkthisway–itisthenumberoftimesthemodulewillretrytheuniqueURLconnection,onasingleexecutionoftheworkflow.Iknowitismisleading,andcustomershaverequestedthisbechangedtosupportretrycountontheentireworkflow,buttherightwaytogetthisdoneisforacustomertoopenasupportcase,andfilethisasabug/DCR(designchangerequest)forittobeconsidered. ThanksalotfortheinputKevin,alwaysagreathelp! Ipokedaroundlookingfortheupgradeguide/documentationandcouldn’tfindit. https://docs.microsoft.com/en-us/system-center/scom/deploy-upgrade-overview?view=sc-om-2019 Thisisgoodnewsinthelongterm,butitnowmeansihaveuntilJanuarytogetWindows2016or2019uptoupgradeSCOMbeforeJanuary! Iassumeyouarerunning1807–whichhas18monthsofsupport–andthereforewillexpireinJan2020. ThisdoesgiveyouthebetterpartofayeartoupgradeyourOSandSQLversionsforasupportedSCOM2019upgrade.ButIwillagree–thisisoneofthereasonsIadvisedmylargercustomersnottogetonthesemi-annualchannel….asMicrosofthasalonghistoryofdroppingsupportforolderOSandSQLversions,forcingyouintoOSandSQLupgradesmuchfasterthanexistingplannedcadences.IpreferredLTSContheoldmodel,asevenaforcedchangeevery3yearscanbemoredisruptivethancustomerswouldlike. HiKevin, wedeployedSCOM1807onWindowsServer2012R2.Now,wemustuseWindowsServer2016orWindowsServer2019todeploySCOM2019.WehaverelativelycomplexSCOMenvironment. Isthereanyroadmap/stepsforMIGRATIONfromSCOM1807toSCOM2019? Bestregards Birdal Themigrationwouldbethesameasanyupgrade….deploynewmanagementserverstoreplacetheoldones.Migrateresourcestothenewmanagementservers.Uninstalloldmanagementservers.ThenperformaDBmigrationtonewSQLserversifrequired,orperformaninplaceupgradeofSQL. IhavethisfortheMS:https://kevinholman.com/2016/02/03/checklist-removing-migrating-old-management-servers-to-new-ones/ TheDBmigrationispartofourregulardocumentation. HiKevin, thankyouforquickreply.I’llcheckyourpointsinthenextweeksandcreateamigrationplan. Bestregards Birdal Pingback:SCOM2019:FasttracksetuponanAzureVM–blog.johnjoyner.net Pingback:SCOM2019:FasttracksetuponanAzureVM–blog.johnjoyner.net HelloKevin! TheissueswithSSRS2017giving500error,(iwishireadthatearlier),abouttheknownissuesthatyouwrote.IhavebeenspendingALOToftimetryingtofindoutwhy/whatihavepossibledonewrong… Aretheyanyexistingworkaroundsoranyfixforthatyet? CanyoualsopleasetellwhatsoftwareprereqsthereisforaWindows2016serverthatshouldbeadedicatedSCOM2019Reportserver? NotyetthatIknowof–itreallylookslikeaSSRSissue,notSCOM–soitmightbeawaituntilSSRSupdatecomes.Wewillsee. Softwareprereqsareallcoveredinmyquickstart.NothingrequiredforaReportserverexceptSSRSIbelieve. Ok,thankyouKevin! I’mstillgettingthescopeduser“incorrectsyntaxnearthekeyword‘create’”intheregular(notweb)console,likewhathappenedwithSCOM2016UR6.Isthisstillaknownissue? Discovered(afterreadingthecommentsonhttps://kevinholman.com/2018/10/31/ur6-for-scom-2016-step-by-step/)thatfollowingthestepsintheknownissuessection(butusingthe1807insteadoftheUR6updatetogettheDLL)canworkaroundthisissue. Pingback:SCOM2019vsAzureMonitor:Whichonetochoose?-AnalyticOpsInsights Kevin,theofficialdocofor1801/1807(https://docs.microsoft.com/en-us/system-center/scom/system-requirements?view=sc-om-1807#microsoft-monitoring-agent-operating-system)suggeststhereisnoagentsupportforWindowsServer2019,butthereisforSCOM2016andSCOM2019.Doyouknowifthisisgoingtochange? Movingfrom1807toSCOM2019isn’treallyanoptionforusintheshortterm,yetourserverguysarestartingtodevelopWindows2019buildsalready. Idon’tbelievethereismuchefforttosupportWindowsServer2019agentsonSCOM1807.Whileitworksjustfine,andnothingwasaddedtoSCOM2016inordertosupportWS2019–thesemi-annualchannelwasneverdesignedto“addsupport”foranything.Thesemiannualchannelwasacommitmenttoupgradingyourenvironmentevery6months.Ifyouwantanewfeatureorsupport–youmovetothenextversion.1807hasamaximumsupportlifecycleof18months,andexpiresinJanuary2020.TheexpectationisthatcustomerswouldupgradetoSCOM2019.Iunderstandthatwithnewversions–wedropsupportforoldstuff(OSversionsandSQL),andforcesupportfornewstuff(OSversionsandSQL)andthiswasthereasonIalwaysadvisedmycustomersnottoadopttheSemiAnnualChannelunlesstheywerecommittedtoanychangeMicrosoftcameoutwith.ThiswasalwaystheriskwithSAC. MyadviceistoupgradetoSCOM2019.ThatisthenaturalpathforanyoneontheSAC.IfyouMigratetoSCOM2019–youmighthaveashorttermissueofoldagentsnotsupported.Ifyoustaywhereyouareat,yourWS2019agentsaren’tsupportedandsupportforyourversionwillexpiresoon.IfyourebuildyourenvironmentasSCOM2016–youhavethemostoptionsforlongtermsupport,butalsothebiggestpain.Personally,I’djustmovetoSCOM2019andleaveoldagentsonWS2008servers,untiltheyaregone(whichalsolosesupportinJan2020)….asyoucannotstayon1807andhaveanysupportatallformuchlonger. Somyquestiontoyouis–whyisSCOM2019“notreallyanoption”? Hi,thankyouforthispost. Dowehaveanyideawhenthe500HTTPerroronreportingserverwillbefixed? Thankyou. HiKevin, doyouhavealreadyexperiencerunninganolderagentversiononRHEL6communicatingto2019? Thanks, Patrick Idon’t,sorry. HiKevin, WehaveSCOM2012R2.SeveralManagementServersrunningonWindows2012R2Servers.SQLis2012.WewouldliketoupgradeourSCOMto2019.Soasafirsthop,isitsupported(afterdoingin-placeupgradeofSCOMto2016)todoanin-placeupgradeoftheOSto2016?asthisapproachisexpectedtohavelesseffortandtimerequiredtoachieve..Appreciateyouradvice. Thanks, Alaa Idonotlikein-placeOSupgradesonservers.ThiscanleavebehindthingsinSCOM,andaddsrisk.ImuchpreferaddingnewmanagementserverswithWS2016OStoreplaceoldones. TomovefromSCOM2012R2toSCOM2016….withtheeventualtargetbeingSCOM2019–Iwould: 1.BuildnewManagementserversonWindowsServer2016.Migrateanyspecialroles/services.Retire/Removeoldmanagementservers.https://kevinholman.com/2016/02/03/checklist-removing-migrating-old-management-servers-to-new-ones/ 2.BuildnewSQLserversonWindowsServer2016andSQL2016.Migrateyourdatabases,andusethenewreportingserver.https://docs.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/hh456421(v%3dsc.12) 3.Upgrade/ReplaceanyGatewayserverstoWindowsServer2016. 4.UpgradeSCOMtoSCOM2019. HiKevin, Onceagain,thankyouforallyourcontributionsto…well,everything. WouldthisapproachworkifyouwantedtoupgradeOStoWindowsServer2019,e.g.: 1.BuildnewMSonWindowsServer2019.Migrateanyspecialroles/services.Retire/Removeoldmanagementservers. 2.BuildnewSQLserversonWindowsServer2019andSQL2016.Migrateyourdatabases,andusethenewreportingserver. 3.Upgrade/ReplaceanyGatewayserverstoWindowsServer2019. 4.UpgradeSCOMtoSCOM2016andthenSCOM2019. ordoyouneedtodoOSupgradesto2019in2steps? 1.BuildnewMSonWindowsServer2016.Migrateanyspecialroles/services.Retire/Removeoldmanagementservers. 2.BuildnewSQLserversonWindowsServer2016andSQL2016.Migrateyourdatabases,andusethenewreportingserver. 3.Upgrade/ReplaceanyGatewayserverstoWindowsServer2016. 4.UpgradeSCOMtoSCOM2016. 5.BuildnewMSonWindowsServer2019.Migrateanyspecialroles/services.Retire/Removeoldmanagementservers. 6.BuildnewSQLserversonWindowsServer2019andSQL2017.Migrateyourdatabases,andusethenewreportingserver. 7.Upgrade/ReplaceanyGatewayserverstoWindowsServer2019. 8.UpgradeSCOMtoSCOM2019. Cheers Ifyouarestuckoninplaceupgrades–movingfromSCOM2012toSCOM2019isapain–you’dneedtodothe2-stepprocess…toalwaysbeinasupportedconfiguration.Upgradeguidesandsupportedconfigurationsarepostedinourdocumentation. Thankyou!appreciateyourpromptresponse. IhavebeenreadingathesecommentsandIdoseetheworkaround,butIhaveaquestion.Weupgradedto2019anddidnothaveanyissuesbeforethen.NowthatwehaveupgradedIhaveauserthattriestogotothewebsiteandgetsanerrorthatstates“Incorrectsytnaxneartheword“create””. Iamabletogettothewebsitefinewithmycredentials,andIknownothingchangedasfarascredentialsinthesoftware.Isthispartofthebug,oramImissingsomethingelse. HiEmily– Thisisaknownissue,andrelatedtothebugnotedinthearticle–forscopedusers.ThiswasfirstfoundinSCOM2016,andwasfixedinSCOM2016UR7.ItshouldbeslatedtobefixedinSCOM2019UR1.Thereislikelyaworkaroundoraprivatefixavailable,andIrecommendopeningasupportcasewithMicrosofttogetadefinitiveanswertothis. Hello!Ithinkimayhavefoundoutanalternativewaytomigrate(sidebyside)fromScom2012R2toScom2019.Wellitseemstowork,becausewejustdidit. InouroldScom2012environmentwehave2008R2OSontheMGMTServers.Thereforewecannot(inplace)upgradetoScom2016becauseitrequire2012orlaterOS.WiththenewScom2019environmentwecannoteitherupgradetheold2012R2agentsbecausethenewScom2019agentrequiresaScom2016agentorlatertotoupgrade. Ialsoknowthat2008R2OSisnotreallysupportedbutihavereadthatthetheold2012R2agentson2008R2shouldbeabletoreportfinetoScom2019.ItesteditfirstandcorrectitreportedjustfinetoScom2019.Thatgotmethinking.Ifthisworks,whatabouttheScom1801agentwhoiscompatiblewithScom2012R2.SowhatifwefirstupgradeourScom2012R2agentsto1801.Diditanditworkedwell.StillreportingwelltotheoldScom2012R2environment. AfterthatwepushinstalledthenewScom2019agentfromtheScom2019environmenttotheserverswiththeScom1801agent.ItworkedandnowtheScom2019agentisinstalledonour2008R2serversanditreportsfinetobothScomenvironments2012R2and2019. InthiswaywecannowactuallyhaveouroldSCOMenvironmentupandrunningwhenweconfigurethenewone. Whitthismethodwecanavoidtheotherway,whois1.FirstinstallaScom1801environmentand(inplace)upgradeitto2019.2.WenowdontneedtofirstinstallSql2016for1801.WecaninsteadgodirectlytoSql2017whoisourchoiseforScom2019.Iguessthismethodisnotthesupportedone,butitreallyworksandthatisthemostimportantthingnow.WearesoonclosingtheoldScomenvironment.Alsoallthe2008R2serversareontherewayoutfromourdomain.Thatisgoodincaseoffutureupgradeforthe2019agentthatmaybecangiveproblemson2008R2. Cheers! HiKevin, DoyouthinkthataSCOM2019AgentinstalledonaWindows2008R2serverwillreportintoaSCOM2012R2runningonaUR14infrastructure?Orthisisaunsupportedfeature. Pleaseletmeknowwhatyouthink,sincethisisforaclient. BestRegards SCOMwillbealwaysmuchmoreworse! SCOM2019includesnotonlyoldbugs,butalsonewbugsinWebConsole,andinOperartionsConsole! https://social.technet.microsoft.com/Forums/en-US/3ad279ef-b007-4d2b-a1bc-b73047802b6c/bugs-paradise-named-microsoft-scom?forum=operationsmanagergeneral Bestregards Birdal HiKevin, Ihaveanissuewithoneofmycustomerswhohasinstalledascomagentonserverwokstation(iewinserver20161607built),theproblemisitsa4gbramworkstationandbecozofscomagent201or2016thememoryutilizationisreaching98%.itsaIISserverandisconnectedthroughagatewayserver.THemanagementserverfis2012r2withur14.Ihaveremovedthesymantecantivirusfromthevmandtriedstillnogo.Couldyoupleaseguidemeintherightdirectiononhowtot/sthisissue.Ifweremovethescomagentthereisnomemoryutilization,itseemstheagentiseatingupthewinrmservice.Anyideaswouldbeofgreathelp. 4GBofRAMonanyOSwillnothavemuchmemoryavailableforanyadd-onor3rdpartysoftware(includingtheSCOMagent),astheOSwillconsumenearlyallthememoryavailable.ESPECIALLYaserverrunningIIS.IISconsumesalotofmemoryitself,competingforresourceswiththeOS. Forlimitedmemoryserverslikethis,ifyouwantmonitoring,eitheraddmoreRAM,orlimitwhatSCOMisabletodiscoverandmonitor.Iwoulddisabletheseedclassdiscoveriesforalladd-onmanagementpacks,soyouwillonlydiscoverandmonitortheOS,disks,CPU,etc…Thiswillnotrequireasmanyresources. HelloKevin, Iwouldliketounderstandmoreonthebelowpoints: Upgradeto2019willimpactanyexistingManagementPacksandwilltheseworkpostupgradewithoutanyissues?Needyourvalidinputsandsupportingarticles. WhatallbackupswecantakelikeManagementPacksetcbeforewestartupgrade.anyreferencearticles.? AnyMPthatworkedinapreviousversionofSCOMupgrade-abletoSCOM2019shouldworkthesame.TherearenoschemachangestotheXML. TheUpgradeguideismyrecommendedreadingfortheupgradeprocess,inourdocumentation. HiKevin, HowthelicensingstructureforSCOM2019is?IfwehaveprocuredlicenseforSCOM1801or1807.IsthesamelicensecanbeappliedonceupgradingtoSCOM2019? IsthereanylicensestructurechangeforSCOM2019/SystemCenter2019 Iamnotalicensingexpert.However,generallyifyouhavesoftwareassuranceonSystemCenter,youcandeployanyversion.1801/1807*required*softwareassurance,soifyouwereproperlylicensedforthoseversions,movingtoSCOM2019isanon-issue. HiKevin, InoticedfromMicrosoft’sdocumentationonsupportedLinux/UnixOSandfoundoutthattheyhaveremovedthesupportforHP-UX!ItwasthereforSCOM1807butnotpresentforSCOM2019.Isthisintended?Ihaven’tdownloadedyettheMPforSCOM2019unix/linuxbutdoyouseeanyscxoromsagentforHP-UX? https://docs.microsoft.com/en-us/system-center/scom/plan-supported-crossplat-os?view=sc-om-2019 Idon’tknowanyspecificsnothaveaccesstothosedecisions.MyconjecturewouldsayitlikelyhassomethingtodowithItaniumprocessorsbeingdiscontinuedbyIntel(whichwastheonlyplatformsupported)andmostflavorsbeingoutofsupportbyHPin2020.Butagain,that’sonlyaguess.Ifacustomerrequiredthissupport,theyshouldprobablykeepaSCOMmanagementgrouparoundwithSCOM2016whichisalongtermsupportedrelease. InSCOM2019underMonitoringtab->MicrosoftAzurefolder->OtherAzureResourceInventory,theSubscriptionStatesays“NotMonitored”forSubscriptionIDsinmyenvironment. Iwasabletoaddallthesubscriptionssuccessfullywithouterrors. Whyisthesubscriptionstatereading“Notmonitored”? HowcanItroubleshootthisinSCOM2019forAzuresubscriptionaddedsuccessfully? AndunderMonitoringtab->Office365->ActiveAlerts==>gettinganalertwithandescription“Anerroroccurredwhilesendingtherequest.Endpointsmessage:Authorizationfailed” PleaseadvicetowhereitwentwrongwhileconfiguringOffice365subscriptionandAzureinSCOM2019 HiKevin!Thisquestionmaynotfitin,butiwillgiveitatry.🙂IamwonderingifSCOM2019needsMSDTCconfiguredwhenthedatabasesrunsinaA/AclusteredSQL17environment?AsiunderstandMSDTCisonlyinvolvedinexplicitdistributedtransactionsbetweenmorethanonecomputer.IftheSCOMDBinstanceisrunningonSQL-node1andSCOM_DWDBinstanceandACSDBinstancearerunningontheotherSQLnode2,doweneedMSDTCconfiguredincaseslikethat.DoesSCOMhaveexplicitdistributedtransactionsbetweenmorethanonecomputer? No,IamnotawareofanysuchrequirementsforMSDTCspecifictoSCOM.DoyoustillreallyusefailoverclustersinSQL2017?EveryoneIworkwithhastransitionedtoAlwaysOnthesedays. ThankyouforanswertheMSDTCquestion.WellyepwerestillintheSQLOldSchoolhere😉 WearefacingissuewithSCOM2019WebconsolewherewhenwetrytoopentheDashboardlink,itthrowserror0x800700b7“Cannotaddduplicatecollectionentryoftype‘add’withuniquekeyattribute‘name’setto‘X-Content-Type-Options’.UnlikeSCOM1801wedonotfind“Webhost”folderunder“C:\ProgramFiles\MicrosoftSystemCenter\OperationsManager\WebConsole”.Pleaseadviseifanyfixavailable. HiKevin, Wearealsofacingthesameissue.IsSCOMdashboardURLisdeprecatedonSCOM2019andwecanaccesstheweb-consoleanddashboardusingthesameURL? Ifyes,thenwehavesecondproblem.WearenotabletoviewtheTopology/DatacenterdashboardinSCOMwebconsolewhicharecreatedonSCOMmanagementconsole. DoesSCOM2019workwiththeServicenow2016connector?AreyouawareofanythinginpipelineforofficialconnectortoServicenow? HiKevin,Thanksforthisgreatarticle.IhaveonelittlequestionthatisnotansweredintheQ&A. WearerunningSCOM1807,sowehavetoupgradeto2019becausetheSemi-AnnualCycleisending.BecauseourWindowsOS(2012R2)isnotsupportedanymore,wedecidedtoinstallnewserversinsteadofupgradingboththeOSandSCOM. OurapproachisthatweaddournewserverstotheexcistingManagementGroup1by1,andthendeletetheolderMS. Nowthequestionis,doIhavetoinstallthosenewserversasSCOM1807first,andthenupgradethemallatthesametime.OrcanIinstallthemasSCOM2019rightaway,andlaterdeleteourSCOM1807MS’s.Sotosummarizemyquestion,canSCOM1807andSCOM2019ManagementServersco-excistin1ManagementGroup.ThereasonwhyIhavemydoubtsisbecauseIdon’tknowwhatkindofDatabasechangeswillbemadeandifthiswillbeaproblemornot. Thanksforyourreply, Raoul Youmustinstallthemas1807,thenstarttheupgrade.Iwouldinstallallthenewmanagementservers,thenshiftroles,thenremovetheoldmanagementservers.Ihaveachecklistwhichmighthelp:https://kevinholman.com/2016/02/03/checklist-removing-migrating-old-management-servers-to-new-ones/ Thanksfortheadvice! Idon’tunderstand.ThedownloadlinkatthetopofthepagegoestoanEvaluationtype.Idon’twanttoevaluate.Iwanttoupgradedirectlyfrom1807to2019inplace.Isthatevaluationlinkthesame.exetoupgradealicensed1807? Youshouldgetyourofficialmediafromanofficialsourcethen.ThereisalmostzeroMicrosoftlicensedsoftwareavailablefordownloadthatisnteval.Everycompanyhasaninternalsourceforgettingaccesstotheirlicensedsoftware. HiKevin, WearemanagingSCOMinfrastructurewith2000agents(IncludesLinuxOS)managedwith10ManagementServersandalsomonitoringnetworkdevices.Wearemovingon-premiseworkloadstoAzure. Andwearein-needofmoving\MigratingSCOM2012R2toAzure. Pleaseadvicethebestapproach&practicetobefollowedtoMigrateSCOM2012R2toAzureandalsoshareideas. HiKevin, WearecurrentlyonSCOM2007R2withWinOS2008R2/Win2012agentsreportingtohost,weareplanningonaupgradenearquick.whichversionwouldyourecommend. Also,wewillberetiringalloftheWin2008OSserversandreplacedby2016WinOS. Iwoulddoasimpleside-bysidemigrationtoanewSCOM2019environment. Howeverthose2007R2agentsarenotupgradecompatible….soyouragentstrategywillbeinterestingtoautomate. HiKevin, Firstofall–thanksforyourblog.Yourarticlesovertheyearshavebeenaconstantsourceofhelpandknowledge. We’vegotareasonablysmallenvironment(approx.160VM’s),andwe’vebeenrunningthefullSystemCentersuitesince2009/10–allversionsalongthewaysince2007. Weupgradedto2019inthemiddleoflastyearand,doingitinabitofarush,ploughedaheadandworkedoutinstallationissuesaswewent.Anyhow–longstory–butI’venowgottimetogobackandtryandtidythingsupandonethingwehavehadproblemswithconstantlyisDPMcrashing/slownessetc–inpartbecauseduringtheinstallwecouldnotsharetheSSRS(2017)instancewithotherSCcomponents,andwithnowSSRSitonlyletsyouinstallasingleinstance,andhencewejustinstalledalocalSQLversionandSSRSforDPM(ontheDPMserver)->leadingtoalotoftheperformanceissues. Lookingagainatitnow–itstillappearstobethesameissue.YoucanonlyinstallasingledefaultinstanceofSSRS2017onaserver,andbetweenthevariousSystemCentrecomponents(DPM,OM,CM)theredoesnotappeartobeanywaytoutiliseasharedSSRSinstallation–sotheonlyoptionappearstobetobuildmultipleVM’sjustforrunningSSRS.Inourcasewearenottooconcernedabouttheperformanceofthereportingservices,it’smoreapracticalityissueoftheadditionalresourcerequirements(CPU/RAMetc)andmaintainingmultipleserversforwhatwehavehadrunningonasingleVMhistorically(andperformancewasn’tanissue). Soafterallthat,myquestionis–haveIgotthiswrongand/orisitpossibletogeteachoftheSSRSrequirementsfortheSystemCentersuiterunningonthesameVMwiththelatestversions? Cheers I’mnotsureweeversupportedsharingSSRS,anditiscertainlynotrecommendedinmostcases.EspeciallyforOperationsManager,asSCOMrequiresadedicatedSSRSdeployment,becauseweremovethebuiltinsecuritymodelforSSRSandreplaceitwithacustomizedsecurityextensiontomakeitintegratewithourconsoleandrolebasedaccess.IwouldrecommendeachcomponentofSSRSuseadedicatedserver,orinstallSSRSonyourexistingSQLserver.Forinstance,inSCOMforsmallerenvironments,IalwaysinstallSSRSonthesameSQLserverhostingtheOpsDBandDW.SQLstandardlicensingisincludedwithsystemcenter,sotheonlyrealTCOhereisaVM,ifyouareunwillingorunabletocolocateSSRSontheSQLserveritself. HaveyouseenanythingsuggestingthatSQL2019mightbesupportedcurrentlyorsoon? OperationsManager2019supportsSQL2019withCU8 Fixedarticle! Kevin,loveyourarticles Engineersneedtostopcomplainingaboutwhatdoesanddoesntwork.Again,readthedocumentationitwillanswerallyourquestionsandconcerns.Ifnot,Kevinwill.Ifyoudoyourduediligencebeforehandthisthreadwouldntbesolong.IreiteratetomyengineersandarchitectsREAD!READ!READ!itspartofthenatureofthefield.Ifyoucantcarveoutanhourtoreadandnotethenyouneedtoconsidertimemanagementandprioritization.Getlunch1dayaweek,sitatyourdeskandread.Itwillsaveyouaworldofheadachesandothersaswell.Neverstoplearning.Learnsomethingneweverydayorconsideranewfieldofwork🙂 HiKevin, IalreadyhaveSQLServer2016butitishostedonWindowsServer2012R2.ThisissupportedasperdocumentationforSQLServer. However,I’vereadsomethingsthatimplythisisnotsupportedbySCOM2019andthatIwillhavetoupgradethisSQLVMOSto2016minimum.Isthisthecase? Thesupportedconfigurationishere:https://docs.microsoft.com/en-us/system-center/scom/system-requirements?view=sc-om-2019#software-requirements-for-operations-manager-components WindowsServer2016isaminimumrequirementfortheOSforanySCOMserverroleperthedocumentabove,forSCOM2019. HelloKevin, Ifi’moptingforasidebysidemigration,Canidualhomelinuxagents? Ihaveheardthatpeoplehavegottenthistowork,however,IhaveneverworkedwithitsoIdonotknow. “AgenericerroroccurredinGDI+.” Icantseemtofigureoutwhatiscausingthisissueand/orhowtoresolveit. Seemslikeitshouldbeaprettysimplefixasitappearstobeapermissions-relatederror. TheerrorappearsonlywhenIclickon‘Monitors’under“Authoring>ManagementPacks” AdditionalInforation: Application:OperationsManager ApplicationVersion:10.19.10050.0 Severity:Error Message: System.Runtime.InteropServices.ExternalException(0x80004005):AgenericerroroccurredinGDI+. atSystem.Drawing.Image.Save(Stringfilename,ImageCodecInfoencoder,EncoderParametersencoderParams) atMicrosoft.EnterpriseManagement.Internal.UI.Authoring.Views.MonitorDetailsView.c__DisplayClass1.b__0(Objectparam0,ConsoleJobEventArgsparam1) atMicrosoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponentcomponent,EventHandler`1job,Objectsender,ConsoleJobEventArgsargs) HaveyouupdatedtoUR2? Isthiswhenrunningtheconsoleonamanagementserver,oranytimeyouopenaconsoleanywhere? HiKevin,IhavethesameissuethanAndy,andIreceivethat“GenericerrorinGDI+”whenIexecuteaGenericMicrosoftAvailabilityreportonaconsole(managementserverorPC),andIclickon“Downtimeperiods”.Itshowsthedataandmetricsbutthechartsimagefails.WehaveSCOM2012R2(7.1.10226.0).Weknowthatitisprettyoutdated,butitworkedfinebeforeandwegotthisissueaftermigrationofSQLservertoanotherone(sameversionbutcleaninstallationofSQLandSSRS).Couldyouhelpus?Thanks!!! FromthedocsI’veseenonMicrosoft’ssiteforEndpointandConfigurationManager,itappearsthatMicrosoftisn’tsellinganynewlicensesanymoreforSCOM2019andonlypermitsittobeusedifpreviouslypurchased.Isthistrue.whatifapublicsectorsoftwareassurancecustomeralreadyhaslicensesforSCOMinuseandwanttodeployadditionalSCOMatdifferentsites? HiKevin, IsitstillpossibletouseSCOM2012or2016agentstomonitorWindows2008R2servers,connectingthemtoournewSCOM2019environment? Thanks. Yes.IgenerallyrecommendusingaSCOM2016agentasthatisthe“mostcurrent”.ButIhavetestedboth. HiKevin, I’musingSCOM2019,IknewthatSCOM2019issupportedwindowsserver2012R2,2012.HoweverIaddedwindowsserver2012R2,everythingisfine,stateishealthy,exceptWindowsOperatingSystemcolumngetstatus“NotMonitored”.Idon’tknowwhy.Canyouhelpmefixit?IhavesomewindowsOS2012R2cannotupgrade2016duetospecificservers.IalsoimportedMPlatestfrommicrosoftlink. ThemostcommonreasonforthatisyouaremissingtheOperationsSystemManagementpackforWindowsServer2012/R2.https://www.microsoft.com/en-us/download/details.aspx?id=9296 Or,youhavetheMPimported,buthavenotwaitedlongenoughfortheOStobediscovered. Or,thereisanissuewheretheMPdiscoveryisnotworkingorrunning.(veryrare) Juststartedanewposition,workingoncleaningupanewsidebysideinstallationof2019.NoticedintheadminsectionthattheOperationsConsoleshavealltheold2012severslist\ed.The2012managementservershavebeendecommdbuttheDNSrecordisstillup,anychancethatistheproblem?theredoesn’tappeartobeanywaytoremovethemfromtheconsole. Theremightbearemnantleftoverfromthem–dotheyshowupunder“AgentManaged”orunder“ManagementServers”viewinAdministration?Ifso–deletethem. WerecentlyupdatedSCOM2019managementserverswithUR3,andweareinstallingawebconsoleonaseparateserver.Wegotanerrorduringinstallationonwebconsole“:Error:Themanagementserverisadifferentversionthanthecurrentsetupbuild.Pleaseuseadifferentmanagementserverorthecorrectversionofsetup.ServerVersion:10.19.10475.0”.Wecannotroll-backthemanagementserverssinceitisalreadyonproduction.Isthereawaytoinstallwebconsolewithoutcheckingtheversion? ThisiscoveredinmyblogpostforUR3,intheKNOWNISSUESsection: https://kevinholman.com/2021/03/31/ur3-for-scom-2019-step-by-step/ LeaveaReplyCancelreplyYouremailaddresswillnotbepublished.Requiredfieldsaremarked*Comment*Name* Email* Website Δ Searchfor: RecentPosts DemoCookdownManagementPackExample AutomatingSCOMmaintenancemodeforagentsassignedtoaGatewaywhentheirGatewayisunavailable ExplicitGroupMembershipinSCOMusingPowerShell SCOM–HowtogetClusterAlertsfromtheNodes,nottheVirtualComputer AutomatingAgentLoadBalancingforManagementServersandGateways Archives Archives SelectMonth February2022 (1) January2022 (1) September2021 (3) August2021 (3) July2021 (1) May2021 (2) March2021 (2) February2021 (1) January2021 (1) December2020 (1) September2020 (3) August2020 (4) July2020 (5) June2020 (1) May2020 (6) April2020 (1) March2020 (2) February2020 (1) January2020 (1) November2019 (1) September2019 (3) July2019 (7) June2019 (2) April2019 (2) March2019 (5) January2019 (1) December2018 (2) November2018 (1) October2018 (5) August2018 (4) June2018 (1) May2018 (2) March2018 (1) January2018 (1) December2017 (1) November2017 (2) October2017 (2) September2017 (1) August2017 (8) July2017 (2) June2017 (1) May2017 (4) March2017 (3) February2017 (3) January2017 (1) December2016 (9) November2016 (6) October2016 (2) August2016 (1) July2016 (1) June2016 (11) May2016 (2) April2016 (4) March2016 (2) February2016 (2) January2016 (1) December2015 (1) October2015 (1) September2015 (1) June2015 (5) May2015 (1) February2015 (2) December2014 (1) November2014 (1) October2014 (4) July2014 (1) June2014 (2) April2014 (1) March2014 (3) February2014 (1) January2014 (6) November2013 (2) October2013 (4) July2013 (1) June2013 (1) May2013 (2) February2013 (1) September2012 (1) April2012 (1) March2012 (3) February2012 (1) August2011 (3) July2011 (1) March2011 (1) February2011 (2) January2011 (1) December2010 (1) November2010 (1) October2010 (1) September2010 (2) August2010 (2) July2010 (5) April2010 (2) March2010 (1) February2010 (2) January2010 (1) December2009 (1) November2009 (3) October2009 (2) September2009 (1) July2009 (2) June2009 (6) April2009 (1) February2009 (3) January2009 (2) November2008 (2) October2008 (1) September2008 (2) July2008 (2) June2008 (2) April2008 (3) March2008 (4) February2008 (2) December2007 (4)