rakkad
asked on
AD/Citrix and tsprofiles
We have an application that uses Citrix, during launch it creates two files BCS.INI and HOST.INI which should create these in the home tsprofiles e.g. \\cslwinprn01\tsprofiles$\ tek-rjk.NB S which it does, if the 'Connect' option in AD profile is not set to use u: \\cslwindat01\homes\tek-rj k
However, we have a policy that users have the u: drive which acts as their personal drive to save their documents etc...
I checked the parameters (from DOS...) and found the following:-
HOMEDRIVE=U:
HOMEPATH=\tek-rjk
HOMESHARE=\cslwindat01\hom es\tek-rjk
Therefore it appears that because of this when uses access this application, the BCS.INI and HOST.INI is written to the U:\ drive, which I need it to write to \\cslwinprn01\tsprofiles\t ek-rjk
So...
1) How can I override the HOMEDRIVE, HOMEPATH, HOMESHARE, so it does not use the U: drive, could a script for be used prior to logging onto the domain so these parameters are blanked out and not used as the default location???
Any suggestions will be much appreciated....
Thanks
However, we have a policy that users have the u: drive which acts as their personal drive to save their documents etc...
I checked the parameters (from DOS...) and found the following:-
HOMEDRIVE=U:
HOMEPATH=\tek-rjk
HOMESHARE=\cslwindat01\hom
Therefore it appears that because of this when uses access this application, the BCS.INI and HOST.INI is written to the U:\ drive, which I need it to write to \\cslwinprn01\tsprofiles\t
So...
1) How can I override the HOMEDRIVE, HOMEPATH, HOMESHARE, so it does not use the U: drive, could a script for be used prior to logging onto the domain so these parameters are blanked out and not used as the default location???
Any suggestions will be much appreciated....
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This solution worked for me
I think we need to start by finding out where your application gets the settings from that it writes into the file. Its very specific information.
Try updating your user account to use the H drive letter in AD instead of U and see if the BCS.INI and HOST.INI still reflect U. If the files change to H then you know the application is getting the information directly from AD and if it still states U then there must be another location (Perhaps in the registry or application setting files) that we can update not to reflect the U drive.