We use SIMSPERMS.BAT to set up the access rights - this machine I'm using updates SIMS fine but I don't have admin access to it as a whole. I believe it's a question of allowing write access to the SIMS program folder.
We use SIMSPERMS.BAT to set up the access rights - this machine I'm using updates SIMS fine but I don't have admin access to it as a whole. I believe it's a question of allowing write access to the SIMS program folder.
We run simsload in a startup script so the users never see the update process - it works for us
+1 for SIMSLoad in a startup (not login) script.
Combine it with simsperm and a security group (which you should have anyway) for it to work properly.
Sometimes simsload doesn't do everything - particularly SIMSAMPARKSetup, if simsperm is run then end users won't have a problem if the program calls AMPARK when they try and access Assessment Manager.
In the spirit of trying to keep startup as lean as possible - has anyone tried calling simsload from a MSI then just redeploying the msi whenever an update is available? Or is so quick whenever there's no update it's not worth it?
Ive been told and im about to test, if you do the following:
In the setups folder of sims there is a "simsperm.bat"* file that needs to be run on each machine that has sims installed on it. to do this you need to follow a few rules:
1.Install sims on the machine
2.From CMD run "simsperm.bat allusers"
Job Done
Now I'm waiting for the next update to try this out but ive done it on a few machines so fingers crossed!
There are currently 1 users browsing this thread. (0 members and 1 guests)