Status for .NET FW 1.1 show up "Not Applicable" MAJohnson 6/14/2007 11:42:00 PM Our company recently deployed WSUS 3. I setup the .NET FW v1.1 to install on a group of computers. The approval shows up as install, but the status shows "Not Applicable". Other updates are installing just fine.

Re: Status for .NET FW 1.1 show up "Not Applicable" Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/15/2007 1:15:55 AM MAJohnson wrote: [Quoted Text] > Our company recently deployed WSUS 3. I setup the .NET FW v1.1 to install on > a group of computers. The approval shows up as install, but the status shows > "Not Applicable". Other updates are installing just fine. "Not Applicable" can in some circumstances mean "Installed". Is .NET 1.1 already installed on those computers? What operating system are they running? Harry.

Re: Status for .NET FW 1.1 show up "Not Applicable" MAJohnson 6/15/2007 6:17:00 AM The systems are Windows XP SP2. .NET FW 1.1 is not installed on these PCs. I can go out to the MS update site where I am told that .NET FW 1.1 is available to download and install from the update site. On another machine I downloaded the .NET FW v1.1 from the MS update site. It downloaded and installed. After rebooting the PC I checked WSUS. It showed up as installed, and that the latest update for .NET FW v1.1 was needed. "Harry Johnston" wrote: [Quoted Text] > MAJohnson wrote: > > > Our company recently deployed WSUS 3. I setup the .NET FW v1.1 to install on > > a group of computers. The approval shows up as install, but the status shows > > "Not Applicable". Other updates are installing just fine. > > "Not Applicable" can in some circumstances mean "Installed". Is .NET 1.1 > already installed on those computers? What operating system are they running? > > Harry. > >

Re: Status for .NET FW 1.1 show up "Not Applicable" "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/16/2007 3:57:41 AM "MAJohnson" <MAJohnson[ at ]discussions.microsoft.com> wrote in message news:81276340-8B12-4C6C-A6CC-32C44A0CD0E2[ at ]microsoft.com... [Quoted Text] >> > Our company recently deployed WSUS 3. I setup the .NET FW v1.1 to >> > install on >> > a group of computers. The approval shows up as install, but the status >> > shows >> > "Not Applicable". Other updates are installing just fine. >> "Not Applicable" can in some circumstances mean "Installed". Is .NET 1.1 >> already installed on those computers? What operating system are they >> running? > The systems are Windows XP SP2. .NET FW 1.1 is not installed on these > PCs. > I can go out to the MS update site where I am told that .NET FW 1.1 is > available to download and install from the update site. On another > machine I > downloaded the .NET FW v1.1 from the MS update site. It downloaded and > installed. After rebooting the PC I checked WSUS. It showed up as > installed, and that the latest update for .NET FW v1.1 was needed. If the status shows up as "Not Applicable", this means the Windows Update Agent has definitively determined one of two things: [a] The update is not needed by the client system, or [b] The update cannot be installed on the current patch state of the client system. Here's the most likely scenario I can imagine given all the facts currently available. Since the .NET Framework packages are language-specific, I'll venture a speculative, but educated guess, that the language of the installed Operating System(s) do not match the language of the approved .NET Framework v1.1 update packages. Ergo, the approved package is "Not Applicable". -- 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Status for .NET FW 1.1 show up "Not Applicable" MAJohnson 6/18/2007 3:29:00 PM Good Morning Sir, I checked the version of .NET v1.1 SP1 on WSUS. It shows up as supporting all langugages. On Friday I scanned through the Microsoft Update Catalog (Beta) for the older version of .NET FW v1.1 without SP1. I downloaded it, setup a group in WSUS to push, added a couple of systems that were having the problem, and approved the patch to install to this group. (.NET FW v1.1 SP1 and the security patch were still approved to install to all groups). This morning I ran a report on the test group and noticed that .NET FW v1.1 (NoSP1) installed, .NET FW SP1 v1.1 installed and the .NET FW v1.1 Secrutiy patch installed. Do you know why some patches that are installed on the XPSP2 workstations show up as "installed" and other installed patches show up as "Not Applicable" in WSUS 3? I do not remember having this issue with the previous version of WSUS. Thank you for your time in helping me with this. Michael "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "MAJohnson" <MAJohnson[ at ]discussions.microsoft.com> wrote in message > news:81276340-8B12-4C6C-A6CC-32C44A0CD0E2[ at ]microsoft.com... > > >> > Our company recently deployed WSUS 3. I setup the .NET FW v1.1 to > >> > install on > >> > a group of computers. The approval shows up as install, but the status > >> > shows > >> > "Not Applicable". Other updates are installing just fine. > > >> "Not Applicable" can in some circumstances mean "Installed". Is .NET 1.1 > >> already installed on those computers? What operating system are they > >> running? > > > The systems are Windows XP SP2. .NET FW 1.1 is not installed on these > > PCs. > > I can go out to the MS update site where I am told that .NET FW 1.1 is > > available to download and install from the update site. On another > > machine I > > downloaded the .NET FW v1.1 from the MS update site. It downloaded and > > installed. After rebooting the PC I checked WSUS. It showed up as > > installed, and that the latest update for .NET FW v1.1 was needed. > > If the status shows up as "Not Applicable", this means the Windows Update > Agent has definitively determined one of two things: > [a] The update is not needed by the client system, or > [b] The update cannot be installed on the current patch state of the > client system. > > Here's the most likely scenario I can imagine given all the facts currently > available. > > Since the .NET Framework packages are language-specific, I'll venture a > speculative, but educated guess, that the language of the installed > Operating System(s) do not match the language of the approved .NET Framework > v1.1 update packages. Ergo, the approved package is "Not Applicable". > > > -- > 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >

Re: Status for .NET FW 1.1 show up "Not Applicable" Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/18/2007 6:59:14 PM MAJohnson wrote: [Quoted Text] > Do you know why some patches that are installed on the XPSP2 workstations > show up as "installed" and other installed patches show up as "Not > Applicable" in WSUS 3? I do not remember having this issue with the previous > version of WSUS. I can confirm that WSUS 2 behaves in the same way. I suspect this is due to design limitations in the specific software being patched, although it may be an error in the detection logic for the update. So long as you're aware of it, it's relatively harmless. Harry.

Re: Status for .NET FW 1.1 show up "Not Applicable" MAJohnson 6/18/2007 7:10:01 PM Thank you Sir. I appreciate your help regards, Michael "Harry Johnston" wrote: [Quoted Text] > MAJohnson wrote: > > > Do you know why some patches that are installed on the XPSP2 workstations > > show up as "installed" and other installed patches show up as "Not > > Applicable" in WSUS 3? I do not remember having this issue with the previous > > version of WSUS. > > I can confirm that WSUS 2 behaves in the same way. I suspect this is due to > design limitations in the specific software being patched, although it may be an > error in the detection logic for the update. So long as you're aware of it, > it's relatively harmless. > > Harry. >

Re: Status for .NET FW 1.1 show up "Not Applicable" "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/19/2007 1:55:01 AM "MAJohnson" <MAJohnson[ at ]discussions.microsoft.com> wrote in message news:1B8B694E-B9A2-478A-AAED-0B1D7AE1B762[ at ]microsoft.com... [Quoted Text] > Do you know why some patches that are installed on the XPSP2 workstations > show up as "installed" and other installed patches show up as "Not > Applicable" in WSUS 3? I do not remember having this issue with the > previous > version of WSUS. I know exactly why. If the product/update/application is installed as a part of the core operating system installation (e.g. XP SP2 on a slipstreamed XP SP2 installation, or .NET Framework v1.1 wSP1 on a slipstreamed Win2003SP1 installation), then those updates will be reported as "Not Applicable", because, they are, in fact, not applicable. They cannot be installed, they are not needed, and they cannot be uninstalled. If the product/update/application is not part of the core OS installation, then it will be detected and reported as "Needed" or "Not Installed" as is appropriate to the circumstances. The behavior has not changed from WSUS2 to WSUS3, except to note that ALL product/classifications are set to auto-detect on WSUS3, so you're likely to see more occurrences of this behavior than before (where auto-detect was generally only configured for Security/Critical updates). -- 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Status for .NET FW 1.1 show up "Not Applicable" Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/19/2007 3:19:20 AM Lawrence Garvin (MVP) wrote: [Quoted Text] > If the product/update/application is installed as a part of the core > operating system installation (e.g. XP SP2 on a slipstreamed XP SP2 > installation, or .NET Framework v1.1 wSP1 on a slipstreamed Win2003SP1 > installation), then those updates will be reported as "Not Applicable", There are also other cases. For example, the XML 4 updates, e.g., 925672, have the same behaviour. In this case I suspect it is related to the fact that the update is actually a full installer for the most recent version of the component. Harry.

Re: Status for .NET FW 1.1 show up "Not Applicable" MAJohnson 6/19/2007 2:49:04 PM Lawrence, Thank you for the information. I appreciate the detail that you have provided. I was able to get the .NET FW 1.1 (w/o SP1) installed. Once that installed, then the SP1 installed and the security updates. This version of ..NET is needed to install ChemFinder v10. Without this version of .NET the application will not even install. Once again I appreciate your help with this matter. Regards, Michael "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "MAJohnson" <MAJohnson[ at ]discussions.microsoft.com> wrote in message > news:1B8B694E-B9A2-478A-AAED-0B1D7AE1B762[ at ]microsoft.com... > > > Do you know why some patches that are installed on the XPSP2 workstations > > show up as "installed" and other installed patches show up as "Not > > Applicable" in WSUS 3? I do not remember having this issue with the > > previous > > version of WSUS. > > I know exactly why. > > If the product/update/application is installed as a part of the core > operating system installation (e.g. XP SP2 on a slipstreamed XP SP2 > installation, or .NET Framework v1.1 wSP1 on a slipstreamed Win2003SP1 > installation), then those updates will be reported as "Not Applicable", > because, they are, in fact, not applicable. They cannot be installed, they > are not needed, and they cannot be uninstalled. > > If the product/update/application is not part of the core OS installation, > then it will be detected and reported as "Needed" or "Not Installed" as is > appropriate to the circumstances. > > The behavior has not changed from WSUS2 to WSUS3, except to note that ALL > product/classifications are set to auto-detect on WSUS3, so you're likely to > see more occurrences of this behavior than before (where auto-detect was > generally only configured for Security/Critical updates). > > -- > 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >