A brand new web console for Orchestrator 2019

With the latest UR6 release for SCORCH 2019, and the fact it states its no longer patching up the "older" silverlight web sites, i'm revisiting the "newer" console for our 2019 setup.

There are still issues with the newer console that haven't been addressed - is there any indication that these ever will be, or am i missing something?

• Folder / Runbook structure still isn't in order
• Where's the Events and Runbook Server Tabs gone?
• On installation i picked ports 8081 and 8082, but the installer installs as 5001 and 8082, so straight away you need to manually edit a config file to fix this and get the sites working - not great.

Any further update on this re bugs / issues / newer version since Sep 2023?

3 feedbacks submitted so far anyway - 3 bugs i had in initial version are still there:

- Not all folders / runbooks are loaded. Some folders are missing, and some folders are blank instead of listing the runbooks inside them (some sort of max number being returned?)

- Folders / Runbooks not in alphabetic order and can't change order

- Summary page shows "10" active jobs, but the list under it is blank.

StefanHorz that worked (changed port to the port number of the API endpoint) and we're up and running - thanks, now to test it...

Hi Andy_Stewart ,

configure WebConsole in C:\Program Files\Microsoft System Center\Orchestrator\WebConsole\assets\configuration.json to use the same domain and type (http/https) for WebApi (http://xxxxxx.testdomain.com:8082 ").

Regards,

Stefan

Dev Console is showing:

Access to XMLHttpRequest at 'http://xxxxxxxx:8082/api/folders' from origin 'http://yyyyyy.testdomain.com:8082' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

But i DO have this entry in the API web.config

<add allowCredentials="true" maxAge="7200" origin="http://yyyyyy.testdomain.com:8082">
<allowMethods>
<add method="GET"/>
<add method="PUT"/>
<add method="POST"/>
<add method="PATCH"/>
<add method="DELETE"/>
</allowMethods>
<allowHeaders allowAllRequestedHeaders="true"/>
</add>

Hi jukedude ,

Installed latest version onto our web server to test.

Powershell calls to the API endpoint are returning lists of jobs, runbooks, runbook servers etc, so that proves the API endpoint can retrieve details from the SCORCH DB itself.

The issue i'm having is trying to run the Web Console itself - constantly get the popup error "Uh oh! Trouble connecting to WebApi [status 0]"

Nothing really obvious that I can see i've missed? Hoping its something simple - any thoughts on what to check ?

Hi Andy_Stewart, Microsoft has released an update on the WebAPI/WebConsole components ~17 Aug. Please try it out, it is essentially the latest SCO 2022 Web components bundled for SCO 2019.

The migration steps provide a changelog as well.

Hi PChip1976 ,

thanks a lot for your Code triggering a Runbook with Orchestraor 2022 webAPI!

I can pass a value for a parameter in the Initialize Data activity like below:

$OrchURI = 'https://sco2022.stefan.local' #Replace 5001 by the WebService port
$RunbookPath = '\Test\TEST.Runbook'
$RunbookID =  ((Invoke-RestMethod -uri ('{0}/api/Runbooks' -f $OrchURI) -UseDefaultCredentials)  | Select -ExpandProperty value | where {$_.Path -eq $RunbookPath}).Id

# To Start a job
    $body = @{
        RunbookId = $RunbookID
        Parameters = @(
                [pscustomobject]@{Name='HyperVName';Value='HyperV01'}
                )
        CreatedBy = $null
    } | ConvertTo-Json 
Invoke-RestMethod -Uri ('{0}/api/Jobs' -f $OrchURI) -Body $body -Method Post -ContentType 'application/json' -UseDefaultCredentials

Hiya,

Thanks for the info in this blog been really helpful. 

Managed to get SCORCH 2019 WebApi working but the console side doesn't work.  Only got anonymous authentication set there and fire it up and still asks for username/password.  I input it anyway, use my own account which has sql perms also tried the SCORCH service account and it fails to connect to the WebAPI and get this "Uh oh! Trouble connecting to WebApi..." error.  

Any ideas please.