Hi Scott,
In my paper, I made the following statement when building a vm-ware or fat-farm soultion:
"Install EnterpriseOne onto each virtual PC. Be sure to include the developer as well as the production objects. Install all of the pathcodes that you will need. Run R98CRTGL and R92TAM as per the previous section.
You may have noted that I did not include EnterpriseOne in the PC template. That was intentional. EnterpriseOne licenses its clients on a per seat basis. Installing Enterprise-One on a template would confuse the count. As a side benefit, you will have a list of workstations that have received a client. You can use that list to “Push” out client updates to."
I left the JDE client off of the VM-ware image for several reasons:
1) License count - installing the client to the virtual PC will assign the JDE license. The license is per seat, not per user. It is something installed on the C drive of the PC. The license file is an everygreen file, updated everytime you use JDE. If you change the date and time of the PC more than 24 hours backwards, your JDE license expires.
2) Build a list - installing JDE individually will help you to build a list of places where the fat client is installed. This will pay off later if you want to "push" an update or full package out to the clients. If JDE was part of an image, you loose the ability to "push" the package.
3) Registry - Have you ever looked at all of the registry entries that JDE dumps on your system? It's in the thousands. If you had JDE as part of the PC image and replicated it, god knows how many registry entries would need to be tweaked to get it to work on the cloned machine.
Bottom line, the JDE fat client was not designed to be part of standard PC image. You could try it that way, but my gut tells me that that would be an exercise in frustration. But don't let me stop you, have at it!
Gregg Larkin
Praxair North American System Admin
JDE CNC and Security, Websphere, Tidal, Princeton Softech
175 E Park Drive
Tonawanda, NY 14150
(716) 879-3169