Onboarding Microsoft365 endpoints for Microsoft Defender365 using Active Directory Group Policy

Onboarding Microsoft365 endpoints for Defender365 using Active Directory Group Policy

First Download on boarding package from security.microosft.com

  • Go to Settings and Endpoints
  • Select Operating system for on-boarding
  • In the Deployment method field, select Group policy. And Click Download Package

Note: Extract the package at share location with read-only location that will be accessed by the devices,

You Should named this folder OptionalParamsPolicy and the file WindowsDefenderATPOnboardingScript.cmd



Create Group Policy using downloaded package 

  • Go to Group policy management console
  • Right Click Group Policy Objects then New

  • Give then name (We are creating for Windows Client OS)


  • Now Right Click newly created Group Policy Object (GPO) you want to configure and click Edit.
  • In the Group Policy Management Editor, go to Computer configuration, then Preferences, and then Control panel settings.
  • Right-click Scheduled tasks, point to New, and then click Immediate Task (At least Windows 7)



In the Task window that opens, go to the General tab. Under Security options click Change User or Group and type SYSTEM and then click OK. NT AUTHORITY\SYSTEM appears as the user account the task will run as.

  • Select Run whether user is logged on or not and check the Run with highest privileges check box.
  • 1.    In the Name field, type an appropriate name for the scheduled task (for example, Defender for Endpoint Deployment).


  • Go to the Actions tab and select New... Ensure that Start a program is selected in the Action field. Enter the UNC path, using the file server's fully qualified domain name (FQDN), of the shared WindowsDefenderATPOnboardingScript.cmd file
  • Click Ok then ok

Link An Existing GPO or Newly created GPO to Systems/Computers OU

  • To link the GPO to an Organization Unit (OU), right-click and select Link an existing GPO. In the dialogue box that is displayed, select the Group Policy Object that you wish to link. Click OK.

Check in https://security.microsoft.com under Device Inventory you will have all newly listed machines 

If Devices are not showing or Getting issue please follow following the troubleshooting steps to resolve the problem.

  1. Check if Group Policy is applied on Client Computer 
  2. Open Task Scheduler in client computer and check if Created Task is showing in Task Scheduler Library 
  3. If Task is not showing please check what step is missing from above setps.
  4. is Showing and Giving error (0x41303) or Giving other Errors please change following settings. 
  5. Go To Domain Group Policies and Edit following settings in Immediate Task
  6. Now Restart your computer and check Task scheduler in your computer if running then check device list https://security.microsoft.com under Device Inventory you will see newly listed machines 



Thank you :) 



Comments

Post a Comment

Popular posts from this blog

How to check when Sharepoint List was created using PowerShell.

Image
While the SharePoint admin console may not offer a straightforward way to view the creation date of a SharePoint list, PowerShell comes to the rescue. In this blog post, we'll explore how you can effortlessly retrieve this information using SharePoint PowerShell. Let's dive into the steps and make list creation dates a breeze to access in your SharePoint environment. Install SharePoint module in your PS using following PS-CMD. Install-Module -Name Microsoft.Online.SharePoint.PowerShell If you want to check version of SharePoint install module using following CMD Get-Module -Name Microsoft.Online.SharePoint.PowerShell -ListAvailable | Select Name,Version Now connect SharePoint Admin center using following CMD in PowerShell. Connect-SPOService -Url https://YourAdminWebAddress.sharepoint.com If you don’t know address go to https://admin.microsoft.com/ Admin Centers and open SharePoint admin center and copy URL.   Now connect your SharePoint site using following ...
Read more

How to connect SharePoint online with SharePoint designer 2013

How to connect SharePoint online with SharePoint designer 2013 Note: If you encounter the permission error, the following steps will help you resolve it as well. Download SharePoint designer 2013 Allow custom scripting feature from SharePoint Management Shell.       Connect SharePoint Online site with SharePoint designer 2013.   Allow custom scripting feature from SharePoint Management Shell 1.        Download and Install SharePoint Online Management Shell 2.       Connect your SharePoint Admin portal to SharePoint Management shell by using following PS-CMD. if you don't have SharePoint Management Shell first please download and Install it.      Connect-SPOService -Url https://admin-domain.sharepoint.com -Credential Admin@youradminidEmailID.com      Run following CMD after connecting to allow custom scripting to connect SharePoint Designer 2013      set-SPOsite h...
Read more

Unable to add SMTP address in Office365 (Detailed error message: Unable to update the specified properties for on-premises mastered Directory Sync objects or objects currently undergoing migration. )

Image
 Scenario: You have migrated from In-House Exchange server to Microsoft365 You Decommissioned you Exchange server You have disbaled/deleted users mailbox and want to add old users SMTP in Microsoft365 mailbox Exchange online error: While trying to add SMTP from Exchange online to Microsoft365 getting error “  Email address type update failed Error: Error executing request. An Azure Active Directory call was made to keep object in sync between Azure Active Directory and Exchange Online. However, it failed. Detailed error message: Unable to update the specified properties for on-premises mastered Directory Sync objects or objects currently undergoing migration. DualWrite (Graph) RequestId: The issue may be transient and please retry a couple of minutes later. If issue persists, please see exception members for more information. ” | You cannot directly add additional SMTP for Migrated users from Exchange Online because If you are syncing from your AD to Azure (using AAD...
Read more