Kayode Bristol

@ykuijs @andikrueger Trying to make this as simple as possible. - Don't really care which server is WFE. If node is performing SPProductUpdate, block load balancer IP with Firewall Rule....

@ykuijs Great explanation, thank you. Totally get it. There might be another way, if one could detect when SPProductUpdate was running... maybe with a mutex? Nix the UnBlockLoadBalancer script resources...

@andikrueger Yes. #1097 Deals with EnableSideBySide & SideBySideToken. I handle that with EnableSideBySideFarmWide and SetSideBySideTokenFarmWide Script resources in [SPFarmUpdateZDT Configruation](https://github.com/PowerShell/SharePointDsc/issues/1096#issuecomment-549906844), above. @ykuijs pointed out that my handling of the loadbalancer...

@andikrueger Looks like I missed something. Node should be pulled out of loadbalancer during SPProductUpdate and SPConfigWizard steps. It doesn't matter that SPConfigWizard shuts down services. Dumb loadbalancer will still...

@andikrueger I disagree. User gets 404 if server doesn't reply. That's not zero down time. The blocking firewall rule is used because even the most basic load balancer does a...

@jimbrayDel In theory, Yes. In practice, not so much. ADFS authentication sends back a redirect, which even the most advanced load balancers have issues with. A static, anonymous auth site,...

@jimbrayDel I get it. Some security Nazis in certain environments will call that unauthenticated content. Crazy, I agree. But some folks even block icmp between servers. Even using authenticated content...

Was reminded that Windows Firewall is also disabled in some environments in favor of other 3rd party tools like McAfee. Perhaps we leave load balancing out for the time being...

@andikrueger Awesome! I revised my example configuration ([SPZDPDSCConfig](https://github.com/kayodebristol/SPZDPDSCConfig/blob/master/SPZDPDSCConfig.ps1)). Removed load balancing stuff, and cleaned up a bit to only do the SideBySide stuff on localhost. Maybe it will be useful...

Looks like I haven’t kept up to date with changes in robot3. This was tested with sveltekit but with an earlier version of robot3. You can try dialing the robot3...