OFSV3.3 on Windows NT4.0 station

Goals and symptoms:

A customer has bought Unity v2.3 and so he has got OFS v3. He has WinNT as corporative system on his site so he heeds to get OFS v2.5 instead of OFS v3 in order to be WinNT compatible.
Could you please explain how to get OFS v2.5 license instead of OFS v3?

Causes and fixes:

OFS V2.5 is compliant with WinNT4.0 but isn't compliant with UNITY PRO. OFS works with Unity only from version 3.0.

Moreover, the Unity V2.3 requirements don't allow installing on Windows NT.

System requirements to use Unity v2.3
==============================
System : Pentium Processor 1.2 GHz or higher, recommended 2.4 GHz
RAM memory : 512 MB recommended minimum
Hard disk : minimum available free space 2 GB, recommended 4 GB
Microsoft Windows 2000, Microsoft Windows XP Professional Edition

There is no problem to design Unity application for PLC on WinXP taking into account necessity to use only located variables in project in order to work with OFS v2.5. The client needs to access his PLC from some SCADA via OFS installed separately on WinNT. I do not know how he has got the OFS v3.3 but the question is how to change OFS version in order to be WinNT compliant (OFS v3.3->OFS v2.5)?

Sorry for the response time but we did several tests in order to find a solution for the customer.
The HUB Web Service don t support OFS version 2.5. Consequently, we can t provide an authorization for this version.

We reflected at 2 solutions:
======================

* First solution: (Its an complex solution and you have to build the OFS configuration just one time)
--------------------------------------------------------------------------------------------------------------------------------------------------------
1.You install OFS V3.3 in silent mode with the following command:

[DRIVE]:\...\Server\setup.exe -C<Part Number> -N<SerialNumber>
[DRIVE]:\...\OFSConf\setup.exe

But with this version, we can t use the configuration tool on NT4.0.

2. Nevertheless, if you install the OFS configuration tool on another compliant computer (Like XP SP2), you could build the OFS configuration.

3. In order to export the OFS configuration on the NT4.0 platform, you have to export the OFS configuration in the registry [HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Automation\OPCsrv].

4. Finally, you send me the reg file. (I have to convert the reg file for NT4.0)

* Second solution: (In according the customer architecture, we will risk to occur some performance issues)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Could you describe me the customer architecture? Used communication?
The goal of this solution would be to install a OFSV3.3 on compliant platform, in order to communicate with the NT4.0 Station through the network (using DCOM technologie) .

How to?
1. Install OFSV3.3 on compliant Operating system (XP SP2),
2. Install the remote client available on the OFS setup on the NT4.0 Station,
3. Configure the DCOM security rights in according the OFS documentation (See the attached file: OFSv2.5_doc) on the NT station (Client) and also on XP station (Server).