Guest Harry Johnston [MVP] Posted August 5, 2008 Posted August 5, 2008 Joseph Rinaldi wrote: > Are you sure? Yes. The superficial symptoms may be the same, but jwchoo's Windows Update log shows no evidence of the problem you were having - it's failing at an earlier point in the process. > jwchoo, > > Can you please try the hotfix and see if it works for you? Well, it won't do any harm, assuming he is running WSUS 3 service pack 1. Harry. -- Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174
Guest jwchoo@gmail.com Posted August 7, 2008 Posted August 7, 2008 On Aug 5, 11:03 pm, Joseph Rinaldi <JosephRina...@discussions.microsoft.com> wrote: > Hi Harry, > > Are you sure? The problem I was getting was that a few computers were > appearing in WSUS but getting "This computer has not reported status yet".. > It had been ongoing for about 3 weeks. I installed the hotfix KB954960, and > then they all started to work. > > jwchoo, > > Can you please try the hotfix and see if it works for you? > > Joseph Rinaldi > > -- > Joseph Rinaldi > Clarius Group Ltd > > > > "Harry Johnston [MVP]" wrote: > > Joseph Rinaldi wrote: > > > > NOTE 1 > > > ~~~~~ > > > I have had this problem and been at it for nearly three weeks,. MS has found > > > that there was a problem with a DDL in WSUS. Go to > > >http://support.microsoft.com/kb/954960. > > > This isn't the same problem that jwchoo has. > > > Harry. > > > -- > > Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174- Hide quoted text - > > - Show quoted text - Hi Joseph/Harry/David I am happy to report I have got it working. Clients are reporting and getting updates. The only issue now is they are not populating the WSUS Computer Groups as in GP OUs. I followed instructions from http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-SelfUpdate-service-automatic-updates.aspx. To summarise what I have done:- 1. check the correct level of permission, ISUR_IISserver user for all the relevant folders. and anonynous user is checked on the Default Website. 2. IP address is Unassign for Default website Thank for all the help Jeremy
Guest jwchoo@gmail.com Posted August 7, 2008 Posted August 7, 2008 On Aug 8, 12:03 am, jwc...@gmail.com wrote: > On Aug 5, 11:03 pm, Joseph Rinaldi > > > > > > <JosephRina...@discussions.microsoft.com> wrote: > > Hi Harry, > > > Are you sure? The problem I was getting was that a few computers were > > appearing in WSUS but getting "This computer has not reported status yet". > > It had been ongoing for about 3 weeks. I installed the hotfix KB954960, and > > then they all started to work. > > > jwchoo, > > > Can you please try the hotfix and see if it works for you? > > > Joseph Rinaldi > > > -- > > Joseph Rinaldi > > Clarius Group Ltd > > > "Harry Johnston [MVP]" wrote: > > > Joseph Rinaldi wrote: > > > > > NOTE 1 > > > > ~~~~~ > > > > I have had this problem and been at it for nearly three weeks,. MS has found > > > > that there was a problem with a DDL in WSUS. Go to > > > >http://support.microsoft.com/kb/954960. > > > > This isn't the same problem that jwchoo has. > > > > Harry. > > > > -- > > > Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174-Hide quoted text - > > > - Show quoted text - > > Hi Joseph/Harry/David > > I am happy to report I have got it working. Clients are reporting and > getting updates. The only issue now is they are not populating the > WSUS Computer Groups as in GP OUs. I followed instructions fromhttp://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-S.... > To summarise what I have done:- > 1. check the correct level of permission, ISUR_IISserver user for all > the relevant folders. and anonynous user is checked on the Default > Website. > 2. IP address is Unassign for Default website > > Thank for all the help > Jeremy- Hide quoted text - > > - Show quoted text - I also started WHTTP web proxy service. I am not sure it is necessary. Jeremy
Guest DaveMills Posted August 8, 2008 Posted August 8, 2008 On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwchoo@gmail.com wrote: >I am happy to report I have got it working. Clients are reporting and >getting updates. The only issue now is they are not populating the >WSUS Computer Groups as in GP OUs. Two possibilities: 1) The client is not being told which group to use in the GPO or the spelling of the group does not match that is WSUS console. 2) The WSUS server is not set to use Client Side Targeting. > I followed instructions from >http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-SelfUpdate-service-automatic-updates.aspx. >To summarise what I have done:- >1. check the correct level of permission, ISUR_IISserver user for all >the relevant folders. and anonynous user is checked on the Default >Website. >2. IP address is Unassign for Default website > >Thank for all the help >Jeremy -- Dave Mills There are 10 type of people, those that understand binary and those that don't.
Guest jwchoo@gmail.com Posted August 8, 2008 Posted August 8, 2008 On Aug 8, 5:08 am, DaveMills <DaveMi...@newsgroup.nospam> wrote: > On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwc...@gmail.com wrote: > >I am happy to report I have got it working. Clients are reporting and > >getting updates. The only issue now is they are not populating the > >WSUS Computer Groups as in GP OUs. > > Two possibilities: > 1) The client is not being told which group to use in the GPO or the spelling of > the group does not match that is WSUS console. > 2) The WSUS server is not set to use Client Side Targeting. > > > I followed instructions from > >http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-S..... > >To summarise what I have done:- > >1. check the correct level of permission, ISUR_IISserver user for all > >the relevant folders. and anonynous user is checked on the Default > >Website. > >2. IP address is Unassign for Default website > > >Thank for all the help > >Jeremy > > -- > Dave Mills > There are 10 type of people, those that understand binary and those that don't. Dave I have Client side targeting setup. The OUs are nested like 1. Client systems\XP\Workstations 2. Client systems\XP\Laptops How do I name them in GP ? Jeremy
Guest DaveMills Posted August 9, 2008 Posted August 9, 2008 On Fri, 8 Aug 2008 06:58:08 -0700 (PDT), jwchoo@gmail.com wrote: >On Aug 8, 5:08 am, DaveMills <DaveMi...@newsgroup.nospam> wrote: >> On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwc...@gmail.com wrote: >> >I am happy to report I have got it working. Clients are reporting and >> >getting updates. The only issue now is they are not populating the >> >WSUS Computer Groups as in GP OUs. >> >> Two possibilities: >> 1) The client is not being told which group to use in the GPO or the spelling of >> the group does not match that is WSUS console. >> 2) The WSUS server is not set to use Client Side Targeting. >> >> > I followed instructions from >> >http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-S.... >> >To summarise what I have done:- >> >1. check the correct level of permission, ISUR_IISserver user for all >> >the relevant folders. and anonynous user is checked on the Default >> >Website. >> >2. IP address is Unassign for Default website >> >> >Thank for all the help >> >Jeremy >> >> -- >> Dave Mills >> There are 10 type of people, those that understand binary and those that don't. > >Dave > >I have Client side targeting setup. The OUs are nested like >1. Client systems\XP\Workstations >2. Client systems\XP\Laptops > >How do I name them in GP ? Use the setting in the WSUS policy settings Computer\Windows Components\Windows Update\Target group name for this computer You can either create a separate GPO for Laptops and Workstations with all the setting you need for each. or Create a GPO for XP with all the settings for all sub OUs and then have other GPO for Loptops OU etc which supply just the different settings such as groupname etc. You decide which, is it easier to have central setting for everything and overwrite these with the exception or just have totally separate GPOs and have to make change in all if something changes. I would definitely have WSUS setting in a GPO or their own and not added to Workstation Settings or Laptop Settings. It is too hard to maintain otherwise. > >Jeremy -- Dave Mills There are 10 type of people, those that understand binary and those that don't.
Guest jwchoo@gmail.com Posted August 12, 2008 Posted August 12, 2008 On Aug 9, 12:44 pm, DaveMills <DaveMi...@newsgroup.nospam> wrote: > On Fri, 8 Aug 2008 06:58:08 -0700 (PDT), jwc...@gmail.com wrote: > >On Aug 8, 5:08 am, DaveMills <DaveMi...@newsgroup.nospam> wrote: > >> On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwc...@gmail.com wrote: > >> >I am happy to report I have got it working. Clients are reporting and > >> >getting updates. The only issue now is they are not populating the > >> >WSUS Computer Groups as in GP OUs. > > >> Two possibilities: > >> 1) The client is not being told which group to use in the GPO or the spelling of > >> the group does not match that is WSUS console. > >> 2) The WSUS server is not set to use Client Side Targeting. > > >> > I followed instructions from > >> >http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-S..... > >> >To summarise what I have done:- > >> >1. check the correct level of permission, ISUR_IISserver user for all > >> >the relevant folders. and anonynous user is checked on the Default > >> >Website. > >> >2. IP address is Unassign for Default website > > >> >Thank for all the help > >> >Jeremy > > >> -- > >> Dave Mills > >> There are 10 type of people, those that understand binary and those that don't. > > >Dave > > >I have Client side targeting setup. The OUs are nested like > >1. Client systems\XP\Workstations > >2. Client systems\XP\Laptops > > >How do I name them in GP ? > > Use the setting in the WSUS policy settings > Computer\Windows Components\Windows Update\Target group name for this computer > > You can either create a separate GPO for Laptops and Workstations with all the > setting you need for each. > > or > > Create a GPO for XP with all the settings for all sub OUs and then have other > GPO for Loptops OU etc which supply just the different settings such as > groupname etc. > > You decide which, is it easier to have central setting for everything and > overwrite these with the exception or just have totally separate GPOs and have > to make change in all if something changes. > I would definitely have WSUS setting in a GPO or their own and not added to > Workstation Settings or Laptop Settings. It is too hard to maintain otherwise. > > > > >Jeremy > > -- > Dave Mills > There are 10 type of people, those that understand binary and those that don't.- Hide quoted text - > > - Show quoted text - I have done Computer\Windows Components\Windows Update\Target group name for this computer all the groups but still the same - not populating the groups as the ones in Group Policy. Jeremy
Guest DaveMills Posted August 12, 2008 Posted August 12, 2008 On Tue, 12 Aug 2008 09:20:15 -0700 (PDT), jwchoo@gmail.com wrote: >On Aug 9, 12:44 pm, DaveMills <DaveMi...@newsgroup.nospam> wrote: >> On Fri, 8 Aug 2008 06:58:08 -0700 (PDT), jwc...@gmail.com wrote: >> >On Aug 8, 5:08 am, DaveMills <DaveMi...@newsgroup.nospam> wrote: >> >> On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwc...@gmail.com wrote: >> >> >I am happy to report I have got it working. Clients are reporting and >> >> >getting updates. The only issue now is they are not populating the >> >> >WSUS Computer Groups as in GP OUs. >> >> >> Two possibilities: >> >> 1) The client is not being told which group to use in the GPO or the spelling of >> >> the group does not match that is WSUS console. >> >> 2) The WSUS server is not set to use Client Side Targeting. >> >> >> > I followed instructions from >> >> >http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-S.... >> >> >To summarise what I have done:- >> >> >1. check the correct level of permission, ISUR_IISserver user for all >> >> >the relevant folders. and anonynous user is checked on the Default >> >> >Website. >> >> >2. IP address is Unassign for Default website >> >> >> >Thank for all the help >> >> >Jeremy >> >> >> -- >> >> Dave Mills >> >> There are 10 type of people, those that understand binary and those that don't. >> >> >Dave >> >> >I have Client side targeting setup. The OUs are nested like >> >1. Client systems\XP\Workstations >> >2. Client systems\XP\Laptops >> >> >How do I name them in GP ? >> >> Use the setting in the WSUS policy settings >> Computer\Windows Components\Windows Update\Target group name for this computer >> >> You can either create a separate GPO for Laptops and Workstations with all the >> setting you need for each. >> >> or >> >> Create a GPO for XP with all the settings for all sub OUs and then have other >> GPO for Loptops OU etc which supply just the different settings such as >> groupname etc. >> >> You decide which, is it easier to have central setting for everything and >> overwrite these with the exception or just have totally separate GPOs and have >> to make change in all if something changes. >> I would definitely have WSUS setting in a GPO or their own and not added to >> Workstation Settings or Laptop Settings. It is too hard to maintain otherwise. >> >> >> >> >Jeremy >> >> -- >> Dave Mills >> There are 10 type of people, those that understand binary and those that don't.- Hide quoted text - >> >> - Show quoted text - > >I have done Computer\Windows Components\Windows Update\Target group >name for this computer >all the groups but still the same - not populating the groups as the >ones in Group Policy. What does WindowsUpdate.log say the client is getting for "Target Group" > >Jeremy -- Dave Mills There are 10 type of people, those that understand binary and those that don't.
Guest Harry Johnston [MVP] Posted August 14, 2008 Posted August 14, 2008 jwchoo@gmail.com wrote: > I have Client side targeting setup. The OUs are nested like > 1. Client systems\XP\Workstations > 2. Client systems\XP\Laptops > > How do I name them in GP ? I believe you should specify Workstations and Laptops respectively, i.e., ignore the nesting entirely and only specify the last component. I may be misremembering, I don't do this routinely - but it's worth a try. :-) Harry. -- Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174
Guest jwchoo@gmail.com Posted August 18, 2008 Posted August 18, 2008 On Aug 14, 1:18 am, "Harry Johnston [MVP]" <ha...@scms.waikato.ac.nz> wrote: > jwc...@gmail.com wrote: > > I have Client side targeting setup. The OUs are nested like > > 1. Client systems\XP\Workstations > > 2. Client systems\XP\Laptops > > > How do I name them in GP ? > > I believe you should specify Workstations and Laptops respectively, i.e., ignore > the nesting entirely and only specify the last component. I may be > misremembering, I don't do this routinely - but it's worth a try. :-) > > Harry. > > -- > Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174 ok I will give it a try. Thanks Jeremy
Recommended Posts