Yet another thread from me..
Does anyone know if its possible to configure the MSI installer/xml config file for NOD32 to not create shortcuts?
Reason being, is that whilst ive got it configured to hide 90% of the 'dangerous' options in the program from the kids/staff, the icons on the start menu have still been made. Including the uninstall one. And it works.
Either a way to configure it so no shortcuts are made at install, or a script that i can run that removes the shorcuts from machines would be most helpful.
Thanks in advance everyone.
Hi
You can password protect the uninstall.
I'm not sure about stopping the shortcuts off the top of my head, can you not prevent them seeing shortcuts in the all users folder?
How do i password protect it?
There must be a way to script the removal of shortcuts...?
When you're editing the package in the console you can set the password under General - Settings - General - 'Password to unlock'
I'm pretty sure thats the password that locks all settings, i can't even uninstall it as an admin without the password.
Ive done some testing, and its true, normal users cant really do alot with the 4 shortcuts that NOD32 creates, but i'd still like a way to remove them from each machines.
Ive tryed creating a batch file with a DOS command in, but it doesnt work:
Code:deltree c:\documents and settings\all users\start menu\programs\eset
Last edited by boomam; 3rd March 2008 at 01:18 PM.
Deltree doesn't exist in 2K/XP. Try RMDIR instead. Also, you'll need quotes around a long pathname...
RMDIR /S /Q "c:\documents and settings\all users\start menu\programs\eset"
Doesnt work still.
Im testing it on my workstation, and it still doesnt remove the ESET folder..
##EDIT##
I changed the paths so the correct cases were in, and now all it does is delete everything in the all users start menu?
Im gonna try changing it to the folder under the ESET one, even if it means leaving the top level ESET one there, empty.
Last edited by boomam; 3rd March 2008 at 01:39 PM.
If i put that line in a .bat file and run it it works just fine are you just copying and pasting it?
Sorry, forgot to post back, got it working, i forgot to add \eset\ to the command..
Thanks everyone..
There are currently 1 users browsing this thread. (0 members and 1 guests)