i'm on 2016 now, thought 2019 was the only option as it offered an 'Essentials' version, but i see that WSEE can be installed on 2019, 2022 & 2025 the 'essentials' version allowed enough users w/o requiring CAL licenses - is 2022 the same?
not sure WSEE is totally working on 2019 new 2019 install - WSEE installed, dashboard opens properly use ProfWiz to migrate laptop computer & user acct to 2019 (so i keep everything that is in the user profile) all good, except i don't see the added computer in WSEE dashboard, it is under domain users & computers?? on 2016 ProfWiz added same laptop to WSEE dashboard
are you helping me or just pointing out the extra 's'?? strange... on 2016 i see all my computers in 'active directory users & computers' and WSEE there are 2 entries as i was playing with 2019 installs that don't show up in WSEE any ideas why my laptop doesn't show in WSEE??
Hi I am using Server 2022 standard and then install WSEE from this gentleman who has perfected the install. h**s://w**theofficemaven.com/news/installing-windows-server-essentials-experience-on-windows-server-2019 It can be installed on 2019,2022 and 2025 seamlessly you just need to buy a licence to one of his other products and the WSEE is then free including all updates
Good point with pm67310 and I stick with Server 2022 while I am testing Server 2025 on LGA 2011 to be sure nothing wrong or buggy.. So, I would wait slightly longer more bug free on Server 2025... Note: Windows Server 2022 EOL is Oct 14th, 2031 SO, give another year or longer to get ready for Server 2025! ATGPUD2003
Today I installed Windows 11 24h2 Pro on various 2012 lenovo AIO PCs, (bypassing UEFI, TPM etc.) Eager to try using the old "essentials connector software" to join the domain of a Server Essentials 2016 and register various users for every PC. I was happy to see that the "connector tool" did not crash once and did not hand out cryptic error messages, like it did with 22h1 back in the days. Would there be "essentials connector software" update history available or would this still be the very same version that required manual powershell fixing back then?