There I was, doing homework or something, when I see a handful of important-ish emails pop up on my phone. I don’t want to deal with anything requiring more than a passing acknowledgement on a mobile device, and I’m sitting right there at my laptop, so I fire up Outlook. I’m greeted with this: Something went wrong? That’s all you have for me? I need my emails. What on earth are you complaining about....
tl;dr – Close your Synchronization Rules Editor and just populate the mailNickname attribute in AD. There is a growing number of business networks that have never had Exchange installed on-premises. That’s awesome. You absolutely do not want to waste your time protecting your Exchange environment against whatever scripted threats can be thrown at you 24/7, especially when you can just pay Microsoft to do it for you. However, what that means is you end up missing information in a few places that Azure AD Connect is looking....
While following Elan Shudnow’s excellent guide on Connecting Azure Runbooks to Exchange Online and Microsoft Graph, I ran into the following error while uploading a self-signed certificate: And that’s weird, because I was just pasting the exact password I had generated with HSXKPasswd. I recreated the certificate and tried again – no dice. This “The specified network password is not correct” error can come from multiple areas in Azure, and searching for an answer didn’t really help....
Let’s say you’re testing something. I don’t know…hyperlinking from plaintext emails generated by ADManager Plus, for instance. And let’s say while you’re doing that, you accidentally send a test email everyone at your largest client. That sucks! So here’s how you can search for and purge emails from Powershell. Try to do this as quickly as you can, becuase you absolutely do not want to explain to 400 end users why they just got some random internal email when the VP of IT has been pushing some poorly-designed anti-phishing training on everyone....
I recently tried installing a package with winget, which is included with Windows 11. Like, out of the box. Imagine my surprise when I see this: winget: The term 'winget' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. Now I realize I’m running an Insider flight of Windows 11 on ARM, so things can get wonky....