WSUS 3.0 & Windows Home Edition


i'm testing setup in lab since deployment failed @ client's location. test server windows server 2008 r2 standard. wsus 3.0 , working on port 80. client's office , lab setups on workgroup , without active directory. have created .reg file , merged client desktops. client's office , lab computers are mix of windows 7 pro , home windows 10 pro , home editions. pro pcs reporting in , getting updates. home editions not. i've seen mixed information online if home can used. see people saying need proper registry entries i've been finding bit different.

with registry entries imported known work on pro clients, home clients check , updates they're getting them microsoft. verified looking @ (very messy) windowsupdatelog producted get-windowsupdatelog powershell command. http:// servers microsoft ones , not wsus one. internet in lab disabled, updates fail expected on home editions of windows 10. also, home edition clients never show in status section of wsas server. home editions lack red sentence in windows update reads, "some settings managed organization". i've tried force reset , register commands @ client , @ server. clients can open .cab file mentioned in the mentioned in troubleshooting guides via web browser. since 1 windows 10 home client 32 bit, able test wsus client diagnostic tool (that hear doesn't work on 64-bit windows). server url listed , passes.

i guessing people may have assumed home editions work wsus because never disconnected internet. i'm going fresh install of windows 10 home on pc sure. need home , pro work wsus so, here am.


edit: did testing. erased hdd. installed windows 10 home x64. shutdown internet, merged registry file, , restarted windows update service. updates failed. reenabled internet , updates proceeded watched network , hdd traffic on wsus server , there none. reformatted hdd , installed windows 10 pro x64. did exact same steps in same order different results. internet disabled, w10 pro box started apply updates while wsus server peaked @ 100% network utilization , updates started flying. i've had experience in past. once tried follow people said that you enable gpo settings such ability change network type private public on windows home registry entry while connected static ip network. guess registry settings doesn't equal features. </sarcasm> think time fallout 4.

hi roy,

according description, did test in lab, got same result you.

during research, found not alone in having this issue, , it's pity didn't found official explanation or work around it.

so, is, seems home editions of windows 10 cannot configured use wsus server update.

you may turn window 10 forum, maybe may got there.

windows 10 forum link:

https://social.technet.microsoft.com/forums/en-us/home?forum=win10itprogeneral

someone meet same issue:

https://social.technet.microsoft.com/forums/en-us/915792c0-229e-4eb5-ba5d-178888e30f79/how-to-set-10-home-for-wsus-7-home-81-core-are-good?forum=winserverwsus

best regards,

anne


please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com.




Windows Server  >  WSUS



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client