Microsoft 365 learnings

Following query will give you list of the mobile device managed by Intune and its user from Configmgr. SELECT        dbo.v_R_System.Name0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.IMEI0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.PhoneNumber0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.DeviceManufacturer0,                           dbo.v_GS_DEVICE_COMPUTERSYSTEM.DeviceModel0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.SerialNumber0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.TimeStamp AS Expr1,                           dbo.v_GS_DEVICE_COMPUTERSYSTEM.FirmwareVersion0, dbo.v_GS_DEVICE_COMPUTERSYSTEM.SoftwareVersion0, dbo.v_R_User.Full_User_Name0, dbo.v_R_User.Name0 AS UserID,                           dbo.v_R_User.User_Principal_Name0 FROM            dbo.v_GS_DEVICE_COMPUTERSYSTEM RIGHT OUTER JOIN                          dbo.v_R_System INNER JOIN                          dbo.v_UsersPrimaryMachines INNER JOIN                          dbo.v_R_User ON dbo.v_UsersPrimaryMachines.UserResourceID = dbo.v_R_User.ResourceID ON dbo.v_R_Sys

Issue :  Unable to add device to Apple DEP Program Manually using Apple Configurator 2 Error :  Apple Configurator 2 was showing following error message: Provisional Enrollment failed. Network Communication error MCCloudConfigErrorDomain – 0x80EF (33007), The Error screenshot is shown below.  Fix: Connect ipad to wifi or mobile network and restart the enrollment process.

Unable to sync the Apple DEP devices from Microsoft Intune Portal  while Intune is running in Hybrid mode. If you are victim to the same limitation, please provide the feedback to the product group about the migration process and ask them to consider the improvement.  I have  come across the issue with the hybrid Intune environment while migrating to Intune Standalone. Intune does not allow to sync Apple DEP devices with Intune standalone as a result new user with Apple DEP device must be enrolled with Hybrid Intune. They cannot leverage Intune standalone directly until the Intune MDM authority is changed from ConfigMgr to Intune Standalone. Apple DEP have capabilities to add multiple MDM and Intune should provide capabilities  to sync devices with Apple DEP. However Microsoft support have suggested this could create conflict.(I do not thinks so since it is different MDM server !) Besides, here is the document of the MDM authority change for your reference:  https://d

Make most of Microsoft Intune Check list to make most of Microsoft Intune MDM and MAM features/ In this post, I have cover the Intune MDM and MAM features that can help enterprises to improve user experience and security. I have seen multiple MDM setups where its utilisation becomes limited to email profile deployment and password policies. I hope this checklist will help to enhance the capabilities and make most of the Microsoft Intune/EMS. Please note that this checklist might not complete due to fluid nature of the cloud services, I will keep adding link of the existing resources that might help you to kick start with design, deployment and Testing. I will keep revising this list on frequent basis, please review latest Microsoft Documentation for new Intune features.       ·         Identity o    Configure Azure AD & AD Connect : Required to provision users and assign licenses ·          Device and Application Management o    Intune Standalone vs Intune H

I am working on couple of exciting SCCM Projects and still learning something new every day. I have been figuring out why SCCM task sequences are not deploying to workstations. Client was showing following error prior to showing option to select task sequence. Usually, you receive error 80004005 if time is not set correctly on computer or there is mismatch between SCCM DP/Primary site time and client time. In may case issue caused due to SHA1 Certificate chain. Somehow client have not upgraded their certificate authority to Sha2 due to some limitation with one of the applications. SCCM has been configured with SHA1 Certificates.  However, i forgot to untick the box 'Require SHA-256'.As a result , Boot image was failing to communicate with SCCM Management. To fix the issue untick 'Require SHA-256 from \Administration\Overview\Site Configuration\Sites. As shown below. Happy SCCM....

SCCM site backup was failing with following error,  smsbkup.log showing following error. Cannot find the dependent writer. The dependant component cannot be backed up. AddDependentComponent(pDependency) failed. Error code = 0x80,004,005.Error description = . Error: GatherWriterMetadata failed. 1. To fix this issue  Run 'VSSAdmin list writers' command. 2. Ensure following writers listed. 3. If you identify these two writers are not listed, restart 'SQL Server VSS Writer' if SQLServierWriter' is missing or 'SMS_Site_VSS_Writer' if SMS writer is missing. 4. 'VSSAdmin list writers', ensure both services are listed. 5. start sms_site_backup service to start backup, monitor smsbkup.log, ensure backup completed successfully.

Dell Latitude 7480 Unable to Detect NVMe Drive while PXE booting using UEFI secureboot. To fix the issue download ' Intel Rapid Storage Technology Driver and Management Console' drivers from Dell Website.   Extract all drivers files, go to Drivers\Prodcution\Windows10-x64.  Inject iastoreAC.INF file drivers using DRVLoad command during PXEboot or in the bootimage. i.e Drvload \path\iastoreac.inf