N

[N @Niko_v2]

@AzureSupport The job is not in running state, it's stuck in the state called 'Queued'. Normally the jobs are in the 'queued' state for 5 seconds, before changing state to 'Running'. However, Bruno from Azure Support is helping me now. Thanks for the reply.

[N @Niko_v2]

@AzureSupport Hi Support, I've got a azure automation Powershell runbook job which has now been in the state 'queued' for 2.5 hours now. Can I terminate the job through powershell (Stop-AzureRmAutomationJob doesn't work) or can you please terminate the job?

[N @Niko_v2]

@m_meisler @ScsmSe Any news on the Incident part for Send Email 2016?

[N @Niko_v2]

@thekevinholman I'm trying to design the best SQL Server 2016 scenario for System Center 2016. Is this post valid? https://t.co/rIdo3MmfEi

[N @Niko_v2]

@ABaumgarten Is it possible that you couldn take a look at?https://t.co/ULwnfXN2gA

[N @Niko_v2]

@JohnerStefan You're a star! However, I'm confused & angry about SCSM DW and OPS DB Server Core supported, but not SCOM? What is that, MS?

[N @Niko_v2]

@JohnerStefan I loved your post, but regarding the new SCSM 2016 on WS Server Core - please check this link https://t.co/yhXXtDw2hW