[redfive19]

RunWait(@ScriptDir & '\' & "MicrosoftAntiSpywareInstall.exe" & ' /s /v"/qn"')
Opt("TrayIconDebug", 1)
#include <process.au3>
FileChangeDir(@ProgramFilesDir & "\Microsoft AntiSpyware")
If ProcessExists("gcasServ.exe") Then
	ProcessClose("gcasServ.exe")
EndIf

Run("gcasDTserv.exe -Embedding")
Run("gcasServ.exe")
FileDelete(@DesktopDir & "\Microsoft AntiSpyware.*")
FileDelete(@DesktopCommonDir & "\Microsoft AntiSpyware.*")
SplashOff()
If @IPAddress1 <> "0.0.0.0" Then
	run(@Programfilesdir & "\Microsoft AntiSpyware\GIANTAntiSpywareMain.exe update")
	WinWaitActive("Microsoft AntiSpyware AutoUpdater", "")
	Sleep(2000)
	$close = ControlCommand("Microsoft AntiSpyware AutoUpdater", "", "ThunderRT6UserControlDC4", "IsEnabled", "")
	Do
  Call("waitaround")
  Sleep(100)
	Until $close = 1
	
	WinClose("Microsoft AntiSpyware AutoUpdater", "")
EndIf


Exit

Func waitaround() 
	$close = ControlCommand("Microsoft AntiSpyware AutoUpdater", "", "ThunderRT6UserControlDC4", "IsEnabled", "")
EndFunc

There's my autoit script that'll do it all.

That will install ms antispyware & get rid of your 110 error. If you have an IP
Address, it will update to the newest defs.

[Kelsenellenelvian]

Nice script thank you for sharing.

[edusnow]

Thanks,...
I will try.

snow

[cardinal808]

If some one is interested, this is the working script

msiexec.exe /qb /i MicrosoftAntiSpyware.msi

[edusnow]

""msiexec.exe /qb /i MicrosoftAntiSpyware.msi""

i´ll steal have the same 101 error

thanks
snow

[redfive19]

My autoit script installs silently and fixes the 101 error, but to each his own. Good luck with the MSI because as edusnow said, it will give the 101 error unless you're install it OVER a previous installation. big difference.

[redfive19]

My autoit script installs silently and fixes the 101 error, but to each his own. Good luck with the MSI because as edusnow said, it will give the 101 error unless you're install it OVER a previous installation. big difference.

[edusnow]

Hi,... redfive 19
You have right. In the second try the 101 error desapears. Can you explain more how autoit works. I dónt know nothing about it,... to i try.

thanks
snow

[fanatf1]

You say put reg file in $OEM$/$$ and run it from cmdlines as

REGEDIT /s MenuOrder.reg

But i heard that we must put this files in $OEM$ folde near the cmdlines!!

I have a lot regs in $OEM$ folder (which need to execute AFTER first logon)
like this

[COMMANDS]
"RunOnceEx.cmd"
"useraccounts.cmd"
"REGEDIT /S regtweaks.reg"
"REGEDIT /S ACDsee.reg"
"REGEDIT /s menuorder.reg"

Here the question: Can i make some folder in $OEM$ (like REGS) and put all regs (include menuorder.reg) in it. My cmdlines STILL work after that and apply regs from folder REGS? And how to write a command in cmdlines to REGS folder?

Help please !

EDIT: Or maybe you have better way to apply REGs (with keys, settings) which need to by applyed AFTER first logon?

It would be GREAT!

This post has been edited by fanatf1: 22 July 2005 - 01:15 AM

[edusnow]

Redfive19,... you are my men!
I use your script,... and off course,... it works. Erros 101 ?- What is that?

thanks
snow

next: ssh and wsftp_le

[JasonGW]

JasonGW, on May 2 2005, 11:15 AM, said:

TheeBeets, on May 2 2005, 02:38 AM, said:

Thx had a look at the other topic and download the script and well test out in Ms Virt Mach, Cheers
<{POST_SNAPBACK}>

REG ADD %KEY%\085 /VE /D "Microsoft AntiSpyware" /f
REG ADD %KEY%\085 /V 1 /D "%systemdrive%\install\MSAS\MSASInstall.exe /S /v/qn" /f
REG ADD %KEY%\085 /V 2 /D "%systemdrive%\Progra~1\Micros~1\gcasDtServ.exe /regserver" /f

Put that in your RunOnceEx.cmd file

Jason
<{POST_SNAPBACK}>

I don't tend to quote myself, but this, my friend, works perfectly for me *every* time. I have the absolute newest, truest, bluest version of MSAS and the same setup that worked 6 months ago works fine today.

Jason

[tbma]

JasonGW, on Jul 26 2005, 08:23 AM, said:

I don't tend to quote myself, but this, my friend, works perfectly for me *every* time. I have the absolute newest, truest, bluest version of MSAS and the same setup that worked 6 months ago works fine today.

Jason
<{POST_SNAPBACK}>

This will work, unless somebody have folders named "Microsoft blah-blah etc." in "Program Files" already (i.e some other Microsoft products installed).
In that case "Progra~1\Micros~1" will point to some other place, and this installation will fail... with error 101.

/offtopic on
Is anybody experimented with MsAS command line switches?
I have found -LaunchMode N (where N is a number), as well as known switches -scan -withui -withreultui,
but but I haven't figured out -schedule yet.
/offtopic off

This post has been edited by tbma: 26 July 2005 - 10:50 AM

[JasonGW]

tbma, on Jul 26 2005, 10:48 AM, said:

JasonGW, on Jul 26 2005, 08:23 AM, said:

I don't tend to quote myself, but this, my friend, works perfectly for me *every* time. I have the absolute newest, truest, bluest version of MSAS and the same setup that worked 6 months ago works fine today.

Jason
<{POST_SNAPBACK}>

This will work, unless somebody have folders named "Microsoft blah-blah etc." in "Program Files" already (i.e some other Microsoft products installed).
In that case "Progra~1\Micros~1" will point to some other place, and this installation will fail... with error 101.

/offtopic on
Is anybody experimented with MsAS command line switches?
I have found -LaunchMode N (where N is a number), as well as known switches -scan -withui -withreultui,
but but I haven't figured out -schedule yet.
/offtopic off
<{POST_SNAPBACK}>

If they have other stuff with the name Microsoft, they will have 8.3 names sequentially in alphabetical order. Even with Microsoft Office, Microsoft Project, Microsoft Visio, Microsoft Publisher and Microsoft Antispyware installed, antispyware will *still* be micros~1, unless Microsoft Activesync is installed first.

In any case, resolution is simple: Install MS Antispyware BEFORE you install those other apps. Setting the install to kick off earlier in the RunOnceEx.cmd is a 30 second job.

Jason

[tbma]

JasonGW, on Jul 26 2005, 02:23 PM, said:

In any case, resolution is simple: Install MS Antispyware BEFORE you install those other apps. Setting the install to kick off earlier in the RunOnceEx.cmd is a 30 second job.

Jason
<{POST_SNAPBACK}>

It creates short name every time it creates a file, not dynamically. So they will be named in order of creation.

On my machine for example:

Quote

MICROS~3    Microsoft ActiveSync
MICROS~4    Microsoft AntiSpyware
MICROS~1    microsoft frontpage
MICROS~2    Microsoft Office

How about even simplier resolution? Just use long names? DOS is officially dead at least 5 years now

[blinkdt]

@redfive19: nice work on the autoupdate feature, I'll definitely be putting that into all of my installs, worked like a charm.

[redfive19]

well I am getting to the back to this topic a little late but I am glad it worked for you! you can find out more about autoit by downloading it here:

www.autoitscript.com

All I did was read the help file. Did the tutorials in it and it kind of took off from there. I've been using it since March......

good luck

[InTheWayBoy]

RunWait ( "msiexec /qn /i setup.msi" )

Sleep ( 5000 )

Run ( @ProgramFilesDir & "\Microsoft AntiSpyware\gcasDtServ.exe /regserver" )

FileDelete ( @DesktopCommonDir & "\Microsoft AntiSpyware.lnk" )

That's an AuotIT script that does it all for you...just like it was previously mentioned. You have to have the .msi already extracted. What this does is install the program, wait five seconds, runs the necessary command to fix the stupid error with a silent install, and then deletes the icon on the desktop. After I reboot it autoruns and works fine.