SIMS Client Upgrade Permissions

[theeggmaster]

Hi all,

 

We moved SIMS in-house a couple of years ago, and I've never managed to get the SIMS client to automatically update when a member of staff clicks on the shortcut. Currently I do a mass logon with Impero out of hours and run simsload.exe on each machine so it is ready for staff after the upgrade, which isn't a problem as I think it helps. However, there are always a couple of machines that don't power on (sockets switched off at walls), so I'd like to catch these by allowing them to upgrade automatically.

 

My SIMS .Net shortcut points to simsload and then pulsar, so it does attempt to run the upgrade. However, it doesn't actually perform the upgrade and then tries to load SIMS with the 'Incompatible Database' error.

 

I've applied simsperm.bat on each machine in school, and I have a GPO which has the following settings:

Computer Settings | Windows Settings | Security Settings | File System

%Program Files%\SIMS - Staff have modify

%SYSTEMROOT%\sims.ini - Staff have modify

 

Computer Settings | Windows Settings | Security Settings | Registry

Machine\Software\Classes - Staff have full control

 

Everything is set to propagate to subfolders and subkeys.

 

The c: drive is hidden to staff, and they have read-only access to the Setups folder on our SIMS server.

 

Any help would be appreciated!

[3s-gtech]

I wouldn't spend time on this now. SOLUS3 will be required for the next release (according to the material I've seen) so you're better off getting that working now. The client for that doesn't suffer with the SOLUS2 permissions quirks (usually).

[superfletch]

Perhaps give a bit more access here:

 

%Program Files%\SIMS

%SYSTEMROOT%\sims.ini

 

Also would read permissions allow them to execute the files in the Setups folder?

 

That said - I think SIMSPerm should probably have done it - are any of your other GPO's affecting the users by denying rights you are granting here? My memory of NTFS permissions is a bit fuzzy and out of date, but I'm sure I remember that a deny permission would always take presidence over an allow one...

 

- - - Updated - - -

 

I wouldn't spend time on this now. SOLUS3 will be required for the next release (according to the material I've seen) so you're better off getting that working now. The client for that doesn't suffer with the SOLUS2 permissions quirks (usually).

 

Good point - probably more relevant than mine...

[theeggmaster]

I wouldn't spend time on this now. SOLUS3 will be required for the next release (according to the material I've seen) so you're better off getting that working now. The client for that doesn't suffer with the SOLUS2 permissions quirks (usually).

 

Aah, that's one thing I forgot to mention. We are supported by our LA and as far as I can tell, they don't currently have a plan to move to SOLUS3. That's why I'm still working on this...

[PhilNeal]

S2 will not be supported after spring release. Either S3, ISO delivery is needed.

[theeggmaster]

Perhaps give a bit more access here:

 

%Program Files%\SIMS

%SYSTEMROOT%\sims.ini

 

Also would read permissions allow them to execute the files in the Setups folder?

 

That said - I think SIMSPerm should probably have done it - are any of your other GPO's affecting the users by denying rights you are granting here?

 

Even with read and execute permissions it doesn't work. I also checked the permissions on the folder with the staff member logged on, and the permissions are as expected.

[theeggmaster]

S2 will not be supported after spring release. Either S3, ISO delivery is needed.

 

I currently upgrade our server from an ISO provided by the LA.