tgore
Reputable Poster
I know where to find the JDE.INI file on a FAT client (on my "C:\" drive), but I have not been able to determine what tells it where to create it for thin (CITRIX) clients. We have switched to AD (active directory) and are experiencing some performance issues for users that are not "local". This is because the CITRIX servers are "local" (Chicago) but some of our user's AD are at their location (Houston). Their profiles are travelling over the WAN and causing significant slow downs.
I know that the "OutputDirectory=" controls where the PDFs are stored when you view a report. Does this also control where the JDE.INI file is placed? I have noticed a few other "strange" things. On my deployment server the JDELOG and JDEDEBUG parameters are "C:\", on my CITRIX servers they are "C:\WINNT". If I delete my thin client's JDE.INI a new one is created from the CITRIX server, but it places the JDELOG & JDEDEBUG files at "U:\WINDOWS". The "U:\WINDOWS" directory is my AD and also where I can find my JDE.INI file.
Thanks in advance for any assistance
I know that the "OutputDirectory=" controls where the PDFs are stored when you view a report. Does this also control where the JDE.INI file is placed? I have noticed a few other "strange" things. On my deployment server the JDELOG and JDEDEBUG parameters are "C:\", on my CITRIX servers they are "C:\WINNT". If I delete my thin client's JDE.INI a new one is created from the CITRIX server, but it places the JDELOG & JDEDEBUG files at "U:\WINDOWS". The "U:\WINDOWS" directory is my AD and also where I can find my JDE.INI file.
Thanks in advance for any assistance