Drive Mappings and Solus 3
I'm getting problems with drive mappings and Solus 3.
Initially I set up Solus 3 's configuration drive mappings like this:
Sims Drive: G
Sims UNC Path: \\simsserver\apps$
Sims Setups Drive: G
Sims Setups UNC Path: \\simsserver\apps$\sims\setups
Our G: drive is mapped with a GPO driven login script:
When the Solus 3 service is running on the local machine, and the user logs out, the G drive is left in a "half open" state. When the user logs back in, they get a wsh script error saying the G drive cannot be mapped, because the drive letter is in use.
Set gObj = Wscript.CreateObject("WScript.Network")
gObj.MapNetworkDrive "g:", "\\simsserver\apps$"
When I go into My Computer, the G drive is there, but is listed as:
"Disconnected Network Drive G:"
I returned to the Solus 3 Phase 1 manual. It appears that you are supposed to have two different drive mappings, one for Setups and one for Sims. I have now set up both as separate drive mappings and updated the configuration in the SIMS Remote Agent Installer. I now have Z: for Setups and G: for Sims.
I removed the agent from the PC, then reinstalled it. Now i get the failed drive mappings for both, with both drive letters blocked by drives with "Disconnected Network Drive"
Digital Signature Check Fails
After successfully deploying the agent to workstations SIMS still does not install. When checking the log file on the client machine (see below) we get an error on the digital signature check. This is the third version of the SIMSInfrastructureSetup.EXE we have tried. Does anyone have any ideas?
2009-11-30 16:10:26.1805|Error|CheckSetupSignature(): Digital signature failure for SIMSInfrastructureSetup
2009-11-30 16:10:26.1805|Warn|runSetups(): Installer failed digital signature check: SIMSInfrastructureSetup.EXE
2009-11-30 16:10:26.1805|Info|Check(): Update check complete
Solus 3 and drive mappings cont.
I have tried manually, after logging in, to do
Originally Posted by mounters
and to try and right click to disconnect. Neither works. I get:
"The network connection could not be found" in an error box.
In reply to the question about apps$, we have not had any problems with using a hidden share. All it does is not advertise it's existance. If it is specified by name, then it works fine.