Ini file being replace on Citrix for Full Packages

wgrantusa

Well Known Member
When I do a full package, the ini files of our citrix and TSE clients get over written. Is there a way to not do this? Some of the users are upset, OK a little ticked that their changes are gone and have to be redone.

Thanks
Stephanie
 
You're right, it's very annoying! Make the "main" JDE.INI on the terminal server read-only (C:\Wtsrv\Winnt\JDE.INI).
 
Hi there,

Another easy way to get around the problem, is before the deploy commences:

1. Open JDE.INI in notepad and leave it open.
2. Deploy the Full Package to the Citrix Server
3. Save and Close the JDE.INI file in notepad, thereby overwriting the JDE.INI file installed during the package deployment.

Good luck..
/Porup
 
Hi,
If you install full package through setup.exe you replace jde.ini on workstation or Terminal Server/Citrix, if you deploy full package like an update package jde.ini will not replace.
Gigi
 
Hey Stephanie,

When you create a new package in the package build option, do not select / tick the option 'Replace Jde.ini'

Rgds
Nailesh
 
We found that even when ensuring the Replace JDE.ini option is deselected before the FULL package build, the package.INF is still set to ReplaceIni=Y in the [Attributes] section. We manually update the package.INF after each FULL package build to change this setting to ReplaceIni=N, so the JDE.INI is left alone and not replaced when running the OneWorld Client Install setup.
 
When you say that you update the inf after each Full build, do you change it
before you deploy the package? Or are you updating it before you run the OW
Client Install?
Since we are still doing CRP, we do not have a schedule of when we do full
or update packages. We also do not have a written procedure to follow. We
are in the 'learn as you go' part and it is so much fun!




Stephanie Strohmenger
William Grant & Sons, Inc
Edison, NJ
 
Re: RE: Ini file being replace on Citrix for Full Packages

We update the INF after EntSrv deployment, but before OW Client Installs and deployment to multi-tier DepSrv. This problem only occurs on FULL package builds, update packages maintain the ReplaceINI setting appropriately when built. Good Luck!
 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\IniFiles

Create DWORD value named JDE
Give it a hex value of 4C
 
Thanks Brother of Ka

Would this be only for our citrix and TSE servers? Or does this need to be done on the fat client as well?

Stephanie
 
I forgot to ask on my last reply, What does the DWORD do? How will having one named JDE not change the ini file?

Stephanie
 
Back
Top