49 replies to this topic

[_def_x_]

Cristiano said:

i'm thinking about remove it from the xp script and make another script, something like "Microsoft Security", with Windows Defender and Microsoft Security Essentials...i'm not sure about where put it. under components or at stand alones?

I like the idea.

'Stand Alone' or 'Updated Components' is good. I would try to be consistant though, if it is a separate script like Java, Adobe, etc and isn't required for MU/WU, 'Stand Alone' is a good place for these scripts, this is why I thought it was created.

[Cristiano]

so, stand alone will be. well, the removal for windows defender will be set tomorrow. i can't add an "move" because isn't the same script, but the file seems to be the same. so, an hint: save that file to save some download time...

[]s

[DesertJerry]

I don't really like Stand Alone as a separate item. It fails to convey any indication of what it actually includes.

I would propose a new and different item: Windows Complementary Items. I picked 'complement' because of this usage: A 'complement' is something added to enhance a thing and make it complete. (Not to be confused with 'compliment' which is to praise someone.)

Then I would move all of those non-Microsft items like Adobe Reader, Sun Java, Flash Player, Shockwave Player, etc so they are listed under Windows Complementary Items as they are not really Microsft items and should not be included as if they were Windows or Office components.

#1 = Stand Alone or #2 = Windows Complementary Items - I vote for #2.

[DesertJerry]

Also, go here: http://social.answer...4f-0dcedb9ab9fd and be aware that you may have to provide similar comments for those people running Win7 - which installs Windows Defender by default, and those that installed Windows Defender in XP - Microsoft Security Essentials should uninstall/disable Windows Defender.

[Cristiano]

that's also an idea. the main problem is that to rename it several scripts also have to be re-signed. about java, flash players, shockwave, etc, it's the same thing. the only one issue with flash player is that this one replaces one kb from microsoft that is still included in the xp script. but it's possible do that. one idea: move them when each one is replaced and

[]s

[_def_x_]

DesertJerry said:

I don't really like Stand Alone as a separate item. It fails to convey any indication of what it actually includes.

This may be true but no single 'Title' can convey such meaning, this is where the 'Description' comes in...

Title=Stand Alone: Complementary Addons
Description=The Stand Alone category contains complementary software titles such as Adobe Reader, Microsoft Security Essentials, Windows Defender, among others, and user created AddOns

You could simply add the names to the 'description' as they are released (in alphabetical order),
Description=Adobe Reader, Cristiano's Super 7 Addon, DesertJerry's XP Pack, Java, Microsft Security Essentials, Windows Defender...

My opinion is don't overthink this

[DesertJerry]

 gUiTaR_mIkE, on 25 August 2010 - 05:16 PM, said:

My opinion is don't overthink this

I'll stick with my comment.

[Cristiano]

ok, finally i've found some free time to work with ms security... the modules aren't really ready yet, but it's an start. for those that wish to test it, attached are the modules required to run the modules and at this post, yours can find the download links as well

Spoiler

Item=WindowsDefenderX64.msi
DetectFile=autopatcher:\modules\stand_alone\WindowsDefenderX64.apm_files\WindowsDefenderX64.msi
DetectHash=861F0521375FA10BB3E4B7A59386DC4E
DownloadFrom=http://download.microsoft.com/download/d/6/d/d6d8f548-69f2-4c5d-84be-a64fe41cc87a/WindowsDefenderX64.msi
DownloadTo=autopatcher:\modules\stand_alone\WindowsDefenderX64.apm_files\WindowsDefenderX64.msi
ExpectedSize=7308288
ExpectedHash=861F0521375FA10BB3E4B7A59386DC4E

Item=WindowsDefender.msi
DetectFile=autopatcher:\modules\stand_alone\WindowsDefender.apm_files\WindowsDefender.msi
DetectHash=B5429CC7F9A55F5DE0182E88BB619AFF
DownloadFrom=http://download.microsoft.com/download/e/d/0/ed099d5e-dc60-4740-8747-1c72f053b800/WindowsDefender.msi
DownloadTo=autopatcher:\modules\stand_alone\WindowsDefender.apm_files\WindowsDefender.msi
ExpectedSize=5154304
ExpectedHash=B5429CC7F9A55F5DE0182E88BB619AFF

Item=mssefullinstall-amd64fre-en-us-vista-win7.exe
DetectFile=autopatcher:\modules\stand_alone\mssefullinstall-amd64fre-en-us-vista-win7.apm_files\mssefullinstall-amd64fre-en-us-vista-win7.exe
DetectHash=81B42A4041B67F645153EB7D3194CBC5
DownloadFrom=http://download.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/mssefullinstall-amd64fre-en-us-vista-win7.exe
DownloadTo=autopatcher:\modules\stand_alone\mssefullinstall-amd64fre-en-us-vista-win7.apm_files\mssefullinstall-amd64fre-en-us-vista-win7.exe
ExpectedSize=7537912
ExpectedHash=81B42A4041B67F645153EB7D3194CBC5

Item=mssefullinstall-x86fre-en-us-vista-win7.exe
DetectFile=autopatcher:\modules\stand_alone\mssefullinstall-x86fre-en-us-vista-win7.apm_files\mssefullinstall-x86fre-en-us-vista-win7.exe
DetectHash=23E41A03B733D7124145674519EB7C80
DownloadFrom=http://download.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/mssefullinstall-x86fre-en-us-vista-win7.exe
DownloadTo=autopatcher:\modules\stand_alone\mssefullinstall-x86fre-en-us-vista-win7.apm_files\mssefullinstall-x86fre-en-us-vista-win7.exe
ExpectedSize=7315936
ExpectedHash=23E41A03B733D7124145674519EB7C80

Item=mssefullinstall-x86fre-en-us-xp.exe
DetectFile=autopatcher:\modules\stand_alone\mssefullinstall-x86fre-en-us-xp.apm_files\mssefullinstall-x86fre-en-us-xp.exe
DetectHash=8214B1EE37E6D5F514A70E26F945F63A
DownloadFrom=http://download.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/mssefullinstall-x86fre-en-us-xp.exe
DownloadTo=autopatcher:\modules\stand_alone\mssefullinstall-x86fre-en-us-xp.apm_files\mssefullinstall-x86fre-en-us-xp.exe
ExpectedSize=11862384
ExpectedHash=8214B1EE37E6D5F514A70E26F945F63A

issues:
1 - i didn't tested any removal command and they are probably broken. in order to take those commands, the removal command under the uninstall key in windows registry must be taken

2 - ms security essentials is tricky to do an silent install. in order to work, an command has to be set to kill the update task that prompts as soon the module is deployed. i think that i've done it right but it requires further testing, even more under xp. worst case scenario: the install will not be fully silent

[]s

Edited by Cristiano, 06 September 2010 - 11:43 PM.

[DesertJerry]

I revieved the APM files for XP Pro, XP Pro x64, Win7 32- and 64-bit and the information matched what appears here.

One minor item concerning XP Pro x64 - the latest update is SP2 so you may want to edit:

[OperatingSystem]
WindowsVersion=XP_X64,2K3_SP1_X64,2K3_SP2_X64,VISTA_X64
SystemLanguage=ANY

so it includes: XP_SP2_X64

[Cristiano]

but sp2 it's included anyway. the restriction works in this way:
XP_X64 -> all service packs x64
xp_sp2_x64 -> xp sp2 x64 (only)

so, it is lacking the removal command only. i can't check the silent install for xp x64, but i will try find it for the other versions. for vista/seven, the removal is the same for x86 (the same thing happens to x64, but it's the same between the x64 versions, except for xp x64)

i will try find the removals for the x86 versions today

thanks

[]s

[DesertJerry]

 Cristiano, on 09 September 2010 - 12:03 PM, said:

but sp2 it's included anyway. the restriction works in this way:
XP_X64 -> all service packs x64
xp_sp2_x64 -> xp sp2 x64 (only)

If the above is true concerning SP's or not then why bother including the SP's at all in any of the APMs?

For example, in one APM it's listed this way:
[OperatingSystem]
WindowsVersion=XP_SP2_X86,XP_SP3_X86,XP_MCE2005_X86,2K3_SP1_X86,2K3_SP2_X86,VISTA_X86
SystemLanguage=ANY

Your answer indicates all the _SP2_ or _SP1_ etc are not necessary.

[Cristiano]

> Your answer indicates all the _SP2_ or _SP1_ etc are not necessary.
half true. that update probably doesn't work for xp sp1 or xp rtm. in this particular case, when you have to restrict the update to not work under sp1 and rtm, you have to enforce XP_SP2_X86,XP_SP3_X86, making the update load only into those serve packs. by other hand, if the update is intended to run under any SP version, then the restrict variable can be set to be XP and X86, that will make the update run under any service pack or version of windows xp (since x86, of course)

by the way, this seems to work as an removal for all the Microsoft Security Essentials:
%PROGRAMFILES%:\Microsoft Security Essentials\setup.exe /s /x

it's also possible do an removal with MsiExec.exe, but i don't advise it under seven. after do that into an seven vm, Microsoft Security Essentials was unable to install again

as for windows defender x86, only this was possible as uninstall:
MsiExec.exe /qn /x{A06275F4-324B-4E85-95E6-87B2CD729401}

as i don't have xp x64, i can't even look at windows registry for an removal, sorry

[]s

[DesertJerry]

XP Pro x64 w/SP2

Windows Defender 1.1.1593.0
Engine Version: 1.1.6103.0
Definition Version: 1.89.1411.0 created on 09 Sep 10 at 17:44 <--- this will change as definitions are updated.

Registry Editor 64-bit:

HKEY_CLASSES_ROOT\Installer\Products\4F57260AB42358E4596E782BDC274910
KeyName=ProductName
KeyValue=Windows Defender

This should help.

[Cristiano]

not quite right. right now, it's missing the removal command, that us to be located under here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

as an guess, the info is located under "Windows Defender" or something else, under "UninstallString"

[]s

[DesertJerry]

 Cristiano, on 11 September 2010 - 03:04 AM, said:

not quite right. right now, it's missing the removal command, that us to be located under here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

as an guess, the info is located under "Windows Defender" or something else, under "UninstallString"

[]s

I checked all of the usual places - as posted above - found no listing

[Cristiano]

oh well... it's possible that there's not an uninstall, but let's see what i can i do about it...

thanks

[]s

[Cristiano]

well, it's amazing what you can do when you really wanna do sometimes...

this shall work as an removal for windows defender x64 under xp x64:
MsiExec.exe /qn /x{A06275F4-324B-4E85-95E6-87B2CD729401}

if everything is ok, this script will be released later today

thanks

[]s

[DesertJerry]

My error yesterday.

XP Pro x64 w/SP2
Registry Editor 64-bit
Windows Defender

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{A06275F4-324B-4E85-95E6-87B2CD729401}

UninstallString=MsiExec.exe /I{A06275F4-324B-4E85-95E6-87B2CD729401}

I tried again this afternoon and - there it was; matches yours.

[Cristiano]

good. i've interpreted right the data

so, the initial release for ms security is online. it targets english, but the modules will load into any language

[]s

[DesertJerry]

XP Pro w/SP3

AutoPatcher - Microsoft Security - test

Started APUP > check mark in box: Microsoft Security ENU Addon Pack > Next > Downloads > Finish

Started AutoPatcher > did not find Microsoft Security ENU Addon Pack. (Where is it supposed to be located?) Tried APUP and Autopatcher twice - same results.

Information: I do not have Windows Defender or Microsoft Security Essentials installed in this operating system - is that why the addon does not appear? (I would think it should appear but be all black - indicating software not installed.)

Navigated to \AutoPatcher folder - \modules\addons and it was not to be found - why?

Reboot to XP Pro x64 w/SP2 - this operating system has Windows Defender installed.

Started Autopatcher - same results as above - no Microsoft Security Addon.

Started APUP > check mark in box: Microsoft Security ENU Addon Pack > Next > Downloads > Finish

Started Autopatcher - same results - no addon

If the script has been updated it appears to not have been downloaded.

At this time I see no point in testing from within Win7 32- or 64-bit.

Edited by DesertJerry, 11 September 2010 - 09:51 PM.