+ Post New Thread
Results 1 to 3 of 3
MIS Systems Thread, Personnel 5.1 on Terminal Services in Technical; As the last part of our Terminal Services puzzle, we've been getting Personnel 5.1 to run (via the SIMS launcher). ...
  1. #1

    Join Date
    Feb 2006
    Location
    Isle of Wight, UK
    Posts
    149
    Thank Post
    28
    Thanked 28 Times in 25 Posts
    Rep Power
    22

    Personnel 5.1 on Terminal Services

    As the last part of our Terminal Services puzzle, we've been getting Personnel 5.1 to run (via the SIMS launcher). After a lot of digging around, it is now installed, but I did have to add some compatibility information into the registry on the terminal server to allow it to run:

    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\LAUNCHER
    The 'Flags' (a REG_DWORD) value are set to '504' (hex) which basically directs all DLL and .ini references to the server system root (ie C:\windows) rather than each user's profile (C:\documents and settings\user\windows).

    The only problem I'm currently encountering is that anyone running the Launcher has to be a machine admin, which isn't ideal.

    If there was a definitive list of files/registry paths that Launcher/Personnel accesses, I could change permissions accordingly. Bit of a long shot, I know, but it never hurts to ask

    Stephen

  2. #2
    fooby's Avatar
    Join Date
    Dec 2005
    Posts
    351
    Thank Post
    0
    Thanked 5 Times in 4 Posts
    Rep Power
    20

    Re: Personnel 5.1 on Terminal Services

    You would use a comination of filemon and regmon from sysinternals or the new process monitor from microsofts acquisiton of sysinternals. this will list all the things the process is attempting to access.

    after looking throught this i imagine you will be able to sort it

    fooby

  3. #3

    Join Date
    Feb 2006
    Location
    Isle of Wight, UK
    Posts
    149
    Thank Post
    28
    Thanked 28 Times in 25 Posts
    Rep Power
    22

    Re: Personnel 5.1 on Terminal Services

    After spending a mind-numbingly long time reading through registry/file access logs, I discovered that the problem lay with the SIMS server machines, and not the terminal server

    I'd given the Windows users full control over the SIMS folder within the SIMS share, but I apparently needed to give them full control over the root of the share too! Can't really see why, since nothing gets put in the share root, but I'll put it down to a combination of crusty old code and Microsoft Terminal Services.

    Now, if RM could just discover why the VPNs don't work, I'll be happy...

    Stephen



SHARE:
+ Post New Thread

Similar Threads

  1. Mac Terminal Services
    By StuartC in forum Mac
    Replies: 5
    Last Post: 1st September 2009, 09:17 PM
  2. MS Terminal Services Connections
    By Lee_K_81 in forum Thin Client and Virtual Machines
    Replies: 13
    Last Post: 7th November 2007, 10:49 AM
  3. Terminal Services
    By wesleyw in forum Thin Client and Virtual Machines
    Replies: 2
    Last Post: 30th June 2006, 01:34 PM
  4. Terminal Services
    By faza in forum Windows
    Replies: 15
    Last Post: 1st June 2006, 11:37 AM
  5. Terminal Services +USB
    By Dos_Box in forum Windows
    Replies: 4
    Last Post: 25th May 2006, 02:26 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •