Posted by Robert G Laurin on June 15, 2006 at 11:02:39:
In Reply to: Re: Comet Exployer posted by Grant Foraker on June 15, 2006 at 10:29:59:
I also see a lot of problems with the COSW.INI...
Isn't it time to get rid of it? This is legacy stuff from Win95. It used to be in C:\Windows, it is still in C:\Windows if one has admin rights to the local machine, otherwise it ends up in "D&S\All Users" which is read-only for most end users on a domain. Problem is that an administrator installs it but an operator uses it.
Why not just put all of that stuff in the registry (like any other software would do)? Problem solved and no more COSW.INI nightmare.
With CFAM that allows us to "hide" the Comet folders on the servers, we rely more and more on Directory Alias. Not beeing able to update the COSW.INI is a problem. Not beeing able to get the User Environment Path for D&S is another problem that prevents us from creating Alias and sub-folders from within Comet.
Installing a Domain is frustrating enough, the fight with COSW.INI is unjustified.