Rondelltron

Good day WS1 world: we seem to be having an issue where our conditional access integration is broken . A user can go through registration and they get the last pop up saying registration went through , you now have access to stuff etc . But when we check intune the device info is weird , it has a different dns name vs the computer name and a plethora of fields are not filled in when compared to devices that registered properly . right no one new can register with conditional access and we were able to pinpoint the day it started as well but we can confirm we did no changes to our environment . Any help would be greatly appreciated

Good day i am trying to figur out what i have to do to force devices to update . I was given two commands that was used to update devices to 21H2 and wanted to confirm if i can continue using this method . Below are the syntax's used <Replace> <CmdID>b5eba4a1-269c-4ecf-a929-79ba3c541312</CmdID> <Item> <Target> <LocURI>./Vendor/MSFT/Policy/Config/Update/TargetReleaseVersion</LocURI> </Target> <Meta> <Format xmlns="syncml:metinf">chr</Format> </Meta> <Data>21H2</Data> </Item> </Replace> <Delete> <CmdID>b5eba4a1-269c-4ecf-a929-79ba3c541312</CmdID> <Item> <Target> <LocURI>./Vendor/MSFT/Policy/Config/Update/TargetReleaseVersion</LocURI> </Target> <Meta> <Format xmlns="syncml:metinf">chr</Format> </Meta> <Data></Data> </Item> </Delete> Do i simply replace 21h2 with 22H2 and do a custom deployment like before ?

Good day and thank you in advance with any help / recommendations So i am learning a new environment and am tasked with highlighting if there is anything wrong with the way they update pc's. What they do is in production they push out a legacy windows update profile. every super tuesday they go to the device update module in WS1 and assign the KB to the Ring 1 , 2 and then production . Now im being told They should of stopped doing this a while ago as microsoft has depreciated this feature . So i ask if they want to continue pushing out the KB should they stop doing the approval and switch to using windows update profile only and just assigning profiles still doing ring based deployment

So you saying we should no longer use this method to release KB's to PC's? I am new to this team and am learning what they have been doing for a while now . Maybe these guys never updated their way of pushing updates to pc's. Right now they push out this profile : Windows Update (legacy) to around 10k PC's and every super tuesday they push out the new KB via the device updates module in WS1. around 1500-2k devices are in these one of three pots ive figured out : 1. device just stopped getting updates randomly at a specific date but will then show they have done updates recently 2. Device shows that it stopped getting updates at a specific date and nothing after . device just stuck on a specific os build and will not update 3. Device shows that is stuck in a "installing updates" and will not update if you manually log in to any of these types of device and poweshell windows updates . the pc will update

thank you for the reply but im not sure that is referencing my inquiry . This is windows updates not custom app deployments

Is there a way to force re-approval to past updates in mass? Also we have devices that show they got approved for an update but when we go to the updates section on that computer the KB release does not show its like the device does not know there is an update even available . this is what happens every month . we push the KB to 8k devices and close to 2k dot get them . in that 2 k we have devices that are in a stuck showing install in progress for weeks and then devices that just dont show the update at all . But then a month or two will go by and it gets a new KB we released and updates . So we go through this issue of around 2 devices that are not updating but its not always the same devices

thank you for the reply its hundreds of pc in our environment and all different dates and i am finding some that just stopped updating from a specific date . So this environment has around 8k PC's and for months around 2k of them dont update when they push a release . Ifigured out the first part "they were pushing legacy windows update profiles" The second being this issue were hundreds of pc's either show install status in progress or they are just. not updating anymore

I have hundreds of devices in my environment that shows windows updates stuck on in progress I am trying to figure out the best way to either force the windows update or restart WSUS ? any help would be appreciated