Does anyone have a solution for this problem? I'm trying to connect from 20348.51 to Windows Server 2008 R2 using Remote Desktop. Connecting from Windows Server 17763 is no problem!
OK, svf extractor was too old, it seems. Had to use SV 3.82, because svfx.exe 2.1.15.4341 would not start on this machine (server 2012 R2)
10 would be the best guess since its a long term branch, and they've released a preview iso that is. Shoving the new UI on top now would be madness as far as testing goes...
The same way since XP and Server 2003 Depends on what use case That's why anyone can use same LCU on certain server and client version XP = Home, Professional, POSReady 2009, etc. 2003 = Server Standard, Server Datacenter, XP X64, etc. Remember how to extend XP up to 2019 update? So on development of Windows 10 there are 2 branch servicing as SAC and LTSC SAC = Home, Pro, Pro for Education, Enterprise, Server Core, IoT Enterprise, etc. LTSC = Enterprise S (LTSB later LTSC), Server Standard, Server Datacenter, IoT Enterprise, etc. Then upgrade was easier with enablement package (EKB). Jumping from 2004 to 21H2.
xcept it isn't really true teh "family tree" of windos is a lot more complcated than most ppl think esp in the early days 4 example xp & svr2003 r more cousins than parent->child cos their development diverged bout build 2250 2500 (xp was build 2600 & svr2003 was build 3790 - & remember win2k was 2195) so when u think about it u will realise vista (& therefor 7) is hardly related 2 xp at all cos vista was built from svr2003 but since vista pretty much all been built ontop of the last version yeah