Forum Widgets
Latest Discussions
Setting Wallpaper via Intune (Workgroup Environment)
Hello All, We are attempting to set a Windows 11 device wallpaper via Intune using the following configuration: OMA-URI: ./Vendor/MSFT/Personalization/DesktopImageUrl Data Type: String Value: HTTP/HTTPS URL to a JPG/PNG image We used a SharePoint link as the image URL. However, the policy report shows Not Applicable, and the wallpaper does not update. A few questions: 1. Does the URL need to point directly to the image file (e.g., ending in `.png` or `.jpg`)? Our current link is a shared SharePoint URL without a direct file path. 2. The device is in a workgroup setup, and access to the SharePoint file is granted to the user account used to enroll the device in Intune. Could authentication be causing the issue? Although when we open the URL from that device, it redirects and opens the image. What is the recommended approach to applying wallpaper in a workgroup environment with URL using a SharePoint-hosted image? Appreciate your guidance. Thanks.
Device don't report to Windows Update for Business reports
We start using Autopatch. I setup all thigs for this report. Create LA and setup it. https://learn.microsoft.com/en-us/windows/deployment/update/wufb-reports-overview But from 750 device i see only 42. I try creating new LA, and onboard it but number of computers is same. On my NB i try even script but nothing works https://learn.microsoft.com/en-us/windows/deployment/update/wufb-reports-configuration-script Any help?
Autopilot deployment app count jumping around
Hi All! Just a quick post for some clarification. We have multiple Intune deployments for different clients and something we have noticed on at least two of them in the past few days is during the App deployment for autopilot we are noticing that the app count seems to jump around a bit. For example we had a deployment that was on the account setup stage on 5 out of 7 apps, I check it again a couple minutes later and for some reason it is now on 4 out of 7 apps installed. Sometimes it jumps up and down between those two app installs. It does not happen every single time but just wanted to know if anyone else has experienced this? The deployment generally still goes through but just want to to try and find a cause to address before it becomes an issue. Also note that the continue anyway button also shows up despite the deployment still being active sometimes. Thanks in advance!
Windows Autopilot and Configuration Management Client Installation Methods
I'm using Windows Autopilot to build my machines with AzureAD hybrid join. Currently as part of the ESP we deploy the configuration manager client and our VPN software (both Win32 apps) to them so we can get them co-managed ASAP. We also do this in ESP as blocking apps to control the device availability to users until they are completed. Our implementation partner advised us to install the Configuration Manager client in this manner to speed up co-management. Autopilot works (albeit slow at _ 60 mins). I am confused though on whether or not adding the configuration manager client into the autopilot build in this manner is supported? Reading this (Co-manage internet-based devices - Configuration Manager | Microsoft Learn) it states: You can't deploy the Configuration Manager client while provisioning a new computer in Windows Autopilot user-driven mode for hybrid Azure AD join. This limitation is due to the identity change of the device during the hybrid Azure AD-join process. Deploy the Configuration Manager client after the Autopilot process. For alternative options to install the client, see Client installation methods in Configuration Manager. So reading this it seems what we are doing is invalid. So question 1: Is it incorrect/unsupported to install the configuration manager client as a Win32 app during autopilot (ESP or otherwise)? Furthermore I read here (Co-manage internet-based devices - Configuration Manager | Microsoft Learn) that it appears there is no longer a need to to deploy configuration manager client as an app at all but it can simply be configured in it via Home -> Device -> Enroll Devices -> Windows Enrollment > Co-management Authority You no longer need to create and assign an Intune app to install the Configuration Manager client. The Intune enrollment policy automatically installs the Configuration Manager client as a first-party app. The device gets the client content from the Configuration Manager cloud management gateway (CMG), so you don't need to provide and manage the client content in Intune. Is this method only valid post autopilot?Did expediting the 2024-08 Quality Updates fail for anyone else?
I posted this question yesterday on the Windows Servicing board, but there isn't much activity there. I hope it's okay to re-post it here. Due to the CVE-2024-38063 vulnerability, we attempted to use the Expedited Quality Updates feature to enforce the immediate installation of the 2024-08 security updates. Unfortunately, the feature simply did not work. Even a couple weeks after deploying the expedited update profile, we had about 25% of our Windows endpoints still in "Pending" status, most of which were powered on 24/7. We still have ConfigMgr in our environment, so I used CMPivot to run a query for events in the System log with "2024-08" in the message. This showed me that rather than installing the update and forcing a restart one day later as configured, the update was being installed, then reverted about ten hours later, then immediately re-installed again, over and over: If I manually initiated a restart on any of the affected machines, the update was successfully finalized, so the issue wasn't a failure to install the update. I've opened a case with Microsoft Support, but it is progressing slowly. If nobody else is seeing the issue, I will throw in the towel, but if it's more widespread, I think it is worth fighting to get this fixed (assuming that Microsoft isn't already aware and has simply chosen not to publicize it — for example, in the Windows release health blade in the Microsoft 365 Admin Center).Reset M365 Apps Activation from User to Device
Hi All We have just procured some M365 Apps for Enterprise device based licenses. Now I have followed the initial setup guide of: Creating a security group for the devices Assign this group to the M365 Apps for Enterprise licenses Created an Intune settings catalogue profile to set device based licensing Guide here: Device-based licensing for Microsoft 365 Apps for enterprise - Microsoft 365 Apps | Microsoft Learn While this is great for new devices, the process gets slightly more trickier with devices that are already in use where M365 Apps for Enterprise has already been activated on a "User" type license. From this guide, I can see that the user activation has to be reset using various methods. Reset activation state for Microsoft 365 Apps for enterprise - Microsoft 365 Apps | Microsoft Learn Has anyone got any experience or knowledge on how to do this reset via Intune? Info greatly appreciated. SKIntune tenant migration
Hi, I could use some help about an Intune tenant migration. The company I work at acquired a company last year, and they have an Intune environment already that needs to be migrated to our organization's tenant. I found some information how I could possibly do this with Windows Autopilot, and going for a wipe and re-deploy. Their domain isn't migrated yet, and they are still using their own accounts and license. They have a 2nd and separate account from our company domain. What would be the right order? Do the domain migration first? Or assign licenses and policies to our accounts, and when the domain migration is done and the accounts are synced as one do the Intune tenant migration? Some advice would be very appreciated!
