%3CLINGO-SUB%20id%3D%22lingo-sub-392805%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-392805%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Intune%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20are%20having%20a%20very%20serious%20issue%20with%20Hybrid%20AAD%20Joined%20Windows%2010%20machines%20and%20our%20MDM%20users.%3C%2FP%3E%3CP%3EThey%20are%20able%20to%20see%20their%20Windows%2010%20Corporate-Owned%20Hybrid%20AAD%20Joined%20machines%20in%20the%20Company%20Portal%20and%20from%20there%2C%20issue%20a%20Refresh%20(Wipe)%20command!%20This%20is%20very%20dangerous%20as%20it%20allows%20end%20users%20to%20reset%20their%20assigned%20company%20machines%20through%20their%20mobile.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20already%20been%20informed%20by%20Intune%20Support%20that%20this%20is%20a%20known%20issue%20and%20should%20be%20resolved.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20logic%20here%20should%20be%20that%20if%20a%20Windows%2010%20Domain%20Joined%20%2F%20Hybrid%20AAD%20joined%20machine%20is%20Corporate%20owned%20(GPO%20or%20SCCM%20used%20for%20automatic%20enrollment)%2C%20the%20%22Enrollment%20user%22%20shouldn't%20be%20able%20to%20act%20against%20those%20systems.%20Only%20designated%20entities%20should.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20raise%20this%20case's%20impact%20as%20it%20could%20really%20cause%20issues%20where%20users%20unknowingly%20do%20such%20actions%20(rename%20should%20also%20be%20blocked%20for%20them)%20as%20these%20devices%20are%20not%20under%20their%20ownership%2C%20rather%20they%20are%20company%20resources.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-819488%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-819488%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EAny%20update%20on%20this%20issue%3F%20we%20are%20still%20seeing%20updates%20to%20hybrid%20join%20devices%20still%20not%20being%20reflected%20within%20On-Premise%20AD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-854798%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-854798%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20idea%20when%20this%20will%20be%20resolved%3F%20We%20would%20like%20to%20have%20the%20ability%20to%20rename%20computers%20from%20the%20Intune%20portal.%20Waiting%20anxiously%20on%20this!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-908797%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-908797%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20chance%20that%20what%20was%20done%20to%20block%20this%20functionality%20could%20be%20preventing%20hybrid%20joined%26nbsp%3B%20machines%20from%20being%20renamed%20period%3F%3F%3F%20....%20even%20locally%20from%20the%20machine%20itself%3F%20...%20i%20have%20an%20autopilot%20joined%20machine%20that%20neither%20I%20(with%20domain%20admin%20priviledge%20and%20local%20admin)%20nor%20the%20end%20user%20(local%20admin)%20can%20apparently%20rename%20his%20machine...%20we%20both%20get%20%22access%20denied%22%20when%20we%20attempt%20to%20do%20so...%20the%20machine%20is%20here%20in%20the%20office.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-910026%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-910026%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72289%22%20target%3D%22_blank%22%3E%40Jim%20MCKAY%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20having%20this%20issue%20only%20with%20my%20PowerShell%20scripts%20-%20When%20I%20deploy%20the%20script%20for%20AzureAD%20joined%20devices%20the%20script%20works%20perfectly%20and%20the%20computer%20name%20changes.%20But%20when%20the%20machine%20is%20a%20Hybrid%20domain%20joined%20device%2C%20the%20PS%20script%20fails.%20Of%20course%2C%20getting%20the%20reason%20for%20the%20failure%20is%20near%20impossible%20with%20the%20Intune%20portal%20so...%20I'm%20just%20stuck%20with%20it%20for%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-988484%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-988484%22%20slang%3D%22en-US%22%3E%3CP%3Ecan%20we%20get%20an%20status%20update%20form%20someone%20form%20microsoft%20as%20this%20still%20a%20problem%20with%20or%20organization%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-989015%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-989015%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20appeared%20to%20have%20been%20addressed%20at%20least%20for%20us....%20my%20most%20recent%20hybrid%20joined%20autopilot%20box%20renamed%20fine...%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1003379%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1003379%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20still%20an%20issue%20for%20us.%26nbsp%3B%20I%20just%20renamed%20a%20hybrid%20joined%20device%20using%20the%20Intune%20console%20and%20now%20I%20get%20the%20following%20error%20when%20attempting%20to%20sign%20in%20to%20the%20device%20with%20an%20AD%20account%20--%20%22The%20security%20database%20on%20the%20server%20does%20not%20have%20a%20computer%20account%20for%20this%20workstation%20trust%20relationship.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1004957%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1004957%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWe%20are%20facing%20the%20same%20issue%20after%20renaming%20a%20test%20client%20via%20Intune%20--%20%22The%20security%20database%20on%20the%20server%20does%20not%20have%20a%20computer%20account%20for%20this%20workstation%20trust%20relationship.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1014499%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1014499%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20confirm%20that%20I%20am%20also%20having%20the%20rename%20issue.%20Windows%2010%201909%20and%20Hybrid%20AD%20Join.%20Is%20there%20a%20way%20to%20turn%20this%20feature%20off%20per%20tenant%20to%20prevent%20people%20breaking%20users'%20computers%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390868%22%20slang%3D%22en-US%22%3EKnown%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390868%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3EUpdated%201%2F17%2F20%20-%26nbsp%3B%20Engineering%20is%20continuing%20to%20work%20with%20the%20Windows%20and%20AD%20teams%20to%20restore%20this%20feature%20within%20the%20Intune%20Console.%20Though%20we%20don't%20have%20an%20ETA%20to%20share%20at%20this%20time%2C%20stay%20tuned%20for%20more%20information%20as%20we%20look%20into%20this!%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%E2%80%99ve%20discovered%20an%20issue%20with%20a%20new%20feature%20that%20was%20recently%20released%20in%20the%20console.%20If%20you%20manage%20Windows%2010%20devices%2C%20you%20may%20have%20seen%20a%20new%20%E2%80%9CRename%20device%E2%80%9D%20setting%20in%20the%20console%20to%20rename%20an%20enrolled%20Windows%2010%20device.%20We%E2%80%99ve%20found%20that%20the%20renaming%20flow%20using%20this%20setting%20might%20not%20complete%20on%20Windows%20devices%20that%20are%20joined%20to%20on%20premises%20Active%20Directory%2C%20including%20Hybrid%20Azure%20AD%20joined%20devices.%20This%20setting%20has%20now%20been%20temporarily%20disabled%20for%20Hybrid%20Azure%20AD%20joined%20devices.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere%E2%80%99s%20the%20current%20experience%20in%20the%20Intune%20console.%20When%20you%20go%20to%20Devices%20%26gt%3B%20All%20Devices%20and%20choose%20a%20Windows%20device%2C%20you%20will%20see%20an%20option%20to%20rename%20the%20device.%20On%20renaming%20the%20device%2C%20the%20new%20name%20is%20reflected%20in%20the%20Intune%20console%20and%20in%20Azure%20AD.%20However%2C%20we%E2%80%99ve%20seen%20some%20cases%20where%20the%20new%20device%20name%20is%20not%20reflected%20in%20the%20on%20premises%20Active%20Directory.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20can%20result%20in%20login%20errors%20where%20a%20user%20may%20be%20able%20to%20log%20on%20to%20their%20device%20initially%20but%20may%20experience%20single%20sign-on%20(SSO)%20errors%20when%20they%20try%20to%20login%20again%20after%20a%20password%20change.%3C%2FP%3E%0A%3CP%3EEngineering%20is%20still%20working%20to%20understand%20the%20cause%20and%20remediation.%20We've%20temporarily%20disabled%20this%20setting%20in%20the%20console%20for%20Hybrid%20Azure%20AD%20joined%20devices%20and%20Azure%20AD%20joined%20co-managed%20devices%20until%20we%20have%20a%20fix%20for%20this%20issue.%20Stay%20tuned%20for%20more%20information%20as%20we%20look%20into%20this!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBlog%20post%20updates%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CP%3E5%2F17%2F19%20-%20This%20post%20previously%20shared%20that%20the%20impact%20was%20limited%20to%20Hybrid%20Azure%20AD%20joined%20devices.%20We've%20since%20updated%20the%20post%20to%20include%20Azure%20AD%20co-managed%20devices.%3C%2FP%3E%0A%3C%2FLI%3E%0A%3CLI%3E8%2F7%2F19%20-%20We%E2%80%99ve%20received%20reports%20from%20customers%20around%20this%20issue.%20Engineering%20is%20still%20continuing%20to%20restore%20this%20feature%20within%20the%20Intune%20Console.%3C%2FLI%3E%0A%3CLI%3E1%2F17%2F20%20with%20an%20update%20that%20we've%20followed%20up%20with%20the%20team%2C%20and%20they%20are%20continuing%20to%20work%20with%20the%20respective%20teams%20on%20this%20feature.%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-390868%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eknown%20issue%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%2010%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1161473%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1161473%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20having%20the%20same%20issue.%20This%20is%20making%20Autopilot%20nearly%20unusable%20in%20a%20Hybrid%20scenario.%20We%20are%20forced%20to%20join%20on-prem%20first%2C%20and%20then%20rely%20on%20gpo%20and%20multiple%20reboots%20to%20register%20MDM%20etc.%20All%20this%20just%20to%20let%20us%20chose%20a%20name%20without%20a%20forced%20prefix%20and%20a%20random%20number.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20would%20be%20less%20irked%20if%20there%20was%20a%20workaround%20of%20some%20sort%20(without%20having%20to%20install%20SCCM)%2C%20no%20matter%20how%20technical.%20Renaming%20doesn't%20happen%20that%20often%2C%20but%20it%20is%20pretty%20vital%20when%20we%20need%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1164860%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1164860%22%20slang%3D%22en-US%22%3E%3CP%3ESimilar%20issues%20with%20our%20tenant%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262769%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262769%22%20slang%3D%22en-US%22%3E%3CP%3EIm%20having%20a%20similar%20issue%2C%20but%20for%20me%20when%20the%20Computer%20Object%20is%20renamed%20in%20AD%20DS%2C%20and%20the%20Azure%20Connector%20Sync%20makes%20the%20change%20in%20Azure%20AD%20(for%20Hybrid%20Domain%20Joined%20Win10%20devices)%2C%20the%20Intune%20obect%20device%20name%20doesnt%20change.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpdate%20-%20The%20object%20is%20removed%20from%20Intune%20but%20the%20local%20Win10%20device%20then%20complains%20when%20trying%20to%20're-enroll'%20with%20%3A-%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222020-03-29_19-20-26.jpg%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F180351i1FE98478A2B46550%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%222020-03-29_19-20-26.jpg%22%20alt%3D%222020-03-29_19-20-26.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262831%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262831%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20will%20probably%20be%20the%20case%20until%20AAD%20Connect%20Syncs%20the%20computer%20object%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1262852%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1262852%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F460719%22%20target%3D%22_blank%22%3E%40DeanBrighton%3C%2FA%3E%26nbsp%3B%2C%20the%20connector%20has%20completed%20a%20few%20syncs.%20The%20Azure%20AD%20object%20name%20is%20correct%2C%20but%20it's%20not%20correct%20in%20Intune%20still.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1284467%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1284467%22%20slang%3D%22en-US%22%3E%3CP%3EAutopilot%20Deployment%20Mode%3A%20HydridAzureJoin%3C%2FP%3E%3CP%3E%3CSPAN%3EIssue%3A%20Hybrid%20Azure%20AD%20Joined%20devices%20looses%20the%20workstation%20trust%20relationship%20after%20renaming%20the%20device%20from%20the%20Intune%20Portal.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3Eafter%20renaming%20it%20gets%20reflected%20in%20the%20Intune%20portal%20but%20not%20in%20on-prem%20activedirectory.%20In%20my%20opinion%2C%20this%20has%20to%20be%20addressed%20as%20soon%20as%20possible%20because%20there%20are%20no%20alternative%20ways%20to%20figure%20this%20out.%20(May%20be%20I%20should%20give%20out%20a%20try%20re-naming%20it%20using%20GPO).%3C%2FP%3E%3CP%3EI%20had%20to%20rename%20the%20device%20because%20of%20the%20device%20configuration%20domain%20join%20profile%20limitation%20where%20it%20does%20not%20allow%20naming%20the%20devices%20with%20%25Serial%25%20or%20%25random%25.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETroubleshooting%20performed%20so%20far%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20did%20Initial%20Sync%20on%20AD%20Connect%20Server%20-%20no%20luck%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1284526%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1284526%22%20slang%3D%22en-US%22%3E%3CP%3EI%20tried%20changing%20it%20from%20the%20device%20like%20the%20usual%20way%20and%20it%20worked.%26nbsp%3B%20I%20was%20able%20to%20see%20changes%20on%20on-prem%20AD%20and%20after%20a%20sync%20it%20has%20also%20updated%20on%20azure%20ad%20and%20Intune%20as%20well.%26nbsp%3B%20but%20this%20is%20a%20kind%20of%20a%20manually%20work%20and%20it%20would%20be%20great%20if%20the%20Intune%20connector%20can%20do%20this%20update%2C%20as%20it%20has%20all%20right%20delegation%20rights%20over%20the%20targeted%20OU.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1390423%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1390423%22%20slang%3D%22en-US%22%3E%3CP%3EAutopilot%20Deployment%20Mode%3A%20HydridAzureJoin%3C%2FP%3E%3CP%3ESame%20Issue%20here%3AHybrid%20Azure%20AD%20Joined%20devices%20looses%20the%20workstation%20trust%20relationship%20after%20renaming%20the%20device%20from%20the%20Intune%20Portal%20or%20from%20AD.%3C%2FP%3E%3CP%3EIs%20there%20any%20updates%20on%20this%20fix.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1405050%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1405050%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWe%20can%20give%20a%20try%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22https%3A%2F%2Foofhours.com%2F2020%2F05%2F19%2Frenaming-autopilot-deployed-hybrid-azure-ad-join-devices%2Famp%2F%22%20href%3D%22https%3A%2F%2Foofhours.com%2F2020%2F05%2F19%2Frenaming-autopilot-deployed-hybrid-azure-ad-join-devices%2Famp%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CSPAN%3Ehttps%3A%2F%2Foofhours.com%2F2020%2F05%2F19%2Frenaming-autopilot-deployed-hybrid-azure-ad-join-devices%2Famp%2F%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1439546%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1439546%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20it%20resolved%20in%20Windows%2010%2C%20version%202004%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1601171%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1601171%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%2C%20do%20we%20have%20an%20update%20with%20regards%20to%20this%20issue%3F%20I%20am%20running%20Windows%2010%20version%202004%20enrolled%20in%20Intune.%20I%20still%20need%20to%20disjoin%20domain%20and%20rejoin%20post%20renaming%20to%20make%20it%20work.%20This%20is%20not%20feasible%20for%20my%20pool%20of%20devices.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20be%20great%20to%20have%20an%20ETA%20for%20the%20issue%20to%20be%20fixed!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1654869%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1654869%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20Organization%20is%20heading%20to%20Hybrid%20Azure%20AD%20Join%20for%20our%20Windows%2010%20Computers%20and%20would%20love%20to%20have%20this%20renaming%20devices%20resolved.%20Is%20there%20any%20update%20for%20this%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1657592%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1657592%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F789428%22%20target%3D%22_blank%22%3E%40dcorona1360%3C%2FA%3E%26nbsp%3BI've%20heard%20nothing.%20This%20issue%20and%20others%20make%20using%20Intune%20in%20a%20hybrid%20AD%20environment%20really%20problematic.%20Do%20you%20have%20any%20news%20for%20us%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F226779%22%20target%3D%22_blank%22%3E%40Intune%20Support%20Team%3C%2FA%3E%26nbsp%3B%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1660379%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20%E2%80%9CRename%20device%E2%80%9D%20setting%20for%20Windows%2010%20devices%20in%20the%20Intune%20console%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1660379%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20sure%20if%20this%20will%20help%20anyone%20but%20this%20is%20the%20recap%20of%20my%20testing%20of%20Hybrid%20device%20renaming%3A%3C%2FP%3E%3CP%3E-%20Logging%20as%20local%20admin%20and%20manually%20changing%20the%20name%20of%20the%20machine%3A%20It%20works%3C%2FP%3E%3CP%3E-%20Remotely%20using%20Rename-Computer%20powershell%20command%2C%20works.%26nbsp%3B%3C%2FP%3E%3CP%3EBoth%20actions%20above%20see%20the%20change%20of%20name%20reflected%20in%20Endpoint%20Manager.%20If%20joined%20by%20Autopilot%2C%20only%20the%20Hybrid%20object%20changes%20name%2C%20the%20Autopilot%20(duplicate%3F)%20AD%20joined%20object%20stays%20the%20same%2C%20although%20I%20haven't%20found%20any%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Rename%20Device%20in%20Endpoint%20Manager.%20Does%20not%20work.%20Worse%2C%20it%20breaks%20DC%20trust%20for%20all%20user's%20devices.%20I%20haven't%20found%20a%20way%20to%20recover%20this%20apart%20from%20resetting%20and%20reenrolling.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20User%20changing%20name%20in%20Company%20Portal%3A%20Nothing%20happens.%20All%20the%20AD%20and%20AAD%20names%20stay%20the%20same.%20It%20seems%20to%20just%20update%20the%20%22Display%20name%22%20for%20the%20user.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20else%20replicate%20the%20above%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E

Updated 1/17/20 -  Engineering is continuing to work with the Windows and AD teams to restore this feature within the Intune Console. Though we don't have an ETA to share at this time, stay tuned for more information as we look into this!

 

We’ve discovered an issue with a new feature that was recently released in the console. If you manage Windows 10 devices, you may have seen a new “Rename device” setting in the console to rename an enrolled Windows 10 device. We’ve found that the renaming flow using this setting might not complete on Windows devices that are joined to on premises Active Directory, including Hybrid Azure AD joined devices. This setting has now been temporarily disabled for Hybrid Azure AD joined devices.

 

Here’s the current experience in the Intune console. When you go to Devices > All Devices and choose a Windows device, you will see an option to rename the device. On renaming the device, the new name is reflected in the Intune console and in Azure AD. However, we’ve seen some cases where the new device name is not reflected in the on premises Active Directory.

 

This can result in login errors where a user may be able to log on to their device initially but may experience single sign-on (SSO) errors when they try to login again after a password change.

Engineering is still working to understand the cause and remediation. We've temporarily disabled this setting in the console for Hybrid Azure AD joined devices and Azure AD joined co-managed devices until we have a fix for this issue. Stay tuned for more information as we look into this!

 

Blog post updates:

  • 5/17/19 - This post previously shared that the impact was limited to Hybrid Azure AD joined devices. We've since updated the post to include Azure AD co-managed devices.

  • 8/7/19 - We’ve received reports from customers around this issue. Engineering is still continuing to restore this feature within the Intune Console.
  • 1/17/20 with an update that we've followed up with the team, and they are continuing to work with the respective teams on this feature.
24 Comments
Senior Member

Hello Intune,

 

we are having a very serious issue with Hybrid AAD Joined Windows 10 machines and our MDM users.

They are able to see their Windows 10 Corporate-Owned Hybrid AAD Joined machines in the Company Portal and from there, issue a Refresh (Wipe) command! This is very dangerous as it allows end users to reset their assigned company machines through their mobile.

 

I have already been informed by Intune Support that this is a known issue and should be resolved.

 

The logic here should be that if a Windows 10 Domain Joined / Hybrid AAD joined machine is Corporate owned (GPO or SCCM used for automatic enrollment), the "Enrollment user" shouldn't be able to act against those systems. Only designated entities should.

 

Please raise this case's impact as it could really cause issues where users unknowingly do such actions (rename should also be blocked for them) as these devices are not under their ownership, rather they are company resources.

 

Thanks

Occasional Contributor

Hi,

Any update on this issue? we are still seeing updates to hybrid join devices still not being reflected within On-Premise AD.

 

Thanks,

Established Member

Any idea when this will be resolved? We would like to have the ability to rename computers from the Intune portal. Waiting anxiously on this!

Regular Visitor

Any chance that what was done to block this functionality could be preventing hybrid joined  machines from being renamed period??? .... even locally from the machine itself? ... i have an autopilot joined machine that neither I (with domain admin priviledge and local admin) nor the end user (local admin) can apparently rename his machine... we both get "access denied" when we attempt to do so... the machine is here in the office. 

 

 

Established Member

@Jim MCKAY 

I'm having this issue only with my PowerShell scripts - When I deploy the script for AzureAD joined devices the script works perfectly and the computer name changes. But when the machine is a Hybrid domain joined device, the PS script fails. Of course, getting the reason for the failure is near impossible with the Intune portal so... I'm just stuck with it for now.

Occasional Visitor

can we get an status update form someone form microsoft as this still a problem with or organization

Regular Visitor

It appeared to have been addressed at least for us.... my most recent hybrid joined autopilot box renamed fine... 

 

Contributor

It's still an issue for us.  I just renamed a hybrid joined device using the Intune console and now I get the following error when attempting to sign in to the device with an AD account -- "The security database on the server does not have a computer account for this workstation trust relationship."

Senior Member

We are facing the same issue after renaming a test client via Intune -- "The security database on the server does not have a computer account for this workstation trust relationship."

Senior Member

Can confirm that I am also having the rename issue. Windows 10 1909 and Hybrid AD Join. Is there a way to turn this feature off per tenant to prevent people breaking users' computers?

Occasional Visitor

We are having the same issue. This is making Autopilot nearly unusable in a Hybrid scenario. We are forced to join on-prem first, and then rely on gpo and multiple reboots to register MDM etc. All this just to let us chose a name without a forced prefix and a random number.

 

We would be less irked if there was a workaround of some sort (without having to install SCCM), no matter how technical. Renaming doesn't happen that often, but it is pretty vital when we need it.

Regular Visitor

Similar issues with our tenant

Occasional Contributor

Im having a similar issue, but for me when the Computer Object is renamed in AD DS, and the Azure Connector Sync makes the change in Azure AD (for Hybrid Domain Joined Win10 devices), the Intune obect device name doesnt change. 

 

Update - The object is removed from Intune but the local Win10 device then complains when trying to 're-enroll' with :-

 
 
 
 

2020-03-29_19-20-26.jpg

 

 

Senior Member

This will probably be the case until AAD Connect Syncs the computer object again.

Occasional Contributor

Thanks @DeanBrighton , the connector has completed a few syncs. The Azure AD object name is correct, but it's not correct in Intune still.

Occasional Contributor

Autopilot Deployment Mode: HydridAzureJoin

Issue: Hybrid Azure AD Joined devices looses the workstation trust relationship after renaming the device from the Intune Portal. 

after renaming it gets reflected in the Intune portal but not in on-prem activedirectory. In my opinion, this has to be addressed as soon as possible because there are no alternative ways to figure this out. (May be I should give out a try re-naming it using GPO).

I had to rename the device because of the device configuration domain join profile limitation where it does not allow naming the devices with %Serial% or %random%. 

 

Troubleshooting performed so far:

 

1) did Initial Sync on AD Connect Server - no luck

 

Occasional Contributor

I tried changing it from the device like the usual way and it worked.  I was able to see changes on on-prem AD and after a sync it has also updated on azure ad and Intune as well.  but this is a kind of a manually work and it would be great if the Intune connector can do this update, as it has all right delegation rights over the targeted OU.

Occasional Visitor

Autopilot Deployment Mode: HydridAzureJoin

Same Issue here:Hybrid Azure AD Joined devices looses the workstation trust relationship after renaming the device from the Intune Portal or from AD.

Is there any updates on this fix.

 

Occasional Visitor
Occasional Visitor

Is it resolved in Windows 10, version 2004?

New Contributor

Hello , do we have an update with regards to this issue? I am running Windows 10 version 2004 enrolled in Intune. I still need to disjoin domain and rejoin post renaming to make it work. This is not feasible for my pool of devices.

 

Would be great to have an ETA for the issue to be fixed!

Occasional Visitor

Our Organization is heading to Hybrid Azure AD Join for our Windows 10 Computers and would love to have this renaming devices resolved. Is there any update for this issue?

New Contributor

@dcorona1360 I've heard nothing. This issue and others make using Intune in a hybrid AD environment really problematic. Do you have any news for us, @Intune Support Team ?

Occasional Visitor

Not sure if this will help anyone but this is the recap of my testing of Hybrid device renaming:

- Logging as local admin and manually changing the name of the machine: It works

- Remotely using Rename-Computer powershell command, works. 

Both actions above see the change of name reflected in Endpoint Manager. If joined by Autopilot, only the Hybrid object changes name, the Autopilot (duplicate?) AD joined object stays the same, although I haven't found any issues.

 

- Rename Device in Endpoint Manager. Does not work. Worse, it breaks DC trust for all user's devices. I haven't found a way to recover this apart from resetting and reenrolling.

 

- User changing name in Company Portal: Nothing happens. All the AD and AAD names stay the same. It seems to just update the "Display name" for the user.

 

Can anyone else replicate the above?