Deployment of MIMS 4.3.1.1 and above 2

[ptsakiss]

Couple of questions, concerning the deployment of MIMS Ver 4.3.1.2

Has anyone deployed MIMS Ver 4.3.1.2 or 4.3.1.1 as a Network Client? If so what issues did you encounter and how did you manage to overcome these?

Has anyone deployed MIMS 4.3.1.2 or 4.3.1.1 utilising CITRIX. If so, what made you decide on CITRIX?

Thank you for your time.

Regards,
Pete

 

[blakej]

Network installation is good for administration purposes,
(applying patches, code control etc), but you can suffer slower performance than a full client install.
You also have the option of selecting what components you have on the client and network sides.
The popups database can be a pain since paradox can only support around 35 users. This means you have to replicate the database a number of times to support many users.

Most people select TSE (CITRIX), it has the benefit of centralised administration.
one problems is that TSE under NT does not scale that well, with 30-40 users maximum. (unless your HECO who seem to do better somehow).
A dual CPU 2gb memory config appears to be pretty standard. Adding extra CPU's do not seem to help.
This fits with the Paradox 30-35 user limit anyway.
Under Win 2000 the scalability is improved so you might be able to squeeze more users on.
The TSE/Citrix install needs a little more work with installation. (Registry setting,and directories).

 

[Glen]

Don't underestimate the difficulty of applying patches and updates to client systems. This can be a very major headache. If you have some form or automated distribution system, this may not be as much of a problem.

Remember, most front end (client) patches/changes/updates must be synchronized with a back end change. Give a lot of consideration to things like network deployment. It can save you a lot of effort later on.

Glen
Glen Colbert
gcolbert@RAG_American.com

 

[mrmad]

We use dual staging locations on our network servers. This way we update one location and direct the client to look at this whilst the old location is maintained so that we can revert if there are any issues.
We use NetWare Application Launcher(NAL) to provide the client updates and distribution of the popup databases. The paradox client is distributed as part of the NAL update process. As we only distribute middleware and borland through NAL the overhead is minimised.

We also apply this to our citrix environment, using NAL to provide the neccesary registry updates.

Jerome

 

[ridz]

Everyone,
In the company that I'm working, we have 4 main districts. The main one uses fat client (MIMS Explorer). Other districts use Citrix. Even though I've been informed that Citrix offers better connectivity, I find pretty much easier to use the fat client. By the way, we just Gone-Live and not so sure on other problems. It seems that our network is still unstable and veryhard to determine problems, credits of 4.3.1.2 and Citrix. But, we decide to use Citrix because we can run MIMS through old PCs and moreover the others districts are located at a very remote area.