![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: User specific addins under Citrix Topic Summary: Created On: 7-Sep-2005 07:36 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We have a common set of DXL addins which people have been accessing by updating the relevant registry entry (done via a script) to point to a central area. People/projects can develop their own addins and append the location to the relevant registry entry.
We are now moving to a Citrix based solution and the problem I think we will have is that the registry entry is under the HKey_Local_Machine not HKey_Current_User so every user will pick this up which means it is not possible to have people/project addins. Does anybody know how to get round this problem? Is there a feature of citrix that gets it to look at hkey_current_user instead of hkey_local_machine? |
|
![]() |
|
![]() |
|
Hello Richard,
I cannot yet help you with experience on Critix with DOORS (just Citrix with other apps) but I imagine that the solution you're looking for comes already with DOORS itself. Instead of using the HKLM area, which might be copied from the "system default" at each start of a Citrix client session, use the HKCU area for the addins / projectaddins. I havent't got working a mixture of path settings in HKLM and HKCU but the single use of one of both possibilities works fine. If you preset your settings in the HK_Users\.default area your administration effort might be limited. ------------------------- Regards Karsten |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
User specific addins under Citrix
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.