Home

Future for Orchestrator

%3CLINGO-SUB%20id%3D%22lingo-sub-114090%22%20slang%3D%22en-US%22%3EFuture%20for%20Orchestrator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-114090%22%20slang%3D%22en-US%22%3E%3CP%3EHello%3C%2FP%3E%3CP%3EI%20might%20have%20missed%20the%20news%2C%20but%20has%20there%20been%20any%20official%20announcement%20on%20Orchestrator%20part%20of%20System%20Center%2C%20regarding%20it's%20development%3F%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20far%20I%20believe%20the%20development%20and%20bugfixing%20for%20this%20software%20is%20non-existent%2C%20hence%20I'd%20like%20to%20ask%20what%20do%20you%20see%20as%20future%20automation%20platform%20for%20on-premise%3F%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20in%20advance%20for%20some%20insight%3C%2FP%3E%3CP%3EAlexP%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-127143%22%20slang%3D%22en-US%22%3ERe%3A%20Future%20for%20Orchestrator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-127143%22%20slang%3D%22en-US%22%3EIt%20is%20a%20total%20scandal%20that%20Microsoft%20have%20ignored%20the%20Orchestrator%2032bit%20part%20for%20years.%20With%20all%20the%20workarounds%20you%20have%20to%20do%20to%20make%20ORCH%20Powershell%20activities%2064bit%20Powershell%205.%20It%20is%20a%20great%20mystery%20why%20they%20haven't%20fixed%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125744%22%20slang%3D%22en-US%22%3ERe%3A%20Future%20for%20Orchestrator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125744%22%20slang%3D%22en-US%22%3E%3CP%3EHey%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20replies%3CBR%20%2F%3EOn%20the%20other%20hand%2C%20I've%20watched%20in%20the%20meanwhile%20Ignite%20statement%2C%20which%20is%20confirming%20my%20worries%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DlCFPSE8TRiI%26amp%3Bfeature%3Dyoutu.be%26amp%3Bt%3D4710%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DlCFPSE8TRiI%26amp%3Bfeature%3Dyoutu.be%26amp%3Bt%3D4710%3C%2FA%3E%3CBR%20%2F%3EIn%20short%2C%20MS%20would%20be%20releasing%20a%20%22migration%20toolkit%22%20which%20I%20doubt%20would%20cover%20all%20Orchestrator%20solutions%20(think%20custom%20IPs%2C%20vmware%20and%20other).%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20other%20words%2C%20we%20would%20need%20to%20seemingly%20move%20some%20workloads%20to%20Microsoft%20Flow%20(which%20is%20a%20great%20automation%20product%20otherwise)%20or%20Azure%20Automation.%20Unfortunately%20this%20adds%20a%20lot%20of%20complexity%20when%20building%20workflows%2C%20and%20SCOM-%26gt%3BOrchestrator%20integration%20is%20good%20example.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125734%22%20slang%3D%22en-US%22%3ERe%3A%20Future%20for%20Orchestrator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125734%22%20slang%3D%22en-US%22%3E%3CP%3EWhile%20not%20about%20Orchestrator%20explicitly%2C%20this%20page%2C%20and%20the%20one%20it%20links%20to%2C%20may%20be%20somewhat%20informative%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fscsmfromthefield%2F2017%2F11%2F03%2Fscsm-roadmap-and-future%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fscsmfromthefield%2F2017%2F11%2F03%2Fscsm-roadmap-and-future%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20for%20Orchestrator%2C%20I%20believe%20the%20second%20to%20the%20last%20line%20in%20that%20post%20says%20quite%20a%20bit.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-125474%22%20slang%3D%22en-US%22%3ERe%3A%20Future%20for%20Orchestrator%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-125474%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20the%20least%20-%20upgrade%20it%20to%20deal%20with%2064-bit%20Powershell%20natively%2C%20or%20add%20a%20SCSM%20connector%20to%20Azure%20Automation%20to%20simplify%20the%20move%20to%20Azure%20Automation.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Alex Pawlak
New Contributor

Hello

I might have missed the news, but has there been any official announcement on Orchestrator part of System Center, regarding it's development? 

So far I believe the development and bugfixing for this software is non-existent, hence I'd like to ask what do you see as future automation platform for on-premise? 

Thanks in advance for some insight

AlexP

4 Replies

To the least - upgrade it to deal with 64-bit Powershell natively, or add a SCSM connector to Azure Automation to simplify the move to Azure Automation.

While not about Orchestrator explicitly, this page, and the one it links to, may be somewhat informative:

https://blogs.technet.microsoft.com/scsmfromthefield/2017/11/03/scsm-roadmap-and-future/

 

As for Orchestrator, I believe the second to the last line in that post says quite a bit.

Hey

Thanks for replies
On the other hand, I've watched in the meanwhile Ignite statement, which is confirming my worries:
https://www.youtube.com/watch?v=lCFPSE8TRiI&feature=youtu.be&t=4710
In short, MS would be releasing a "migration toolkit" which I doubt would cover all Orchestrator solutions (think custom IPs, vmware and other).

In other words, we would need to seemingly move some workloads to Microsoft Flow (which is a great automation product otherwise) or Azure Automation. Unfortunately this adds a lot of complexity when building workflows, and SCOM->Orchestrator integration is good example. 

It is a total scandal that Microsoft have ignored the Orchestrator 32bit part for years. With all the workarounds you have to do to make ORCH Powershell activities 64bit Powershell 5. It is a great mystery why they haven't fixed it.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies