SIMS.Net upgrade on clients

[_techie_]

Hi,

 

For this september, we have moved back to SIMS only from a dual system.

We successfully managed to roll out SIMS.Net to client workstations.

 

We had our first update on Thursday, and had one or two upgrade problems on machines with a few members of staff, particularly one who broke the upgrade on every machine he went on!!

 

We have checked the one Staff members group membership in AD, and it is fine, while also checking the permissions on the SIMS folders in his home directory, and the permissions on the home dir as well, but nothing obvious has come up yet.

 

Once logged in as domain admin, and run simsload, the program continues to function, and the said staff member can continue to use SIMS without problems.

 

Is there anything else we need to check?

 

Thanks,

[localzuk]

Have you ran the SIMSPerm script on each machine, to allow non-local admins to update it? Otherwise, staff would need local admin permissions on computers.

[_techie_]

No, but we made teachers "power users" on the machines with SIMS.Net on through group policy. It was only the odd one or two machines, and the one member of staff which followed the problem around on the machines he used LOL!

The majority of them updated without problems AFAIK. Not too sure, why only some of them didn't update, which was a little strange :-S

 

Thanks for the advice though, I was aware of the SIMSPerm.bat file, we have used that in the past, but this seemed to apply the same result that the GPO Power users setting did.

 

The only other thing that I can think of is to do with .Net Framework. We had deployed .Net 2.0 to the workstations, along with SIMS.Net, (SIMSLoad actually, which calls the setup from the server, when pulsar.exe is run as an argument in the shortcut.) Back to .Net, I can only think that the SP1 for .Net 2.0 had not yet applied to the workstation from our WSUS server. Will check the status on Monday for the updates applied to workstations.

 

The only reason I think of this, is that we had put out some machines quite late in September, ready for teachers to use, and they had not quite picked up the SP1 for .Net 2.0

 

Thanks anyway.

[synaesthesia]

Be careful about adding the users as power users - make sure you add the *domain* user as power user, not the local user.

[_techie_]

Yes, we have added the "Domain\Staff" group to power users on the sims machines, and also "Domain\Administrators" to administrators on the same machines, as they locked out unless we did the latter (basically replicated Domain Users type settings).

 

Thanks!