Disconnected BigFix Server Import

(imported topic written by JasonO91)

Greetings,

I’ve got a remote BigFix server that we do not have the ability to setup as a relay server. We’d like to get the client information imported into the main BigFix server so that we can perform reports on the data. We had initially planned on using the disconnected client utility to simply import the client information. It’s been suggested that we make an SQL backup of the remote server, copy the data to the main server, then import the data to run reports on.

What files do we need to copy over, and what would the process be to import the data properly? We don’t want to overwrite any files that are on the main BigFix server.

Thanks,

Jason

(imported comment written by BenKus)

Hey Jason,

Are you trying to maintain two deployments, one “disconnected” and one that is “connected”? So you will have two BES Servers and two mastheads?

The easiest thing to do is to export the database (or back it up), copy it to another computer that we can call ReportComputer (not a current BigFix Server) and then restore the database on ReportComputer. Then configure the BES Web Reports to use the ReportComputer.

You don’t want to mess with importing data in an existing BigFix deployment from another deployment because you will likely screw up the existing BigFix deployment if you muck around in the database too much.

Ben

(imported comment written by JasonO91)

Ben,

Are you trying to maintain two deployments, one “disconnected” and one that is “connected”? So you will have two BES Servers and two mastheads?

We’ve got several servers at a location where we only have the ability to transfer files to and from the location. Opening up new ports to the network is unacceptable. We would like to get information about the servers in the environment back to our main BigFix server.

To answer your question specifically, one BigFix server is connected, and one server would not have access to the masthead. Currently, they do not have a BigFix server in the new environment and we are going to be installing one there. Will we need a new license to do this?

Wouldn’t it be easier to run a disconnected agent on the machines in the environment and then transfer the files generated to the production site?

Jason

(imported comment written by BenKus)

Hey Jason,

Sorry, I am still not 100% sure of what you are trying to do… but to answer your last question, I need to know how many computers do not have the ability to access the main connected BES Server?

If a computer doesn’t have access to the main BES Server at all (meaning that the agent cannot connect to a BES Relay that can directly connect to the BES Server), then it won’t report results to you. So if you have an isolated network, you will need to install a new BES Server deployment with a new license.

Ben

(imported comment written by JasonO91)

Ben,

So if you have an isolated network, you will need to install a new BES Server deployment with a new license.

This is exactly the case, as we are installing a BigFix server this morning. I was under the impression that we could use the same licenses from the main server, and simply split the licenses between the two sites.

This may be resolved faster if we take this offline.

Jason