Currently mfreg is used to point to a specific Presentation server in a farm from the client machine. All the MFCOM calls get routed to that specific machine and talk to MFCOM running on that Presentation Server. This technique uses DCOM client machine defaults when it gets new MFCOM interfaces on that machine.
The main drawback with the above method is that it always points to only one server in the farm and you could potentially manage only one farm. What if you want to manage more than one farm by talking to more than one server in the same program? You can achieve this programmatically instead of using mfreg.
Basically it involves using the “servername” of the Presentation Server where MFCOM is running while creating objects and interfaces. We will look at how this could be achieved in C# and VBScript.
If ServerName1 and ServerName2 CPS Servers belong to two different Farms, then you have theFarm1 and theServer1 pointing to Farm1 and theFarm2 and theServer2 Objects pointing to Farm2.
These above mentioned techniques will help you to create MFCOM objects and interfaces on any CPS Server without restricting yourself to one CPS Server in a program pointed by mfreg. You still need to run mfreg to resgiter MFCOM on the client machine but you could either just register locally or even preferred CPS Server. The above mentioned methods ignore the server pointed by mfreg.