Tirsdag 25 september 2007 10:16, skrev Juan Jose Pablos: > Nils Olav Fossum escribió: > > Should have splitted the .net out too, but Im not shure about > > (confused!) asp.net and .net .. > > maybe we should split them up and create a iis.bat file?
Microsoft have it mixed up in their usual way ;-) see http://www.microsoft.com/technet/security/bulletin/ms07-040.mspx ..a asp.net fix in the .net framework. Im sure we can expect them to continue current practice.. Some reading I just did, Im not an expert on this.. asp.net: http://en.wikipedia.org/wiki/ASP.NET .net: http://en.wikipedia.org/wiki/.NET_Framework I vote for naming the file %winver%-dotnet.bat and take care of iis on case by case. The reasoning behind installing iis as default (but disable the service) in unattended was to get security updates onto the system with less pain. This has worked good for me over the years I have used unattended. I see no reason to change this.. ;-) > After the system was build, when conected to the internet, the windows > update want to install the following patches (11): > > KB890830 ah, yes, the "The Microsoft Windows Malicious Software Removal Tool" usually this the first thing i comment out when updating scripts. I am seeing this as a joke from our friends in Redmond. If I get an infected machine, I have this tool called unattended I use to reinstall these. Could be splittet out as win-common-MWMSRTjoke.bat hehe, I guess someone have better ideas for the name. :-D > KB933360 > KB938828 > KB936357 > KB927891 > KB930916 > KB923789 Do you see this on a fully patched system with the latest flash installed? > KB922582 > KB916595 > KB920872 > KB900485 > > Do you seee the same problem? Yes I do. But Im not shure they are a problem, except for KB923789. We should probably install this one just in case. > > > tested on Norwegian WinXp Pro. > I had tested in another system and they seem to work. > > > patches attached. > > I hope they can be used, Im not sure about the winxpsp2-mediaplayer.bat > > file naming.. ..but here goes > > I have same feeling, I belive that we should change the name to > mediaplayer10.bat Naming philosophy :-) I think we should use the %winver% start of the filename (for clarity and scripting) and end it with something humanreadable. As for mediaplayer script; skip the version info and do all the mediaplayer work in one file. (we also patch an old mediaplayer version in there) That way its easy to find the correct file If the user would like to customize the mediaplayer. We should always ship the latest version, thats what the end user wants. I do not think we have the manpower to maintain several versions anyway. So for winxpsp2 we get: winxpsp2-updates.bat winxpsp2-mediaplayer.bat winxpsp2-dotnet.bat win-common-MWMSRTjoke.bat or winall.. or wincommon.. ?? hehe, I hope more people will provide comments ;-) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ unattended-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-devel
