Configuring Strong authentication b/w WSUS Server in AD AND non-domain clients ?


i have wsus server sitting on win2008 platform in window 2003 ad domain pushes windows update around 10 servers. challenge push updates 3 win 2003 servers sitting behind firewall not part of ad domain belongs workgroup. network team wants me enable strong authentication b/w 3 servers (non-domain) behind firewall , wsus server belongs windows 2003 ad domain) before open traffic flow in firewall. using customized port 8530 in iis7 , using local computer policy these 3 computers push windows update using  http://wsusservername:8530 in local policy

does have idea configure strong authentication in specific scenario? please let me know if need further detail

i imagine depends on network team considers strong authentication.

personally, in response such request, i'd suggest enabling server-to-server ipsec, better alternative ssl. ssl one-way authentication technology when implemented wsus -- validates *server* known, client still anonymous far wsus server concerned.
lawrence garvin, m.s., mcitp:ea, mcdba, mcsa
principal/cto, onsite technology solutions, houston, texas
microsoft mvp - software distribution (2005-2010)
mvp profile: http://mvp.support.microsoft.com/profile/lawrence.garvin
blog: http://onsitechsolutions.spaces.live.com


Windows Server  >  WSUS



Comments

Popular posts from this blog

Azure MFA with Azure AD and RDS

Failed to setup initiator portal. Error status is given in the dump data.

Invalid pointer on gpresult /h gpreport.html