Onboarding 2019 Hyper-V

%3CLINGO-SUB%20id%3D%22lingo-sub-855010%22%20slang%3D%22en-US%22%3EOnboarding%202019%20Hyper-V%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-855010%22%20slang%3D%22en-US%22%3EOur%20organization%20has%20started%20installing%202019%20Hyper-V%20(Build%2010.0.17763).%20It%20looks%20like%202019%20Core%2C%20but%20behaves%20differently%20when%20onboarding%20to%20WDATP.%20Here%20is%20my%20issue.%20I%20use%20the%20onboarding%20script%20like%20I%20have%20done%20on%20our%20other%202019%20servers%2C%20but%20fails%20to%20Onboard%20because%20there%20is%20no%20SENSE%20service.%20I%20verified%20in%20Windows%20features%20that%20Defender%20was%20installed%20and%20the%20windefend%20service%20was%20running.%20I%20tried%20re-installing%20the%20feature%2C%20and%20verified%20everything%20was%20installed.%20The%20Windows%20Defender%20Advanced%20Threat%20Protection%20Service%20(SENSE)%20was%20still%20missing.%20It%20was%20there%20on%20my%20other%20core%20machines%2C%20but%20the%202019%20Hyper%20V%20OS%20was%20not.%20I%20cannot%20seem%20to%20onboard%20without%20this%20service.%20So%20I%20then%20tried%20just%20Installing%20the%20Microsoft%20Monitoring%20Agent%2C%20but%20of%20course%20I%20get%20a%20healthservice%20error%20saying%20it%20was%20incompatible%20with%202019.%20All%20other%20OS's%20in%20our%20environment%20are%20fine%2C%202012R2%2C%202016%2C%202019%20standard%20and%20core.%20Is%20there%20a%20different%20process%20to%20Onboard%202019%20Hyper-V%20OS.%20We%20currently%20have%20two%20of%20these%20in%20our%20environment%2C%20and%20I%20am%20sure%20we%20will%20have%20more%20coming%20soon.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor
Our organization has started installing 2019 Hyper-V (Build 10.0.17763). It looks like 2019 Core, but behaves differently when onboarding to WDATP. Here is my issue. I use the onboarding script like I have done on our other 2019 servers, but fails to Onboard because there is no SENSE service. I verified in Windows features that Defender was installed and the windefend service was running. I tried re-installing the feature, and verified everything was installed. The Windows Defender Advanced Threat Protection Service (SENSE) was still missing. It was there on my other core machines, but the 2019 Hyper V OS was not. I cannot seem to onboard without this service. So I then tried just Installing the Microsoft Monitoring Agent, but of course I get a healthservice error saying it was incompatible with 2019. All other OS's in our environment are fine, 2012R2, 2016, 2019 standard and core. Is there a different process to Onboard 2019 Hyper-V OS. We currently have two of these in our environment, and I am sure we will have more coming soon.
0 Replies