MIS Systems Thread, Sims install windows 7 problem (unable to write to shared directory "(S:\SIMS)" in Technical; (pooley) Nope, the xp clients still update fine. (rh91uk) No I'm running the 32bit win7 pro but I also checked ...
24th December 2010, 09:42 AM #16
(pooley) Nope, the xp clients still update fine. (rh91uk) No I'm running the 32bit win7 pro but I also checked that the staff SG ACL entry was there.
24th December 2010, 10:08 AM #17
OK, the problem seems to be one of my own doing, becuase of the way I installed SIMS in the first place (changing the shared app dir) the installer goes wrong even as an admin. It looks as if I must address the S: drive issue under windows 7.
24th December 2010, 11:19 AM #18
The os can be an issue. Win7 / vista are extra secure. But the issues will mainly manifest on the local machine. For these sorts of problems you end up starting with full admin and then eliminating things one at a time. It's a real pain. We've never used simsperm but there was a good thread a while ago with what to apply by group policy. I think by Bossman.
24th December 2010, 11:59 PM #19
OK, I've finally sorted the installer problem! So from the already mapped s: drive I navigate to the SIMSInst.exe and run as administrator, wherein I'm greeted with the message that it can't access the S:\SIMS folder. I'm forced to correct this so I try retyping the directory with "S:\SIMS" it will repeat the error and I can't proceed. However if I use the folder icon next to the field to browse to the s drive and select the sims folder the field will now still says "S:\SIMS but does not complain.
I don't get it but it may have something to do with security tokens. A similar situation I ran into when trying to figure out why the administrator CMD couldn't access mapped drives.
I'll have to assume the the directory ACL entries will allow my non administrative users to update SIMS as I don't know how to test this without an actual update being needed.
Thanks everyone for your help as this has truly sucked.
29th December 2010, 08:32 AM #20
It couldn't be as simple as the S drive being mapped but disconnected. So it only becomes accessible after double clicking in explorer. I have a number of users instructed to do that first to ensure they are "talking" to the S drive before they run sims. However this would affect normal usage too not just upgrades..
22nd February 2011, 03:23 PM #21
quick post just incase anyone made it this far and is still wanting to kill sims...
if sims runs fine on xp and not in 7:
uac = on
logged in as admin
eventhough your s drive is mapped re map it using the administrator CMD (run as admin) net use s: \\servername\sims
installer should run fine now.
map s drive using admin again
set you current directory "cd /d s:\sims\setups"
run the "simsperm.bat yourdomainname\securitygroup"
should motor through that lot check for fails..
normal user should now be able to do the final look for the connect.ini in s:\sims and work.
By Disease in forum MIS Systems
Last Post: 13th July 2010, 01:27 PM
By Rowley_THS in forum MIS Systems
Last Post: 9th September 2009, 08:59 AM
By burgemaster in forum Scripts
Last Post: 11th August 2009, 11:08 AM
By Tom in forum MIS Systems
Last Post: 6th February 2009, 05:45 PM
By John_Howarth in forum MIS Systems
Last Post: 12th October 2008, 08:33 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)