Orchestrator Install Error on DBSetup. exe After a recent crash, we are doing a clean setup of Orchestrator 1801 on Windows Server 2016 The database is going to be stored on a SQL 2017 instance The Microsoft requirements made no mention of SQL 2017, but I'm not sure if this could be the source of my problem
Authoring tool requires Visual Studio Shell 2008 but cant download it I notice this still hasn't been fixed yet Any update on when we can expect a resolution? I must say the attention to detail paid to the latest releases (1801 onwards) of SCSM and Orchestrator with regards to issues like this, SCOM IP in orchestrator and the issues around having both SCOM and SCSM consoles coexisting on the same machine are starting to become incredibly frustrating Friday