SMS and largescale pushout of .net framework 1.1

We are preparing to use microsoft SMS to do a largescale pushout of the dot net framework 1.1 to about 3000 computers on a network. In a test scenario we issued the package to about 200 and only about 3/4 of the computers succesfully received and installed the package.

The system requirements of all systems is consistent with those listed on the Microsoft website. There appears to be no rhyme or reason to those that failed or those that didn't. Some were new, some were old, some had NT4.0 some had WinXP. Has anyone else had any experience using SMS to pushout the framework to all network clients.

The error reported by SMS on those that failed was...

The program for advertisement "CO1200CE" failed (".NET Framework" - "DotNETfix"). A non-zero exit code of 1603 was returned. Possible cause: SMS Advertised Program Manager (APM) determines status for each program it executes. If APM cannot find or correlate any install status Management Information Format (MIF) files for the program

Anyone else had luck with this? Thanks.

This has nothing to do with the particular error you experienced - but when a user logs in and has quite an unusually long wait to install the framework and perhaps doesn't realise why and say they reboot in frustration - what happens to the installation?

The package actually waits until they are all logged in and then runs in the background. They might notice a little lag in the system but it wouldn't keep them from being able to work. Supposedly if it does get interuppted it just starts over the next time the computer connects to the network.

Thanks, can it (and if so) what is involved in using it to install in house .NET application and updates?

It can install anything with an install package. It can also copy files to known directories or directories created by SMS. Check the microsoft website or product documentation for exact implementation. It has countless options.