mrbios (12th October 2010)
Have you made sure that the Apps are enabled for TS Web access in the list and also that you are using the correct server as a source for the apps?
Publishing Applications with TS RemoteApp - IT Tutorials - OS
mrbios (12th October 2010)
We have about 80 schools using SIMS and FMS through remote app. The main problem we’ve had, like you, is that configuration and dll files often can not be found. What I’ve noticed in the past is that on the terminal server it creates a Windows directory within C:\Users\[username]\Windows. Often the files in that windows directory are out of sync with the ones in the real Windows directory. You can either correct the files in the users windows folder or delete the folder forcing the terminal server to recreate them.
This has solved most of our problems, specifically with FMS. The only ongoing issue we have with remote app is printing from FMS. FMS is quite temperamental with detecting printers mapped using TS easy print.
We are testing sims.net on a windows 2008 R2 remoteapps at the moment and have resolved the issue of the commandpulsar.exe by carrying out the following procedure:
1) Load up FMS as usual and login to it
2) Let the error message of commandpulsar.exe not found come up and OK to it
3) In the FMS Application goto Tool menu and select Star 7 settings and update the path i.e. put in c:\program files (x86)\Sims\sims .net.
4) Save the changes and restart FMS. The error will no longer appear now.
Hope this help anyone who's having this issue. We fixed it by looking at this site and it mentioned about this error:
Helplines Online: July 2010 - about a third way down is some info regarding this error. This actually says to untick the Star 7 settings but we just modified the path and it works happily.
Hi spc-rocket, does that setting change affect any users of 32bit OS's or is the setting change specific to the machine the setting is changed on?
Good point, didn't think about that, just tested it and its not machine specific it does cause issue for other users on windows xp stations. I've reverted it back again now.
Bummer! back to the drawing board again
I suppose another way to do it would be to copy the sims .net folder into the proper program files (i.e. c:\program files\sims\sims .net) and when there is any upgrades just do the copy again i.e. overwriting. We've tested this and it seems to work i.e no commandpulsar.exe error and the rest of the users on 32bit OS are fine as well. Its a workaround until capita fixes this for 64bit installs.
Last edited by spc-rocket; 18th November 2010 at 01:15 PM.
Will try the reparse point method.
There are currently 1 users browsing this thread. (0 members and 1 guests)