BRONZE PARTNER:
BRONZE PARTNER:
Industry News:
| |
| |
|
|
|
|
|
| MS's AntiSpyware App beta Customization |
|
|
|
By: Paul Teodorescu
Posted On: 1/14/2005
As a follow up to Rod’s great informative article about Microsoft new AntiSpyware software (posted here http://myitforum.techtarget.com/articles/21/view.asp?id=8249), please allow me to share with all of you several technical matters related to its deployment and functionality.
The installation is made available as an Install Shield wrapper EXE, which can be easily “transformed” into a pure MSI for deployment purposes.
How? Simply launch the installation, and after the first dialog look into your local TEMP folder for a MSI and copy it to your package source.
The main issue of this application is not the deployment, but its launch after installation.
When I launch the Microsoft Antispyware program from its icon, I get an error that reads "Warning, Microsoft Antispyware has encountered a critical error (Error 101). Please restart Microsoft Antipyware again. If you continue to experience this problem, please contact Microsoft technical support at support@giantcompany.com for immediate assistance."
So what now?
The way I am dealing with this is by modifying the registry.
First create a batch file on the local machine in a restricted directory called MtSpy.CMD that contains the following line only:
"C:\Program Files\Microsoft AntiSpyware\gcasDtServ.exe"
Then go to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppPaths key and add a new key called "MySpy.exe".
Set this to the "MySpy.CMD" file (wherever you put it).
MySpy.EXE -> default = "c:\my folder\MySpy.CMD"
Now, anytime you want to run Antispyware, simply bring a “Run” command and type MySpy.
For automation, you could get even fancier and add MySpy.cmd to the Startup folder.
Hope this article helps if you engage in scale deployments!
As always, I am available for your feedback at pteodore@ptd.net
|
|
|
|
|
|
