[sims] SIMS on RDS Server

[eddyc]

Hi all,

 

We have always had SIMS available to key staff remotely via RDS.

 

We have recently migrated this from 2008 R2 (where everything worked perfectly) to 2019.

 

I am having issues with Examinations, Nova T, etc which all complain of a connect.ini issue. I have copied the connect.ini to the root of C:\Windows as suggested on another post on here and still no joy!

 

Capita have helpfully told me RDS is not supported although it did work fine previously and I am aware from other posts on here that others are doing the same.

 

After a bit of process monitor I have discovered that it is crashing for staff users when trying to read this registry key;

 

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\IniFiles

 

There should be a SIMS value in there but we don't have one by the looks of things. Could anyone who has a working RDS setup with SIMS (and Examinations) working on it and do me a favour and upload their SIMS registry key?

 

I am considering restoring the 2008 R2 box into a sandbox to investigate and look at the key but thought this may be a quicker route.

 

Thanks all

 

eddyc

[Cache]

I think I just granted Modify permission on SIMS.ini and that seemed to resolve the issue.

[eddyc]

I think I just granted Modify permission on SIMS.ini and that seemed to resolve the issue.

 

Thanks for the reply, I have tried that - The one in C:\Windows ?

 

Unfortunately it is still the same :-(

 

 

 

Searching the error brought me to this post http://www.edugeek.net/forums/mis-systems/68289-incorrect-connect-ini-file-sims-processes-exception-when-opening-exams-org-solved.html but copying the connect.ini to the root of the C:\Windows folder hasn't helped either unfortunately.

[mukz]

Dumb question but when you are logged in do you have access to the SIMs folder on the main MIS server?

If so, then how was sims initially installed on your rds setup?

[eddyc]

Dumb question but when you are logged in do you have access to the SIMs folder on the main MIS server?

If so, then how was sims initially installed on your rds setup?

 

SIMS was installed on the 2019 RDS box the same way that it was deployed on the 2008 R2 box - via Solus 3.

 

The S drive is mapped on the RDS server to the usual share on the SIMS server.

[eddyc]

Process Monitor is here too, in case I am missing something obvious

 

[Cache]

I assume you've tried modify on connect.ini too?

 

Is it a single user or all users? Somethings ringing a bell about one of our users, but I can't quite remember what I did to solve it. I'm sure it was permissions related. Might also be worth checking the virtual store within the user profile incase there's something odd in there...

 

Edit: Might have just hit me. Check the virtualstore and check the permissions on sims.ini and connect.ini. Also check that the SIMS.ini is correctly formed and that the paths are correct, particularly the simsdirectory, seem to recall that potentially causing a problem.

Edited March 16, 2020 by Cache

[MagicMalc]

I have had similar issues, basically SIMS works but other older modules fail.

 

I was told by Capita that Solus3 is designed to be an update tool rather than an installation tool.

 

I installed SIMS using the SIMSinst.exe from the setups folder on the SIMS server then Solus keeps it updated and the older modules all work.

 

i have found Solus3 deploys SIMS fine except for users that need the additional modules.

 

 

i hope this helps.

[eddyc]

I assume you've tried modify on connect.ini too?

 

Is it a single user or all users? Somethings ringing a bell about one of our users, but I can't quite remember what I did to solve it. I'm sure it was permissions related. Might also be worth checking the virtual store within the user profile incase there's something odd in there...

 

Edit: Might have just hit me. Check the virtualstore and check the permissions on sims.ini and connect.ini. Also check that the SIMS.ini is correctly formed and that the paths are correct, particularly the simsdirectory, seem to recall that potentially causing a problem.

 

Yes I've set everyone to modify the connect.ini and I have also ran SIMSPerms.bat to try and help the situation but no joy.

 

It works for any domain admins just not non domain admins - i.e. staff.

 

The paths are correct in both INI files but should they be in single/double quotes because of the spaces in the paths? They aren't currently.

 

- - - Updated - - -

 

I have had similar issues, basically SIMS works but other older modules fail.

 

I was told by Capita that Solus3 is designed to be an update tool rather than an installation tool.

 

I installed SIMS using the SIMSinst.exe from the setups folder on the SIMS server then Solus keeps it updated and the older modules all work.

 

i have found Solus3 deploys SIMS fine except for users that need the additional modules.

 

 

i hope this helps.

 

 

Thanks for the suggestion. I have used simsinst.exe via the "Install Application on Remote Desktop Server" process and then deployed SOLUS3 but still the same I am afraid.

 

Very annoying!

[mukz]

Weird! I have always used the method which i think is the same as the method you did but i could be wrong

 

 

change user /install

 

Install sims

 

 

change user /execute

[AngryITGuy]

We had a similar issue quite recently which drove me crazy and I’m pretty sure the generated error code is the same.

 

For us though Exam Manager on the RAS wouldn’t work for the Exams Officer but would for me and the rest of the IT Team.

 

Just like you we did the usual checks with regards to the ini file copied them from the SIMS server and nothing worked.

 

That was until I stumbled across the SIMS.INI file in the Windows folder in the Exams Officers User area. Path in the ini file and SIMS installation path were wrong in this file so I replaced it with the one from my user area which was correct and voila problem solved!

 

Hope this helps you out.

[Cache]

We had a similar issue quite recently which drove me crazy and I’m pretty sure the generated error code is the same.

 

For us though Exam Manager on the RAS wouldn’t work for the Exams Officer but would for me and the rest of the IT Team.

 

Just like you we did the usual checks with regards to the ini file copied them from the SIMS server and nothing worked.

 

That was until I stumbled across the SIMS.INI file in the Windows folder in the Exams Officers User area. Path in the ini file and SIMS installation path were wrong in this file so I replaced it with the one from my user area which was correct and voila problem solved!

 

Hope this helps you out.

 

You've just reminded me exactly what I did - however your method of fixing it worked for me this time and is far simpler.

 

The way I actually fixed it was to create a symlink from c:\program files\SIMS to c:\program files (x86)\sims and that solved the issue.

[eddyc]

We had a similar issue quite recently which drove me crazy and I’m pretty sure the generated error code is the same.

 

For us though Exam Manager on the RAS wouldn’t work for the Exams Officer but would for me and the rest of the IT Team.

 

Just like you we did the usual checks with regards to the ini file copied them from the SIMS server and nothing worked.

 

That was until I stumbled across the SIMS.INI file in the Windows folder in the Exams Officers User area. Path in the ini file and SIMS installation path were wrong in this file so I replaced it with the one from my user area which was correct and voila problem solved!

 

Hope this helps you out.

 

Thanks for the suggestion. We have checked both the user profile, app data and home drive and cannot find any user specific .ini files I'm afraid.

[eddyc]

You've just reminded me exactly what I did - however your method of fixing it worked for me this time and is far simpler.

 

The way I actually fixed it was to create a symlink from c:\program files\SIMS to c:\program files (x86)\sims and that solved the issue.

 

Thanks for your reply. I am doing this right? It doesn't seem to work and am not sure if I am missing something?

 

 

Our sims.ini is here:

[setup]
SIMSDotNetDirectory=C:\Program Files\SIMS\SIMS .net
SIMSDirectory=\\SERVERNAME\SIMSDATA$\SIMS
SIMSSetupsDirectory=\\SERVERNAME\SIMSDATA$\SIMS\Setups
SIMSDiscoverDirectory=C:\Program Files (x86)\SIMS\Discover Client\
Folder=SIMS Applications
[LastChecked]
SIMSInfrastructureSetup=5.592.2.0

[Cache]

if you go to c:\program files\sims\sims .net - you should find it opens up the folder with your SIMS install does it?

 

I think your folders should possibly be the other way round in the command.