w
Size: a a a
2021 May 26
TF
это прям опыт я свой вам вещаю, а бекапить контроллеры тоже не бекапят разве что через system center
TF
потом все снапшоты - до пизды, если в контроллерах будет старая инфа по политикам и юзерам - ваш бекап полный треш и тупо занятоеместо на бекапсервере
TF
только наверно system center с этим разруливает или может ещекакой-то дорогой софт
w
Hi All,
Just to give an update about this WIndows Server DataCenter licensing to a VM on Proxmox host. I had to ring Microsoft Licensing Support as well for a case to be created and was passed to one of their technical support engineers.
They sent me the instructions below and have provided a KMS Datacenter setup key (AAAAA-BBBBB-CCCCC-DDDDD-EEEE - not the exact key/s)
As you are using a MAK key, the steps below for your reference:
1. Please backup important data before making changes
2. Here let’s proceed with the help of Windows Server 2019 KMS Datacenter client setup key,
3. Please run Powershell as admin, run the command below:
dism /online /set-edition:ServerDatacenter /productkey:AAAAA-BBBBB-CCCCC-DDDDD-EEEEE /AcceptEula
4. After the command completed, please run the commands below to install your product key
Slmgr /upk
Slmgr /ipk <Your MAK Product key>
Slmgr /ato
With this; we were able to activate Windows Server 2019 DataCenter on one of the VM's on a Proxmox host.
I just quite confused as Windows Server 2019 DataCenter license suppose to be able to activate unlimited VM's per host. I imagine that the license should be activated on the host rather to the individual VM. There are a number of online references about licensing the host but mostly on a Hyper-V which is a microsoft product all together (may this is why it's possible for them to integrate). Can find much either if you need to activate the DC license to a VMware host and not on a VM...so quite lost on that part.
Just to give an update about this WIndows Server DataCenter licensing to a VM on Proxmox host. I had to ring Microsoft Licensing Support as well for a case to be created and was passed to one of their technical support engineers.
They sent me the instructions below and have provided a KMS Datacenter setup key (AAAAA-BBBBB-CCCCC-DDDDD-EEEE - not the exact key/s)
As you are using a MAK key, the steps below for your reference:
1. Please backup important data before making changes
2. Here let’s proceed with the help of Windows Server 2019 KMS Datacenter client setup key,
3. Please run Powershell as admin, run the command below:
dism /online /set-edition:ServerDatacenter /productkey:AAAAA-BBBBB-CCCCC-DDDDD-EEEEE /AcceptEula
4. After the command completed, please run the commands below to install your product key
Slmgr /upk
Slmgr /ipk <Your MAK Product key>
Slmgr /ato
With this; we were able to activate Windows Server 2019 DataCenter on one of the VM's on a Proxmox host.
I just quite confused as Windows Server 2019 DataCenter license suppose to be able to activate unlimited VM's per host. I imagine that the license should be activated on the host rather to the individual VM. There are a number of online references about licensing the host but mostly on a Hyper-V which is a microsoft product all together (may this is why it's possible for them to integrate). Can find much either if you need to activate the DC license to a VMware host and not on a VM...so quite lost on that part.
w
надо бы в МС позвонить )
TF
уж лучше не звонить, а сбрасывать лицуху на сервере на триал
w
ну, ТС-у надо чтобы все было в белую
TF
шара с доками на ад сервере - это просто топ...
TF
по вам безопасники плачут ;)
Н
Ну так то да, но даже если нода была бы только одна, лучше её держать на втором сервере. Ведь если упадёт гипервизор, то упадёт всё
Н
Ну какбы так сейчас и сделано. Но я хотя бы бекапы точно защищу
Н
Могу сделать её read-only из SMB
w
truenas\xigmanas\omv так тоже умееют )
w
еще и zfs-снепшоты по крону
w
хоть кажные 10 сек )
Н
Что именно умеют, не совсем понял?
w
рид-онли шару делать
w
и не только это