. I try to open the download url in the web browser, but it fails. (FYI if you want to force Device Configuration Profiles use the Sync button on the device page and not restart). In any case, that was what I was initially doing, but this seemed to work better in my case, and I did not see anyone else sharing much on the matter, so I tought I would try my luck with it, and share the solution. edit: this is what I found in the logs\IntuneManagementExtension.log:
This is not always the desired behavior. Source: DeviceManagement-Enterprise-Diagnostics-Provider.
If you deploy Win32 applications (.exe), you also have to restart the Microsoft Intune Management Extension service. ), Error code: (Unknown Win32 Error code: 0x80072ee7). ]LOG]!>
Registry has the following values: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\EnterpriseDesktopAppManagement\\S-0-0-00-0000000000-0000000000-000000000-000\\MSI\\4832C413-61A3-4703-BCB8-BB9AD35FD643: CurrentDownloadUrl: https://prodamsub0202rcdata.azureedge.net/IntuneWindowsAgent.msi
User has Enterprise Mobility + Security E5 license, User has powershell script and win32 app assigned to it.
The IME runs a health evaluation every day as a scheduled task, and logs the results in the ClientHealth.log: Microsoft > Intune > Intune Management Extension Health Evaluation Scheduled Task. Please remember to mark the replies as answers if they help. Monitoring: No, because the clients don't get the extension, scripts are never run. The Intune management extension supports Azure AD joined, hybrid Azure AD domain joined, and co-managed enrolled Windows devices. I have opened a case with Microsoft, but wondering if someone else is experiencing same issues and/or has a workaround/solution available. But, for some settings, you need to wait between 8 and 24 hours to be completely applied. After downloading and installing the Microsoft Intune Management Extension manually, my Win32 apps and PowerShell scripts were also being deployed. Will update thread when I hear from Microsoft.
This is not always the desired behavior. Source: DeviceManagement-Enterprise-Diagnostics-Provider.
If you deploy Win32 applications (.exe), you also have to restart the Microsoft Intune Management Extension service. ), Error code: (Unknown Win32 Error code: 0x80072ee7). ]LOG]!>
Registry has the following values: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\EnterpriseDesktopAppManagement\\S-0-0-00-0000000000-0000000000-000000000-000\\MSI\\4832C413-61A3-4703-BCB8-BB9AD35FD643: CurrentDownloadUrl: https://prodamsub0202rcdata.azureedge.net/IntuneWindowsAgent.msi
User has Enterprise Mobility + Security E5 license, User has powershell script and win32 app assigned to it.
The IME runs a health evaluation every day as a scheduled task, and logs the results in the ClientHealth.log: Microsoft > Intune > Intune Management Extension Health Evaluation Scheduled Task. Please remember to mark the replies as answers if they help. Monitoring: No, because the clients don't get the extension, scripts are never run. The Intune management extension supports Azure AD joined, hybrid Azure AD domain joined, and co-managed enrolled Windows devices. I have opened a case with Microsoft, but wondering if someone else is experiencing same issues and/or has a workaround/solution available. But, for some settings, you need to wait between 8 and 24 hours to be completely applied. After downloading and installing the Microsoft Intune Management Extension manually, my Win32 apps and PowerShell scripts were also being deployed. Will update thread when I hear from Microsoft.
This is not always the desired behavior. Source: DeviceManagement-Enterprise-Diagnostics-Provider.
If you deploy Win32 applications (.exe), you also have to restart the Microsoft Intune Management Extension service. ), Error code: (Unknown Win32 Error code: 0x80072ee7). ]LOG]!>
Registry has the following values: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\EnterpriseDesktopAppManagement\\S-0-0-00-0000000000-0000000000-000000000-000\\MSI\\4832C413-61A3-4703-BCB8-BB9AD35FD643: CurrentDownloadUrl: https://prodamsub0202rcdata.azureedge.net/IntuneWindowsAgent.msi
User has Enterprise Mobility + Security E5 license, User has powershell script and win32 app assigned to it.
The IME runs a health evaluation every day as a scheduled task, and logs the results in the ClientHealth.log: Microsoft > Intune > Intune Management Extension Health Evaluation Scheduled Task. Please remember to mark the replies as answers if they help. Monitoring: No, because the clients don't get the extension, scripts are never run. The Intune management extension supports Azure AD joined, hybrid Azure AD domain joined, and co-managed enrolled Windows devices. I have opened a case with Microsoft, but wondering if someone else is experiencing same issues and/or has a workaround/solution available. But, for some settings, you need to wait between 8 and 24 hours to be completely applied. After downloading and installing the Microsoft Intune Management Extension manually, my Win32 apps and PowerShell scripts were also being deployed. Will update thread when I hear from Microsoft.
This is not always the desired behavior. Source: DeviceManagement-Enterprise-Diagnostics-Provider.
If you deploy Win32 applications (.exe), you also have to restart the Microsoft Intune Management Extension service. ), Error code: (Unknown Win32 Error code: 0x80072ee7). ]LOG]!>
Registry has the following values: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\EnterpriseDesktopAppManagement\\S-0-0-00-0000000000-0000000000-000000000-000\\MSI\\4832C413-61A3-4703-BCB8-BB9AD35FD643: CurrentDownloadUrl: https://prodamsub0202rcdata.azureedge.net/IntuneWindowsAgent.msi
User has Enterprise Mobility + Security E5 license, User has powershell script and win32 app assigned to it.
The IME runs a health evaluation every day as a scheduled task, and logs the results in the ClientHealth.log: Microsoft > Intune > Intune Management Extension Health Evaluation Scheduled Task. Please remember to mark the replies as answers if they help. Monitoring: No, because the clients don't get the extension, scripts are never run. The Intune management extension supports Azure AD joined, hybrid Azure AD domain joined, and co-managed enrolled Windows devices. I have opened a case with Microsoft, but wondering if someone else is experiencing same issues and/or has a workaround/solution available. But, for some settings, you need to wait between 8 and 24 hours to be completely applied. After downloading and installing the Microsoft Intune Management Extension manually, my Win32 apps and PowerShell scripts were also being deployed. Will update thread when I hear from Microsoft.
This is not always the desired behavior. Source: DeviceManagement-Enterprise-Diagnostics-Provider.
If you deploy Win32 applications (.exe), you also have to restart the Microsoft Intune Management Extension service. ), Error code: (Unknown Win32 Error code: 0x80072ee7). ]LOG]!>
Registry has the following values: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\EnterpriseDesktopAppManagement\\S-0-0-00-0000000000-0000000000-000000000-000\\MSI\\4832C413-61A3-4703-BCB8-BB9AD35FD643: CurrentDownloadUrl: https://prodamsub0202rcdata.azureedge.net/IntuneWindowsAgent.msi
User has Enterprise Mobility + Security E5 license, User has powershell script and win32 app assigned to it.
The IME runs a health evaluation every day as a scheduled task, and logs the results in the ClientHealth.log: Microsoft > Intune > Intune Management Extension Health Evaluation Scheduled Task. Please remember to mark the replies as answers if they help. Monitoring: No, because the clients don't get the extension, scripts are never run. The Intune management extension supports Azure AD joined, hybrid Azure AD domain joined, and co-managed enrolled Windows devices. I have opened a case with Microsoft, but wondering if someone else is experiencing same issues and/or has a workaround/solution available. But, for some settings, you need to wait between 8 and 24 hours to be completely applied. After downloading and installing the Microsoft Intune Management Extension manually, my Win32 apps and PowerShell scripts were also being deployed. Will update thread when I hear from Microsoft.
Apparently on the client you can load services.msc and restart the Microsoft Intune Management Extension service to force the script but I have not had any luck with this personally. [LOG[started the uninstallation with argument /x {E06FC724-790D-4119-B078-17984CA2490A} /qn]LOG]!>