MRP Log & 20334 ServerDatacenter 2022 LTSC desktop: https://forums.mydigitallife.net/th...l-project-mrp-mk3.71555/page-357#post-1654960
Does anybody know what those frequent releases bring new which each almost weekly release? I cannot find anything relevant from my limited testing, but the reliability is good enough even for a full release. Otherwise, they are the same thing with Windows Server 2019 for what matters to me.
MRP Log & 20339.2 Server Desktop: https://forums.mydigitallife.net/th...l-project-mrp-mk3.71555/page-358#post-1655973
got sum hashes 4 those who r intrested: Code: Windows_InsiderPreview_Server_vNext_en-us_20339.iso: SHA-1: 443a5568c9b897b2c9eb92b33cbd1255d324c311 SHA-256: 61139abe2b999680769316f548f9ae73bc4345a96bea707f0bda7f00da522bfb SHA-256 Base64: YROaviuZloB2kxb1SPmuc7xDRalr6nB/C9p/ANpSK/s= SHA-384: 2b062ebdad40a0a31d3d3ad3e8bfad38334c829e0aa60af8d307de2aa29670c2c50d6702160b3b6e90cffc75c637030e SHA-512: 6b94ab935ea40f0febe18ec79f3c886259f53614dbc46f58169c140d5f165429b27e7bdad8cab11eeb81f714e65bd479502208a41b1f06f653a6d32abff4b4bc Adler32: b87f07eb BLAKE2sp: 7cb1b583d826379ac50097f82bace4d64733f820b66c5411c10bd902e7313af5 BTIH: cbdbbfe7580391ba4005bfbea5665412153b48c6 CRC32: 2cec3c30 CRC64: b2d580a4ad49891d ED2K: fe22cde5cd919f2ed24b287254ef5142 GOST: 8b02040576cb75a81b75961183873dc0ea31580506857ed571f0987a2a84756a Keccak-224: 4c16b1dc0d88ff6b91bba498360c4ed10c4134616ee71caa68d5bdbb Keccak-256: 451c9bf32e4a2e23064a24ee93934661634f6ac085ebfee5fe0c9cc1a214b230 Keccak-384: 0ee842f4f508395ddd60ec16c99d4dc5556d144ef7ad4f646a37349442d771eac83154ca347a65d14469c780634a2dbe Keccak-512: 4d3d4b4187c2dd1dbc797173c3a177f68e01bca6b6b98f68f430241977c2719a0ca81c33dc518183318ed5e84c6abfe4667a4256ca4c88fa98c21eb25f0d9334 MD2: 2dd61971c2d95c7dfa73c4cb82f60e56 MD4: 47caa7fbec25bd5900c01e0d8c4f8bc7 MD5: d70015786619b0a124138ba457b095ea RIPEMD-128: a4565dac74b59978211a4033c6a3e8d6 RIPEMD-160: ddb80d6d573803c706c1145812fd01ac377430a6 RIPEMD-256: 138eaea6c1c0170e5145644f1611d832ab224d74b878ec84a247411bfe670f34 RIPEMD-320: 1dd39cc41ebf941f6ce7c6ecb4d2783483ae31acbb24a16cb8135bfab31afbb6bdb983ce6d86ed27 SHA3-224: 2b4aa56c358e3e658b7a7121c711b818f546f8b7f3de58b74225416f SHA3-256: d8e5a29458df690858b75a99995c7c1e730de38dfb5d4e3b739b5db5a597fd8e SHA3-384: 32d64185ba8873919cb0f2992d55dd4902bb7a9b0497cf0ce4dd15ecf9e7542b0a2d41bf8ae1532874153999872cb519 SHA3-512: 2dbf40373b58a8197453949d8673ab480af23092112efacdbf8ab9fe1e7461b76da746dff4e7b53d5d2a0316cae52d9247529f6a9e92e5bf3ded87e19f0b05ed TTH: ap5sj6x6gx6j57aex34575rd3zqrekvv43axwii Tiger: 3b5b267415f2d1973245d621fc2d846faa4c851b50bada1d Whirlpool: 44ea9d70750a30756abd00ea2459a735de10d948559c3925b9d195ecd68a44c78e1c4be49d2b8be7bb33677274b5894d0ac6d3efcda0d34343b078285a3d1159 Windows_Server_InsiderPreview_LangPack_FOD_20339.iso: SHA-1: e18c3b2616cbfa0503c0e58e16a2cb0ea8433f55 SHA-256: acbc5a69f705ac7f5b1734c993f8242621ec9ceacffbc1e2797f7238c9807bb5 SHA-256 Base64: rLxaafcFrH9bFzTJk/gkJiHsnOrP+8HieX9yOMmAe7U= SHA-384: 06ed7de2f67ed2656b7d9cbce579311e18f63996f98376767beb867454cb7bdbcd3c673db409bc8e7f70632db5b3b5d7 SHA-512: 98e2b75f2c6637162cc263d488a8bdc77fd9d80e0e9d6b3f3e2c1f5d753f7abc3a52fd232d2d3e16e8e3f95f19a3a7574a0a021f1f640fd10205c507c1c21226 Adler32: 5d0b21c5 BLAKE2sp: b114b1641a45a0945cb5fcce8c19dae665a27e7b9149be87c42ff1fe1f17db58 BTIH: 2d3d29cbcf380e10e6b71cbc6e6022d636626eba CRC32: a9540cac CRC64: cc6e9edb2ba22d4c ED2K: e2fd2115a8df6a610f02ca6fea5d2676 GOST: 6319c85eb5f5de297b7eeac0a47a757898fa567491012b5b322dd8aad93a694a Keccak-224: 431a1bb5e11a9700232cbf2f8b0770775c007123629d71cbddc2f866 Keccak-256: 28283b09d9c5926c80d4d06b8787096a3714e47df6ce22ed17d6497402ebf605 Keccak-384: fe22baefca747add109a23d39d68ac87b5556dc932ee34a49a12ccec1b09ac9712ce8f36276cfd79f463abd1ef2e29ac Keccak-512: d1d8f90bd3765374a08129e3d02f6c513203b12defe4667dc025b16112a440f83ad09da987b3ec2ab7781620ba14cf0b9b348a8fcd401e56a319dd5068c68940 MD2: 8680d8d66327eb5f207cb7061fe76f22 MD4: ae598520665380c6f6ac611988de87d3 MD5: e26f81c1dae3f0b4f380a3aea5802ef1 RIPEMD-128: cde43ec99496426bdfc15c0cb4bef6e7 RIPEMD-160: 28c07599d08866a1bb635dbf8e7ff878a527eef0 RIPEMD-256: 61462af6142882f5c07e0a7b655f1da68ed7a825be0ce2206c59af58f662f8fa RIPEMD-320: 27d196e5e8ce43acb69dc1a7404d0247e704ad4afcb601501c53ba537a4e1ebf50ab97e8bd4cd425 SHA3-224: 983c2f34b4b20ee270c9d8ca6addc9de17685986dda3ab18afa05630 SHA3-256: bd03e0aab763aa7f660d950393cd73a2a3469487f1af9b5bc3057ec95961eff1 SHA3-384: 7e0f203f96205e4942c9d7e8e1cc5fd0ffaf3763764267d680db6594a117dae599ceb8674f55b54efabda61d9f815e85 SHA3-512: 496482f0be77f1e1d867d2cec2379c8bed6704f44c757233a4e12295911b51048c3f8757bae2b4b34cec6c3e03114450c4903343d3fc3135f9d55ddd399635c4 TTH: r6rzejdx7fe7jsslf7ffqsn4m5zdhn267kybymq Tiger: 06b622f88aabe4244748291cdba41d2d6fb7fbdab9344e6c Whirlpool: d4eeba4368e2a013a9f10e91696daefe9806cfa541d38e2dcdafe1801cd1ee1c227ee7c98fa6d0f53caac909e4e737b3a1f88e9242931b61d4fd4fca02f6eadd
@RobrPatty &/or @mrbbq how habe u fellas been doin ur upgrades ? background: im thinging bout deployin ws2022 on my (& gfs) home svrs (seems stable enuff during my testsin vms wanna take the next step) but we use native boot vhds & there r blocks on inplace upgrades on native boot lats I checekd have ether of u tried upgrading a vhd or r u fellas upgrading "flat" installs ? dont wanna have 2 clean reinstall 4 each new ver
You might find that when the release time comes, you will not be able to upgrade in place the insider preview to release. This is still unknown but something to consider. Otherwise all current upgrades in place are fine. What is your actual setup? Windows Server in a Hyper-V virtual machine or the Microsoft released server on vhd?
that I can cope with atm my svr is runnin 20339 baremetal & "flat" (edit: plugged in a lapto hdd last nite & installed it alredy found my 1st bug it bsods when I htswap a hdd) gf is running svr 2019 barematal but ina native boot vhdx
Is there any specific purpose for this configuration? It is not typical and while there are few instances when this is useful, e.g. defragging a Citrix Virtual Desktop Image, in general it is done only for the sake of it, just because it can be done. I don't think a lot of people use this configuration and as such support is likely to be relatively limited. I don't have an answer if this can be upgraded in place as per your previous post.
ease of bakup & makes it easy 2 move windos around just mov the vhdx gf collects drvs so we change her boot device alot k thx neway ill just try it out myself & c what happes
It is all good, but the same can be achieved with the same vhdx running as a virtual disk in a virtual machine with all the flexibility required. Maybe I don't understand enough the concept, so let's leave this discussion for another time. Anyway, please let us know here if you or your girlfriend will be able to upgrade in place in the vhdx boot configuration as I am quite interested.