Guest Milos Puchta Posted October 28, 2007 Posted October 28, 2007 Hi I have installed WSUS 3 and have problem with client side detection. I have created groups and set up the group policy. GPMC results confirm the correct GPO settings. Clients are connecting to proxy instead of local update server. wuauclt /detectnow does not help. I would appreciate any help that make the process convergent. TIA Regards, Milos
Guest PA Bear Posted October 28, 2007 Posted October 28, 2007 Forwarded to WSUS newsgroup via crosspost: microsoft.public.windows.server.update_services as a convenience to OP. On the web: http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services In your newsreader: http://news://msnews.microsoft.com/microsoft.public.windows.server.update_services -- ~Robear Dyer (PA Bear) MS MVP-Windows (IE, OE, Security, Shell/User) AumHa VSOP & Admin http://aumha.net DTS-L http://dts-l.org/ Milos Puchta wrote: > Hi > > I have installed WSUS 3 and have problem with > client side detection. I have created groups and > set up the group policy. GPMC results confirm the > correct GPO settings. > Clients are connecting to proxy instead of local > update server. > wuauclt /detectnow > does not help. > > I would appreciate any help that make the process > convergent. > > TIA > Regards, > Milos
Guest Harry Johnston [MVP] Posted October 28, 2007 Posted October 28, 2007 Milos Puchta wrote: > I have installed WSUS 3 and have problem with > client side detection. I have created groups and > set up the group policy. GPMC results confirm the > correct GPO settings. > Clients are connecting to proxy instead of local > update server. You can configure the BITS proxy settings using BITSadmin: <http://msdn2.microsoft.com/en-us/library/aa362813.aspx> The appropriate command is probably (I haven't tested this): bitsadmin /util /setieproxy LOCALSYSTEM NO_PROXY (Windows Update Agent uses BITS as local system.) Harry.
Recommended Posts