Problems Installing on School Network.
Posted: 22.07.2003, 11:26
I am trying to install Celestia 1.3.0 (Windows Version) onto a Network of computers in a school. The school has "RM Community Connect 3.0" as it's Network system. To install new software on it, you need to create a "package" using a special utility, and then it installs it automatically to each machine.
Well that is the theory!
With Celestia, the package appears to build ok, but won't actually run on a local machine, unless you are logged in as an Admin or you remove ALL station protection! Neither is an acceptable solution in a classroom environment.
I'm sure there will be a way to get it to install properly. Can anyone help? Has anyone successfully installed this on a Connect3 network?
FURTHER INFO
Community Connect is based on WinXP Pro Clients with Win2000 as a Server with some custom tools for management and protection.
The specific error messages we get as a warning in the log from the package-builder is:-
Warning: this package contains one or more shortcuts destined for common folders - consider installing per-machine or using the ALLUSERS property.
Warning: this package contains references to absolute paths or UNCs which may not be available on all machines when deployed.
We have it installed using ALLUSERS already.
Does anyone know what absolute paths or UNC's are referenced in this program? Are they just web-addresses? (which should be fine, as all our machines have web-access)
The software is installed and runs from drive Q: on the server and the local C: drive on the workstations are generally write protected. The package builder detects Celestia's needs and accordingly creates this .ini file to enable write access to the follow places on the local machine:-
[C:\.]
Everyone=0x1301BF
[C:\WINDOWS\system32\config\systemprofile\History\History.IE5\index.dat]
Everyone=0x1301BF
[C:\WINDOWS\Temp]
Everyone=0x1301BF
[HKLM\SOFTWARE\Microsoft\Cryptography\RNG]
Everyone=0x3003F
[HKLM\SOFTWARE\Microsoft\Direct3D\MostRecentApplication]
Everyone=0x3003F
[HKLM\SOFTWARE\Microsoft\DirectDraw\MostRecentApplication]
Everyone=0x3003F
[HKLM\SOFTWARE\Network Associates\TVD\Shared Components\On Access Scanner\McShield]
Everyone=0x3003F
Why is it asking for full write access to ROOT of C: drive? (I am guessing that the file-protection system is actually blocking this request as being too risky even though the package is meant to bypass the security as this .ini file dictates). If I know what it needs access to on C:\ and why, we might be able to enable just the write access it genuinely needs!
I think the implication of the program working with local file protection off (but not with it on), is that Celestia is trying to access something else on the local machine... particularly a "common file". Does anyone know what file/s these could be? It appears that it needs access to other local settings on the machine to run.
I would appreciate any help with this. Thanks
Well that is the theory!
With Celestia, the package appears to build ok, but won't actually run on a local machine, unless you are logged in as an Admin or you remove ALL station protection! Neither is an acceptable solution in a classroom environment.
I'm sure there will be a way to get it to install properly. Can anyone help? Has anyone successfully installed this on a Connect3 network?
FURTHER INFO
Community Connect is based on WinXP Pro Clients with Win2000 as a Server with some custom tools for management and protection.
The specific error messages we get as a warning in the log from the package-builder is:-
Warning: this package contains one or more shortcuts destined for common folders - consider installing per-machine or using the ALLUSERS property.
Warning: this package contains references to absolute paths or UNCs which may not be available on all machines when deployed.
We have it installed using ALLUSERS already.
Does anyone know what absolute paths or UNC's are referenced in this program? Are they just web-addresses? (which should be fine, as all our machines have web-access)
The software is installed and runs from drive Q: on the server and the local C: drive on the workstations are generally write protected. The package builder detects Celestia's needs and accordingly creates this .ini file to enable write access to the follow places on the local machine:-
[C:\.]
Everyone=0x1301BF
[C:\WINDOWS\system32\config\systemprofile\History\History.IE5\index.dat]
Everyone=0x1301BF
[C:\WINDOWS\Temp]
Everyone=0x1301BF
[HKLM\SOFTWARE\Microsoft\Cryptography\RNG]
Everyone=0x3003F
[HKLM\SOFTWARE\Microsoft\Direct3D\MostRecentApplication]
Everyone=0x3003F
[HKLM\SOFTWARE\Microsoft\DirectDraw\MostRecentApplication]
Everyone=0x3003F
[HKLM\SOFTWARE\Network Associates\TVD\Shared Components\On Access Scanner\McShield]
Everyone=0x3003F
Why is it asking for full write access to ROOT of C: drive? (I am guessing that the file-protection system is actually blocking this request as being too risky even though the package is meant to bypass the security as this .ini file dictates). If I know what it needs access to on C:\ and why, we might be able to enable just the write access it genuinely needs!
I think the implication of the program working with local file protection off (but not with it on), is that Celestia is trying to access something else on the local machine... particularly a "common file". Does anyone know what file/s these could be? It appears that it needs access to other local settings on the machine to run.
I would appreciate any help with this. Thanks