Register client through Network Gatewatey

Short answer yes.

long answer, we need detailed information about the network layer to give you a definitive answer.

that said what exactly are you trying to achieve?

Before the migration a decoupled install will be pushed out to ~100 servers that will be migrated to another side. The migration will be staggered and as they are moved we would like to join them to a Commcell that the clients will need to connect through network gateways. Once the clients are ready, we would like to be able to register the servers after their migration has been completed from the Console and complete the backup configuration. 

In the past we have had issues with large number of clients being registered at the same time and also caused some confusion. 

I would just join them ahead of time rather than setting them up decoupled.

you can pre-create a firewall group and then add them to the firewall group after moving.

the reason why I suggest pre-registering them is that as long as the client is listening and the commserve can contact the client you can push network configuration changes.

you can also check readiness post migration.

That wouldn’t be possible as they can’t reach the gateways at their current location and will only be able to reach them after they are migrated. 

They don’t have to reach the gateways at their current location. The gateway configuration would be applied to a group and updated post migration.

question.

can they currently talk to the commserve?

The reason I am making these suggestions is that way that you configure clients for networking communication is by updating the client networking rules and this is much simpler when the client has already established communication.

Typically you want to apply these communication updates via group especially for mass changes.

assuming that the commserve can reach the clients pre and post migration in order for the clients to receive and apply these communication updates rules the gateway configuration needs to be setup ahead of time.

meaning install the agents and configure them.

update their gateway configuration just prior to the migration.

this way once they are migrated they will have the gateway information already applied to resume communication.

No. Clients can’t talk to the commserve and will not be able to until after the migration so pre-registering is not an option. 

We can either do a decoupled install before the migration and run the “simcallwrapper.exe” command once the clients are connected at their new location or run the install after the migration when the clients will be able to reach the Commserver through the gateways. 

We are just looking to speed up the process by having the packages installed before the migration and register them from the console when they are ready without having log back into the servers one-by-one. 

Awesome. Makes sense.

​@christopherlecky You said there is a way to regisiter a client from the console that was behind a gateway, would you be able to explain how?