> "Toph" <Toph[ at ]discussions.microsoft.com> wrote in message
> news:DB000D36-8D00-4AD7-88D9-891C3EFEA85F[ at ]microsoft.com...
> > Hello,
> > I've got kind of a unique situation. I have a group of systems (200+) that
> > are internal, and run a custom application. These computers are Windows XP
> > SP1 systems. They do not have SP2 or any subsequent updates applied to
> > them.
> > In transitioning to a new version of this custom application, we required
> > the
> > .NET Framework version 2.0 installed.
> >
> > In a manual testing enviroment, we are able to install just the Windows
> > Installer v3.1 and .NET Framework v2.0 redist installs and everything
> > works.
> > To publish these updates out in a network enviroment, we installed a WSUS
> > server and approved all WSUS updates (including the Windows Installer) and
> > then the .NET Framework packages.
> >
> > Windows Installer 3.1 installed successfully, however the .NET Framework
> > returned a green light but when viewing the report, the update showed as
> > "Not
> > Applicable". Why wouldn't this update be applicable? All listed
> > prerequisites
> > have been met for this update, and it CAN be installed with the redist
> > package manually.
> >
> > Any ideas on why this isn't working?
>
> Well, without digging into the specifics of installing .NET Framework v2.0
> on an (unsupported) operating system (XP SP1), I can think of three possible
> reasons immediately:
>
> [a] Installation of the Windows Installer v3.1 is an *exclusive*/*mandatory*
> update for WSUS clients. Until that package is installed, and reported back
> to the WSUS Server as "Installed", the Windows Update Agent will *not*
> detect/download any other MSI-based installers (including .NET Framework
> packages).
>
> [b] .NET Framework v2.0 detection logic is determining that it cannot be
> supported on an XP SP1 system (even though you were able to successfully
> force the installation on that unsupported operating system).
>
> [c] One or more updates, post-SP1/pre-SP2, have not been applied which are
> *required* in order to install .NET Framework v2.0 -- also something you
> would not have encountered as a result of forcing the installation from the
> redist.
>
> If the reason is [a], then the issue should resolve itself upon the next
> detection event after reporting the successful reboot from installing
> Windows Installer v3.1
>
> If the reason is [b], then you'll have to force the installation of .NET
> Framework 2.0 on your XP SP1 systems.
>
> If the reason is [c], then you'll need to identify what the "missing"
> post-SP1 update are that .NET Framework needs to see in order to be
> installed via WSUS.
>
>
> You should also be extremely conscious of the fact that XP SP1 is an
> unsupported operating system platform, and .NET Framework v2.0 is
> unsupported on an XP SP1 system, and any applications (Microsoft,
> particularly) written to use the .NET Framework v2.0 will also be
> unsupported on an XP SP1 system.
>
> Furthermore, since you're "transitioning to a new version of this custom
> application", it's absolutely the time also to get this "custom application"
> working on a *supported* Windows XP Service Pack 2 platform. Unless this is
> an in-house "custom application" (in which case there's no excuse at all for
> not supporting the *latest* OS/SP), your vendor couldn't possibly have
> developed this application to use .NET Framework v2.0, unless their
> development machines were running Windows XP SP2 or Windows Server 2003 --
> either of which is required to develop with .NET Framework v2.0 -- which
> means that the application should be fully functional on XP SP2. Further,
> I'd be surprised if your *vendor* is willing to support their application in
> an XP SP1/.NET Framework v2 environment!
>
>
> --
> 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> .....
>
>
>
>