Internet Explorer & Outlook Express

[sevi]

Anyone know how to uninstall Outlook Express and Internet Explorer from Windows 2000 Pro.

We don’t want them, we don’t use them, we want rid of them all together. It just gives users more things to play with.

I’ve seen a couple of postings before about how to restrict access etc, but this doesn’t work in our environment.

The workstations are used in an industrial environment, and are there in place of NT4 workstations. On the NT4 ones we could uninstall Outlook Express and Internet Explorer ok.

We are still using NT4 servers, NT4 policies and mandatory profiles which we found worked well in a true NT4 environment, but they don’t restrict access to these applications on a W2K Pro.

It seems that the shortcuts to these applications are created every time a user logs on, even after we have deleted them.

Anyone any ideas?

Regards

A frustrated W2K User.

 

[jasonwichman]

Go to the control panel, then Add/Remove Programs. On the left you will see windows components. In that list you can change and get rid of them. You will probably need the Win2k disk. Jason Wichman

http://jasonwichman.ath.cx:81

ftp://jwichman.ath.cx:22

 

[wolluf]

You can't uninstall these components from win2k - they're effectively integrated with the operating system (remember all that legal stuff with Microsoft - unbundling browser from o/s system being one of the points of contention).

 

[Guest_imported]

These do not appear in that list. This is how I used to do it in NT4.

Any other ideas?

 

[jasonwichman]

open the file sysoc.inf found in c:\windows. Just do a search for the file.

Mine is as follows.

Signature = "$Windows NT$"
DriverVer=11/14/1999,5.00.2183.1

[Components]
NtComponents=ntoc.dll,NtOcSetupProc,,4
Display=desk.cpl,DisplayOcSetupProc,,6
Fax=faxocm.dll,FaxOcmSetupProc,faxsetup.inf,hide,7
NetOC=netoc.dll,NetOcSetupProc,netoc.inf,,7
iis=iis.dll,OcEntry,iis.inf,,7
com=comsetup.dll,OcEntry,comnt5.inf,hide,7 ; temp fix for 64-bits
dtc=comsetup.dll,OcEntry,dtcnt5.inf,hide,7 ; temp fix for 64-bits
IndexSrv_System = setupqry.dll,IndexSrv,setupqry.inf,,7
msmq=msmqocm.dll,MsmqOcm,msmqocm.inf,,6 ; temp fix for 64-bits
ims=imsinsnt.dll,OcEntry,ims.inf,,7
fp_extensions=fp40ext.dll,FrontPage4Extensions,fp40ext.inf,,7 ; temp fix for 64-bits
iisdbg=iisdbg.dll,ScrptDbg,iisdbg.inf,,7 ; temp fix for 64-bits
imagevue=ockodak.dll,ImagingOcEntry,imagevue.inf,hide,7 ; temp fix for 64-bits

; old base components
Games=ocgen.dll,OcEntry,games.inf,HIDE,7
AccessUtil=ocgen.dll,OcEntry,accessor.inf,HIDE,7
CommApps=ocgen.dll,OcEntry,communic.inf,HIDE,7
media_clips=ocgen.dll,OcEntry,mmopt.inf,HIDE,7
MultiM=ocgen.dll,OcEntry,multimed.inf,HIDE,7
AccessOpt=ocgen.dll,OcEntry,optional.inf,HIDE,7
Pinball=ocgen.dll,OcEntry,pinball.inf,HIDE,7
MSWordPad=ocgen.dll,OcEntry,wordpad.inf,HIDE,7


[Global]
WindowTitle=%WindowTitle%
WindowTitle.StandAlone=%WindowTitle_Standalone%


[Strings]
WindowTitle=Windows 2000 Professional Setup
WindowTitle_Standalone=Windows Components Wizard


Take out the "HIDE" parameter anywhere in this document. Reboot, and see if you can unistall it then. Jason Wichman

http://jasonwichman.ath.cx:81

ftp://jwichman.ath.cx:22

 

[Guest_imported]

Hi,

I'm sure this isn't your first choice, but it will be effective in meeting your objective of not having access to the app.

If you delete msoe.dll from one location in win2k pro, windows will restore it in seconds from another location. fascinating how efficient they can be when it serves there own purpose (excuse the commentary).

To get around this, simply go to folder options as admin and remove all of the "hide" options. Then do a simple search for msoe.dll. Finally, delete all occurances of this file. Accept all of the 'doom and gloom' end of the world warnings that follow.

Now try starting outlook express. you can not. it does not matter which user points to it now. you will get a simple message informing you that oe can not start because of the missing .dll. nothing more.

This is something that worked for me when i wanted to restrict access to the app. please know that you are messing with system files and are doing so at your own risk (non in my opinion).

hope this helps.