Does a joined machine to a server site also be federated to a Portal?

[Yogesh_Chavan]

We have an ArcGIS Enterprise Multi Machine Deployment involving 2 machines for ArcGIS Server (Machine C joined to Machine B in the screenshot below). We have successfully federated the Server Site on Machine B.

Now, Does a joined machine to a server site also be federated to a Portal? If we try it returns an error stating Federateserverstatus0. 

Thank you!!

[Scott_Tansley]

Yes it can and it definitely works, I’ve done it.  

But if you’ve federated to machine B using its machine name and not a load balancer or web adapter (with DNS records) then I would imagine that it will not work.  

The portal would always be trying to communicate with machine B.  So, if for example, machine B is powered down then how would the portal know that machine C exists?  

[Yogesh_Chavan]

Thank you @Scott_Tansley 

Yes, the Server on Machine B is federated through a web adaptor URL.

It still does not work for us and allow us to federate the Joined Machine C to the Portal.

Also, in our case after joining Machine C with B ArcGIS Server Manager through Machine C does not opens.

https://machineC.test.net:6443/arcgis/manager

Just keeps on loading please wait bar and nothing happens.

[Scott_Tansley]

Im sorry. Its very late here so this will be my last message today.

are all of the documented firewalls open between machines b and c?

where is you configuration (file) store in relation to machines b and c?  Can both machines communicate freely with it?

cam you communicate from the web adaptor machine to machine c?

[BillFox]

take a look here: https://enterprise.arcgis.com/en/server/11.1/deploy/windows/configuring-a-multiple-machine-deploymen...

[TimoT]

If you've joined machine C to the existing federated server site, you don't need to perform the federation workflow again.

Think of it more as though you're federating a server site rather than just an individual server. Any new machines you join to the existing site will simply be added to the federated site. If you navigate to the security section in either server manager or server admin for machine C, you should find these security pages tell you this server is federated and has adopted the Portal's security model.

If you have another server site that is unfederated and you add additional machines to that site, then all machines in this site will be unfederated.

As for the perpetual please wait loading bar when accessing ArcGIS Server Manager via https://machineC.test.net:6443/arcgis/manager - according to Esri documentation, it seems intended for you not to be able to access ArcGIS Server Manager via port 6443 after you configure a highly available server site. See the documentation below:

• Also be aware that using a load balancer URL affects the way you connect to ArcGIS Server Manager. F...

However, I've been able to get around this by ensuring the SSL certificate you have bound to machineC's ArcGIS Server on port 6443 (the underlying tomcat webserver) is trusted by your browser. See the Esri tech article below - Problem: Unable to Access a Federated Server Manager Using the Google Chrome Browser (esri.com)