G
George Hester
This is a prime example of - what Microsoft Windows IMPLIES is NOT what Microsoft Windows DOES. For example.
You would think that if something is changing the home page of IE then all you would need to do is set it to what you want. Then go into Group Policy find the Windows Components | Internet Explorer and enable "Disable changing home page settings." What do you think? Doesn't this imply that changing home page settings has been disabled until this Group policy has been disabled? Doesn't this imply that? Seems so to me or I'm not all that bright. Oh forget about the Domain client issue that has been provided for.
BUT IT DOES NOT!!!
I don't know what good this Group policy setting is if it dosen't do what it imples. Seems to me this issue is a major security flaw not just of Microsoft Windows 2000 but of the company themselves. They do not realize that when they imply something can be used for security that in reality don't do sh*t, that is Security violation 101.
In this case my home page was reset to http://coolwebsearch.com with this Gorup policy enabled with a home page NOT set to this.
All ActiveX was off. All scripting disabled. No trojans lets not go there. That is just an excuse for avoiding this issue. No BHO's. No virus. Folks it is a security issue plain and simple. It is a failure of Group policy implying something it is unable to provide.
I could fix this I believe (of course I am going on implications not reality here) if I could set permmissions in regedt32 on a value not a key. But that cannot be done in Microsoft Windows 2000. You can only set permissions on a Key not on a value. Maybe this is why Group policy FAILS in this case. Because Group policy would have to set permissions on values (HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer:Search URl - REG_SZ - http://www.microsoft.com) not Keys (HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer) and that is not possible. So it seems to me any Group policy in Windows 2000 that imples making changes to just a value not a Key in the registry is doomed to fail.
You would think that if something is changing the home page of IE then all you would need to do is set it to what you want. Then go into Group Policy find the Windows Components | Internet Explorer and enable "Disable changing home page settings." What do you think? Doesn't this imply that changing home page settings has been disabled until this Group policy has been disabled? Doesn't this imply that? Seems so to me or I'm not all that bright. Oh forget about the Domain client issue that has been provided for.
BUT IT DOES NOT!!!
I don't know what good this Group policy setting is if it dosen't do what it imples. Seems to me this issue is a major security flaw not just of Microsoft Windows 2000 but of the company themselves. They do not realize that when they imply something can be used for security that in reality don't do sh*t, that is Security violation 101.
In this case my home page was reset to http://coolwebsearch.com with this Gorup policy enabled with a home page NOT set to this.
All ActiveX was off. All scripting disabled. No trojans lets not go there. That is just an excuse for avoiding this issue. No BHO's. No virus. Folks it is a security issue plain and simple. It is a failure of Group policy implying something it is unable to provide.
I could fix this I believe (of course I am going on implications not reality here) if I could set permmissions in regedt32 on a value not a key. But that cannot be done in Microsoft Windows 2000. You can only set permissions on a Key not on a value. Maybe this is why Group policy FAILS in this case. Because Group policy would have to set permissions on values (HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer:Search URl - REG_SZ - http://www.microsoft.com) not Keys (HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer) and that is not possible. So it seems to me any Group policy in Windows 2000 that imples making changes to just a value not a Key in the registry is doomed to fail.