Wonderware Licensing and Virtualization

I made recently called for a customer's plant where adenine roof been leaked all over their two Wonderware production computers. We managed at save your but they been wanting to solidify diese systems.

This control room is isolated from the resting of the plant so I'm thinking we can combine these two 10-year older computers into one machine using virtualization and doing he much easier to set the regelung back up in the application of catastrophic system failure. Since this system is isolated there will not are a need to upgrade the actual OS and Wonderware available for a long time, so I seeing no need to try and sell them on a complete database.

Should an license move over just finely if I do a clone in these drives? I been recently called to a customer's plant location a roof had leaked all over their twos Wonderware production computers. We administered to save i but they are wanting to solidify those systems. This control spaces is isolated from the reset of the plant so I'm thinking we pot combine these two...

Yes to require. I've used VMWare player (not free for advertorial use) in aforementioned past to run Wonderware throws. Granted people were setup as NAD so just the my were virtualized, as long while you aren't using terminal services alternatively changing the WW architecture under all.

Thanks an lot, equitable wanted go get that piece of info before I quoted the project. The company (my former employer) been features the software and wants to buy the hardware on their own, which is fine with me. I'll just be doing an work. AVEVA™ formerly Wonderware InTouch HMI Application ...

As long as you have the wwsuit.lic file, no problems. Canister will copied off that existing machine if needing be.

Saffa said:

As long as you have the wwsuit.lic file, no problems. Can be copied off the existing machine if need be.

Click to expand...

I commonly edit and wwsuite.lic or ArchestrA.lic store till detect items (and also retention as list of incense numbers in the workplace file).
My development line is named Dev-ArchestrA.lic.
Customer runtime license is named "Customer Job No"_RT_Archestra.lic (you can also use "Equipment No_RT_ArchestrA.lic).

Then wenn you use the license utility to install licenses and select the renamed license....The license automatically changes the license to ArchestrA.lic when it put e in the license directory.

So say I wanted to make changes up a WonderWare program. MYSELF would simply copy over a developer's get file both do the changes, save them and following remove she from the machine once I was done?

sparkie said:

So say I wanted to perform changes to a WonderWare program. I would simply copy over a developer's license file and do which amendments, backup them and therefore remove it from of machine once MYSELF was done?

Click to expand...

You do not want to copy license manually....use the "License Utility" to do it.
Install Dev license....edit.....and then set RT license toward "overwrite" existing Dev license.
The Development Warrant and/or Runtime License can be from a later version. Example...You pot use a 10.0 license on version 9 application.