Good stuff. However I do have 2 questions:
1. During an upgrade, don't we need to turn off IIS? If yes, how will we be able to use the offline/redirect page?
2. During a regular package installation, and we use the redirect page, how do we allow Sys Admin's(who are doing the package installation) access to the Archer URL?
1. When upgrading Archer, IIS does not need to be stopped.
2. To use the offline/redirect page during a Package install, install the Archer Web component on one of the Services servers to act like a "management server" for Package installs. To prevent users from accessing the Web site on the Services server, just stop/disable IIS and enable it when needed.
Thank you Jeff.
1. I assume that keeping IIS running during an upgrade is applicable for the different deployment configurations(Single Host, Multi-Host, etc.)
2. Does this mean installing the Web component in multiple servers: one in the "Web role" services and then also in the "Services Role" server. If I understand this right, during an upgrade, the standard Archer URL found in the "Web role" services will be redirected to the offline page. The web component installed in the Services server will act as a "gateway" for Sys Admins to get into Archer.
Appreciate the help.
BKRP8rcAPvZAF0pR7uouAYqW78MAIkUapXd2nXyOIVE= - Yes, you are correct. Users accessing Archer via the normal Web Servers will be redirected to the offline page. The System Administrators will access the Web component on the Services Server as a "gateway".
Thank you very much .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.