Automation to Innovation
Notice: This post does not contain any pictures. They were all lost during the import from my old Gonjer.com site. I do apologize for that but I hope that the post will still help. For some time ago I stumbled upon a strange credential prompt in Outlook for an entire organization after changing the Autodiscover […]
Outlook prompts for credentials with Exchange 2010 and 2013/2016 coexistence Read More »
For some time ago I was in the process of setting up a Hybrid “Skype for Business Online” and “Lync 2013 On-oprem” environment. When it was time to activate the Lync-federation with the New-CsOnlineSession cmdlet I got rejected with a (404) Not Found
|
1 2 3 |
$Credential = Get-Credential $CsSession = New-CsOnlineSession -Credential $Credential -Verbose |
I received the following output: VERBOSE: Determining domain to admin VERBOSE:
New-CsOnlineSession returns (404) Not Found Read More »
I’ve been working on a script for our customers so we more accurately can measure the load on IIS Websites using Nagios. Currently the script only gets the performance data and outputs an OK (exitcode 0). In the future I will implement WARNING and CRITICAL the performance values we need. Example graph from a labserver.
Monitor IIS Performance Data with Nagios / NSClient Read More »
I’ve been struggling some time now on why Powershell 4.0 are unable to “Catch” terminating errors when using Exchange 2010 Cmdlets. When using a standard “Set-Mailbox” with Erroraction set to Stop using Powershell 3.0 the terminating error is validated by the “Try/Catch”-block:
|
1 2 3 4 5 6 |
try { Set-Mailbox -Identity 'NoMailbox' -ErrorAction Stop } catch { 'Error with Set-Mailbox' } |
Error with Set-Mailbox When we use Powershell 4.0 with the same “Try/Catch”-block
Powershell 4.0 – Try/Catch Exchange 2010 Bug? Read More »