WSUS v3.0 upgrade client download issue John 6/29/2007 12:26:01 AM All, Upgraded WSUS v2.0 (SP1) to v3.0. The new MMC v3.0 Console populated with all the clients in their Computer Groups. A couple things of concern: 1) I have a new anomaly, Approval called Install (inherited) and Deadline called None (inherited) which are grayed out on various Computer Groups. At one time we had Client-Side Targeting with one Computer Group, but broke that group into separate Computer Groups and set Server-Side Targeting. All before the Upgrade. Could this "inherited" have something to do with this? Also, it shows many machines needing these Updates which were previously Approved & pushed out before the Upgrade. How can I clear this? Do these updates need to be re-approved? 2) Now after the upgrade, new RIS'd PC's are failing in the Download process. In troubleshooting I've performed the following: a) Stopped the wuauclt service, deleted the WindowsUpdate registry keys & SoftwareDistribution folder contents, started the service, reauthorized & detected. b) Verified the selfupdate tree on the WSUS server port 80 with the cscript cmd. c) Verify I can call up the wuident.cab in Internet Explorer. d) Checked the windowsupdate.log file and discovered "download failed, error = 0x80244019" which is leading me to a 404 file not found (please correct me if I'm wrong). At this point I'm not sure of my next step. The URL is the old v2.0 (SP1) web page. What would it need that for now? I can see the new client self update tree, but has IIS become corrupt in the Upgrade process? Any assistance is surely appreciated! Thanks, John

RE: WSUS v3.0 upgrade client download issue John 6/29/2007 5:10:01 PM All, Regarding entry # 2 below: I found the Upgrade created a new WsusContent share under the install directory. I had to create a new share on the original (which I have under the data partition (E:\Wsus\WsusContent) & replace the newly created w/ the original on E. Then in IIS, point the Content virtual directory from the newly created path to the original on E. New RIS'd machines are now getting their updates. But I still haven't figured out what the grayed out "inherited" Approval & Deadline is & what to do. If anyone can help with that, I'd certainly appreciate it. Thanks, John "John" wrote: [Quoted Text] > All, > > Upgraded WSUS v2.0 (SP1) to v3.0. The new MMC v3.0 Console populated with > all the clients in their Computer Groups. > > A couple things of concern: > > 1) I have a new anomaly, Approval called Install (inherited) and Deadline > called None (inherited) which are grayed out on various Computer Groups. At > one time we had Client-Side Targeting with one Computer Group, but broke that > group into separate Computer Groups and set Server-Side Targeting. All before > the Upgrade. Could this "inherited" have something to do with this? Also, it > shows many machines needing these Updates which were previously Approved & > pushed out before the Upgrade. How can I clear this? Do these updates need to > be re-approved? > > 2) Now after the upgrade, new RIS'd PC's are failing in the Download > process. In troubleshooting I've performed the following: > a) Stopped the wuauclt service, deleted the WindowsUpdate registry keys & > SoftwareDistribution folder contents, started the service, reauthorized & > detected. > b) Verified the selfupdate tree on the WSUS server port 80 with the cscript > cmd. > c) Verify I can call up the wuident.cab in Internet Explorer. > d) Checked the windowsupdate.log file and discovered "download failed, error > = 0x80244019" which is leading me to a 404 file not found (please correct me > if I'm wrong). At this point I'm not sure of my next step. The URL is the old > v2.0 (SP1) web page. What would it need that for now? I can see the new > client self update tree, but has IIS become corrupt in the Upgrade process? > > Any assistance is surely appreciated! > Thanks, > John >

Re: WSUS v3.0 upgrade client download issue "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 7/10/2007 4:16:24 AM "John" <John[ at ]discussions.microsoft.com> wrote in message news:6C8B9717-D39C-4B5D-80AA-AC5408C63E8F[ at ]microsoft.com... [Quoted Text] > But I still haven't figured out what the grayed out "inherited" Approval & > Deadline is & what to do. If anyone can help with that, I'd certainly > appreciate it. Maybe they're not grayed out. Maybe you just need to click on the little box to the left of the line for the desired group, and select the appropriate approval type from the context menu? -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://www.microsoft.com/wsus And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: WSUS v3.0 upgrade client download issue John 7/10/2007 1:50:02 PM Lawrence, You mentioned in another post for me that the grey inherited in v3.0 was from approving All Computers in the v2.0 (SP1) prior to the upgrade. I would normally select All Computers Install, then the appropriate selection for the sub groups. As for a better managed approach to approvals in v3.0, any suggestion would be greatly appreciated. I'm currently testing All Computers Install and All Computers Not Approved, then the appropriate selection for the sub groups. Thanks, John "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "John" <John[ at ]discussions.microsoft.com> wrote in message > news:6C8B9717-D39C-4B5D-80AA-AC5408C63E8F[ at ]microsoft.com... > > > But I still haven't figured out what the grayed out "inherited" Approval & > > Deadline is & what to do. If anyone can help with that, I'd certainly > > appreciate it. > > Maybe they're not grayed out. Maybe you just need to click on the little box > to the left of the line for the desired group, and select the appropriate > approval type from the context menu? > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://www.microsoft.com/wsus > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >

Re: WSUS v3.0 upgrade client download issue "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 7/11/2007 1:46:06 AM "John" <John[ at ]discussions.microsoft.com> wrote in message news:8AF4265A-0CBC-48C8-B8CB-80E4052D534C[ at ]microsoft.com... [Quoted Text] > Lawrence, > > You mentioned in another post for me that the grey inherited in v3.0 was > from approving All Computers in the v2.0 (SP1) prior to the upgrade. I > would > normally select All Computers Install, then the appropriate selection for > the > sub groups. The label "(inherited)" is a default behavior of WSUS 3, and it's picking up whatever was migrated/upgraded from WSUS 2. If your practice was to approve updates for "All Computers", then it makes sense that "All Computers" = Install, and everything else shows as Install (inherited) Practices vary from admin to admin, according to what works best, but in my case, I almost always leave "All Computers" and "Unassigned Computers" set to "Not Approved", and I assign approvals at the group level, appropriate for the systems that are members of those groups. However, there are some exceptions. For example, I auto-approve Windows Defender updates for "All Computers". Whether or not something is "greyed out" may be simply a matter of (mis)interpretation. I'm not aware of any circumstances in which any objects in the approval dialog are disabled -- in the typical sense of something being "greyed out". But groups with *inherited* permissions are displayed in grey. Groups with "not approved" permissions display in red, and groups with "install" permissions display in green. The color coding only applies to the dropdown/button. The text is always grey. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://www.microsoft.com/wsus And, almost everything else is at http://wsusinfo.onsitechsolutions.com ..... > > As for a better managed approach to approvals in v3.0, any suggestion > would > be greatly appreciated. I'm currently testing All Computers Install and > All > Computers Not Approved, then the appropriate selection for the sub groups. > > Thanks, > John > > > "Lawrence Garvin (MVP)" wrote: > >> "John" <John[ at ]discussions.microsoft.com> wrote in message >> news:6C8B9717-D39C-4B5D-80AA-AC5408C63E8F[ at ]microsoft.com... >> >> > But I still haven't figured out what the grayed out "inherited" >> > Approval & >> > Deadline is & what to do. If anyone can help with that, I'd certainly >> > appreciate it. >> >> Maybe they're not grayed out. Maybe you just need to click on the little >> box >> to the left of the line for the desired group, and select the appropriate >> approval type from the context menu? >> >> -- >> Lawrence Garvin, M.S., MCTS, MCP >> Independent WSUS Evangelist >> MVP-Software Distribution (2005-2007) >> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E >> >> Everything you need for WSUS is at >> http://www.microsoft.com/wsus >> >> And, almost everything else is at >> http://wsusinfo.onsitechsolutions.com >> ..... >> >> >>

Re: WSUS v3.0 upgrade client download issue John 7/11/2007 1:48:02 PM Lawrence, I'll try the Not Approved for All Computers and be specific for my sub groups as you mentioned. This will be our 1st month pushing out with v3.0. Again, thank you. John "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "John" <John[ at ]discussions.microsoft.com> wrote in message > news:8AF4265A-0CBC-48C8-B8CB-80E4052D534C[ at ]microsoft.com... > > Lawrence, > > > > You mentioned in another post for me that the grey inherited in v3.0 was > > from approving All Computers in the v2.0 (SP1) prior to the upgrade. I > > would > > normally select All Computers Install, then the appropriate selection for > > the > > sub groups. > > The label "(inherited)" is a default behavior of WSUS 3, and it's picking up > whatever was migrated/upgraded from WSUS 2. If your practice was to approve > updates for "All Computers", then it makes sense that "All Computers" = > Install, and everything else shows as Install (inherited) > > Practices vary from admin to admin, according to what works best, but in my > case, I almost always leave "All Computers" and "Unassigned Computers" set > to "Not Approved", and I assign approvals at the group level, appropriate > for the systems that are members of those groups. However, there are some > exceptions. For example, I auto-approve Windows Defender updates for "All > Computers". > > Whether or not something is "greyed out" may be simply a matter of > (mis)interpretation. I'm not aware of any circumstances in which any objects > in the approval dialog are disabled -- in the typical sense of something > being "greyed out". > > But groups with *inherited* permissions are displayed in grey. Groups with > "not approved" permissions display in red, and groups with "install" > permissions display in green. The color coding only applies to the > dropdown/button. The text is always grey. > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://www.microsoft.com/wsus > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > > > > > As for a better managed approach to approvals in v3.0, any suggestion > > would > > be greatly appreciated. I'm currently testing All Computers Install and > > All > > Computers Not Approved, then the appropriate selection for the sub groups. > > > > Thanks, > > John > > > > > > "Lawrence Garvin (MVP)" wrote: > > > >> "John" <John[ at ]discussions.microsoft.com> wrote in message > >> news:6C8B9717-D39C-4B5D-80AA-AC5408C63E8F[ at ]microsoft.com... > >> > >> > But I still haven't figured out what the grayed out "inherited" > >> > Approval & > >> > Deadline is & what to do. If anyone can help with that, I'd certainly > >> > appreciate it. > >> > >> Maybe they're not grayed out. Maybe you just need to click on the little > >> box > >> to the left of the line for the desired group, and select the appropriate > >> approval type from the context menu? > >> > >> -- > >> Lawrence Garvin, M.S., MCTS, MCP > >> Independent WSUS Evangelist > >> MVP-Software Distribution (2005-2007) > >> https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > >> > >> Everything you need for WSUS is at > >> http://www.microsoft.com/wsus > >> > >> And, almost everything else is at > >> http://wsusinfo.onsitechsolutions.com > >> ..... > >> > >> > >> > > >