Home› Service Manager Portal Feature Requests
We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.

We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.

For more information around feature requests in the Cireson Community click here.
Options

Ability to put portal offline (for maintenance)

Sharon_SpearsSharon_Spears Customer Advanced IT Monkey ✭✭✭
in Service Manager Portal Feature Requests

It would be great to be able to put the portal offline with to everybody other than administrators.

Enable maintenance during business hours. 

I had an situation were a key runbook was accidently deleted form Orch and I had to recreate and test, but users were still using the portal and bugging me about problems which extended out the time to fix and increase stress levels.

If I could have put it offline for a few hours I would have got the fix done quicker.

19
Up Down
19 votes

Submitted · Last Updated

Comments

  • Options
    Dakota_GreenDakota_Green Member Advanced IT Monkey ✭✭✭
    Very good idea. You sir are getting a +1.
  • Options
    Tom_HendricksTom_Hendricks Customer Super IT Monkey ✭✭✭✭✭
    Voted up as a great feature, but I can also share a manual workaround that has worked well for this situation, to hold you over until they start developing this feature.  I am probably not the first/only person to do this, but perhaps someone will find it helpful.

    Create another web site (remember to use the same bindings if you do any https redirection) at the same level as your portal, which will be stopped during normal operation.  If it is set up correctly, you should get an error ("This website cannot be started.  Another website may be using the same port.") any time you try to start it, if your CiresonPortal site is still running.

    The other web site can have a static HTML file, such as a text notice about the planned outage--whatever you like.  If you want to really take good care of your users, you can add rules to this site that redirect/rewrite all URLs within it back to your static page (e.g., https://yoursite/Incident/Edit/IR1234 gets sent to https://yoursite/message.html).

    When you want to put your site in maintenance mode:
    1. Change the ports to CiresonPortal to something different, such as 81/444 (external traffic into to these ports is probably disallowed in most externally-facing implementations, but that is not necessarily a problem in this scenario)
    2. Start your "other" web site (which will begin accepting traffic at ports 80/443)
    Now they are both running, but your users will just get a message about the downtime, because they are not specifying the alternate ports.  Reverse these steps to set things back to normal.

    Caveats:
    • The 6+ portal installer will bulldoze some of these settings, and I am not sure if the second site would cause problems for the installer.  This worked fine for older versions, and works great for anything other than a portal upgrade.
    • If you script your IIS settings, you can mitigate what the portal installer does by running your scripts immediately after.
    • This won't stop anyone who knows the alternate port numbers
    • You probably want to create enable / disable scripts, because it is prone to human errors, otherwise.
  • Options
    Eugene_RackEugene_Rack Customer Adept IT Monkey ✭✭
    Good morning
    We have just migrated from SCSM2012 to SCSM2016 and latest Cireson portal version using the Cireson LM app. We also changed our website address to something more meaningful. I had to enabled the HTTP redirect so that anyone that had a link to the old url address would be redirected to the new address. What I am trying to do now is enable a non redirect for the old link for our analysts to check the old tickets (Closed / Resolved as we did not bring these across.) I noticed the Webconfig file has a redirect setting in it. 

    I was wondering if there is a way to add code to say that if you are using Firefox or Chrome to not redirect but use the old site address so that analysts could look at the old data? Below is the extract from Webconfig file. I would like to redirect to http://xyz.com for the analysts. Is this possible?

    </handlers>
            <applicationInitialization doAppInitAfterRestart="true" />
            <httpRedirect enabled="true" destination="https://abc.com/" exactDestination="false" httpResponseStatus="Permanent" />
      </system.webServer>
Sign In or Register to comment.