User Profile
egoodman
Brass Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Not Ready - Must be managed by Intune
Hi, I am starting testing with AutoPatch and it says that my devices are not managed by Intune, but they look fine in the MEM portal. I was able to initiate a remote restart on them to confirm communication and I also successfully deployed a Win32 app to to the devices. Do you have any suggestions on on how I can get these devices into 'Ready' status?Feature Update Preview - how is it going?
Just curious what feedback you are getting from customers on the Feature Update Preview feature in Intune. I've seen mixed results during my testing (existing machine was targeted for the policy for Win10 2004 but didn't have itsTargetReleaseVersion populated in the registry and updated incorrectly to 20H2), and also posts online where people have to pause the updates, etc. In general, what challenges are you hearing and what are you actively working on with this feature. How long do you estimate until it becomes GA?WUfB + Third Party Patches
Hi guys, Are there any plans to add support for third party patches (i.e. those published from PatchMyPC) via WUfB? Right now, the only way to deploy Third Party Patches that I'm aware of is via co-management. We deploy security updates from WUfB and Third Party patches using our on-prem ConfigMgr environment. This works, but the user experience isn't great since we'll get notifications from WUfB for installs & reboots andseparate notifications from Software Center for the other updates & reboots. Depending on your answer to my first question, are there plans to unify this experience? Thank you!WUfB Feature Updates & Co-Management
Hi guys, Do you have a timeline on when this known issue will be fixed? "...when you co-manage devices by using Configuration Manager and Intune, there is a limitation where feature update policies may not immediately take effect. This limitation causes devices to update to a later feature update than the one that's configured in Intune. This limitation will be removed in a future update to Configuration Manager" https://docs.microsoft.com/en-us/troubleshoot/mem/intune/create-feature-update-hold-co-managed-devicesClients not sending state messages through CMG during remote In-Place Upgrade
Hey guys, We are performing Win10 in-place upgrades from 1803 to 1909 using Task Sequences to people working at home. We do have a CMG in place, but clients are usually connected to VPN when the TS first starts. Things run along fine until after the first reboot, and then the SMSTS.LOG is loaded with 80072ee7 status message failures: The VPN we're using is not always-on, so after the reboot the connection is terminated.I would presume that the clients would still be able to send their status messages over the CMG, but they don't seem to be.In most cases, the TS does actually finish "locally" just fine but Deployment Status in the console doesn't update the status. LocationServices.log shows the machine switch over to the CMG. ClientLocation.log does flip to 'Client is in Internet' but still has URL entries for the on-prem MP: The docs indicate that if status messages can't be sent, they are not queued or re-sent, so it's been difficult to easily tell in the Console how things went without reviewing logs individually on each machine. Can you comment on whether this could be aknown issue or a possible configuration problem on our end? If a configuration problem, any suggestions on what specifically to check? Thanks so much!Task Sequence Media Support for Cloud-based content
Hi guys! In the latest TP 2005, it is mentioned that content for boot media and PXE deployments can now be downloaded from cloud-based sources. What is the behavior today on 1910 or 2002 if we already have our boundary group setup as described in the article? (associated the CMG with boundary group and enabled 'Prefer cloud sources...').
