sjatkn Posted January 5, 2015 Posted January 5, 2015 We have several 64 bit Windows 7 machines where SIMS has installed to the "c:\program files\" folder rather than "c:\program files (x86)" folder. We have: Uninstalled SOLUS3 and deleted the c:\program files\SIMS and c:\program files (x86)\SIMS folders (this was left over from a previous SOLUS3 install). Reinstalled SOLUS3 from the SOLUS3 server UI. Waited for SOLUS3 Agent to download and install SIMS. In SOLUS3 server UI we have install to default location selected. Other 64 bit Windows 7 machines do not have this problem and I think they even use the same base image, though I would need to confirm that with one of my technicians. We were running SOLUS 3.6 until early December when we upgraded to SOLUS 3.8. The first SIMS install on these machines was done using SOLUS 3.6 and installed SIMS to the correct place. We currently use different desktops for the 32bit / 64bit installs we have, so having this install to the wrong place breaks the existing shortcuts (I know I could use batch file to start SIMS based on which version it finds). Any thoughts as to how to resolve this and get SIMS installing to the right place?
Ghostgame Posted January 6, 2015 Posted January 6, 2015 Take a look in the SOLUS3 Enviroment --> Configure Workstations In the SIMS.ini tab you can specify a different location for SIMS and FMS to install to. Include the SIMS .net folder or FMSSQL folder in the different location otherwise it will get a bit messy. Select Save & Send to Agents. Will only take effect when you run an update, install a SOLUS3 agent. SOLUS3 always makes the default location for installing SIMS/FMS as C:\Program Files (x86)\SIMS\... If it can't find that, the next default is C:\Program Files\... Hope this helps.
sjatkn Posted January 12, 2015 Author Posted January 12, 2015 Sorry about the delay in getting back to this, unfortunately this was not the solution, as it was only happening to one particular model of laptop that was sharing a common image. In the end we have reimaged the offending machines (with the same image) and this time SOLUS installed SIMS to the right place. Capita suggested we look at the Windows 7 Virtual Store to see if that could be the cause as they had seen problems with sims.ini before, but by then we had done the reimaging (it took them 2 days to get back to us so we gave up)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now