Remote installation - error 101

[Guest]

I'm trying to install antispyware remotely using GPOs. I've extracted the msi
(antivirus.exe /a) and i've set it up to install remotely. It installs on the
client successfully, but when i try to run the program it says:
Warning: microsoft antivirus has encountered a critical error (error 101).
please restart or reinstall bla bla bla..

anybody hit this error before?

Thanks

 

[Bill Sanderson]

Access these groups via NNTP, load the messages from the .install group, and
check them out. This has been seen before.

I strongly recommend against deploying this beta1 product in this fashion.
Once deployed, you will have no control over it. Users are able to block
administrative script files. If you need to deploy an app that Microsoft
Antispyware is going to raise dialogs about, how will you manage that?

That said, if you read a little--perhaps even the thread immediately
adjacent to this one, initiated by Dave Bunch--you can see what references I
do have to methods that others claim to have used successfully.

I repeat, however, that Microsoft recommends against such a deployment, and
I do too.

 

[Guest]

I dont fully understand. why wouldnt you load antispyware this way?
I've got about 50 computers and I dont have any other means to deploy
software. I dont have any administrative scripts, so i'm not worried about
blocking them.

thanks

 

[Guest]

Troy,

I did the same thing, and got the same error. The problem is that, on every
machine when you install "manually" you get a couple of config screens. When
you install remotely, the config screens are not launched, thus the program
isn't completely installed. You would have to goto each client, and goto
add/remove programs...click change, and re-install....which defeats the
purpose of remote install.

To work around this, I copied my "c:\program files\msantispyware\" from my
machine that I ran setup and config manually, to the target clients after
remote install using scripts. It works that way.

-Good luck

 

[Guest]

If you are comfortable widely deploying a beta product which specifically
states that it is not to be used on production machines in your environment,
you're welcome to deploy however you are able. Please see the other thread I
referred to for some actual technical details that might make this easier for
you.