UnInstalling games from 2000 professional.

  • Thread starter Thread starter Rich
  • Start date Start date
R

Rich

Is there a command-line I can run that will uninstall the
games from Windows 2000 Professional? I need to run it on
over 300 PCs.
 
What games? The built-in stuff?

Worse case, run a batch file that just goes and
deletes the exe files from a startup script (GPO).

It won't officially "uninstall" but it will keep people
from playing at work.
 
I tried that once. The result was that Add/Remove
programs stopped working. How did they manage to make
something so simple so booby-trapped?
Another result might be Windows will self-heal and put
them back.
That's when I started learning about INF files.
When game files are installed (by default) they create
entries in the SYSOC.INF file in C:\WINNT\INF. You
probably already know that hack but want one file that
can be fired off - maybe even pushed - that will
uninstall domain-wide. When MS games are installed, a
file named GAMES.INF is built. Inside this file is the
secret.
Wish I could tell you what to delete and edit, but right
now I don't know. Maybe you can find someone who re-wrote
the games.inf to automatically uninstall games. It can be
done.

(The email address is fake to avoid spam and trojan mail.)
 
I like that!
The look on the face of the $85,000/yr manager that always
plays Freecell all day long... Priceless.
 
The suggestion was tongue firmly in cheek so make sure
you get "permission" for the message fromt the higher
authority that ordered the games removed. (really)
 
Richard A. Insalaco wrote in
Well, I was hoping for a command line but thanks for the
suggestions.
Click to expand...

From a fuzzy memory....I think you can write a custom .INF file and
run it from a command line to un-install, That is not "solid" and I
might be wrong, but perhaps it helps as a direction to look into...
My 0.002 cents.
 
You can also build a Startup Script (command line) to
do it.

It is possible to do it with INF security templates and GPOs
but that is probably more to learn (in one shot) than it's worth
unless you are pursuing the subject further.
 
Over on the AD Newsgroup someone (Rhinehart?)
post this for disabling exe's with GPOs:

##Open the GPO you need to edit then navigate to :
##User Configuration>>Administrative Templates>>System
## >>Don't run specified windows applications
## just need the name of the .exe to restrict.

Now, that doesn't sound so hard -- at least not as difficult
as I made it seem.
 
Herb Martin wrote in
Over on the AD Newsgroup someone (Rhinehart?)
post this for disabling exe's with GPOs:

##Open the GPO you need to edit then navigate to :
##User Configuration>>Administrative Templates>>System
## >>Don't run specified windows applications
## just need the name of the .exe to restrict.

Now, that doesn't sound so hard -- at least not as difficult
as I made it seem.
Click to expand...

But may not be as effective as you think.

"This policy only prevents users from running programs that are
started by the Windows Explorer process. It does not prevent users
from running programs, such as Task Manager, that are started by the
system process or by other processes. Also, if you permit users to
gain access to the command prompt, Cmd.exe, this policy does not
prevent them from starting programs in the command window that they
are not permitted to start by using Windows Explorer."

It depends on how locked-down the system is and how savvy are the
users. For example (notepad.exe locked out) if you can copy
notepad.exe to notepad.com that can be started even via a shortcut
(Explorer shell). And of course from a command prompt as above.
 
But may not be as effective as you think.
"This policy only prevents users from running programs that are
started by the Windows Explorer process. It does not prevent users
from running programs, such as Task Manager, that are started by the
system process or by other processes. Also, if you permit users to
gain access to the command prompt, Cmd.exe, this policy does not
prevent them from starting programs in the command window that they
are not permitted to start by using Windows Explorer."
Click to expand...

Well, that is pretty cruddy. You are right of course since it is merely
an Explorer restriction.

Ok, here's a way that works: Change the Execute special
permission (using a batch file OR GPO) to deny execute
to any group, even Everyone.

Even works for Admins (unless they change the permissions back.)

As long as the individual doesn't have "Full Control" or "own" the
files it works completely.
 
Herb Martin wrote in
Well, that is pretty cruddy. You are right of course since it is
merely an Explorer restriction.

Ok, here's a way that works: Change the Execute special
permission (using a batch file OR GPO) to deny execute
to any group, even Everyone.

Even works for Admins (unless they change the permissions back.)

As long as the individual doesn't have "Full Control" or "own" the
files it works completely.
Click to expand...

All interesting, but it seems we all never came up with an answer for
the OP about scripted uninstallation of the games.... :-(

I once studied .INF files a bit, but that was years ago and far away.
There must be a more easily graspable and more commonly available
solution. I hope someone comes up with one.
 
Back
Top