WSEE connection to Microsoft Cloud Services.
Ok, I originally setup WSE 2016 not long after it’s release and never had an issue – it just worked!!
Fast forward and needed to do a complete reinstall. I can get the OSs to install just fine (WSE 2016/WS 2016 Standard/WS 2022 Standard).
Everything installs just fine until I get to the Essentials step. WSE 2016, I did all of the extra steps, still didn’t work.
Switched to standard, did the Azure AD, PCNS, everything else, still didn’t work.
WS 2022, installed fine, ran the WSEE and still it didn’t work!
EVERYTHING just stops at the Microsoft Cloud Services integration. I’ve done it right after completing the main install, clicked the link in the Server Manager, nope. Tried to do it using the Dashboard! Nothing!!
Can someone please tell me any specific steps that need (should) be taken during the installation so that I can bullet-proof the install and getting it working.
I have the custom Domain Name setup and will be binding my server to that address.
Any help would be greatly appreciated. Thanks in advance.
- RSquared64 asked 2 months ago
- You must log in to post comments.
I haven’t tested the Microsoft Cloud Services integration (Microsoft Online services) stuff in WSEE in many years now and so I cannot say for sure if it still works or not. Although, it wouldn’t at all surprise me if it’s not working. Microsoft has pretty much stopped supporting Windows Server Essentials now and so a lot of the backend stuff for their online services have become neglected and no works as expected. I pretty much gave up on using any of the online services stuff in Essentials long ago.
That being said… If it still works under Windows Server 2016 (in either the Essentials SKU or in Standard/Datacenter with the WSEE server role installed), then it “should” still work in Windows Server 2019, 2022, 2025 with WSEE installed via the WSEE Installer as well seeing as everything required to make the online services work is properly installed and configured by the WSEE Installer (I verified that it was working properly many years ago; i.e. the last time I looked at it). So… If someone can verify that it works under Windows Server 2016, but not under Windows Server 2019, 2022, and/or 2025, then I’ll go ahead and take another look at it. Otherwise, if it’s not working in 2016, then there’s no point in even looking at it under 2019, 2022, and/or 2025.
- Mike answered 3 weeks ago
- You must log in to post comments.
