SOLVED

Windows Admin Center deployment across sites

%3CLINGO-SUB%20id%3D%22lingo-sub-870578%22%20slang%3D%22en-US%22%3EWindows%20Admin%20Center%20deployment%20across%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870578%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20multiple%20sites%20and%20looking%20to%20deploy%20Windows%20Admin%20Center.%20I%20understand%20that%20it%20can%20be%20deployed%20via%20script%20on%20a%20failover%20cluster%20-%20what%20would%20be%20the%20recommended%20topology%20to%20use%20for%20our%204%20sites%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESite%201%20-%20120%20VMs%20with%201Gbps%20connection%20to%20rest%20of%20sites%3C%2FP%3E%3CP%3ESite%202%20-%20400%20VMs%3C%2FP%3E%3CP%3ESIte%203%20-%20400%20VMs%20(there%20is%2010Gbps%20OTV%20connection%20between%20sites%202%20and%203%3C%2FP%3E%3CP%3ESite%204%20-%2020%20VMs%20with%20200MBps%20to%20rest%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20we%20looking%20at%20separate%20deployments%20in%20each%20site%20(I%20think%20I%20saw%20500VM%20limit%20somewhere).%20Or%20is%20there%20a%20way%20to%20nest%20WAC%20deployments.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20overly%20complicated%20to%20disperse%20failover%20cluster%20nodes%20between%20sites%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGeorge%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870773%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Admin%20Center%20deployment%20across%20sites%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870773%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20gateway%20per%20site%20may%20be%20sufficient%20-%20there%20is%20no%20limit%20on%20the%20number%20of%20VMs%20you%20can%20add%20to%20your%20connection%20list.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWAC%20only%20connects%20to%20one%20node%20at%20a%20time%2C%20so%20the%20question%20of%20scale%20really%20only%20applies%20to%20the%20number%20of%20folks%20that%20will%20be%20using%20each%20WAC%20gateway%20concurrently.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20our%20test%20automation%2C%20we%20typically%20have%20more%20than%2050%20simultaneous%20test%20cases%20running%20in%20parallel%2C%20which%20is%20equivalent%20to%20more%20than%2050%20concurrent%20users%20all%20performing%20management%20tasks%20through%20a%20single%20Windows%20Admin%20Center%20gateway%20at%20the%20same%20time.%20Our%20standard%20test%20gateway%20configuration%20is%20a%20VM%20with%202%20virtual%20procs%2C%204%20GB%20of%20RAM%2C%20100%20GB%20storage%20(non-SSD).%20With%20this%20configuration%2C%20we%20see%20an%20acceptable%20level%20of%20performance%20and%20response%20time%20through%20the%20gateway%20with%20no%20timeouts.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We have multiple sites and looking to deploy Windows Admin Center. I understand that it can be deployed via script on a failover cluster - what would be the recommended topology to use for our 4 sites?

 

Site 1 - 120 VMs with 1Gbps connection to rest of sites

Site 2 - 400 VMs

SIte 3 - 400 VMs (there is 10Gbps OTV connection between sites 2 and 3

Site 4 - 20 VMs with 200MBps to rest

 

Are we looking at separate deployments in each site (I think I saw 500VM limit somewhere). Or is there a way to nest WAC deployments.

 

It seems overly complicated to disperse failover cluster nodes between sites etc.

 

George

1 Reply
Highlighted
Best Response confirmed by ppgd2019 (New Contributor)
Solution

One gateway per site may be sufficient - there is no limit on the number of VMs you can add to your connection list.

 

WAC only connects to one node at a time, so the question of scale really only applies to the number of folks that will be using each WAC gateway concurrently. 

 

In our test automation, we typically have more than 50 simultaneous test cases running in parallel, which is equivalent to more than 50 concurrent users all performing management tasks through a single Windows Admin Center gateway at the same time. Our standard test gateway configuration is a VM with 2 virtual procs, 4 GB of RAM, 100 GB storage (non-SSD). With this configuration, we see an acceptable level of performance and response time through the gateway with no timeouts.