Announcement

Collapse
No announcement yet.

Registry Entries for Terminal Server User

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Registry Entries for Terminal Server User

    We have added new keys under HKLM\Software\Company Name\Appl\CSECU.

    From the Desktop (logged in as Administrator) the keys are being read, but if you log in over a Citrix session as User those registry keys are without effect.

    Does someone have an anser? would be greatly appreciated.

    Thanks
    *K*

  • #2
    Re: Registry Entries for Terminal Server User

    Have you checked the permissions on the registry keys you have added?

    Ste
    Steven Roberts
    IT Mercenary

    MCITP:EA|MCTS|MCSE 2003 (Messaging and Security)|MCSA 2003 (Messaging and Security)|MCP|Prince2 Practitioner

    Don't forget to click on the Yin-Yang icon to leave reputation points if you think my advice has been worthwhile!

    Comment


    • #3
      Re: Registry Entries for Terminal Server User

      Yes, we changed the user-permissions to that Registry Key to "full control" but NO effect. There must be something else, maybe policies to read registry? All worked fine under Windows Server 2003.
      Thanks for the effort.
      *K*

      Comment


      • #4
        Re: Registry Entries for Terminal Server User

        When you are sure permissions to that Registry Key are OK (you can export the customized keys, try deleting the actual keys from registry, then import the keys back. Permisions will now be inherited from the existing keys. Check if the entries does not contain strange characters) - then probably the application or service that should read the entries is not fully operating for the users.

        Is this app/svc running under the user's security principals?
        Does the app perhaps try to write/edit files in a folder where the the user does not have permissions?

        Could it be that similar entries under HKCU perhaps take precedence?

        Can you provide us more detail about the added entries in the registry and what application is using it and how (how can you notice that it doesn't work for the users).


        \Rems

        This posting is provided "AS IS" with no warranties, and confers no rights.

        __________________

        ** Remember to give credit where credit's due **
        and leave Reputation Points for meaningful posts

        Comment


        • #5
          Re: Registry Entries for Terminal Server User

          Originally posted by Rems View Post
          When you are sure permissions to that Registry Key are OK (you can export the customized keys, try deleting the actual keys from registry, then import the keys back. Permisions will now be inherited from the existing keys. Check if the entries does not contain strange characters) - then probably the application or service that should read the entries is not fully operating for the users.

          Is this app/svc running under the user's security principals?
          Does the app perhaps try to write/edit files in a folder where the the user does not have permissions?

          Could it be that similar entries under HKCU perhaps take precedence?

          Can you provide us more detail about the added entries in the registry and what application is using it and how (how can you notice that it doesn't work for the users).


          \Rems
          Thanks for your info Rems.
          Your question about the app/svc running under the user's security principals was the essential one. Over a simple VBS Script to Read Registry published under the Users principal, we found out that we were looking at the wrong cause. The app we use that reads the registry appears to have lack of right to read reg.

          Comment

          Working...
          X