Clean install of SIms, FMS and permissions issue.

[Kyle]

We have just had some new computers in the office and have had to reinstall Sims and FMS on them. We had upgraded to the latest version of Sims on the server(September update).

 

We installed Sims.net

TO get this to work w had to give the Staff Group 'Modify on the C:Program Files/Sims folder.

 

We installed FMS

TO get this to work we had to give Staff Group 'Modify on the PDXOUsers file on the root of the C: drive.

 

Then we had the problem of getting 2 of the old DOS modules to work (Personnel and can't remember the other) TO get these to work we had to give Staff Group 'Full Control' on two Sims files in the C:/windows/system folder.

 

 

Now is all this correct, I am very uncertain. I do not look after Sims but i became very concerned when i found out the NM had give 'Full Control to the C: to get this to work. I told him that he should not be doing this, but he ignored me. I can't believe he did this, but then again he'd do anything to make it work has he has no interest whatsoever.

 

I have since changed this on certain PC's to the config above, nut i would like second opinions please because i don't have much experience of installing Sims, I've only seen it recently because we have had new PC's

[meastaugh1]

I don't use it myself, but I would imagine if you run simsperm.bat, there's a chance it will set the correct permissions, but this is Capita, so you never know.

 

You may also need to allow users to modify c:\windows\sims.ini and c:\documents and settings\all users\Start Menu\Program Files\SIMS Applications. In addition, some actions (I think it's a report in performance analysis which gets opened in Excel) requires write access to a part of the HKCR hive, I think it's Excel.Application, or something.

[MkII]

There are several threads on the capitaes forums, with some helpful capita peeps discussing the pros and cons. simsperm is definately what you should be doing for the base install, anything else is risky - Capita warn about leaving your machine open to threats using any other method [this is detailed on capitaes forums somewhere].

 

Is it just me or does the latest version not install the 16bit BWCC.dll anymore that's required by NovaT4 [that we're still running]? Last install I did I had to forage an existing install to copy it over.

[meastaugh1]

Is it just me or does the latest version not install the 16bit BWCC.dll anymore that's required by NovaT4 [that we're still running]? Last install I did I had to forage an existing install to copy it over.

 

It's been that way for some time. I believe it's caused by the 16-bit setup not being called (S:\SIMS\WSSETUP\WSSRTUP.EXE). I've worked around it by just automating the copying of bwcc.dll.