.net framework 1.1 on windows 2003 server

  • Thread starter Thread starter Luk
  • Start date Start date
AFAIK, it would be a manual process. I see no reason to do it, however.

If you want to go that route, you have to delete all registry entries. One
way to figure out which ones is to install on a machine with some registry
checker running, esp. one that can script out the keys. Then use that map to
delete the keys on Server 2003.

After deleting the keys, you should be able to reboot and then delete the
..NET install directories.

NOTE: While there are no .NET dependencies in Server 2003 core, it is likely
there are tools that use the Framework. Consider this before taking brash
action.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************
 
One reason to Uninstall the .net framework is that is has a know
incompatability issue with Oracle 10G infrastructure. With 10G Infra
installed on a Windows 2003 Server CPU cycles can reach 90-100% caused by
nmupm.exe. This demonstrates even more of MS's myopic view of the world. No
reason to uninstall it works; yea, perhaps with MS SQL. Yet another reason
to dump all your windoze machines as vm's and not ms virtual pc either go
with a true vmm, vmware esx mark the HD as undoable and test away. Leave it
to another company to solve MS's issues.
 
Back
Top