Ok so I completed 11.3 upgrade this Saturday. We have a completely distributed deployment, with all of the components - Web Adaptors, Portal, Hosting Site, Relational Datastore, Tile Cache Datastore and a Federated Server Site that supports our Image Server and SDE feature access services on separate servers.
For the first time, I was able to convince our EIT security to allow the capability to suspend active virus scanning during the upgrades. So for Portal, Server and Datastore what used to take 3 -4 hours per server, with various hanging points during both upgrade and post-upgrade, now took 15 - 30 minutes.
So for our entire enterprise, the update would take up to 18 hours. I had the entire deploy upgraded, cleaned and tested, in 5 hours.
I can't express how thrilled I was. Simply by suspending active virus scanning during the upgrade and post-upgrades.
I did run into one hiccup that relates to this thread. While adopting the updated uninstall - reinstall order for web adaptor, the reinstalls went just fine for both Portals' WA and the Hosting Site WA.
But for the Federated Site WA, the reinstall failed with a window installer message:
'Can't complete install because a folder with the same name already exists in the ....\innetpub\wwwroot... directory. Remove the folder or rename the install'. Having never seen this before, I wasn't quite sure what to do.
So I made sure that the 11.2 web adaptor was no longer registered with the 11.3 Federated Site and then I went into the wwwroot folder and physically delete the windows directory. Then I ran the install again and it did complete. It then took a few minutes for the IIS to recognize? I guess? my 'agsfed' WA name and it spun up via localhost and I was then able to configure.
Everything is up and clean so far, but am now thinking, that for my Federated Site, I may go back to removing the WA prior to running the Server upgrade exe . . . but otherwise not real sure if there was a better way to handle this.
@MarceloMarques
@Scott_Tansley
