bmair
Posts: 228
Score: 0 Joined: 3/3/2003 From: Da Bronx Status: offline
|
I am still working on this. I thought that I might have got the procedure by using my best quess. I can use the Distribute SoftwareWizard to build the Update packages,and the clients will successfully run the packages, as per the logs. However they don't install the patches. I check the Windows directory and Regsitry and I don't see anything to indicate the patches got installed. I am thinking that the problem is that the scanwrapper part of the package isn't running properly, somehow and it maybe that I emssed up somewhere in my attempt to upgrade. Therefore, I am asking for a step - by- step procedure of what you would do if you had to work with SMS 2003 SUSFP and had to upgrade the MBSA portion of the SUSFP? Here's what I did when I tried to do the upgrade from MBSA 1.2.1 to 2.0.1 a: Installed MBSA 2.0.1 on the server and then copied the Pkgsource folder from the MBSA 2.0.1 installation folder to the SecurityPatch folder. 2: Created and advertised a package for the new scanwrapper.exe which I ran on all the clients. Since I was then able to get clients requesting patches in Software Updates and then able to use the DSW, I thought that I was good to go. But, now I see that the patches aren't actually being installed, success messages notwithstanding. I realize that we've gone past using that method, but, unfortunately I am stuck with this now for the next year, at least! Thanks in advance
_____________________________
Bancroft Affiliated Computer Services, Inc. Information Management Senior Analyst New York, New York
|