When you are going to install an ISO Server 2019 or 2022 there will be 4 options: Standard Core Standard DataCenter Core DataCenter Avoid the Core Editions. That simple. Avoid 2022 Azure Stack HCI ISO
But both are Win10 based. Which are cleaner than Win10, the user asked for a cleaner Win11 version So I suggested Server 11.
Yes, he asked. But I prefer to stick to the non-Insider recommendation. It has already been demonstrated to use only non-Insider versions. So he can choose W10 Feature 20348, W11 22478 or 25290.
Insider servers are not more dangerous than monthly updates, on released flavours. They are servers. Not toys like home versions Adkins need to test them in production. The last major problem in windows (profile data loss) was in 1809. A released windows not a preview. If you have some examples of major troubles with previews I'm all ears. It's always better to stick to facts rather than debatable opinions.
I would use a Server Insider on my machine, but I would only use an Officially Released one at my company. I would never pay to see possible data loss with an Insider. Because it would not have any legal support, due to the fact of having used an Insider Distribution in production.
There may be some errors in the toolkit.cmd script, line 62. I'm a total retard when it comes to batch coding, but I think I've figured it out. Current line: Code: for /f "tokens=4-5 delims=[]. " %%s in ('ver 2^>nul') do (set "HostVersion=%%s.%%t" & set "HostOSName=Windows %%s %HostEdition% %HostInstallationType%" & if "%HostBuild%" equ "7601" set "HostOSName=!HostOSName:6=7! SP1" & if "%HostBuild%" equ "9600" set "HostOSName=!HostOSName:6=8!.1" & if "%HostBuild%" geq "21996" set "HostOSName=!HostOSName:10=11!") - Due to missing (), the commands after the windows 7 detection (7601) ar not executed. If you chain with "&", use subsequent commands between () (like this). - If you put HostBuild variable between "" it becomes a string. This is OK for windows 7 SP1 (7601) and windows 8.1 (9600) because you are doing a literal comparison (equ) of both values, but for windows 11 (geq) it is different, because you want to do a numerical comparison, not a string. I tested this modified line and found it to be working as intended: Code: for /f "tokens=4-5 delims=[]. " %%s in ('ver 2^>nul') do (set "HostVersion=%%s.%%t" & set "HostOSName=Windows %%s %HostEdition% %HostInstallationType%" & if "%HostBuild%" equ "7601" set "HostOSName=!HostOSName:6=7! SP1") & (if "%HostBuild%" equ "9600" set "HostOSName=!HostOSName:6=8!.1") & (if %HostBuild% geq 21996 set "HostOSName=!HostOSName:10=11!") Cheers.
Nice. I had fixed this and forgot to report. Sometimes using commands outside of double quotes also causes problems. I would have to convert to numbers using set /A, yet sometimes there are breaks in the script. But even in string mode, when the number of numbers is the same, the batch can compare whether it is smaller or larger. I'll check your correction and merge if there's anything extra to add here. Basically what me and @Bira had done was identify if HostBuild neq 7601, neq 9200, neq 9600 and geq 22000 will make that switch from 10 to 11. @Bira had informed me about this problem on W7 and W 8.1. There is a problem in identifying the HostLanguage as well, but I think this is only on IMCK.
Me too, but that to cover my back not because I fear problems. No one would ever pay for an unreleased SW, on the contrary that's a way to run for free a SW that normally would cost thousands of $ w/o pirating anything. I think you should spend some time reading some EULAs of commercial SW, starting from Windows.
"I would never pay to see." This is a term used in Brazil. Maybe it wasn't well inserted in my speech. It would be something like "try your luck and if there is no loss it will be great." But it remains a gamble. The well-known fifty/fifty. Maybe I have to read EULA for other countries and check if there is any difference in the fine print and for other countries I have to learn their laws. But here in Brazil it's like I said. To have some Legal Support, you cannot be incongruous and irresponsible to want to put something in production in tests. Unless it's previously approved by MS if you're risking losing something for the sake of testing. And, you'll excuse me... But if MS didn't release it, it's because it's not well tuned for production use.
Just to be clear, what I mean is not that you can't loose your data with a unreleased SW, It's that you can lose your data using a released SW as well. Released means basically nothing, technically. And also means almost nothing legally. Few years ago a my client had a 100% data loss because a SW bug in a couple of Intel NAS (which used a proprietary FS) one was the main storage, the other was the backup unit and both failed at the same time. Well basically they said sorry, we can't recover your data. That's all That was the same client that refused my solution based on a well proven open source Linux RAID, because the "lack of official support". In short, safety is matter of having sane backup practices, differentiation on HW and SW, and knowledge. Not relying on meaningless definition like "Prerelease" or "release".
Yes, I understood you in that respect from the beginning. I was focused on legal support. Legally, you have to be astute to deal with them. Otherwise, it is considered resolved only through an apology. Didn't they even get compensation for the losses? Proving that there was some hidden flaw (design flaw) in the hardware? What is the probability of simultaneous Hardware failure? This was probably the fault of the NAS storage itself, my assumption is that it wasn't even a HDD problem.
This is the complete solution I already had ready with a little optimization to make it easier to read and with your option (no double quotes) is in the commented line. HostLanguage line from previous versions is commented out. And the new line added below the commented line. Code: for /F "tokens=6 delims=[]. " %%i in ('ver 2^>nul') do (set /A HostBuild=%%i) for /F "tokens=4-5 delims=[]. " %%s in ('ver 2^>nul') do (set "HostVersion=%%s.%%t" & set "HostOSVersion=%%s") if "%HostVersion%" equ "6.1" set "HostOSVersion=7 SP1" if "%HostVersion%" equ "6.2" set "HostOSVersion=8" if "%HostVersion%" equ "6.3" set "HostOSVersion=8.1" rem if %HostBuild% geq 21996 set "HostOSVersion=11" if "%HostBuild%" neq "7601" if "%HostBuild%" neq "9200" if "%HostBuild%" neq "9600" if "%HostBuild%" geq "21996" set "HostOSVersion=11" for /F "tokens=3 delims= " %%l in ('reg.exe query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "EditionID" ^| find.exe /I "REG_SZ"') do (set "HostEdition=%%l") for /F "tokens=3 delims= " %%j in ('reg.exe query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "BuildBranch" ^| find.exe /I "REG_SZ"') do (set "HostBuildBranch=%%j") for /F "tokens=3 delims= " %%j in ('reg.exe query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "ReleaseId" ^| find.exe /I "REG_SZ"') do (set /A HostReleaseVersion=%%j & if "%%j" leq "2004" set /A HostDisplayVersion=%%j) if "%HostDisplayVersion%" equ "" for /F "tokens=3 delims= " %%k in ('reg.exe query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "DisplayVersion" ^| find.exe /I "REG_SZ"') do (set "HostDisplayVersion=(%HostReleaseVersion% %%k)") for /F "tokens=7 delims=[]. " %%r in ('ver 2^>nul') do (set HostServicePackBuild=%%r) for /F "tokens=3 delims= " %%m in ('reg.exe query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "InstallationType" ^| find.exe /I "REG_SZ"') do (set "HostInstallationType=%%m") set /A HostProcessorThreadsCount=0 for /F "tokens=* delims= " %%p in ('reg.exe query "HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor" /s /v "ProcessorNameString" 2^>nul ^| findstr.exe /I "REG_SZ"') do (set /A HostProcessorThreadsCount+=1) set "HostOSName=Windows %HostOSVersion% %HostEdition% %HostInstallationType%" for /F "tokens=* delims=MicrosoftWindows " %%f in ('ver 2^>nul') do (set "FullHostVersion=%%f") rem for /F "tokens=3 delims= " %%o in ('reg.exe query "HKLM\SYSTEM\CurrentControlSet\Control\CommonGlobUserSettings\Control Panel\International" /v "LocaleName" ^| find.exe /I "REG_SZ"') do (set "HostLanguage=%%o") for /F "tokens=3 delims= " %%o in ('reg.exe query "HKU\.DEFAULT\Control Panel\International" /v "LocaleName" ^| find.exe /I "REG_SZ"') do (set "HostLanguage=%%o") For Windows 11 @MSMG can choose one of these options: Both below lines are in above code. Code: if %HostBuild% geq 21996 set "HostOSVersion=11" or Code: if "%HostBuild%" neq "7601" if "%HostBuild%" neq "9200" if "%HostBuild%" neq "9600" if "%HostBuild%" geq "21996" set "HostOSVersion=11"
Bad luck is surely a thing everywhere, but in that case, the bad luck was vastly helped by the poor decision of thinking that the Intel name warranted something, and also by the poor choice of taking a backup on the very same thing. My suggestion was to keep the backup on a Windows Server (as they did previously) add a new Linux based NAS and keep that situation running for six months or so. I even left the old server up and running W/O the client consent, just because I didn't feel confident on the new infrastructure, but the client disconnected it after a week or so. So bad luck yes, but...
Too many bad experiences with in-place. Besides, I've spent a lot of time over the last 4 years perfecting my script to refresh everything. Gives me a nice, clean starting point each year. Takes a total of 2-3 hours to completely refresh a PC. Client settings and configurations are backed up before the upgrade and restored by my script. The users pick up where they left off, but with a new OS and the latest versions of everything they use. The way I do it is I have a spare PC and I test the OS and all applications and games on it thoroughly before I upgrade the clients PC. An in-place will upgrade the OS but not the programs and games. I'd still have to do that manually, and still have to go through the same testing process if I want to be sure there are not going to be any problems. Oft times I've had issues upgrading programs over the top of old ones. Uninstalls also rarely uninstall properly leaving garbage all over the place. I feel that the way I do it is clean, predictable and takes no longer than the in-place process. I guess my corporate IT background influences the way I do things.