天一剑客

首页 新随笔 联系 管理

   在论坛搜到很多朋友都有这个问题出现,在事件日志会记录ID506错误。呵呵 我也遇到这个问题。这个问题是我的域控制器出了问题(有安装WSUS服务),直接重新安装为成员服务器后再安装WSUS,再接着升为域控制器后就出现此错误。查找相关资料,正常步骤应该为《Unstall WSUS --> 降级AD/重新安装WINDOWS-->加入域/升为域控制器-->Instal WSUS》.
   打开IIS,检查WSUS SITE 目录安全性,确认启用Anonymous访问。执行C:%ProgramFiles%/Update Services/Setup/InstallSelfupdateOnPort80.vbs .问题并没解决。无赖重新安装WSUS,问题依旧,看来问题不在于WSUS.。于是继续上网找找看,呵呵 碰到此问题的朋友还真不少,可给出的方法大致都一样。不过大概可以确定还是在IIS的问题上,最后目标锁定在如下:

1.  Verify IIS Auth on the SelfUpdate tree uses anonymous (I took off Windows Auth for the heck of it)

2.  Add a Server Binding for 127.0.0.1:80 in IIS to your WSUS site (if you are using a specific IP for your WSUS site)

If using IIS 6 Secure Process Isolation mode (also do 3,4 and 5) -- try it anyway if you don't know what secure process isolation mode is -- it won't hurt (unless you are using anonymous elsewhere in your website, and then do step 5 for those webs/nodes also):

3. Verify the username for anonymous access in the ISM (ISM->WSUS Site->Properties->Directory Security->Edit)

4.  Change the IIS user password to a new PW in AD (from step 3)

5.  Change the Anonymous user password in the "ISM->WSUS Site->Properties->Directory Security->Edit" and "ISM->WSUS Site->SelfUpdate->Properties->Directory Security->Edit" to match it's newly defined password from step 4.

Optional: use IIS Resource Kit tool tinyget like so (from the WSUS Server) for additional troubleshooting:

 tinyget -uri:/selfupdate/iuident.cab -srv:127.0.0.1 -a:0 -h(You should get a HTTP 1.1 200 OK if it is all working correctly)

-a:0 forces anonymous

-h sends back header info only

If you are getting back a 401 it's a permissions or password problem (Verify that permissions allow the IUSR_SERVERNAME on the SelfUpdate directory). 

于是按照如上所述,确定WSUS site的IP是否正确,重设IUSR_***密码,同时保证WSUS site的目录安全性启用Anonymous和密码一致。OK,解决此问题,顺利发现客户端计算机! 

   呵呵,看来下次解决问题还是要有耐心哦。仔细冷静。不过发现了一个非常好的网站。http://www.wsuswiki.com

posted on 2006-04-23 09:44  天一剑客  阅读(974)  评论(0)    收藏  举报