I love it, it is fantastic, and makes it so much easier to set up a windows server! I suspect MS is pushing us to the cloud more and wanting us to be/become more skilled IT folks, AND drive us to a more expensive version. None of that makes sense for a SB like me/mine. I'm going to hold my breath and give the script a shot on my company's new server. I've installed and checked this script about 5 times on Virtual Box machines. As long as you manually set AD Domain, it still works great. Stay tuned!
Sounds good to me, but always keeping in mind, that even a "simple update" can screw everything up (even without this script), because of...reasons. And now matter how experienced you are, the Dashboard was a great invention !!! =)
I just learned that WSEE will not allow you to install a TLD (.com, .net, etc.), it only allows .local domains. You can by-pass this by manually setting up an AD Domain Service role, when you first start WS 2019 or WS2022. Then you can start WSEE and it will pick up right after the domain setup part, it detects that an AD Domain has already been installed.
I've tested and retested it on WS 2022 Standard. It still works great! I'm very happy we can still use it!
server 2016 essential french full up to date march 2023 , capture with powershell create install.wim install this on server 2022 french up to date already works coming soon refresh package english with 2023 update replace old 2021 english package
Does it have any connection with these packages? Microsoft-Windows-ServerEssentials-ServerRole-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-ServerEssentials-ServerSetup-Package~31bf3856ad364e35~amd64~~10.0.14393.0 and Microsoft-Windows-ServerEssentials-ServerSetup-Package~31bf3856ad364e35~amd64~~10.0.17763.1
After testing, there is no more recent version of the server essential package ( installation of server essential 2016 up to date to 2023 ) basically the english version does not change , and the pre-installation in sysprep mode does not work the only method , installation of standard server or datacenter, assigning ip fix minimum then reboot and then install the essential package however the addition of the tls managed by the os and not the application allows a better compatibility Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727] "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727] "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions" = dword:00000001 "SchUseStrongCrypto" = dword:00000001
I did the same thing, will test when I buy a new SSD. I do not want to mess with my current 2016 installed SSD, just in case...
This AM I wanted to test out the WSEE setup on Server 2022 & installed on a 500GB external SSD, on luck so far as MS Server install as it doesn't want to install on a USB drive when running the startup.exe from inside the SSD partition. I used a older version of Rufus for the file transfer. It appears that Hasleo has a Enterprise version that will install it (they claim), sadly I don't want or need 100 copies of their app. (for $220.00 USD). Does anyone here have any suggestions I can try? -- I did snag copies of: "WinToUSB Enterprise 5.1" Free Download & "AOMEI Windows to Go" that may work Tied-up today so will try again Wednesday.
Well Guys, I tried 6-7 times & failed w/ getting the "Windows Server Essentials” Role working using the WSEE-setup.ps1 application. My last attempt was w/ the Server 2022 Datacenter w/ Desktop Experience, it failed too. This one I let sit for 30 minutes after running the above app. The other 5-6 attempts I would restart the PC soon after running the app. Attached is WinToUSB setting up the external SSD w/ the Server 2022 Datacenter. & the text file from the WSEE-setup.ps1 app.
Not sure but it could be because your installing in legacy mode. I've always installed on a UEFI partitian.