getting the error message
Windows Server 2008 R2 Standard cannot be upgraded to Windows Server 2012 R2 Standard
when attempting an in-place upgrade with no reason given.
getting the error message
Windows Server 2008 R2 Standard cannot be upgraded to Windows Server 2012 R2 Standard
when attempting an in-place upgrade with no reason given.
One reason could be evaluation media which is not possible to do, licensed media must be used.
--please don't forget to Accept as answer if the reply is helpful--
it does not involve eavaluation media. just want to know why and pls do not post gueses
Too funny. You can review the logs here.
https://docs.microsoft.com/en-us/troubleshoot/windows-client/deployment/windows-setup-log-file-locations
--please don't forget to Accept as answer if the reply is helpful--
only log is the setupact.log whose contents provide no clue other than below going to try and find some compatibility test
22021-04-18 13:45:30, Warning [0x0a0180] UI Failed to change the UI language to en-US.
2021-04-18 13:45:30, Info [0x0a011c] UI WizardDialogPost::SetActive
2021-04-18 13:45:33, Info [0x0a018e] UI Passing command line parameter ("E:\Sources\setup.exe /HideWelcome /uilanguage:en-US /targetlanguage:en-US") to IBS.
There could be any number of reasons. First I'd check the 2008 is patched fully and that health is 100%
I'd verify system and servicing health by running;
sfc /scannow
also system update readiness tool
Then check for errors in;
%SYSTEMROOT%\Logs\CBS\CheckSUR.log
check here and with manufacturer about support for Server 2012 R2
https://www.windowsservercatalog.com/
check the server manufacturer's site for the latest firmware, ROM bios, chipset and driver support pack
uninstall conflicting applications, roles or features
but the safer / cleaner method is to stand up a new one, patch fully, migrate the roles over to new instance.
--please don't forget to Accept as answer if the reply is helpful--
your answer uninstall conflicting applications, roles or features
is mealingless unless the conflicting application roles or features are known
unless the conflicting application roles or features are known
and they're still unknown to us. Other options were mentioned. I'd suggest contacting the application developer or starting a case here with product support.
https://support.serviceshub.microsoft.com/supportforbusiness
--please don't forget to Accept as answer if the reply is helpful--
this is the only dc in this domain so we will probably just export all printer settings , all share settings and install 2012 r2 as a workgroup server and import the printer settings, share settings and not have ad installed ad isnt worth the toruble when its a small network 5 users
The simplest solution for a domain controller is stand up a temp one for the migration (even desktop hardware will do)
I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2012, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
Also at some point after I'd recommend migrating sysvol replication from older FRS technology to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405
--please don't forget to Accept as answer if the reply is helpful--
the app people dont care if it;s workgroup or domain so we will probablly just go with workgroup for now
thx 4 ur hlp
Sounds good, you're welcome.
--please don't forget to Accept as answer if the reply is helpful--
6 people are following this question.