Stevenw (23rd April 2010)
If you have already installed sims on the network run it as a start-up script and it will let non administrators update sims etc
Ok, I think this thread is a little confusing.
The SIMSPerm.bat file is, as Jamo says, supposed to be run after SIMS is installed on a machine, by someone with local admin rights.
You run it on a command prompt like so:
That would set the permissions correctly for the group 'Staff' on our domain.Code:simsperm.bat SCH4290\Staff
It doesn't need running on startup/login, or by end users.
in staid of the user name i did the staff group and it worked for all users
Actually I gave up with simsperm.bat. Sometimes something went wron and I had to go back to the machine to upgrade it. most of the time I forgot about it when I put a new SIMS machine in. Those problems went away when I addedd all the security setting to a GPO.
You would do if you have sims already installed out on the system. It would save visiting every machine. Thats what i am trying to get across.It doesn't need running on startup/login,
I think adding a Group Policy its a easier solution. No step to forget. Also, not sure if it works with Windows 7.
Also worth mentioning that it won't work if you have installed the SIMS client application to a directory other than it's default one - "C:\Program Files\SIMS\SIMS .net"
I generally use a GPO to deploy another batch file which calls "SIMSPerm.bat domain/group" as a startup (not login) script, this way it runs under the system account and just works.
(Be careful to point it at the UNC path ie "\\servername\sims" etc and not at a mapped drive - system accounts won't map drives).
@ Matt40k, I haven't tried on Win7 yet but might get a chance early this week as I'm going to a school where they have a couple of new W7 machines which they want SIMS on - If I find out I'll update this post.
There are currently 1 users browsing this thread. (0 members and 1 guests)