Software Deployment

Chris,

When someone uses the term;
" I pushed an app to about 200 workstations" I think SMS?

I spent a period of time as an SMS Admin in the Financial World. It can make you want to become a drunk. I can't tell you the number of times I heard the words "What did you push!".

I one day discovered that I was being attacked by a group of self impressed senior management types who's favorite pass time was trying out demo software from smiling Jack the software salesman.
Most of which was incompatable with our enviroment then NT-4.

3 failures out of 200 is a 98.5 precent success rate.

Now I don't doubt that the three are having a problem, and there may be more, but a question that you should ask yourself is also what is different on the failed systems.

I know that this is not a solution to your question, but there are way to many different ways to cause this error.

In my experence it is easier to find the differences in the workstations that caused the errors as this is nearly always the cause of your type of failure. I you focus on what should not be present on the involved systems the failure point is usually easily found.

Regards,

I asume you are using Win 2k, Maybe your next push should be SP4.

Correct me if I'm wrong but if you put the CD in and let WFP do it's thing doesn't it log the changes in the event log? I think even if you tell it to go away repatedly it will go away for that boot but log all the files with the incorrect signatures in the eventlog. I want to say the application log but it could be the system log. It's been a while since I've had to deal with that.

Hi kkaminsk, I actually found that you can look in the SYSTEM event log without putting the CD in and it shows the files. I should have looked there, but I only looked in APPLICATION when I was troubleshooting. I noticed all three files are part of MDAC, so instead of having someone walk around with the SP2 CD to anyone who complained about this problem, just run a silent MDAC install and it makes sure their files are up to date.

If you require a way to deploy MDAC via Active Directory using an MSI then you need to use the Windows Installer Wrapper Wizard, it is freeware and will easily wrap a setup.exe with command line switches into an MSI. It worked for me. I noticed the site that used to offer it in the forums no longer has a forums section (this might be temporary). If you email me I will send it to you.

Bob, do you have a storage area that I could upload it to?

WIWW.exe 452KB

Hi CDUPUIS,

MDAC wasn't actually what I was deploying, the app I deployed broke a few files that I noticed were in the MDAC manifest list. So MDAC was deployed as a fix. I don't use GP's to deploy, so deploying it was no big deal - I just pushed the command line MDAC_TYP.EXE /q /C:"setup /qn1" to the workstations.

Thanks,
Chris

What app did you push out? Is it possible that the installer called an older version of MDAC in silent mode and that is what killed the files, thus creating your protected files issue?