pianosynth
Reputable Poster
I am trying test the installation of a new Citrix farm which will replace the old farm. I don't completely understand the mechanism whereby JDE initiates the replacement of the JDE.INI. It will be necessary for everyone to get a new INI because JDE is installed on drive D on the old farm and drive C on the new farm and the installation path is a setting in the JDE.INI. My observations so far: a new Full package always prompts for INI replacement when logging in the first time after a Full deployment. There is a switch during and Update build that allows for replacing the INI. I tried an Update package (include only 1 object) with this switch turned on to replace the INI, deployed it to the new farm ONLY and the first login attempt worked in forcing the new INI. I deleted my INI, logged into the old Citrix farm, received the old INI then tried logging into the new farm, but didn't get the new INI. Is there a table entry somewhere that keeps track of the fact that I was forced to get the new INI the very first time I tested this? I then published the new farm for one of our developers and had him login, but he didn't get a new INI. I'm very puzzled by this. Of course, I can build a full package, install it only on the new farm and turn off the old farm over the weekend, but I don't fully understand why my developer didn't get the new INI. Can someone shed some light on exactly how this process works?