RVM Wiki - User contributions [en]

Ricostruzione indici di Database Adiuto

2026-07-14T15:51:56Z

Gabriele.vivinetto: Created page with "Per migliorare le prestazioni è utile eseguire nottetempo queste query:<pre> EXEC sp_updatestats </pre><pre> SET NOCOUNT ON; DECLARE @db_id int; DECLARE @objectid int; DECLARE @indexid int; DECLARE @partitioncount bigint; DECLARE @schemaname nvarchar(130); DECLARE @objectname nvarchar(130); DECLARE @indexname nvarchar(130); DECLARE @partitionnum bigint; DECLARE @partitions bigint; DECLARE @frag float; DECLARE @command nvarchar(4000); SET @db_id = DB_ID(); -- Condi..."

Per migliorare le prestazioni è utile eseguire nottetempo queste query:<pre>
EXEC sp_updatestats
</pre><pre>
SET NOCOUNT ON;
DECLARE @db_id int;
DECLARE @objectid int;
DECLARE @indexid int;
DECLARE @partitioncount bigint;
DECLARE @schemaname nvarchar(130);
DECLARE @objectname nvarchar(130);
DECLARE @indexname nvarchar(130);
DECLARE @partitionnum bigint;
DECLARE @partitions bigint;
DECLARE @frag float;
DECLARE @command nvarchar(4000);

SET @db_id = DB_ID();
-- Conditionally select tables and indexes from the sys.dm_db_index_physical_stats function
-- and convert object and index IDs to names.
SELECT
object_id AS objectid,
index_id AS indexid,
partition_number AS partitionnum,
avg_fragmentation_in_percent AS frag
INTO #work_to_do
FROM sys.dm_db_index_physical_stats (@db_id, NULL, NULL , NULL, 'LIMITED')
WHERE avg_fragmentation_in_percent > 10.0 AND index_id > 0;

-- Declare the cursor for the list of partitions to be processed.
DECLARE partitions CURSOR FOR SELECT * FROM #work_to_do;

-- Open the cursor.
OPEN partitions;

-- Loop through the partitions.
WHILE (1=1)
BEGIN;
FETCH NEXT
FROM partitions
INTO @objectid, @indexid, @partitionnum, @frag;
IF @@FETCH_STATUS < 0 BREAK;
SELECT @objectname = QUOTENAME(o.name), @schemaname = QUOTENAME(s.name)
FROM sys.objects AS o
JOIN sys.schemas as s ON s.schema_id = o.schema_id
WHERE o.object_id = @objectid;
SELECT @indexname = QUOTENAME(name)
FROM sys.indexes
WHERE object_id = @objectid AND index_id = @indexid;
SELECT @partitioncount = count (*)
FROM sys.partitions
WHERE object_id = @objectid AND index_id = @indexid;

-- 30 is an arbitrary decision point at which to switch between reorganizing and rebuilding.
IF @frag < 30.0
SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REORGANIZE';
IF @frag >= 30.0
SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REBUILD';
IF @partitioncount > 1
SET @command = @command + N' PARTITION=' + CAST(@partitionnum AS nvarchar(10));
EXEC (@command);
PRINT N'Executed: ' + @command+ N' ' + cast(@frag as nvarchar(25)) ;
END;

-- Close and deallocate the cursor.
CLOSE partitions;
DEALLOCATE partitions;

-- Drop the temporary table.
DROP TABLE #work_to_do;
GO

</pre>

Adiuto

2026-07-14T15:50:31Z

Gabriele.vivinetto:

*[[Query utili in Adiuto]]
*[[Impostare un Reverse Proxy Apache per Adiuto per accedere via http su porta 80]]
*[[Creare una vista in Adiuto con i campi di una famiglia ridenominati con le Label]]
*[[Le fasature di import falliscono con un errore di Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.]]
*[[Adiuto non parte e dà errore di License Incompatible]]
*[[Eliminare i collegati duplicati in Adiuto]]
*[[Identificare la famiglia in uno script Adiuto]]
*[[Aggiornare la visibilità di record in Adiuto dopo un cambio nei campi]]
*[[Il servizio AdiFeed rimane bloccato in Starting]]
*[[Aggiornamento Adiuto 6.7.2]]
*[[Adiuto va in crash con errore OutOfMemoryError: GC overhead limit exceeded]]
*[[Caricare delel fatture XML su portale IFIN]]
*[[Impossibile visualizzare il file di un documento in Adiuto]]
*[[Il database di Adiuto su SQL Server Express raggiunge il limite di 10GB]]
*[[I link di reset password in Adiuto non contengono l'URL corretto se dietro un reverse proxy]]
*[[Terminare workflow Massivamente in Adiuto]]
*[[Eliminazione di un utente Adiuto]]
*[[Adiuto indica come Scartate perchè duplicate delle fatture effettivamente consegnate]]
*[[Ricostruzione indici di Database Adiuto]]

Adiuto indica come Scartate perchè duplicate delle fatture effettivamente consegnate

2026-07-14T15:49:26Z

Gabriele.vivinetto:

Può succedere che ci si trovi con degli scarti in Adiuto, ma su ADE e Invoice Channel la fattura sia consegnata.

Succede perchè si invia la fattura più volte (non si capisce se siamo noi a farlo o è ifin e si riceve subito la NS. Una volta acquisita la ricevuta di SCARTO, anche quando arriva quella di consegna, non viene allegata e rimane nel Transito di Immission

Per importarla occorre verificare i filename delle ricevute RC di consegna incagliate, da cui si recupera l'ID_SDI

In [https://fatturapa.ifin.it/ Invoice channel di IFIN] si fa la ricerca per range temporale ed ID SDI e si deduce il numero della Fattura.

In Adiuto si cerca la fattura (che sarà falsamente scartata) e si deduce il FIDD.

Poi si fa un update di F31 di quel FIDD inserendo l'UID IFIN che è la prima parte del filename della ricevuta:.

Fatto questo, si rilancia la fasatura immission di importazione Ricevute e la ricevuta verrà caricata, collegata e la fattura sarà CONSEGNATA

Alla fine bisogna poi modificare anche il FLAF per far bloccare il documento e far apparire la coccarda.

Ad esempio se il filename della ricevuta da importare fosse:<pre>4D0BDE37-4FC0-4973-935C-86E77BE3D5C1_17756685916_IT01071920282_to55h_RC_001.xml</pre>Su Invoice channel, ricerchiamo l'ID SDI<pre>
17756685916
</pre>Troviamo che il numero fattura è, ad esempio <pre>
9833
</pre>In adiuto cerchiamo la fattura e troviamo che il suo FIDD (CTRL-SHIFT-F2) è<pre>1968619</pre>Lanciamo quindi la query:<pre>
UPDATE
A1001
SET F31 = '4D0BDE37-4FC0-4973-935C-86E77BE3D5C1'
WHERE
FIDD = '1968619'
</pre>E importiamo al ricevuta.

Poi recuperiamo nuovamente il fidd della fattura (perchè cambia) che ipotiziaaimo diventi<pre>
1968630
</pre>e facciamo:<pre>
UPDATE
TDOC
SET
FLAF = 1
WHERE
FIDD = 1968630
</pre>Il dettaglio del [https://helpdesk.bluenext.it/it/support/tickets/1053072 ticket] è<pre>Prendo ad esempio la prima ricevuta del log
D:\Adiuto\Transito\RicevuteSDI\201F2760-ADC4-438F-A0C9-99DEAF2D8449_17700396210_IT01071920282_th5fj_RC_003.xml

1. individua la fattura corrispondente, poi modifica il valore del campo F31 (quello che trovi è quello della ricevuta di scarto) e metti quello della ricevuta; il valore lo ricavi dal nome file, tutti i caratteri fino al primo underscore. In questo caso 201F2760-ADC4-438F-A0C9-99DEAF2D8449
UPDATE A1001 set F31 = '201F2760-ADC4-438F-A0C9-99DEAF2D8449 ' where fidd = fidd della fattura

2. Fai girare la fasatura immission delle ricevute. La ricevuta dovrebbe collegarsi alla fattura e modificare lo stato = CONSEGNATA

3. modifica il FLAF del documento facendo update sulla TDOC (per bloccare il documento e far comparire la coccardina colorata)
UPDATE TDOC set FLAF = 1 where fidd = nuovo fidd fattura (attenzione, lo script del workflow delle ricevute fa un ModificaInfo sulla fattura, quindi il FIDD cambia; devi prendere il nuovo FIDD)</pre>

Adiuto indica come Scartate perchè duplicate delle fatture effettivamente consegnate

2026-07-14T15:47:46Z

Gabriele.vivinetto: Created page with "Può succedere che ci si trovi con degli scarti in Adiuto, ma su ADE e Invoice Channel la fattura sia consegnata. Succede perchè si invia la fattura più volte (non si capisce se siamo noi a farlo o è ifin e si riceve subito la NS. Una volta acquisita la ricevuta di SCARTO, anche quando arriva quella di consegna, non viene allegata e rimane nel Transito di Immission Per importarla occorre verificare i filename delel ricevute RC di consegna incagliate, da cui si recup..."

Può succedere che ci si trovi con degli scarti in Adiuto, ma su ADE e Invoice Channel la fattura sia consegnata.

Succede perchè si invia la fattura più volte (non si capisce se siamo noi a farlo o è ifin e si riceve subito la NS. Una volta acquisita la ricevuta di SCARTO, anche quando arriva quella di consegna, non viene allegata e rimane nel Transito di Immission

Per importarla occorre verificare i filename delel ricevute RC di consegna incagliate, da cui si recupera l'ID_SDI

In Invoice channel di IFIN si fa la ricerca per range temporale ed ID SDI e si deduce il numero della Fattura.

In Adiuto si cerca la fattura (che sarà falsamente scartata) e si deduce il FIDD.

Poi si fa un update di F31 di quel FIDD inserendo l'UID IFIN che è la prima parte del filename della ricevuta:.

Fatto questo, si rilancia la fasatura immission di importazione RIcevute e la ricevuta verrà caricata, collegata e la fattura sarà CONSEGNATA

Alla fine bisogna poi modificare anche il FLAF per far bloccae il documento e far apparire la coccarda.

Ad esempio se il filename della ricevuta da importare fosse:<pre>4D0BDE37-4FC0-4973-935C-86E77BE3D5C1_17756685916_IT01071920282_to55h_RC_001.xml</pre>Su Invoice channel, ricerchiamo l'ID SDI<pre>
17756685916
</pre>Troviamo che il numero fattura è, ad esempio <pre>
9833
</pre>In adiuto cerchiamo la fattura e troviamo che il suo FIDD (CTRL-SHIFT-F2) è<pre>1968619</pre>Lanciamo quindi la query:<pre>
UPDATE
A1001
SET F31 = '4D0BDE37-4FC0-4973-935C-86E77BE3D5C1'
WHERE
FIDD = '1968619'
</pre>E importiamo al ricevuta.

Poi recuperiamo nuovamente il fidd della fattura (perchè cambia) che ipotiziaaimo diventi<pre>
1968630
</pre>, e facciamo:<pre>
UPDATE
TDOC
SET
FLAF = 1
WHERE
FIDD = 1968630
</pre>Il dettaglio del [https://helpdesk.bluenext.it/it/support/tickets/1053072 ticket] è<pre>Prendo ad esempio la prima ricevuta del log
D:\Adiuto\Transito\RicevuteSDI\201F2760-ADC4-438F-A0C9-99DEAF2D8449_17700396210_IT01071920282_th5fj_RC_003.xml

1. individua la fattura corrispondente, poi modifica il valore del campo F31 (quello che trovi è quello della ricevuta di scarto) e metti quello della ricevuta; il valore lo ricavi dal nome file, tutti i caratteri fino al primo underscore. In questo caso 201F2760-ADC4-438F-A0C9-99DEAF2D8449
UPDATE A1001 set F31 = '201F2760-ADC4-438F-A0C9-99DEAF2D8449 ' where fidd = fidd della fattura

2. Fai girare la fasatura immission delle ricevute. La ricevuta dovrebbe collegarsi alla fattura e modificare lo stato = CONSEGNATA

3. modifica il FLAF del documento facendo update sulla TDOC (per bloccare il documento e far comparire la coccardina colorata)
UPDATE TDOC set FLAF = 1 where fidd = nuovo fidd fattura (attenzione, lo script del workflow delle ricevute fa un ModificaInfo sulla fattura, quindi il FIDD cambia; devi prendere il nuovo FIDD)</pre>

Adiuto

2026-07-14T15:22:37Z

Gabriele.vivinetto:

Cambiare owner dei backup in Proxmox Backup Server

2026-07-02T09:02:37Z

Gabriele.vivinetto: Created page with "Se si cambia lo user di accesso al Datastore, occorre cambiare l'owner dei backup esistenti. Questo script cambia l'owner per tutti backup dell vm/.*<pre> #!/bin/bash # Script per cambiare proprietario di TUTTI i gruppi di backup # ==================== CONFIGURAZIONE ==================== # Inserisci qui i dati del tuo PBS PBS_SERVER=$1 PBS_PORT="8007" # Porta di default DATASTORE=$2 # Il repository nel formato corretto REPOSITORY="${PBS_SERVER..."

Se si cambia lo user di accesso al Datastore, occorre cambiare l'owner dei backup esistenti. Questo script cambia l'owner per tutti backup dell vm/.*<pre>
#!/bin/bash
# Script per cambiare proprietario di TUTTI i gruppi di backup

# ==================== CONFIGURAZIONE ====================
# Inserisci qui i dati del tuo PBS
PBS_SERVER=$1
PBS_PORT="8007" # Porta di default
DATASTORE=$2

# Il repository nel formato corretto
REPOSITORY="${PBS_SERVER}:${PBS_PORT}:${DATASTORE}"

# Il nuovo proprietario (token)
NEW_OWNER="cluster@pbs!cluster"

# ==================== ESECUZIONE ====================
echo "Inizio cambio proprietario per tutti i backup nel datastore: ${DATASTORE}"
echo "Nuovo proprietario: ${NEW_OWNER}"
echo "Repository: ${REPOSITORY}"
echo "----------------------------------------"

# Ottiene la lista dei gruppi di backup
# Il comando 'list' mostra le colonne: tipo, gruppo, ecc.
# Prendiamo la seconda colonna che contiene il nome del gruppo (es. vm/101)
for group in $(proxmox-backup-client list --repository "${REPOSITORY}" | awk 'NR>1 {print $2}' | grep '^vm\/.*' ); do
echo "Cambiando proprietario per: $group"
proxmox-backup-client change-owner "$group" "$NEW_OWNER" --repository "${REPOSITORY}"

if [ $? -eq 0 ]; then
echo "✓ Proprietario cambiato con successo per $group"
else
echo "✗ ERRORE durante il cambio proprietario per $group"
fi
echo "----------------------------------------"
done

echo "Operazione completata."

</pre>

Proxmox Backup Server

2026-07-02T09:00:53Z

Gabriele.vivinetto:

*[[Backup di Host Fisici con PBS]]
*[[I backup d Proxmox Backup Server bloccano una VM o la rallentano troppo]]
*[[Ottimizzazione di un filesystem ZFS per Proxmox Backup Server]]
*[[Scaricare una immagine disco da Proxmox Backup Server e convertirla]]
*[[I LOG di Proxmox Backup Server occupano troppo spazio]]
*[[Restore di files da command line di una VM con Proxmox Backup Server]]
*[[Restore di un nodo cluster Proxmox VE]]
*[[Proxmox Backup Server non completa il Garbage Collection]]
*[[Cambiare owner dei backup in Proxmox Backup Server]]

Restore di files da command line di una VM con Proxmox Backup Server

2026-07-01T08:54:02Z

Gabriele.vivinetto:

Da GUI l'unico modo è scaricare manualmente lo zip e poi caricarlo sulla VM.

Se invece si vuole fare da command line, è possibile sia con il client che montare l'immagine del disco di backup come loop e poi montare l'eventuale LVM con gutestmount (monatarlo direttamente è più complicato)

== Restore con client: ==

* Settare le variabili necessarie:

source /etc/pbsbackup

* Elencare le sessioni di backup:

proxmox-backup-client snapshots --repository 'myapy@pbs!myuser@pbshost.example.com:MYDATASTORE'

* Fare restore della directory

proxmox-backup-client restore host/myhost/2026-05-28T20:00:02Z root.pxar /restore/examplepath --repository 'myapi@pbs!myuser@pbshost.example.com:MYDATASTORE' --ns MYNAMESPACE --pattern 'folder/path/to/restore/**'

== Restore con mount ==
* Sul server PBS mappare la sessione di backup come loop0:
proxmox-backup-client map vm/101/2025-07-14T19:00:04Z drive-scsi4.img --repository pbs.example.com:MYREPO
* Verificare:

lsblk

<pre>
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 80G 1 loop
└─docker-docker 252:1 0 70G 0 lvm
sda 8:0 0 32G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part
└─sda3 8:3 0 31.5G 0 part
└─pbs-root 252:0 0 23.8G 0 lvm /
sr0 11:0 1 1024M 0 rom

</pre>

* Attivare il volume:

vgchange -ay docker

1 logical volume(s) in volume group "docker" now active

* Verificare i volumi:

lvs

<pre>
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
docker docker -wi-a----- 70.00g
</pre>

* Istallare i tools (si, tanta roba, ma poi si fa autoremove):

apt install libguestfs-tools

*
* Montare il volume

mkdir -p /mnt/restore

guestmount -m /dev/docker/docker -r -a /dev/loop0 /mnt/restore

* Ora dalla VM è possibile fare un rsync:

cd /path/to/restore

rsync -av pbs.example.com:/mnt/restore/ ./

* Alla fine sul server PBS, smontare il volume, demapparlo e rimuovere i tools:
guestunmount /mnt/restore/

proxmox-backup-client unmap /dev/loop0

apt autoremove --purge libguestfs-tools

== Riferimenti ==

* [https://community.nethserver.org/t/howto-restore-a-single-file-from-proxmox-backup-server-pbs/17302 HowTo restore a single file from Proxmox Backup Server (PBS)? - Howto - NethServer Community]

Creazione di un'interfaccia virtuale NAT & Host per VirtualBox

2026-06-26T14:30:47Z

Gabriele.vivinetto: /* Ubuntu 18.04 */

=Introduzione=
Si vuole creare un'interfaccia che permetta di creare una rete con
* delle VM che si vedano tra loro
* delle VM che accedano ad internet
* della VM accessibili dal PC

In pratica una rete Host Only + Nat

=Installazione pacchetti=
* Installare i pacchetti necessari:
sudo apt-get install uml-utilities

=Configurazione interfacce=

* Configurare l'interfaccia tun254, fisica ed il bridge, che così potrà essere utilizzato anche da KVM:

sudoedit /etc/network/interfaces

<pre>
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto tun254
iface tun254 inet manual
pre-up tunctl -t tun254
pre-up iptables -t nat -A POSTROUTING -o wlan0 -s 10.11.12.0/24 -j MASQUERADE
pre-up iptables -t nat -A POSTROUTING -o eth0 -s 10.11.12.0/24 -j MASQUERADE
pre-up iptables -t nat -A POSTROUTING -o tap0 -s 10.11.12.0/24 -j MASQUERADE
pre-up iptables -t nat -A POSTROUTING -o usb0 -s 10.11.12.0/24 -j MASQUERADE
pre-up iptables -t nat -A POSTROUTING -o ppp0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o wlan0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o eth0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o tap0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o usb0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o ppp0 -s 10.11.12.0/24 -j MASQUERADE
post-down tunctl -d tun254

auto br0
iface br0 inet static
address 10.11.12.254
netmask 255.255.255.0
bridge_ports tun254
bridge_stp off
bridge_fd 0

</pre>

* Attivarla
sudo invoke-rc.d networking restart

* Verificare che esistano le interfacce

ifconfig tun254
<pre>
tun254 Link encap:Ethernet HWaddr c6:78:12:8e:19:31
inet6 addr: fe80::c478:12ff:fe8e:1931/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:2048 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
</pre>

ifconfig br0
<pre>
br0 Link encap:Ethernet HWaddr c6:78:12:8e:19:31
inet addr:10.11.12.254 Bcast:10.11.12.255 Mask:255.255.255.0
inet6 addr: fe80::c478:12ff:fe8e:1931/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1657 errors:0 dropped:0 overruns:0 frame:0
TX packets:513 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:227994 (227.9 KB) TX bytes:88648 (88.6 KB)
</pre>

* Verificare che il nat in uscita sia attivato:
sudo iptables -L -n -v -t nat

<pre>
sudo iptables -L -n -v -t nat
Chain PREROUTING (policy ACCEPT 16387 packets, 2414K bytes)
pkts bytes target prot opt in out source destination

Chain INPUT (policy ACCEPT 2318 packets, 353K bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 3789 packets, 290K bytes)
pkts bytes target prot opt in out source destination

Chain POSTROUTING (policy ACCEPT 3782 packets, 290K bytes)
pkts bytes target prot opt in out source destination
11 664 MASQUERADE all -- * wlan0 10.11.12.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * eth0 10.11.12.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * tap0 10.11.12.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * usb0 10.11.12.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * ppp0 10.11.12.0/24 0.0.0.0/0
</pre>

=Server DHCP e DNS=

== Ubuntu 26.04 ==
SOLO DNS: usare direttamente systemd-resolved:
sudoedit /etc/systemd/resolved.conf

<pre>
#DNSStubListener=yes
DNSStubListenerExtra=10.11.12.254
</pre>

systemctl restart systemd-resolved

ss -lunp | grep :53

<pre>
UNCONN 0 0 0.0.0.0:5353 0.0.0.0:*
UNCONN 0 0 10.11.12.254:53 0.0.0.0:*
UNCONN 0 0 127.0.0.54:53 0.0.0.0:*
UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:*
UNCONN 0 0 [::]:5353 [::]:*
</pre>

==Ubuntu 18.04==

* '''<big>----->ATTENZIONE ON USARE FORK, cra migliaia di processi socat<---------------------------------</big>'''
* In questa versione come DNS è installato systemd-resolvd, che non può bindare un'interfaccia.

* Si usa socat: installarlo:
apt-get install socat

* Per fare in modo di usare come dns 10.11.12.254, occorre attivare socat come:

sudo socat -4 UDP-LISTEN:53,fork,reuseaddr,bind=10.11.12.254 UDP:127.0.0.53:53

* Oppure creare la unit systemctl:
vi /etc/systemd/system/socat.service

<pre>
# /etc/systemd/system/socat.service
[Unit]
Description=Socat Service for DNS on tun254 for Virtualbox
After=network.target remote-fs.target nss-lookup.target
# Se il bind è su una interfaccia vpn
# systemctl list-units --no-pager | grep virtual-net
# BindsTo=sys-devices-virtual-net-ztc35dwhra.device
# After=sys-devices-virtual-net-ztc35dwhra.device

[Service]
ExecStart=/usr/bin/socat -4 UDP-LISTEN:53,fork,reuseaddr,bind=10.11.12.254 UDP:127.0.0.53:53
ExecStop=/bin/kill -s QUIT $MAINPID
Restart=on-abort

[Install]
WantedBy=multi-user.target
</pre>

systemctl daemon-reload
systemctl enable socat
systemctl start socat
===Riferimenti===
* [https://unix.stackexchange.com/questions/445782/how-to-allow-systemd-resolved-to-listen-to-an-interface-other-than-loopback dns - How to allow systemd-resolved to listen to an interface other than loopback? - Unix & Linux Stack Exchange]

==Ubuntu 15.04==
* In questa versione, utilizzare l'istanza dnsmaq standard forita da networkmanager
* Fermare dnsmaq
sudo killall dnsmasq
* Creare il file di configurazione
sudoedit /etc/NetworkManager/dnsmasq.d/vboxnat.conf

<pre>
#interface=br0
#log-queries

listen-address=10.11.12.254
dhcp-range=interface:br0,10.11.12.11,10.11.12.99,5m

# static lease
dhcp-host=08:00:27:87:1f:1f,10.11.12.100

# dns forward
local=/vbox.priv/
address=/prox01.vbox.priv/10.11.12.101
address=/prox02.vbox.priv/10.11.12.102

#dns reverse
local=/12.11.10.in-addr.arpa./
ptr-record=101.12.11.10.in-addr.arpa.,"prox01.vbox.priv"
ptr-record=102.12.11.10.in-addr.arpa.,"prox02.vbox.priv"
</pre>

* Riavviare Network Manager
sudo service network-manager restart

* Collegare un'interfaccia esterna

* Per debuggare, scommentare log-queries e ripetere le due operazioni precedenti

* Verificare che il binding sia corretto:
sudo netstat -anp | grep dnsma

<pre>
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 12088/dnsmasq
tcp 0 0 10.11.12.254:53 0.0.0.0:* LISTEN 12088/dnsmasq
udp 0 0 127.0.1.1:53 0.0.0.0:* 12088/dnsmasq
udp 0 0 10.11.12.254:53 0.0.0.0:* 12088/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 12088/dnsmasq
</pre>

==Ubuntu precedenti a 15.04==

* Installare e configurare un server DHCP (dhcpd3-server o dnsmasq)
sudo apt-get install dnsmaq
sudoedit /etc/dnsmasq.con

dhcp-range=interface:tun254,10.11.12.11,10.11.12.99,5m
dhcp-host=08:00:27:87:1f:1f,10.11.12.100

sudo invoke-rc.d dnsmasq restart

=Configurazioni delle VM=

* Configurare le VM come '''Bridged''' sull'interfaccia '''tun254'''. In questo modo si uscirà sempre su internet tra una delle due interfacce nattate.

==Riferimenti==
*[http://prefetch.net/blog/index.php/2009/12/20/creating-linux-bridging-tap-devices-with-tunctl-and-openvpn/ Creating Linux bridging / tap devices with tunctl and openvpn]
*[http://www.iceflatline.com/2010/02/how-to-install-and-configure-dnsmasq/ How to Install and Configure dnsmasq | iceflatline]

Creazione di un'interfaccia virtuale NAT & Host per VirtualBox

2026-06-25T16:38:27Z

Gabriele.vivinetto: /* Ubuntu 18.04 */

=Introduzione=
Si vuole creare un'interfaccia che permetta di creare una rete con
* delle VM che si vedano tra loro
* delle VM che accedano ad internet
* della VM accessibili dal PC

In pratica una rete Host Only + Nat

=Installazione pacchetti=
* Installare i pacchetti necessari:
sudo apt-get install uml-utilities

=Configurazione interfacce=

* Configurare l'interfaccia tun254, fisica ed il bridge, che così potrà essere utilizzato anche da KVM:

sudoedit /etc/network/interfaces

<pre>
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto tun254
iface tun254 inet manual
pre-up tunctl -t tun254
pre-up iptables -t nat -A POSTROUTING -o wlan0 -s 10.11.12.0/24 -j MASQUERADE
pre-up iptables -t nat -A POSTROUTING -o eth0 -s 10.11.12.0/24 -j MASQUERADE
pre-up iptables -t nat -A POSTROUTING -o tap0 -s 10.11.12.0/24 -j MASQUERADE
pre-up iptables -t nat -A POSTROUTING -o usb0 -s 10.11.12.0/24 -j MASQUERADE
pre-up iptables -t nat -A POSTROUTING -o ppp0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o wlan0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o eth0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o tap0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o usb0 -s 10.11.12.0/24 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -o ppp0 -s 10.11.12.0/24 -j MASQUERADE
post-down tunctl -d tun254

auto br0
iface br0 inet static
address 10.11.12.254
netmask 255.255.255.0
bridge_ports tun254
bridge_stp off
bridge_fd 0

</pre>

* Attivarla
sudo invoke-rc.d networking restart

* Verificare che esistano le interfacce

ifconfig tun254
<pre>
tun254 Link encap:Ethernet HWaddr c6:78:12:8e:19:31
inet6 addr: fe80::c478:12ff:fe8e:1931/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:2048 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
</pre>

ifconfig br0
<pre>
br0 Link encap:Ethernet HWaddr c6:78:12:8e:19:31
inet addr:10.11.12.254 Bcast:10.11.12.255 Mask:255.255.255.0
inet6 addr: fe80::c478:12ff:fe8e:1931/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1657 errors:0 dropped:0 overruns:0 frame:0
TX packets:513 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:227994 (227.9 KB) TX bytes:88648 (88.6 KB)
</pre>

* Verificare che il nat in uscita sia attivato:
sudo iptables -L -n -v -t nat

<pre>
sudo iptables -L -n -v -t nat
Chain PREROUTING (policy ACCEPT 16387 packets, 2414K bytes)
pkts bytes target prot opt in out source destination

Chain INPUT (policy ACCEPT 2318 packets, 353K bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 3789 packets, 290K bytes)
pkts bytes target prot opt in out source destination

Chain POSTROUTING (policy ACCEPT 3782 packets, 290K bytes)
pkts bytes target prot opt in out source destination
11 664 MASQUERADE all -- * wlan0 10.11.12.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * eth0 10.11.12.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * tap0 10.11.12.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * usb0 10.11.12.0/24 0.0.0.0/0
0 0 MASQUERADE all -- * ppp0 10.11.12.0/24 0.0.0.0/0
</pre>

=Server DHCP e DNS=

==Ubuntu 18.04==

* '''<big>----->ATTENZIONE ON USARE FORK<---------------------------------</big>'''
* In questa versione come DNS è installato systemd-resolvd, che non può bindare un'interfaccia.

* Si usa socat: installarlo:
apt-get install socat

* Per fare in modo di usare come dns 10.11.12.254, occorre attivare socat come:

sudo socat -4 UDP-LISTEN:53,fork,reuseaddr,bind=10.11.12.254 UDP:127.0.0.53:53

* Oppure creare la unit systemctl:
vi /etc/systemd/system/socat.service

<pre>
# /etc/systemd/system/socat.service
[Unit]
Description=Socat Service for DNS on tun254 for Virtualbox
After=network.target remote-fs.target nss-lookup.target
# Se il bind è su una interfaccia vpn
# systemctl list-units --no-pager | grep virtual-net
# BindsTo=sys-devices-virtual-net-ztc35dwhra.device
# After=sys-devices-virtual-net-ztc35dwhra.device

[Service]
ExecStart=/usr/bin/socat -4 UDP-LISTEN:53,fork,reuseaddr,bind=10.11.12.254 UDP:127.0.0.53:53
ExecStop=/bin/kill -s QUIT $MAINPID
Restart=on-abort

[Install]
WantedBy=multi-user.target
</pre>

systemctl daemon-reload
systemctl enable socat
systemctl start socat
===Riferimenti===
* [https://unix.stackexchange.com/questions/445782/how-to-allow-systemd-resolved-to-listen-to-an-interface-other-than-loopback dns - How to allow systemd-resolved to listen to an interface other than loopback? - Unix & Linux Stack Exchange]

==Ubuntu 15.04==
* In questa versione, utilizzare l'istanza dnsmaq standard forita da networkmanager
* Fermare dnsmaq
sudo killall dnsmasq
* Creare il file di configurazione
sudoedit /etc/NetworkManager/dnsmasq.d/vboxnat.conf

<pre>
#interface=br0
#log-queries

listen-address=10.11.12.254
dhcp-range=interface:br0,10.11.12.11,10.11.12.99,5m

# static lease
dhcp-host=08:00:27:87:1f:1f,10.11.12.100

# dns forward
local=/vbox.priv/
address=/prox01.vbox.priv/10.11.12.101
address=/prox02.vbox.priv/10.11.12.102

#dns reverse
local=/12.11.10.in-addr.arpa./
ptr-record=101.12.11.10.in-addr.arpa.,"prox01.vbox.priv"
ptr-record=102.12.11.10.in-addr.arpa.,"prox02.vbox.priv"
</pre>

* Riavviare Network Manager
sudo service network-manager restart

* Collegare un'interfaccia esterna

* Per debuggare, scommentare log-queries e ripetere le due operazioni precedenti

* Verificare che il binding sia corretto:
sudo netstat -anp | grep dnsma

<pre>
tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 12088/dnsmasq
tcp 0 0 10.11.12.254:53 0.0.0.0:* LISTEN 12088/dnsmasq
udp 0 0 127.0.1.1:53 0.0.0.0:* 12088/dnsmasq
udp 0 0 10.11.12.254:53 0.0.0.0:* 12088/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 12088/dnsmasq
</pre>

==Ubuntu precedenti a 15.04==

* Installare e configurare un server DHCP (dhcpd3-server o dnsmasq)
sudo apt-get install dnsmaq
sudoedit /etc/dnsmasq.con

dhcp-range=interface:tun254,10.11.12.11,10.11.12.99,5m
dhcp-host=08:00:27:87:1f:1f,10.11.12.100

sudo invoke-rc.d dnsmasq restart

=Configurazioni delle VM=

* Configurare le VM come '''Bridged''' sull'interfaccia '''tun254'''. In questo modo si uscirà sempre su internet tra una delle due interfacce nattate.

==Riferimenti==
*[http://prefetch.net/blog/index.php/2009/12/20/creating-linux-bridging-tap-devices-with-tunctl-and-openvpn/ Creating Linux bridging / tap devices with tunctl and openvpn]
*[http://www.iceflatline.com/2010/02/how-to-install-and-configure-dnsmasq/ How to Install and Configure dnsmasq | iceflatline]

Cambiare la priorità di un trigger aperto in Zabbix

2026-05-29T13:36:03Z

Gabriele.vivinetto:

Se si cambia la priorità per un Trigger di un problema aperto, la stessa rimane uguale fino a che non si chiude il problema.

Un modo per aggiornarla è ytramite DB:

* Trovare l'eventid:
<pre>
use zabbix

SELECT p.eventid, h.host, t.description FROM problem p JOIN triggers t ON t.triggerid = p.objectid JOIN functions f ON f.triggerid = t.triggerid JOIN items i ON i.itemid = f.itemid JOIN hosts h ON h.hostid = i.hostid WHERE p.r_eventid IS NULL AND h.host = 'myhostname.example.com';

+-----------+--------------------------------+-----------------------------------------------------------------------------+
| eventid | host | description |
+-----------+--------------------------------+-----------------------------------------------------------------------------+
| 103815828 | myhostname.example.com | Zabbix Agent is OLD |
| 103963978 | myhostname.example.com | MSSQL: Percentage of work tables available from the work table cache is low |
| 104561497 | myhostname.example.com | MSSQL Job 'syspolicy_purge_history': Job duration is high |
+-----------+--------------------------------+-----------------------------------------------------------------------------+
</pre>
* Aggiornare la prioriti ad Informational (1) usando l'eventid voluto (103963978);:
<pre>
UPDATE problem SET severity = 1 WHERE eventid = 103963978;
</pre>

Cambiare la priorità di un trigger aperto in Zabbix

2026-05-28T10:43:53Z

Gabriele.vivinetto: Created page with "Se si cambia la priorità per un Trigger di un problema aperto, la stessa rimane uguale fino a che non si chiude il problema. Un modo per aggiornarla è ytramite DB: * Trovare l'eventid: <pre> use zabbix SELECT p.eventid, h.host, t.description FROM problem p JOIN triggers t ON t.triggerid = p.objectid JOIN functions f ON f.triggerid = t.triggerid JOIN items i ON i.itemid = f.itemid JOIN hosts h ON h.hostid = i.hostid WHERE p.r_eventid IS NULL AND h.host = 'myhostname...."

Se si cambia la priorità per un Trigger di un problema aperto, la stessa rimane uguale fino a che non si chiude il problema.

Un modo per aggiornarla è ytramite DB:

* Trovare l'eventid:
<pre>
use zabbix

SELECT p.eventid, h.host, t.description FROM problem p JOIN triggers t ON t.triggerid = p.objectid JOIN functions f ON f.triggerid = t.triggerid JOIN items i ON i.itemid = f.itemid JOIN hosts h ON h.hostid = i.hostid WHERE p.r_eventid IS NULL AND h.host = 'myhostname.example.com';

+-----------+--------------------------------+-----------------------------------------------------------------------------+
| eventid | host | description |
+-----------+--------------------------------+-----------------------------------------------------------------------------+
| 103815828 | myhostname.example.com | Zabbix Agent is OLD |
| 103963978 | myhostname.example.com | MSSQL: Percentage of work tables available from the work table cache is low |
| 104561497 | myhostname.example.com | MSSQL Job 'syspolicy_purge_history': Job duration is high |
+-----------+--------------------------------+-----------------------------------------------------------------------------+
</pre>
* Aggiornare la prioriti ad Informational (1) usando l'eventid voluto (103963978);:
<pre>
UPDATE problem
SET severity = 1
WHERE eventid = 103963978;
</pre>

Zabbix

2026-05-28T10:38:05Z

Gabriele.vivinetto:

*[[Cambiare la priorità di un trigger aperto in Zabbix]]
*[[Installazione di un agent Zabbix]]
*[[Installazione di un proxy Zabbix]]
*[[Monitoraggio MS SQL Server con Zabbix Agent2]]
*[[Zabbix Agent2 provoca un load altissimo su hardware HP]]
*[[Testare dei comandi con Zabbix]]

*[[Attivare le notifiche Telegram in Zabbix]]
*[[Impostare soglie diverse per un valore di un trigger contenuto in un Template Zabbix]]
*[[Il server Zabbix non riesce più a collegarsi al proxy e da errore Message from proxy.example.com is shorter than expected 123456 bytes. Message ignored]]
*[[Monitoraggio di mysql con Zabbix]]
*[[Monitoraggio Aggiornamenti APT con Zabbix]]
*[[Monitoraggio ZFS in Zabbix]]
*[[Monitoraggio di BackuPc con Zabbix]]
*[[Monitoraggio di dischi SMART con Zabbix]]
*[[Monitoraggio RAID linux md con Zabbix]]
*[[Upgrade da Zabbix 3.4 a Zabbix 4]]
*[[Monitoraggio di LVM con Zabbix]]
*[[Monitoraggio di servizi SSL con Zabbix]]
*[[Monitoraggio di Ceph con Zabbix]]
*[[Monitoraggio di Squid con Zabbix]]
*[[Risolvere il problema Zabbix poller processes more than 75% busy]]
*[[Monitoraggio di PfSense con Zabbix]]
*[[Monitoraggio di OpenWrt con Zabbix]]
*[[Upgrade di Zabbix 4.x a 5.x]]
*[[Upgrade di Zabbix 4.x a 6.2]]
*[[Monitoraggio Docker con Zabbix]]
*[[Installazione di Zabbix con Docker]]
*[[Monitoraggio di Elasticsearch con Zabbix]]
*[[Zabbix Proxy crash con erroe zbx mem malloc(): out of memory|Zabboix Proxy crasha con erroe zbx_mem_malloc(): out of memory]]
*[[Il monitoraggio di un HP iLO in SNMP restituisce errore con status 3]]
*[[Monitoraggio di Proxmox Backup Server con Zabbix]]
*[[Aggiornamento di Zabbix da 6.4 a 7.0 con migrazione a PostgreSQL in Docker]]
*[[Monitoraggio di un Proxy Zabbix]]

Disablitare la modifica del DNS in netbird client su un exit node

2026-05-22T13:46:46Z

Gabriele.vivinetto:

Se si installa netbird client su una macchina linux per usarla come exit node, modificherà /etc/resolv.conf e non risolverà più i nomi locali.

vi /var/lib/netbird/default.json

"DisableDNS": true,

systemctl restart netbird.service
Ripristinare il file resolv.conf originale

Disablitare la modifica del DNS in netbird client su un exit node

2026-05-22T13:40:18Z

Gabriele.vivinetto: Created page with "Se si installa netbird client su una macchina linux per usarla come exit node, modificherà /etc/resolv.conf e non risolverà più i nomi locali. vi /var/lib/netbird/default.json "DisableDNS": true, systemctl restart netbird.service"

Netbird

2026-05-22T13:26:24Z

Gabriele.vivinetto: Created page with "* Disablitare la modifica del DNS in netbird client su un exit node"

* [[Disablitare la modifica del DNS in netbird client su un exit node]]

Linux

2026-05-22T13:25:26Z

Gabriele.vivinetto: /* Pacchetti */

==Distribuzioni==
*[[Alpine]]
*[[Debian]]
*[[Fedora]]
*[[Kali]]
*[[RedHat]]
*[[Ubuntu]]

==Argomenti==
*[[Antivirus]]
*[[Backup]]
*[[Caselle di posta - Creazione]]
*[[Comandi Unix]]
*[[Comunicazione]]
*[[Clustering - High Availability]]
*[[Emulatori]]
*[[Encryption]]
*[[Hardware]]
*[[Linux System Administration]]
*[[Multimedia]]
*[[Networking]]
*[[Pxe]]
*[[Sicurezza]]
*[[Storage]]
*[[Virtualizzazione]]

==Pacchetti==
*[[Amavis]]
*[[Ansible]]
*[[Apache Openmeetings]]
*[[Apache]]
*[[Archivemail]]
*[[Bash]]
*[[Bchunk]]
*[[Bcvi]]
*[[Clamav]]
*[[Courier Imap]]
*[[Cryptsetup]]
*[[Cups]]
*[[Daemon]]
*[[Dhcp]]
*[[Dialog]]
*[[Dovecot]]
*[[Esmtp]]
*[[Fail2ban]]
*[[Fetchmail]]
*[[Ghostscript]]
*[[Git]]
*[[Graylog]]
*[[Hylafax]]
*[[Incron]]
*[[Iptables]]
*[[Jailkit]]
*[[Lftp]]
*[[Lilo]]
*[[Logrotate]]
*[[Mutt]]
*[[Netbird]]
*[[Netextender]]
*[[Nginx]]
*[[Ntop]]
*[[Ntp]]
*[[Nut]]
*[[OpenVpn]]
*[[Pam]]
*[[Perl]]
*[[PhpWiki]]
*[[Php]]
*[[Postfix]]
*[[Ppp]]
*[[Pptpd]]
*[[PrivacyIDEA]]
*[[Proftpd]]
*[[Puppet]]
*[[Razor2]]
*[[Request Tracker]]
*[[Rsyslog]]
*[[Samba]]
*[[Sendmail]]
*[[Shellinabox]]
*[[Squid]]
*[[Squirrelmail]]
*[[Ssh]]
*[[Svn]]
*[[SyncThing]]
*[[Syslinux]]
*[[Syslog]]
*[[Sysrqd]]
*[[Tcpdump]]
*[[Transmission]]
*[[Udev]]
*[[Vi]]
*[[Vnc]]
*[[Vsftpd]]
*[[Webmin]]
*[[Winexe]]
*[[Wireshark]]
*[[Xorg]]
*[[imagemagik]]
*[[initramfs-tools]]
*[[inotify]]
*[[jabber]]
*[[mdadm]]
*[[mgetty]]
[[Category:Linux]]
[[Category:Published]]

Attivazione di prodotti Microsoft con KMS

2026-05-19T14:25:33Z

Gabriele.vivinetto: /* Attivazione Office 2019 Pro Plus */

=Installazione server KMS con docker=

* https://wind4.github.io/vlmcsd/

<pre>
cat > docker-compose.yml <<EOFile
version: '3'
services:
app:
container_name: vlmcsd
image: mikolatero/vlmcsd
restart: unless-stopped
ports:
- '1688:1688'
EOFile
</pre>

docker compose up

= Attivazione WIN 10/11 PRO, WIN2K8R2 STD, WIN7 PRO=

* Comandi comuni

cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

* Windows 10-11

cscript.exe //NoLogo slmgr.vbs -ipk W269N-WFGWX-YVC9B-4J6C9-T83GX

* Windows 2008R2 Standard

cscript.exe //NoLogo slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC

* Windows Seven Pro
cscript.exe //NoLogo slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

* Proseguire

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Riferimenti ===
* https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/get-started/kms-client-activation-keys.md
* [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Key Management Services (KMS) client activation and product keys for Windows Server and Windows | Microsoft Learn]

=Attivazione Windows Server=

=== Installazione da ISO Evaluation ===

* We need to use DISM to change the product version/edition

* Open an elevated command prompt
* Get a list of available version upgrade paths by typing:

DISM.exe /Online /Get-TargetEditions

* Then upgrade to the listed edition by typing:

DISM /Online /Set-Edition:<TargetEdition> /ProductKey:<Product Key from Below Table> /AcceptEula

* '''BE SURE TO REBOOT before proceeding !!!'''

=== Installazione da ISO Retail ===
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

cscript.exe //NoLogo slmgr.vbs -ipk <Product Key from Below Table>

=== [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Product Key Table] ===
<pre>
LICENZA CD-KEY
Windows Server 2025 Standard TVRH6-WHNXV-R9WG3-9XRFY-MY832
Windows Server 2025 Datacenter D764K-2NDRG-47T6Q-P8T8W-YP6DF
Windows Server 2025 Datacenter Azure Edition XGN3F-F394H-FD2MY-PP6FD-8MCRC
Windows Server 2022 Standard VDYBN-27WPP-V4HQT-9VMD4-VMK7H
Windows Server 2022 Datacenter WX4NM-KYWYW-QJJR4-XV3QB-6VM33
Windows Server 2022 Datacenter Azure Edition NTBV8-9K7Q8-V27C6-M2BTV-KHMXV
Windows Server 2019 Standard (SAC v1809) N2KJX-J94YW-TQVFB-DG9YT-724CC
Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C
Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Datacenter (SAC v1809) 6NMRW-2C8FM-D24W7-TQWMY-CWH2D
Windows Server 2019 Azure Core FDNH6-VW9RW-BXPJ7-4XTYG-239TB
Windows Server 2019 ARM64 GRFBW-QNDC4-6QBHG-CCK3B-2PR88
Windows Server 2016 Standard WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2016 Standard (SAC v1803) PTXN8-JFHJM-4WC78-MPCBR-9W4KR
Windows Server 2016 Standard (SAC v1709) DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4
Windows Server 2016 Essentials JCKRF-N37P4-C2D82-9YXRT-4M63B
Windows Server 2016 Datacenter (SAC v1803) 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG
Windows Server 2016 Datacenter (SAC v1709) 6Y6KB-N82V8-D8CQV-23MJW-BWTG6
Windows Server 2016 Datacenter CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Cloud Storage QN4C6-GBJD2-FB422-GHWJK-GJG2R
Windows Server 2016 Azure Core VP34G-4NPPG-79JTQ-864T4-R3MQX
Windows Server 2016 ARM64 K9FYF-G6NCK-73M32-XMVPY-F9DRR

</pre>

=== Parte comune ===
*Proseguire
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Troubleshooting ===
If an error occurred while activating Windows Server:
Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F069' to display the error text.

The reason is that I have an evaluation version of Windows Server 2022 installed. First, you need to convert it to a Standard version according to this article:

dism /online /set-edition:serverstandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula

Then I can activate my Windows instance on the KMS host.

=== Riferimenti ===
* [https://www.aidenwebb.com/posts/how-to-fix-server-2019-activation-error-run-slui.exe-0x2a-0xc004f069/ How to Fix Server 2019 Activation Error: Run “slui.exe 0x2a 0xC004F069” | Aiden Arnkels-Webb]

=Attivazione Office 2019 Pro Plus =

* https://github.com/Wind4/vlmcsd/issues/20

I have one that works for office 2019. But I do NOT know why it works.
cscript "%ProgramFiles(x86)%\Microsoft Office\Office16\ospp.vbs" /dstatus
with the following output

LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 1601-01-01
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004F040 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights.
REMAINING GRACE: 179 days (259199 minute(s) before expiring)

* install volume licensing SKUs for office 2019

<pre>
@echo off
:ADMIN
openfiles >nul 2>nul ||(
echo CreateObject^("Shell.Application"^).ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs"
"%temp%\getadmin.vbs" >nul 2>&1
goto:eof
)
del /f /q "%temp%\getadmin.vbs" >nul 2>nul

for /f "tokens=6 delims=[]. " %%G in ('ver') do set win=%%G

setlocal

pushd "%~dp0"
Title Office 2019 Retail to Volume License Converter

rem SET OfficePath=%ProgramFiles%\Microsoft Office
SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" (
echo Could not find the license files for Office 2019!
pause
goto :eof
)

echo Press Enter to start VL-Conversion...
echo.
pause
echo.
cd /D "%SystemRoot%\System32"

if %win% GEQ 9200 (
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)
if %win% LSS 9200 (
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)

cscript "%OfficePath%\Office16\ospp.vbs" /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript "%OfficePath%\Office16\ospp.vbs" /act

echo.
echo Retail to Volume License conversion finished.
echo.
pause
</pre>

* Turn off KMS Client Online AVS Valdation
<pre>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Software Protection Platform]
"NoGenTicket"=dword:00000001
</pre>

* Activate
<pre>
cd "\Program Files\Microsoft Office\Office16"
cd "\Program Files (x86)\Microsoft Office\Office16"
cd "\Program Files (x86)\Microsoft Office\root\Office16"
cscript ospp.vbs /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript ospp.vbs /sethst:kms.example.com
cscript ospp.vbs /act
cscript ospp.vbs /dstatusall
</pre>

= Office 2021 ProPlus Retail =

* Assicurarsi di aver installato la 2021 ProPlus (non professional) Retail

* Usare lo script
<pre>
@echo off
echo Change kms.example.com to KMS Server IP or Host
pause
REM Change ProgramFiles to ProgramFiles(x86) If install x86 version . Default are x64

Title Converter Office 2021 Retail to Volume And Activate Through KMS Server

set LICPATH=%ProgramFiles%\Microsoft Office\root\Licenses16
set LICPATH1=%ProgramFiles%\Microsoft Office\Office16

cd C:\Windows\System32

cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-bridge-office.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root-bridge-test.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-stil.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\pkeyconfig-office.xrm-ms"
cscript slmgr.vbs /ipk FXYTK-NJJ8C-GB6DW-3DYQT-6F7TH

cscript "%LICPATH1%\ospp.vbs" /sethst:kms.example.com
cscript "%LICPATH1%\ospp.vbs" /act

echo.
echo Finished.
echo.
pause
</pre>

=Riferimenti=

*[https://www.ilsoftware.it/articoli.asp?tag=KMS-cos-e-e-come-funziona-l-attivazione-di-Windows-in-rete-locale_23680 KMS, cos'è e come funziona l'attivazione di Windows in rete locale - IlSoftware.it]
*[https://github.com/Py-KMS-Organization/py-kms Py-KMS-Organization/py-kms: KMS Server Emulator written in Python]
*[https://github.com/FuryGreenwood/FuryKMS FuryGreenwood/FuryKMS: Microsoft Windows and Office KMS Activator]
*[https://github.com/massgravel/Microsoft-Activation-Scripts massgravel/Microsoft-Activation-Scripts: A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, fewer antivirus detection and user-friendliness.]
*[https://massgrave.dev/ index]
*[https://theitbros.com/activate-windows-with-kms-server/ How to Activate Windows with your KMS Server - KMS License Key List]
*[http://blog.51sec.org/2020/05/create-kms-docker-and-use-kms-to.html#point3 Activate Windows/Office (Run KMS Docker / Install KMS) - Cybersecurity Memo]

Consentire il cambio password al primo accesso RDP

2026-04-29T08:33:50Z

Gabriele.vivinetto: Created page with "Se un utente ha password scaduta o c'è impostato "Change password at first logon", di default in RDP non lo fa collegare. Per far questo bisogna impostare questa reg key:<pre> Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp] "SecurityLayer"=dword:00000000 "UserAuthentication"=dword:00000000 </pre>che per UserAuthentication fa la stessa cosa di togliere la spunta dalla System Properties / A..."

Se un utente ha password scaduta o c'è impostato "Change password at first logon", di default in RDP non lo fa collegare.

Per far questo bisogna impostare questa reg key:<pre>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]
"SecurityLayer"=dword:00000000
"UserAuthentication"=dword:00000000
</pre>che per UserAuthentication fa la stessa cosa di togliere la spunta dalla
System Properties / Advanced /Remote / Allow connections only from computer running Remote Desktop with Networ Leven Authentication (recommended)

== Riferimenti ==

* [https://mssec.wordpress.com/2015/12/26/forced-password-change-at-next-logon-and-rdp/ Forced password change at next logon and RDP | Microsoft Security Solutions]
* [https://www.reddit.com/r/sysadmin/comments/8wawx9/you_must_change_your_password_before_logging_on/ You must change your password before logging on for the first time (RDP) : r/sysadmin]

* [https://fixingitpro.com/2011/07/06/disabling-rdp-network-level-authentication-nla-remotely-via-the-registry/ Disabling RDP Network Level Authentication (NLA) remotely via the registry – Fixing IT]

RDP

2026-04-29T08:24:09Z

Gabriele.vivinetto: Created page with "Consentire il cambio password al primo accesso RDP"

[[Consentire il cambio password al primo accesso RDP]]

Windows

2026-04-29T08:23:17Z

Gabriele.vivinetto:

[[Category: Windows]]

*[[Windows Client]]
*[[Windows Server]]
*[[Windows Mobile]]
*[[Batch Files]]
*[[RDP]]
<hr>
*[[HijackThis]]
*[[PDFcreator]]

<hr>
*[[Attivazione di Windows con KMS Client]]
*[[Errore Microsoft Bus High Definition Driver non trovato]]
*[[Attivare il Num Lock alla schermata di Logon di Windows]]
*[[Disattivare l'impostazione delle Preferenze in IE7]]
*[[Recuperare la password di Administrator di Windows]]
*[[Customizzare il Logo di Supporto di Windows]]
*[[Installazione di Apache 2.2 e PHP 5 su Windows]]
*[[Disablitare un servizio di Windows da Recovery Console]]
*[[Errore in mscoree.dll]]
*[[Installare Telnet client in Windows Vista, 2008 e Seven]]
*[[Creare una coda di stampa con Overlay in Windows]]
*[[Il Task Scheduler di Windows 2008 o Windows Seven è lento all'apertura]]
*[[Applicare gli aggiornamenti di Windows Update Offline con WSUSOFFLINE]]
*[[Conversione da Windows Home a Professional]]

Reset del blocco brute force per tentativi falliti di login in Nextcloud

2026-03-04T07:41:05Z

Gabriele.vivinetto:

Il comando è
sudo -u www-data php occ security:bruteforce:reset 0.0.0.0
Da Docker
sudo docker compose exec --user www-data -it nextcloud-app php occ security:bruteforce:reset 0.0.0.0
'''Se non lo sblocca, specifica l'IP'''

== Riferimenti ==

* [https://github.com/nextcloud/all-in-one/discussions/3381 How to clear all bruteforce entries in the database · nextcloud/all-in-one · Discussion #3381]

Aggiornamento da Debian 12 Bookworm a Debian 13 Trixie

2026-02-13T20:08:14Z

Gabriele.vivinetto: /* Riavvio */

== Preparazione ==

=== Mysql ===
* Verificare che Mariadb / Mysql funzioni, e fermarlo
systemctl status mariadb

mysql

systemctl stop mariadb

=== Aggiornamento Bookworm ===
* Aggiornare agli ultimi pacchetti Booworm

apt autoremove --purge && apt update && apt dist-upgrade && apt clean

* Se è presente Zabbix agent o proxy, installare il release file di Zabbix 7 (non c'è Zabbix 6.4):
<pre>
cd /tmp
wget https://repo.zabbix.com/zabbix/7.0/debian/pool/main/z/zabbix-release/zabbix-release_latest_7.0+debian13_all.deb
dpkg -i zabbix-release_latest_7.0+debian13_all.deb
</pre>

* Se è presente Proxmox Backup Client, installare la key e ridefinire la source:
<pre>
wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg -O /usr/share/keyrings/proxmox-archive-keyring.gpg
cd /etc/apt/sources.list.d
mv pbs-client.list pbs-client.sources
cat <<EOFile > pbs-client.sources
Types: deb
URIs: http://download.proxmox.com/debian/pbs-client
Suites: trixie
Components: main
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOFile
</pre>

== Aggiornamento ==
* Aggiornare le sources:
<pre>
cd /etc/apt
sed -e 's/bookworm/trixie/g' sources.list -i
sed -e 's/bookworm/trixie/g' sources.list.d/*.list -i

</pre>

* Aggiornare i repos:

apt update

* Scaricare i pacchetti

apt dist-upgrade -d

* Aggiornare apt

apt install apt

* Aggiornare il kernel

apt install linux-image-amd64

* Aggiornare il resto

apt dist-upgrade

== Nfs ==
Se si definiscono delle share NFS, attenzione che lasciando il parametro subtree_check i client possono generare un erorre "stale file handlke" e non accedere alal share. Sostituirlo con no_subtree_check:
sed -i -e 's/\bsubtree_check\b/no_subtree_check/g' _/etc/exports

cat /etc/exports

== Sysctl ==
Da questa versione, non viene letto più sysctl.conf:<pre>
mv /etc/sysctl.conf.dpkg-bak /etc/sysctl.conf.d/sysctl.conf
systemctl restart systemd-sysctl.service
</pre>

== Comportamento /tmp ==

=== La directory dei file temporanei /tmp è ora memorizzata in un tmpfs ===
A partire da trixie, la directory <code>/tmp/</code> è archiviata in modo predefinito in memoria usando un file system tmpfs(5). Ciò dovrebbe rendere più veloci le applicazioni che usano file temporanei, ma se ci vengono messi file grandi si può esaurire la memoria.

Per i sistemi aggiornati da bookworm, il nuovo comportamento inizia solo dopo un riavvio. I file lasciati in <code>/tmp</code> vengono nascosti dopo che il nuovo è montato, il che genera avvertimenti nel giornale di sistema o in syslog. Si può accedere a tali file usando bind-mount (vedere mount(1)): eseguire <code>mount --bind / /mnt</code> rende possibile accedere alla directory sottostante in <code>/mnt/tmp</code> (eseguire <code>umount /mnt</code> dopo che sono stati ripuliti i file vecchi).

Il comportamento predefinito è allocare fino al 50% della memoria a <code>/tmp</code> (questo è un valore massimo: la memoria viene usato solamente quando vengono effettivamente creati i file in <code>/tmp</code>). Questa dimensione può essere modificata eseguendo <code>systemctl edit tmp.mount</code> come root e impostando, ad esempio:
[Mount]
Options=mode=1777,nosuid,nodev,size=2G
(vedere systemd.mount(5)).

Si può tornare ad avere <code>/tmp</code> come directory regolare eseguendo <code>systemctl mask tmp.mount</code> come root e riavviando.

Le nuove impostazioni predefinite per il file system possono essere scavalcate in <code>/etc/fstab</code>, perciò i sistemi che hanno già definito una partizione <code>/tmp</code> separata non verranno toccati.

== OpenSSH ==

=== OpenSSH non supporta più le chiavi DSA ===
Le chiavi Digital Signature Algorithm (DSA), come specificate nel protocollo Secure Shell (SSH), sono intrinsecamente deboli: sono limitate a chiavi private a 160 bit e a SHA-1 digest. L’implementazione di SSH fornita dai pacchetti '''openssh-client''' e '''openssh-server''' ha il supporto per le chiavi DSA disabilitato a partire da OpenSSH 7.0p1 nel 2015, rilasciato con Debian 9 («stretch»), sebbene potesse ancora essere abilitato usando le opzioni di configurazione <code>HostKeyAlgorithms</code> e <code>PubkeyAcceptedAlgorithms</code>, rispettivamente per le chiavi dell’host e dell’utente.

A questo punto l’unico uso restante di DSA dovrebbe essere quello di connettersi a un qualche dispositivo molto vecchio. Per tutti gli altri usi, gli altri tipi di chiave supportati da OpenSSH (RSA, ECDSA e Ed25519) sono migliori.

A partire da OpenSSH 9.8p1 in trixie, le chiavi DSA non sono più supportate neanche con le opzioni di configurazione descritte sopra. Se si ha un dispositivo a cui ci si può connettere solo usando DSA, allora per farlo si può usare il comando <code>ssh1</code> fornito dal pacchetto '''openssh-client-ssh1'''.

Nella remota eventualità che si stia ancora usando chiavi DSA per connettersi ad un server Debian (se non si è sicuri si può controllare aggiungendo l’opzione <code>-v</code> alla riga di comando di <code>ssh</code> utilizzata per connettersi a quel server e cercare la riga «Server accepts key:»), si devono generare chiavi sostitutive prima di fare l’aggiornamento. Per esempio, per generare una nuova chiave Ed25519 e abilitare il login ad un server usando quella, eseguire quanto segue nel client, sostituendo ad <code>username@server</code> i nomi appropriati per utente e host:
ssh-keygen -t ed25519

ssh-copy-id username@server

== Cryptsetup ==

=== I file system cifrati necessitano del pacchetto systemd-cryptsetup ===
Il supporto per il rilevamento e il montaggio automatico dei file system cifrati è stato spostato nel nuovo pacchetto systemd-cryptsetup. Questo nuovo pacchetto è raccomandato da systemd, perciò dovrebbe essere installato automaticamente con l’aggiornamento.

Se si usano file system cifrati, assicurarsi che il pacchetto systemd-cryptsetup sia installato prima di riavviare.

== Mysql /MariaDB ==

=== Gli aggiornamenti della versione principale di MariaDB funzionano in modo affidabile solo dopo uno spegnimento pulito. ===
MariaDB non supporta il ripristino da errori attraverso versioni maggiori diverse. Per esempio, se un server MariaDB 10.11 ha subito uno spegnimento improvviso a causa di una interruzione di alimentazione o di un problema software, il database deve essere riavviato con gli stessi binari MariaDB 10.11 in modo che possa fare il ripristino dagli errori con successo e possa riconciliare i file dei dati e i file di log per portare avanti o annullare le transazioni che sono state interrotte.

Se si cerca di fare il ripristino da un crash con MariaDB 11.8 usando la directory dei dati da un’istanza di MariaDB 10.11 andata in cash, il nuovo server MariaDB si rifiuterà di avviarsi.

Per assicurarsi che un server MariaDB venga spento in maniera pulita prima di fare un aggiornamento della versione principale, fermare il servizio con
service mariadb stop
e in seguito controllare i log del server cercando <code>Shutdown complete</code> per confermare che tutti i dati e i buffer siano stati svuotati su disco con pieno successo.

Se non è stato spento in modo pulito, riavviarlo per attivare il recupero dai crash, poi fermarlo di nuovo e controllare che il secondo spegnimento sia stato pulito.

Per informazioni aggiunti su come fare backup e altre informazioni correlate per gli amministratori di sistema, vedere /usr/share/doc/mariadb-server/README.Debian.gz.

== Dovecot ==
La suite per server di posta '''dovecot''' in trixie usa un formato di configurazione che è incompatibile con le versioni precedenti. Dettagli sulle modifiche alla configurazione sono disponibili su docs.dovecot.org.

== Samba ==

* La funzionalità Active Directory Domain Controller (AD-DC) è stata scorporata da '''samba'''. Se si usa tale funzionalità è necessario installare il pacchetto '''samba-ad-dc'''.

* Il pacchetto '''samba-vfs-modules''' è stato riorganizzato. La maggior parte dei moduli VFS è ora inclusa nel pacchetto '''samba'''. Tuttavia i moduli per ''ceph'' e ''glusterfs'' sono stati separati in '''samba-vfs-ceph''' e '''samba-vfs-glusterfs'''.

== Request Tracker ==
Il pacchetto request-tracker4 è stato rimosso da trixie. È sostituito da request-tracker5 che include istruzioni su come migrare i propri dati: si può mantenere installato il pacchetto request-tracker4 ora obsoleto da bookworm durante la migrazione.

== Deborphan ==
l pacchetto deborphan è stato rimosso da trixie. Per rimuovere i pacchetti non necessari si dovrebbe utilizzare apt autoremove, dopo apt-mark minimize-manual. Anche debfoster può essere uno strumento utile.

== Riavvio ==
* Pulire la cache:
apt-get clean
* Riavviare

reboot

* Rimuovere i pacchetti obsoleti;

apt autoremove --purge linux-image-5.1.\*

* Controllare se ci sono pacchetti obsoleti, e se necessario, rimuoverli;

dpkg -l | grep deb12

=== Optional: Modernize apt Repository Sources ===
You can migrate existing repository sources to the recommended deb822 style format, by running:
apt modernize-sources
By answering the following prompt with "n" you can check the changes the command would make before applying them. To apply them simply run the command again and respond to the prompt with "Y".

The command will also keep the old <code>.list</code> files around by appending <code>.bak</code> to them. So you will have the new <code>.sources</code> files and the old repository configurations in the <code>.list.bak</code> files. You can remove the leftover backup files once you verified that everything works smoothly with the new format.

Debian 12 Bookworm

2026-02-13T14:45:53Z

Gabriele.vivinetto:

[[Upgade da Debian 11 Bulseye a Debian 12 Bookworm|Upgade da Debian 11 Bullseye a Debian 12 Bookworm]]

Upgade da Debian 11 Buster a Debian 12 Bookworm

2026-02-13T14:44:51Z

Gabriele.vivinetto: Gabriele.vivinetto moved page Upgade da Debian 11 Buster a Debian 12 Bookworm to Upgade da Debian 11 Bulseye a Debian 12 Bookworm

#REDIRECT [[Upgade da Debian 11 Bulseye a Debian 12 Bookworm]]

Upgade da Debian 11 Bulseye a Debian 12 Bookworm

2026-02-13T14:44:51Z

Gabriele.vivinetto: Gabriele.vivinetto moved page Upgade da Debian 11 Buster a Debian 12 Bookworm to Upgade da Debian 11 Bulseye a Debian 12 Bookworm

sudo sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list

sudo sed -i 's/non-free/non-free non-free-firmware/g' /etc/apt/sources.list

sudo sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list.d/*

apt update && apt dist-upgrade -d

apt install apt

apt install linux-image-amd64

apt dist-upgrade

Gestione di un Repository APT multi distribuzione con reprepro

2026-02-03T14:17:56Z

Gabriele.vivinetto:

{{Stub}}

=Aggiunta i pacchetti=
* Compilare i pacchetti e poi importarli con:

reprepro includedeb wheezy path/to/telegram-cli_1.0.6-1_amd64.deb

* Se si vogliono aggiungere due pacchetti della stessa applicazione per due distribuzioni diverse (perchè hanno dipendenze diverse), questi pacchetti devono avere versione e nome diverso: editare il file debian/changelog per includere -nomedistribuzione dopo la versione.

=Aggiunta di un'architettura=
Se si vuole aggiungere un'architettura dopo, editare il file aggiungendo ad esempio armhf:
vi conf/distributions

<pre>
# RVM Debian Stretch packages
Origin: RVM
Label: rvm
Suite: stretch
Codename: stretch
Architectures: i386 amd64 armhf source
Components: main
Description: RVM Debian repository
Contents: .gz .bz2
Tracking: keep
SignWith: yes
Log: packages.stretch.log
</pre>

* Esportare gli indici e poi migrare tutti i pacchetti di architettura all da stretch:
reprepro export
reprepro flood 'stretch' 'armhf'

== Aggiunta di una distribuzione ==
vi conf/distributions

<pre>
# RVM Debian Trixie packages
Origin: RVM
Label: rvm
Suite: trixie
Codename: trixie
Architectures: i386 amd64 armhf source
Components: main
Description: RVM Debian repository
Contents: .gz .bz2
Tracking: keep
SignWith: yes
Log: packages.trixie.log
</pre>

* Importare un pacchetto

== Aggiornamento chiave GPG ==
<pre>
export GNUPGHOME=/usr/local/apache2/htdocs/gpg
gpg --full-generate-key

gpg --import gpg/rvm_debian_package.private.asc

gpg --import gpg/rvm_debian_package.public.asc

gpg --list-secret-keys

sec rsa2048 2026-02-03 [SC]
9220A90503F14F140A78D2E157EE0CD2381115F3
uid [ unknown] RVM Debian Key (For Debian Package Siging) <admin@rvmgroup.it>
ssb rsa2048 2026-02-03 [E]

gpg --list-keys

pub rsa2048 2026-02-03 [SC]
9220A90503F14F140A78D2E157EE0CD2381115F3
uid [ unknown] RVM Debian Key (For Debian Package Siging) <admin@rvmgroup.it>
sub rsa2048 2026-02-03 [E]

gpg --edit-key 9220A90503F14F140A78D2E157EE0CD2381115F3 trust

Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y

reprepro -V export
</pre>

=Riferimenti=
*[https://wiki.debian.org/SettingUpSignedAptRepositoryWithReprepro#Generating_GnuPG_keys SettingUpSignedAptRepositoryWithReprepro - Debian Wiki]
*[https://vincent.bernat.im/en/blog/2014-local-apt-repositories.html#initial-setup Local corporate APT repositories | Vincent Bernat]
*[http://stackoverflow.com/questions/15243613/reprepro-adding-same-deb-package debian - Reprepro adding same deb package - Stack Overflow]
*[http://www.xenuser.org/linux/reprepro-how-to-add-the-same-package-for-multiple-distributions/ reprepro: How to add the same package for multiple distributions | Ascii for Breakfast]

<pre>

adduser --system --disabled-password --disabled-login \
--home /srv/packages \
--group reprepro

sudo apt-get install reprepro

sudo -u reprepro mkdir conf gpg logs www

1 cd /srv/packages/
2 GNUPGHOME=gpg gpg --gen-key
3 ls
4 vi conf/distributions
5 vi conf/distributions
6 ls
7 mkdir incoming
8 ls
9 vi conf/distributions
10 ls incoming/
11 cp /tmp/telegram-cli_1.0.6-1_amd64.deb incoming/
12 reprepro includedeb wheezy incoming/telegram-cli_1.0.6-1_amd64.deb
13 ls
14 ifco
15 ifconfig
16 ip addr show
17 cp /tmp/telegram-cli_1.0.6-1_amd64.deb incoming/
18 reprepro includedeb jessie incoming/telegram-cli_1.0.6-1_amd64.deb
19 cp /tmp/telegram-cli_1.0.6-1-jessie_amd64.deb incoming/
20 reprepro includedeb jessie incoming/telegram-cli_1.0.6-1-jessie_amd64.deb
21 ls
22 cd www/
23 pwd
24 ls
25 vi test.txt
26 ls
27 cd ..
28 ls
29 ls -laR www/
30 ls
31 cd gpg/
32 ls
33 vi mykey.asc
34 gpg --import mykey.asc
35 rm -rf /srv/packages/.gnupg
36 history
37 cd
38 GNUPGHOME=gpg gpg --import mykey.asc
39 ls
40 GNUPGHOME=gpg gpg --import gpg/mykey.asc
41 GNUPGHOME=gpg gpg --list-secret-keys
42 vi gpg/mykey.asc
43 GNUPGHOME=gpg gpg --import gpg/mykey.asc
44 GNUPGHOME=gpg gpg --list-secret-keys
45 GNUPGHOME=gpg gpg --delete-secret-keys 1024D/1C9CF0A7 2048g/E4E9035C
46 GNUPGHOME=gpg gpg --delete-secret-keys 1C9CF0A7 E4E9035C
47 GNUPGHOME=gpg gpg --list-secret-keys
48 GNUPGHOME=gpg gpg --delete-secret-keys F6D289F6
49 GNUPGHOME=gpg gpg --list-secret-keys
50 GNUPGHOME=gpg gpg --list-keys
51 GNUPGHOME=gpg gpg --delete-keys F6D289F6 1C9CF0A7
52 GNUPGHOME=gpg gpg --list-keys
53 GNUPGHOME=gpg gpg --export 61EAB64A --armor
54 GNUPGHOME=gpg gpg --export 61EAB64A --armour
55 GNUPGHOME=gpg gpg --armour --export 61EAB64A
56 GNUPGHOME=gpg gpg --armour --export 61EAB64A > debian.rvmgroup.it.key.asc
57 ls
58 ls -al
59 sudo chmod o- gpg
60 chmod o- gpg
61 GNUPGHOME=gpg gpg --armour --export 61EAB64A
62 ls
63 chmod 700 gpg
64 GNUPGHOME=gpg gpg --armour --export 61EAB64A | xclip
65 GNUPGHOME=gpg gpg --armour --export 61EAB64A
66 ls
67 apt-key add < debian.rvmgroup.it.key.asc
68 cat debian.rvmgroup.it.key.asc
69 mv debian.rvmgroup.it.key.asc www/
70 ls
71 ls logs/packages.jessie.log
72 less logs/packages.jessie.log
73 ls
74 history +
75 history
re
</pre>

Creare un nuovo utente sa in SQL Server senza conoscere le credenziali

2026-01-29T08:47:57Z

Gabriele.vivinetto:

In SQL Server Configuration Manager, selezionare il servizio SQL Server interessato, ad esempio:<pre>
SQL Server Configuration Manager (Local)
SQL Server Services

SQL Server (MSSSQLSERVER)
</pre>
* Tasto destro sul nome dell’istanza, Proprietà e selezionare il tab Startup Parameters. Inserire il parametro

-mSQLCMD

* cliccare su Add per aggiungere il parametro. Successivamente cliccare su Apply.

* Riavviare il servizo dell’istanza SQL Server per poter rendere operativo lo stato di “single user mode”.
* Creare il nuovo login

Sqlcmd -Slocalhost

<pre>
CREATE LOGIN NewSA WITH PASSWORD = 'Password1234';

ALTER SERVER ROLE sysadmin ADD MEMBER NewSA

GO

EXIT
</pre>

* Togliere il parametro -mSQLCMD che avevamo aggiunto tramite SQL Server Configuration Manager sulla sezione Startup Parameters.
* Riavviamo quindi l’istanza.
* Proviamo la connessione tramite SSMS con la nuova utenza creata CASE SENSITIVE

== Riferimenti ==

* https://www.datamaze.it/blog/il-blog-di-datamaze-5/come-recuperare-l-utenza-sa-in-sql-server-151

Creare un nuovo utente sa in SQL Server senza conoscere le credenziali

2026-01-29T08:45:48Z

Gabriele.vivinetto: Created page with "In SQL Server Configuration Manager, selezionare il servizio SQL Server interessato. * Tasto destro sul nome dell’istanza, Proprietà e selezionare il tab Startup Parameters. Inserire il parametro -mSQLCMD * cliccare su Add per aggiungere il parametro. Successivamente cliccare su Apply. * Riavviare il servizo dell’istanza SQL Server per poter rendere operativo lo stato di “single user mode”. * Creare il nuovo login Sqlcmd -Slocalhost <pre> CREATE LOGIN..."

In SQL Server Configuration Manager, selezionare il servizio SQL Server interessato.

* Tasto destro sul nome dell’istanza, Proprietà e selezionare il tab Startup Parameters. Inserire il parametro

-mSQLCMD

* cliccare su Add per aggiungere il parametro. Successivamente cliccare su Apply.

* Riavviare il servizo dell’istanza SQL Server per poter rendere operativo lo stato di “single user mode”.
* Creare il nuovo login

Sqlcmd -Slocalhost

<pre>
CREATE LOGIN NewSA WITH PASSWORD = 'Password1234';

ALTER SERVER ROLE sysadmin ADD MEMBER NewSA

GO

EXIT
</pre>

* Togliere il parametro -mSQLCMD che avevamo aggiunto tramite SQL Server Configuration Manager sulla sezione Startup Parameters.
* Riavviamo quindi l’istanza.
* Proviamo la connessione tramite SSMS con la nuova utenza creata CASE SENSITIVE

== Riferimenti ==

* https://www.datamaze.it/blog/il-blog-di-datamaze-5/come-recuperare-l-utenza-sa-in-sql-server-151

SQLServer

2026-01-29T08:41:09Z

Gabriele.vivinetto:

* [[Aggiornamento di SQL Server]]
* [[Creare un nuovo utente sa in SQL Server senza conoscere le credenziali]]

Upgade da Debian 11 Bulseye a Debian 12 Bookworm

2026-01-26T17:11:03Z

Gabriele.vivinetto: Created page with " sudo sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list sudo sed -i 's/non-free/non-free non-free-firmware/g' /etc/apt/sources.list sudo sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list.d/* apt update && apt dist-upgrade -d apt install apt apt install linux-image-amd64 apt dist-upgrade"

Debian 12 Bookworm

2026-01-26T17:06:52Z

Gabriele.vivinetto: Created page with "Upgade da Debian 11 Buster a Debian 12 Bookworm"

[[Upgade da Debian 11 Buster a Debian 12 Bookworm]]

Debian

2026-01-26T17:06:19Z

Gabriele.vivinetto:

==Distribuzioni==
*[[Sarge]]
*[[Etch]]
*[[Lenny]]
*[[Squeeze]]
*[[Wheezy]]
*[[Jessie]]
*[[Stretch]]
*[[Buster]]
*[[Bullseye]]
*[[Debian 12 Bookworm]]
*[[Trixie]]

==Argomenti Generici==

*[[Acpi]]
*[[Apt]]
*[[Cambiare il font della console in Debian]]
*[[Cambiare il layout di tastiera di default in Debian]]
*[[Cambiare l'editor di sistema di default]]
*[[Cambiare la Timezone di default in Debian]]
*[[Cambiare la lingua di default in Debian]]
*[[Clonare macchine Windows in rete con Partimage]]
*[[Configurazione di un UPS]]
*[[Creare un LiveCD Debian]]
*[[Creazione di un mirror PUSH]]
*[[Fai]]
*[[Grub]]
*[[Impostazione corretta della lingua in Debian]]
*[[Installazione di Debian da periferica USB]]
*[[Installazione di Debian da remoto via rete]]
*[[Installazione di Debian su Hard Disk superiori a 3Tb]]
*[[Installazione di Debian via PXE da server TFTP]]
*[[Installazione di Debian via SSH]]
*[[Installazione software di supporto HP Proliant per Debian]]
*[[Java]]
*[[Logging degli initscripts]]
*[[Migrazione di Debian da 32 a 64 bit]]
*[[Moduli]]
*[[Networking]]
*[[Utilizzare la RAM superiore ai 4Gb in Debian]]
*[[Resettare la password di root in Debian]]
*[[sysv-rc]]
*[[Visualizzare l'indirizzo IP di una macchina sulla schermata di login tramite /etc/issue]]
*[[Effettuare il dist-upgrade di debian con poco spazio]]
*[[UEFI]]

Configurazione di DMARC

2026-01-24T17:29:43Z

Gabriele.vivinetto:

* DMARC is a line of code that goes into your DNS TXT record
* Before DMARC: setup SPF and DKIM

* Create the email account that will receive the xml rejected reports

dmarc-reports@example.com

* Create the TXT Record

Name: _dmarc.example.com

Value: v=DMARC1; p=quarantine; rua=<nowiki>mailto:dmarc-reports@example.com</nowiki>; ruf=<nowiki>mailto:dmarc-reports@example.com</nowiki>; fo=1;

* Verificarlo;

host -t txt _dmarc.example.com

* In seguito aggiornare il record a:

v=DMARC1; p=reject; rua=<nowiki>mailto:dmarc-reports@example.com</nowiki>; ruf=<nowiki>mailto:dmarc-reports@example.com</nowiki>; fo=1;

== Riferimenti ==

* [https://first2host.co.uk/blog/configure-spf-dkim-dmarc-on-second-postfixadmin-server/ Configure SPF, DKIM & DMARC on Second PostFixAdmin Server - First2Host]

Aggiornamento di record DNS in Technitium DNS

2026-01-23T14:56:18Z

Gabriele.vivinetto:

Con lo script:<pre>
#!/bin/bash

# 1. Controllo che la variabile TOKEN sia definita e non vuota
if [ -z "$TOKEN" ]; then
echo "ERRORE: La variabile d'ambiente \$TOKEN non è definita."
echo "Esegui: export TOKEN='tuo_token_qui' prima di lanciare lo script."
exit 1
fi

# Controllo parametri
if [ "$#" -ne 3 ]; then
echo "Utilizzo: $0 <fqdn> <vecchio_ip> <nuovo_ip>"
echo "Esempio: $0 test.example.com 1.2.3.4 5.6.7.8"
exit 1
fi

FQDN=$1
OLD_IP=$2
NEW_IP=$3

# Estrazione del dominio (ultime due parti: es. studio-mauri.it)
DOMAIN=$(echo "$FQDN" | awk -F. '{print $(NF-1)"."$NF}')

echo "--- Esecuzione Update Technitium ---"
echo "Zona: $DOMAIN"
echo "Record: $FQDN"
echo "IP: $OLD_IP -> $NEW_IP"
echo "------------------------------------"

curl -ks \
"https://dns1.rvmgroup.it/api/zones/records/update\
?token=$TOKEN\
&domain=$FQDN\
&zone=$DOMAIN\
&type=A\
&value=$OLD_IP\
&newValue=$NEW_IP" | jq
</pre>Si possono aggiornare record DNS indicando esattamente l vecchio valore ed il nuovo, ad esempio: se si vuole cambiare

mx1.example.com da 1.2.3.4 a 5.6.7.8
export TOKEN="7dd309b596ece532a586f963f7e1e9ae9854fa3791ea2c02c3c82a6ef30f763c

<pre>curl -ks \
"https://dns1.rvmgroup.it/api/zones/records/update\
?token=$TOKEN\
&domain=mx2.example.com\
&zone=example.com\
&type=A\
&value=1.2.3.4\
&newValue=5.6.7.8" | jq</pre>Se il valore vecchio non coincide, fallisce.

Aggiornamento di record DNS in Technitium DNS

2026-01-23T13:47:27Z

Gabriele.vivinetto: Created page with "Si possono aggiornare record DNS indicando esattamente l vecchio valore ed il nuovo, ad esempio: se si vuole cambiare mx1.example.com da 1.2.3.4 a 5.6.7.8 export TOKEN="7dd309b596ece532a586f963f7e1e9ae9854fa3791ea2c02c3c82a6ef30f763c <pre>curl -ks \ "https://dns1.rvmgroup.it/api/zones/records/update\ ?token=$TOKEN\ &domain=mx2.example.com\ &zone=example.com\ &type=A\ &value=1.2.3.4\ &newValue=5.6.7.8" | jq</pre>Se il valore vecchio non coincide, fallisce."

Si possono aggiornare record DNS indicando esattamente l vecchio valore ed il nuovo, ad esempio: se si vuole cambiare

mx1.example.com da 1.2.3.4 a 5.6.7.8
export TOKEN="7dd309b596ece532a586f963f7e1e9ae9854fa3791ea2c02c3c82a6ef30f763c

<pre>curl -ks \
"https://dns1.rvmgroup.it/api/zones/records/update\
?token=$TOKEN\
&domain=mx2.example.com\
&zone=example.com\
&type=A\
&value=1.2.3.4\
&newValue=5.6.7.8" | jq</pre>Se il valore vecchio non coincide, fallisce.

Technitium DNS

2026-01-23T13:44:06Z

Gabriele.vivinetto:

* [[Importazione di zone DNS in Technitium DNS]]
* [[Aggiornamento di record DNS in Technitium DNS]]

Configurazione HP ILO da command line Linux

2026-01-20T18:45:23Z

Gabriele.vivinetto: /* Articolo Originale */

* Installare IPMI Tools:

apt install openipmi ipmitool

* Su debian Bookworm, scaricare un file mancante, altrimenti si ottiene l'errore "IANA PEN registry open failed: No such file or directory":

wget -O /usr/share/misc/enterprise-numbers.txt <nowiki>https://jff.email/cgit/ipmitool.git/plain/debian/enterprise-numbers.txt?h=debian/1.8.19-5</nowiki>

* Stampare la configurazione:

ipmitool lan print

* Impostare i parametri:
<pre>
ipmitool lan set 1 ipsrc static
ipmitool lan set 1 ipaddr 192.168.6.192
ipmitool lan set 1 netmask 255.255.255.0
ipmitool lan set 1 defgw ipaddr 192.168.6.254
</pre>

* Se necessario, resettare l'ILO:

ipmitool mc reset cold

== Riferimenti ==

* [https://dev-random.net/configuring-hp-ilo-through-linux-automatically/ Configuring HP iLO through Linux automatically - /dev/random]
* [https://forum.proxmox.com/threads/ipmi-tool-error-after-v8-upgrade.129334/ [SOLVED] - IPMI Tool error after v8 upgrade | Proxmox Support Forum]

== Articolo Originale ==
<pre>
Configuring HP iLO through Linux automatically

1 Reply

We only use HP servers and we get more and more every week. Someone has to keep track of all those servers and be able to configure them using iLO in case of a disaster
Installation almost runs automatically, except for iLO configuration.

I have to first find the iLO ip, then login to the web interface, create users, set static IP and what not. It takes time, a lot of it.

If only there was some way to automate it without having to use HP’s software.. but wait, THERE IS!
I already posted how to scan for all HP ILO devices in your subnet, but the basics in the following post on how to configure iLO from your guest Linux OS might make everything a little easier for the sysadmins out there

How to configure HP iLO in Linux

First I will show you the useful commands and an example output for each, and then how to automate the configuration of your HP iLO interface using bash scripting
The script for configuring iLO automatically will be included at the end of this post
Needed packages:

OpenIPMI OpenIPMI-libs OpenIPMI-tools

These packages can be installed through your favorite package manager, below you’ll see the defaults in Debian and CentOS/RHEL

Debian:

apt-get install OpenIPMI OpenIPMI-libs OpenIPMI-tools

CentOS/RHEL:

yum install OpenIPMI OpenIPMI-libs OpenIPMI-tools

Once you got those installed, you can move on and configure or fetch info from iLO through the guest Linux

Get the serial number of the server

Getting the serialnumber might be useful, in case you need to log it to a inventory database, or just need the serial number for a warranty call. This is an easy and quick way to find it, without even logging into iLO.

ipmitool fru | grep Serial

Sample output:
Chassis Serial : CZAAAAAAAA
Board Serial : CZAAAAAAAA
Product Serial : CAAAAAAAAA
Serial Number : 0BBBBBB
Get network settings configured on the HP iLO port

Maybe you just want to find the DHCP address of the HP iLO controller? you can do this easily, without having to scan the entire network.

ipmitool lan print

Example output:

Set in Progress : Set Complete Auth Type Support : IP Address Source : DHCP Address IP Address : 123.123.123.123 Subnet Mask : 255.255.255.0 MAC Address : de:ad:be:ef:ca:fe BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled Default Gateway IP : 123.123.123.1 802.1q VLAN ID : Disabled 802.1q VLAN Priority : 0 Cipher Suite Priv Max : Not Available

Restart iLO interface

If you have any problems connecting to the HP ILO controller, you might need to restart it. But you don’t want to restart the entire server because your have to unplug the power to restart iLO. Nobody wants that on a production server! You can initialize a restart of ILO only by running the below command. This way your server stays online, while doing it. It has saved my butt a couple of times.
Remember these two commands will not reboot the OS running on the server, only iLO
For a cold reset (forcefully, in case iLO is not responding in any way including echo requests/ping) use the following:

ipmitool mc reset cold

For a warm reset (in case iLO IS responding) use the following:

ipmitool mc reset warm

Configure network to static ip on the HP iLO port

Without logging into the web interface, you can still set a static IP address to the HP iLO interface using the below commands. Replace the IP, subnet mask and default gateway with what you need it to be.

[root@server ~]# ipmitool lan set 1 ipsrc static

[root@server ~]# ipmitool lan set 1 ipaddr 192.168.1.211

[root@server ~]# ipmitool lan set 1 netmask 255.255.255.0

[root@server ~]# ipmitool lan set 1 defgw ipaddr 192.168.1.1

Configuring users

Configuring users might also come in handy. By default there is only the “Administrator” user with a password located on a sticker or elsewhere physically on the server.

Create a user with admin rights.

To create a user with same rights as the “Administrator” user, use the following. This user will be able to do everything in iLO.
Replace “admin” with the username you want.

In case your create multiple users, you have to increment the number “2” with +1 every time. so the second user you create will have ID 3, and the third, ID 4.

[root@server ~]# ipmitool user set name 2 admin

[root@server ~]# ipmitool user set password 2 Password for user 2: Password for user 2:

[root@server ~]# ipmitool channel setaccess 1 2 link=on ipmi=on callin=on privilege=4

[root@server ~]# ipmitool user enable 2

Create user with user monitoring rights

If a user should only be used for querying sensor data, for example a user for Nagios, Zabbix or other monitoring software, a custom privilege level can be setup for that. This user can not do any changes to the server through iLO. A user named “monitor” will be created for this in the following example:

[root@server ~]# ipmitool user set name 3 monitor

[root@server ~]# ipmitool user set password 3 Password for user 3: Password for user 3:

[root@server ~]# ipmitool channel setaccess 1 3 link=on ipmi=on callin=on privilege=2

[root@server ~]# ipmitool user enable 3

The importance of the various privilege numbers will be displayed when ipmitool channel is called without any additional parameters:

[root@server ~]# ipmitool channel Channel Commands: authcap <channel number> <max privilege>
getaccess <channel number> [user id]
setaccess <channel number> <user id> [callin=on|off] [ipmi=on|off] [link=on|off] [privilege=level]
info [channel number]
getciphers <ipmi | sol> [channel]
Possible privilege levels are:
1 Callback level
2 User level
3 Operator level
4 Administrator level
5 OEM Proprietary level
15 No access
[root@server ~]#

Automatically configure HP iLO using bash

Now you know how to use the commands to configure the basic stuff in your iLO controller manually. But what about doing this automatically when you have new servers coming in every other day that needs to be configured? We can do that using bash scripts.

Below is a script that will set the specified ip address, subnetmask, default gateway and create users if you want to.
Easy to just run after you installed your OS and even automating using puppet or other deployment tools

# !/bin/bash
# Script written by dev-random.net
# Purpose is to automate HP iLO configuration
# Feel free to use this script however you like, as long as you leave these top comments

printhelp() { echo echo "-i <static ip to set> example: 192.168.1.10" echo "-s <static subnet mask to set> example: 255.255.255.0, required if -i is set" echo "-g <static gatewat to set> example: 192.168.1.1, required if -i is set" echo "-a <username for new admin user> example: admin, dont use if no user should be created" echo "-p <password for admin user>, required if -a is set, enclose in \"\" if password contains spaces" echo "-m <username for read-only user>, example: monitor" echo "-o <password for read-only user>, required if -m is set, enclose in \"\" if password contains spaces" echo "-y add this to the command to actually do the changes, else the script will just output what you typed in the parameters" echo exit 1 }

# Print help if no parameters where set

if (($# == 0)); then printhelp fi

# Get parameters

while getopts "i:s:g:a:p:m:o:hy" opt; do case $opt in i) # IP to set IP="$OPTARG" ;; s) # Subnetmask to set SUBNETMASK="$OPTARG" ;; g) # Gatway to set GATEWAY="$OPTARG" ;; a) # New admin username ADMINUSERNAME="$OPTARG" ;; p) # New admin password ADMINPASSWORD="$OPTARG" ;; m) # New read-only users username USERNAME="$OPTARG" ;; o) # New read-only users password PASSWORD="$OPTARG" ;; h) # Print help printhelp ;; y) # Just do it, no need to press any key to continue DOIT=1 ;; \?) # Default if option is not known printhelp ;; # Error if parameter was triggered without value echo "Option -$opt requires an argument" printhelp ;; esac done echo # Print empty line

# Check if we have the needed required software installed
# required packages: OpenIPMI OpenIPMI-libs OpenIPMI-tools

if [ `which ipmitool &>/dev/null ; echo $?` -ne 0 ] ; then echo "ipmitool not available, please install requirements:" echo "required packages: OpenIPMI OpenIPMI-libs OpenIPMI-tools" echo "See https://dev-random.net/configuring-and-controlling-hp-ilo-through-linux for details" exit 2 fi

# print serial number, just because we can and then you dont have to do it manually in case you need it

ipmitool fru | grep Serial echo #print empty line

# Check if IP has to be set

if [[ "$IP"]] && [[ "$SUBNETMASK"]] && [[ "$GATEWAY"]] ; then echo "IP: $IP" echo "Subnetmask: $SUBNETMASK" echo "Gateway: $GATEWAY" if [[ $DOIT]] ; then echo "Setting ip" ipmitool lan set 1 ipsrc static ipmitool lan set 1 ipaddr $IP ipmitool lan set 1 netmask $SUBNETMASK ipmitool lan set 1 defgw ipaddr $GATEWAY echo # print empty line fi fi

# Check if admin user has to be created

if [[ "$ADMINUSERNAME"]] && [[ "$ADMINPASSWORD"]] ; then echo "Admin username: $ADMINUSERNAME" echo "Admin password: $ADMINPASSWORD" if [[ $DOIT]] ; then echo "Creating admin user" ipmitool user set name 2 $ADMINUSERNAME ipmitool user set password 2 $ADMINPASSWORD ipmitool channel setaccess 1 2 link=on ipmi=on callin=on privilege=4 ipmitool user enable 2 echo # print empty line fi fi

# Check if read-only user has to be created

if [[ "$USERNAME"]] && [[ "$PASSWORD"]] ; then echo "Read-only username: $USERNAME" echo "Read-only user password: $PASSWORD" if [[ $DOIT]] ; then echo "Creating read-only user" ipmitool user set name 3 $USERNAME ipmitool user set password 3 $PASSWORD ipmitool channel setaccess 1 3 link=on ipmi=on callin=on privilege=2 ipmitool user enable 3 echo # print empty line fi fi

# If -y was set

if [[ $DOIT]] ; then # Warm restart iLO echo "Restarting iLO, it will be accessible in a couple of minutes using the new IP address (if changed)." ipmitool mc reset warm else # If -y was not set, then ask for it to do the changes echo # print empty line echo "add -y to the command to make the changes, this run only showed you the settings you entered so you can make sure they are correct" fi echo # print empty line exit 0
</pre>

Correggere l'errore the listen ... http2 directive is deprecated, use the http2 directive instead in nginx proxy manager

2026-01-19T18:18:23Z

Gabriele.vivinetto:

Se all'avvio si vede nei log:
nginx-app | nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/12.conf:19
eseguire:<pre>docker compose exec nginx.crodocker01.croalliance.priv-app \
/bin/bash -c "
cd /data/nginx/proxy_host &&
sed -i 's/listen 443 ssl http2;/listen 443 ssl;\nhttp2 on;/g' *.conf &&
sed -i '/^listen \[::\]:443 ssl http2;/s/ http2//' *.conf " \
| tee -a update.log</pre><pre>
docker compose exec nginx.crodocker01.croalliance.priv-app \
/bin/bash -c "
cd /data/nginx/redirection_host &&
sed -i 's/listen 443 ssl http2;/listen 443 ssl;\nhttp2 on;/g' *.conf &&
sed -i '/^listen \[::\]:443 ssl http2;/s/ http2//' *.conf " \
| tee -a update.log
</pre>In pratica cambia:<pre>
listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443 ssl http2;
</pre>in:<pre>
listen 80;
listen [::]:80;

listen 443 ssl;
http2 on;
listen [::]:443 ssl;
</pre>

== Riferimenti ==

* [https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4060 use the "http2" directive instead warning · Issue #4060 · NginxProxyManager/nginx-proxy-manager]

Guacamole

2026-01-19T17:30:59Z

Gabriele.vivinetto:

*[[Installazione di Guacamole con Docker]]
*[[Resettare la password di un utente Guacamole]]
*[[Resettare la chiave TOTP in Guacamole]]
*[[Branding della login page di Guacamole]]

docker logs guacamole-guacd

* Per aprire menu azioni
CTRL-ALT-SHIFT

* Se non si collega a RDP:
[x] ignore certificate
* Se non si collega a SSH
adding “HostKeyAlgorithms +ssh-rsa” to the end of /etc/ssh/sshd_config on the Ubuntu machine and restart sshd.

=Riferimenti=

*[https://www.linode.com/docs/guides/installing-apache-guacamole-on-ubuntu-and-debian/ How to Install Apache Guacamole on Ubuntu and Debian | Linode]
*[https://www.linode.com/docs/guides/installing-apache-guacamole-through-docker/ How to Install Apache Guacamole through Docker | Linode]
*[https://guacamole.apache.org/doc/gug/totp-auth.html TOTP two-factor authentication — Apache Guacamole Manual v1.4.0]
*[https://rdr-it.com/tips/guacamole-reverse-proxy-apache-exemple/ Guacamole : Reverse proxy Apache – Exemple - RDR-IT]
*[https://frigi.ch/en/2021/07/install-guacamole-on-docker-with-traefik-and-2fa/ Install Guacamole on Docker with Traefik and 2FA | My boring Blog]
*[https://www.reddit.com/r/qnap/comments/muahjo/part_2_how_to_install_guacamole_in_docker_with/ (10) Part 2: How To install Guacamole in Docker with 2FA using MariaDB and Apache Reverse Proxy : qnap]
*[https://guacamole.apache.org/doc/gug/guacamole-docker.html#the-guacamole-docker-image Installing Guacamole with Docker — Apache Guacamole Manual v1.4.0]
*[https://guacamole.apache.org/doc/gug/using-guacamole.html#file-transfer Using Guacamole — Apache Guacamole Manual v1.4.0]
*[https://stackoverflow.com/questions/68458381/guacamole-rdp-wont-connect Guacamole RDP won't connect - Stack Overflow]
*[https://www.howtoforge.com/how-to-install-apache-guacamole-on-debian-11/ How to Install Apache Guacamole on Debian 11]
*[https://andymelton.net/2021/11/30/setup-an-apache-guacamole-server-on-debian-11-bulls-eye/ Setup an Apache Guacamole Server on Debian 11 “Bulls Eye” | AndyMelton.net]

Resettare la chiave TOTP in Guacamole

2026-01-19T17:27:31Z

Gabriele.vivinetto: /* Manualmente */

== Con Script ==
* C'è uno script: [https://iriarte.it/index.php/2021/11/02/resetting-guacamole-otp-for-an-user/ Resetting Guacamole OTP for an user | Doing the blog thing]

== Manualmente ==
* Lanciare Mysql nel container docker del DB:

docker compose exec remote.metrica.it-db bash -c 'mariadb -u$MARIADB_USER -p$MARIADB_PASSWORD guacamole_db'
* Identificare l'ID dello username da modificare:

SELECT user_id FROM guacamole_user INNER JOIN guacamole_entity ON guacamole_entity.entity_id = guacamole_user.entity_id WHERE guacamole_entity.name = 'guacadmin';

+---------+| user_id |+---------+| 1 |+---------+
* Identificato l'ID, resettare il flag guac-totp-key-confirmed per quello user_id

UPDATE guacamole_user_attribute SET attribute_value='false' WHERE attribute_name = 'guac-totp-key-confirmed' and user_id = '1';

== Riferimenti ==

* [https://forum.cloudron.io/topic/5051/resetting-2fa-for-guacamole?_=1727711714510 Resetting 2FA for Guacamole | Cloudron Forum]

* [https://www.mogilowski.net/2020/05/06/two-factor-authentication-with-guacamole-1-1-0-part-4/ Two-factor authentication with Guacamole 1.1.0 (Part 4) – Sebastian Mogilowski's Blog]

Attivazione di prodotti Microsoft con KMS

2026-01-16T11:28:51Z

Gabriele.vivinetto: /* Attivazione Windows Server */

=Installazione server KMS con docker=

* https://wind4.github.io/vlmcsd/

<pre>
cat > docker-compose.yml <<EOFile
version: '3'
services:
app:
container_name: vlmcsd
image: mikolatero/vlmcsd
restart: unless-stopped
ports:
- '1688:1688'
EOFile
</pre>

docker compose up

= Attivazione WIN 10/11 PRO, WIN2K8R2 STD, WIN7 PRO=

* Comandi comuni

cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

* Windows 10-11

cscript.exe //NoLogo slmgr.vbs -ipk W269N-WFGWX-YVC9B-4J6C9-T83GX

* Windows 2008R2 Standard

cscript.exe //NoLogo slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC

* Windows Seven Pro
cscript.exe //NoLogo slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

* Proseguire

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Riferimenti ===
* https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/get-started/kms-client-activation-keys.md
* [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Key Management Services (KMS) client activation and product keys for Windows Server and Windows | Microsoft Learn]

=Attivazione Windows Server=

=== Installazione da ISO Evaluation ===

* We need to use DISM to change the product version/edition

* Open an elevated command prompt
* Get a list of available version upgrade paths by typing:

DISM.exe /Online /Get-TargetEditions

* Then upgrade to the listed edition by typing:

DISM /Online /Set-Edition:<TargetEdition> /ProductKey:<Product Key from Below Table> /AcceptEula

* '''BE SURE TO REBOOT before proceeding !!!'''

=== Installazione da ISO Retail ===
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

cscript.exe //NoLogo slmgr.vbs -ipk <Product Key from Below Table>

=== [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Product Key Table] ===
<pre>
LICENZA CD-KEY
Windows Server 2025 Standard TVRH6-WHNXV-R9WG3-9XRFY-MY832
Windows Server 2025 Datacenter D764K-2NDRG-47T6Q-P8T8W-YP6DF
Windows Server 2025 Datacenter Azure Edition XGN3F-F394H-FD2MY-PP6FD-8MCRC
Windows Server 2022 Standard VDYBN-27WPP-V4HQT-9VMD4-VMK7H
Windows Server 2022 Datacenter WX4NM-KYWYW-QJJR4-XV3QB-6VM33
Windows Server 2022 Datacenter Azure Edition NTBV8-9K7Q8-V27C6-M2BTV-KHMXV
Windows Server 2019 Standard (SAC v1809) N2KJX-J94YW-TQVFB-DG9YT-724CC
Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C
Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Datacenter (SAC v1809) 6NMRW-2C8FM-D24W7-TQWMY-CWH2D
Windows Server 2019 Azure Core FDNH6-VW9RW-BXPJ7-4XTYG-239TB
Windows Server 2019 ARM64 GRFBW-QNDC4-6QBHG-CCK3B-2PR88
Windows Server 2016 Standard WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2016 Standard (SAC v1803) PTXN8-JFHJM-4WC78-MPCBR-9W4KR
Windows Server 2016 Standard (SAC v1709) DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4
Windows Server 2016 Essentials JCKRF-N37P4-C2D82-9YXRT-4M63B
Windows Server 2016 Datacenter (SAC v1803) 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG
Windows Server 2016 Datacenter (SAC v1709) 6Y6KB-N82V8-D8CQV-23MJW-BWTG6
Windows Server 2016 Datacenter CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Cloud Storage QN4C6-GBJD2-FB422-GHWJK-GJG2R
Windows Server 2016 Azure Core VP34G-4NPPG-79JTQ-864T4-R3MQX
Windows Server 2016 ARM64 K9FYF-G6NCK-73M32-XMVPY-F9DRR

</pre>

=== Parte comune ===
*Proseguire
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Troubleshooting ===
If an error occurred while activating Windows Server:
Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F069' to display the error text.

The reason is that I have an evaluation version of Windows Server 2022 installed. First, you need to convert it to a Standard version according to this article:

dism /online /set-edition:serverstandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula

Then I can activate my Windows instance on the KMS host.

=== Riferimenti ===
* [https://www.aidenwebb.com/posts/how-to-fix-server-2019-activation-error-run-slui.exe-0x2a-0xc004f069/ How to Fix Server 2019 Activation Error: Run “slui.exe 0x2a 0xC004F069” | Aiden Arnkels-Webb]

=Attivazione Office 2019 Pro Plus =

* https://github.com/Wind4/vlmcsd/issues/20

I have one that works for office 2019. But I do NOT know why it works.
cscript "%ProgramFiles(x86)%\Microsoft Office\Office16\ospp.vbs" /dstatus
with the following output

LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 1601-01-01
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004F040 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights.
REMAINING GRACE: 179 days (259199 minute(s) before expiring)

* install volume licensing SKUs for office 2019

<pre>
@echo off
:ADMIN
openfiles >nul 2>nul ||(
echo CreateObject^("Shell.Application"^).ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs"
"%temp%\getadmin.vbs" >nul 2>&1
goto:eof
)
del /f /q "%temp%\getadmin.vbs" >nul 2>nul

for /f "tokens=6 delims=[]. " %%G in ('ver') do set win=%%G

setlocal

pushd "%~dp0"
Title Office 2019 Retail to Volume License Converter

rem SET OfficePath=%ProgramFiles%\Microsoft Office
SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" (
echo Could not find the license files for Office 2019!
pause
goto :eof
)

echo Press Enter to start VL-Conversion...
echo.
pause
echo.
cd /D "%SystemRoot%\System32"

if %win% GEQ 9200 (
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)
if %win% LSS 9200 (
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)

cscript "%OfficePath%\Office16\ospp.vbs" /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript "%OfficePath%\Office16\ospp.vbs" /act

echo.
echo Retail to Volume License conversion finished.
echo.
pause
</pre>

* Turn off KMS Client Online AVS Valdation
<pre>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Software Protection Platform]
"NoGenTicket"=dword:00000001
</pre>

* Activate
<pre>
cd "\Program Files\Microsoft Office\Office16"
cd "\Program Files (x86)\Microsoft Office\Office16"
cscript ospp.vbs /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript ospp.vbs /sethst:kms.example.com
cscript ospp.vbs /act
cscript ospp.vbs /dstatusall
</pre>

= Office 2021 ProPlus Retail =

* Assicurarsi di aver installato la 2021 ProPlus (non professional) Retail

* Usare lo script
<pre>
@echo off
echo Change kms.example.com to KMS Server IP or Host
pause
REM Change ProgramFiles to ProgramFiles(x86) If install x86 version . Default are x64

Title Converter Office 2021 Retail to Volume And Activate Through KMS Server

set LICPATH=%ProgramFiles%\Microsoft Office\root\Licenses16
set LICPATH1=%ProgramFiles%\Microsoft Office\Office16

cd C:\Windows\System32

cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-bridge-office.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root-bridge-test.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-stil.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\pkeyconfig-office.xrm-ms"
cscript slmgr.vbs /ipk FXYTK-NJJ8C-GB6DW-3DYQT-6F7TH

cscript "%LICPATH1%\ospp.vbs" /sethst:kms.example.com
cscript "%LICPATH1%\ospp.vbs" /act

echo.
echo Finished.
echo.
pause
</pre>

=Riferimenti=

*[https://www.ilsoftware.it/articoli.asp?tag=KMS-cos-e-e-come-funziona-l-attivazione-di-Windows-in-rete-locale_23680 KMS, cos'è e come funziona l'attivazione di Windows in rete locale - IlSoftware.it]
*[https://github.com/Py-KMS-Organization/py-kms Py-KMS-Organization/py-kms: KMS Server Emulator written in Python]
*[https://github.com/FuryGreenwood/FuryKMS FuryGreenwood/FuryKMS: Microsoft Windows and Office KMS Activator]
*[https://github.com/massgravel/Microsoft-Activation-Scripts massgravel/Microsoft-Activation-Scripts: A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, fewer antivirus detection and user-friendliness.]
*[https://massgrave.dev/ index]
*[https://theitbros.com/activate-windows-with-kms-server/ How to Activate Windows with your KMS Server - KMS License Key List]
*[http://blog.51sec.org/2020/05/create-kms-docker-and-use-kms-to.html#point3 Activate Windows/Office (Run KMS Docker / Install KMS) - Cybersecurity Memo]

Attivazione di prodotti Microsoft con KMS

2026-01-16T11:28:13Z

Gabriele.vivinetto: /* Installazione da ISO Retail */

=Installazione server KMS con docker=

* https://wind4.github.io/vlmcsd/

<pre>
cat > docker-compose.yml <<EOFile
version: '3'
services:
app:
container_name: vlmcsd
image: mikolatero/vlmcsd
restart: unless-stopped
ports:
- '1688:1688'
EOFile
</pre>

docker compose up

= Attivazione WIN 10/11 PRO, WIN2K8R2 STD, WIN7 PRO=

* Comandi comuni

cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

* Windows 10-11

cscript.exe //NoLogo slmgr.vbs -ipk W269N-WFGWX-YVC9B-4J6C9-T83GX

* Windows 2008R2 Standard

cscript.exe //NoLogo slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC

* Windows Seven Pro
cscript.exe //NoLogo slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

* Proseguire

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Riferimenti ===
* https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/get-started/kms-client-activation-keys.md
* [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Key Management Services (KMS) client activation and product keys for Windows Server and Windows | Microsoft Learn]

=Attivazione Windows Server=

=== Installazione da ISO Evaluation ===

* We need to use DISM to change the product version/edition

* Open an elevated command prompt
* Get a list of available version upgrade paths by typing:

DISM.exe /Online /Get-TargetEditions

* Then upgrade to the listed edition by typing:

DISM /Online /Set-Edition:<TargetEdition> /ProductKey:<Product Key from Below Table> /AcceptEula

=== Installazione da ISO Retail ===
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

cscript.exe //NoLogo slmgr.vbs -ipk <Product Key from Below Table>

* '''BE SURE TO REBOOT before proceeding !!!'''

=== [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Product Key Table] ===
<pre>
LICENZA CD-KEY
Windows Server 2025 Standard TVRH6-WHNXV-R9WG3-9XRFY-MY832
Windows Server 2025 Datacenter D764K-2NDRG-47T6Q-P8T8W-YP6DF
Windows Server 2025 Datacenter Azure Edition XGN3F-F394H-FD2MY-PP6FD-8MCRC
Windows Server 2022 Standard VDYBN-27WPP-V4HQT-9VMD4-VMK7H
Windows Server 2022 Datacenter WX4NM-KYWYW-QJJR4-XV3QB-6VM33
Windows Server 2022 Datacenter Azure Edition NTBV8-9K7Q8-V27C6-M2BTV-KHMXV
Windows Server 2019 Standard (SAC v1809) N2KJX-J94YW-TQVFB-DG9YT-724CC
Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C
Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Datacenter (SAC v1809) 6NMRW-2C8FM-D24W7-TQWMY-CWH2D
Windows Server 2019 Azure Core FDNH6-VW9RW-BXPJ7-4XTYG-239TB
Windows Server 2019 ARM64 GRFBW-QNDC4-6QBHG-CCK3B-2PR88
Windows Server 2016 Standard WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2016 Standard (SAC v1803) PTXN8-JFHJM-4WC78-MPCBR-9W4KR
Windows Server 2016 Standard (SAC v1709) DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4
Windows Server 2016 Essentials JCKRF-N37P4-C2D82-9YXRT-4M63B
Windows Server 2016 Datacenter (SAC v1803) 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG
Windows Server 2016 Datacenter (SAC v1709) 6Y6KB-N82V8-D8CQV-23MJW-BWTG6
Windows Server 2016 Datacenter CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Cloud Storage QN4C6-GBJD2-FB422-GHWJK-GJG2R
Windows Server 2016 Azure Core VP34G-4NPPG-79JTQ-864T4-R3MQX
Windows Server 2016 ARM64 K9FYF-G6NCK-73M32-XMVPY-F9DRR

</pre>

=== Parte comune ===
*Proseguire
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Troubleshooting ===
If an error occurred while activating Windows Server:
Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F069' to display the error text.

The reason is that I have an evaluation version of Windows Server 2022 installed. First, you need to convert it to a Standard version according to this article:

dism /online /set-edition:serverstandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula

Then I can activate my Windows instance on the KMS host.

=== Riferimenti ===
* [https://www.aidenwebb.com/posts/how-to-fix-server-2019-activation-error-run-slui.exe-0x2a-0xc004f069/ How to Fix Server 2019 Activation Error: Run “slui.exe 0x2a 0xC004F069” | Aiden Arnkels-Webb]

=Attivazione Office 2019 Pro Plus =

* https://github.com/Wind4/vlmcsd/issues/20

I have one that works for office 2019. But I do NOT know why it works.
cscript "%ProgramFiles(x86)%\Microsoft Office\Office16\ospp.vbs" /dstatus
with the following output

LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 1601-01-01
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004F040 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights.
REMAINING GRACE: 179 days (259199 minute(s) before expiring)

* install volume licensing SKUs for office 2019

<pre>
@echo off
:ADMIN
openfiles >nul 2>nul ||(
echo CreateObject^("Shell.Application"^).ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs"
"%temp%\getadmin.vbs" >nul 2>&1
goto:eof
)
del /f /q "%temp%\getadmin.vbs" >nul 2>nul

for /f "tokens=6 delims=[]. " %%G in ('ver') do set win=%%G

setlocal

pushd "%~dp0"
Title Office 2019 Retail to Volume License Converter

rem SET OfficePath=%ProgramFiles%\Microsoft Office
SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" (
echo Could not find the license files for Office 2019!
pause
goto :eof
)

echo Press Enter to start VL-Conversion...
echo.
pause
echo.
cd /D "%SystemRoot%\System32"

if %win% GEQ 9200 (
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)
if %win% LSS 9200 (
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)

cscript "%OfficePath%\Office16\ospp.vbs" /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript "%OfficePath%\Office16\ospp.vbs" /act

echo.
echo Retail to Volume License conversion finished.
echo.
pause
</pre>

* Turn off KMS Client Online AVS Valdation
<pre>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Software Protection Platform]
"NoGenTicket"=dword:00000001
</pre>

* Activate
<pre>
cd "\Program Files\Microsoft Office\Office16"
cd "\Program Files (x86)\Microsoft Office\Office16"
cscript ospp.vbs /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript ospp.vbs /sethst:kms.example.com
cscript ospp.vbs /act
cscript ospp.vbs /dstatusall
</pre>

= Office 2021 ProPlus Retail =

* Assicurarsi di aver installato la 2021 ProPlus (non professional) Retail

* Usare lo script
<pre>
@echo off
echo Change kms.example.com to KMS Server IP or Host
pause
REM Change ProgramFiles to ProgramFiles(x86) If install x86 version . Default are x64

Title Converter Office 2021 Retail to Volume And Activate Through KMS Server

set LICPATH=%ProgramFiles%\Microsoft Office\root\Licenses16
set LICPATH1=%ProgramFiles%\Microsoft Office\Office16

cd C:\Windows\System32

cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-bridge-office.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root-bridge-test.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-stil.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\pkeyconfig-office.xrm-ms"
cscript slmgr.vbs /ipk FXYTK-NJJ8C-GB6DW-3DYQT-6F7TH

cscript "%LICPATH1%\ospp.vbs" /sethst:kms.example.com
cscript "%LICPATH1%\ospp.vbs" /act

echo.
echo Finished.
echo.
pause
</pre>

=Riferimenti=

*[https://www.ilsoftware.it/articoli.asp?tag=KMS-cos-e-e-come-funziona-l-attivazione-di-Windows-in-rete-locale_23680 KMS, cos'è e come funziona l'attivazione di Windows in rete locale - IlSoftware.it]
*[https://github.com/Py-KMS-Organization/py-kms Py-KMS-Organization/py-kms: KMS Server Emulator written in Python]
*[https://github.com/FuryGreenwood/FuryKMS FuryGreenwood/FuryKMS: Microsoft Windows and Office KMS Activator]
*[https://github.com/massgravel/Microsoft-Activation-Scripts massgravel/Microsoft-Activation-Scripts: A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, fewer antivirus detection and user-friendliness.]
*[https://massgrave.dev/ index]
*[https://theitbros.com/activate-windows-with-kms-server/ How to Activate Windows with your KMS Server - KMS License Key List]
*[http://blog.51sec.org/2020/05/create-kms-docker-and-use-kms-to.html#point3 Activate Windows/Office (Run KMS Docker / Install KMS) - Cybersecurity Memo]

Attivazione di prodotti Microsoft con KMS

2026-01-16T11:10:30Z

Gabriele.vivinetto: /* Installazione da ISO Retail */

=Installazione server KMS con docker=

* https://wind4.github.io/vlmcsd/

<pre>
cat > docker-compose.yml <<EOFile
version: '3'
services:
app:
container_name: vlmcsd
image: mikolatero/vlmcsd
restart: unless-stopped
ports:
- '1688:1688'
EOFile
</pre>

docker compose up

= Attivazione WIN 10/11 PRO, WIN2K8R2 STD, WIN7 PRO=

* Comandi comuni

cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

* Windows 10-11

cscript.exe //NoLogo slmgr.vbs -ipk W269N-WFGWX-YVC9B-4J6C9-T83GX

* Windows 2008R2 Standard

cscript.exe //NoLogo slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC

* Windows Seven Pro
cscript.exe //NoLogo slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

* Proseguire

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Riferimenti ===
* https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/get-started/kms-client-activation-keys.md
* [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Key Management Services (KMS) client activation and product keys for Windows Server and Windows | Microsoft Learn]

=Attivazione Windows Server=

=== Installazione da ISO Evaluation ===

* We need to use DISM to change the product version/edition

* Open an elevated command prompt
* Get a list of available version upgrade paths by typing:

DISM.exe /Online /Get-TargetEditions

* Then upgrade to the listed edition by typing:

DISM /Online /Set-Edition:<TargetEdition> /ProductKey:<Product Key from Below Table> /AcceptEula

=== Installazione da ISO Retail ===
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

cscript.exe //NoLogo slmgr.vbs -ipk <Product Key from Below Table>

* '''BE SURE TO REBBOT before proceding !!!'''

=== [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Product Key Table] ===
<pre>
LICENZA CD-KEY
Windows Server 2025 Standard TVRH6-WHNXV-R9WG3-9XRFY-MY832
Windows Server 2025 Datacenter D764K-2NDRG-47T6Q-P8T8W-YP6DF
Windows Server 2025 Datacenter Azure Edition XGN3F-F394H-FD2MY-PP6FD-8MCRC
Windows Server 2022 Standard VDYBN-27WPP-V4HQT-9VMD4-VMK7H
Windows Server 2022 Datacenter WX4NM-KYWYW-QJJR4-XV3QB-6VM33
Windows Server 2022 Datacenter Azure Edition NTBV8-9K7Q8-V27C6-M2BTV-KHMXV
Windows Server 2019 Standard (SAC v1809) N2KJX-J94YW-TQVFB-DG9YT-724CC
Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C
Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Datacenter (SAC v1809) 6NMRW-2C8FM-D24W7-TQWMY-CWH2D
Windows Server 2019 Azure Core FDNH6-VW9RW-BXPJ7-4XTYG-239TB
Windows Server 2019 ARM64 GRFBW-QNDC4-6QBHG-CCK3B-2PR88
Windows Server 2016 Standard WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2016 Standard (SAC v1803) PTXN8-JFHJM-4WC78-MPCBR-9W4KR
Windows Server 2016 Standard (SAC v1709) DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4
Windows Server 2016 Essentials JCKRF-N37P4-C2D82-9YXRT-4M63B
Windows Server 2016 Datacenter (SAC v1803) 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG
Windows Server 2016 Datacenter (SAC v1709) 6Y6KB-N82V8-D8CQV-23MJW-BWTG6
Windows Server 2016 Datacenter CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Cloud Storage QN4C6-GBJD2-FB422-GHWJK-GJG2R
Windows Server 2016 Azure Core VP34G-4NPPG-79JTQ-864T4-R3MQX
Windows Server 2016 ARM64 K9FYF-G6NCK-73M32-XMVPY-F9DRR

</pre>

=== Parte comune ===
*Proseguire
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Troubleshooting ===
If an error occurred while activating Windows Server:
Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F069' to display the error text.

The reason is that I have an evaluation version of Windows Server 2022 installed. First, you need to convert it to a Standard version according to this article:

dism /online /set-edition:serverstandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula

Then I can activate my Windows instance on the KMS host.

=== Riferimenti ===
* [https://www.aidenwebb.com/posts/how-to-fix-server-2019-activation-error-run-slui.exe-0x2a-0xc004f069/ How to Fix Server 2019 Activation Error: Run “slui.exe 0x2a 0xC004F069” | Aiden Arnkels-Webb]

=Attivazione Office 2019 Pro Plus =

* https://github.com/Wind4/vlmcsd/issues/20

I have one that works for office 2019. But I do NOT know why it works.
cscript "%ProgramFiles(x86)%\Microsoft Office\Office16\ospp.vbs" /dstatus
with the following output

LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 1601-01-01
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004F040 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights.
REMAINING GRACE: 179 days (259199 minute(s) before expiring)

* install volume licensing SKUs for office 2019

<pre>
@echo off
:ADMIN
openfiles >nul 2>nul ||(
echo CreateObject^("Shell.Application"^).ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs"
"%temp%\getadmin.vbs" >nul 2>&1
goto:eof
)
del /f /q "%temp%\getadmin.vbs" >nul 2>nul

for /f "tokens=6 delims=[]. " %%G in ('ver') do set win=%%G

setlocal

pushd "%~dp0"
Title Office 2019 Retail to Volume License Converter

rem SET OfficePath=%ProgramFiles%\Microsoft Office
SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" (
echo Could not find the license files for Office 2019!
pause
goto :eof
)

echo Press Enter to start VL-Conversion...
echo.
pause
echo.
cd /D "%SystemRoot%\System32"

if %win% GEQ 9200 (
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)
if %win% LSS 9200 (
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)

cscript "%OfficePath%\Office16\ospp.vbs" /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript "%OfficePath%\Office16\ospp.vbs" /act

echo.
echo Retail to Volume License conversion finished.
echo.
pause
</pre>

* Turn off KMS Client Online AVS Valdation
<pre>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Software Protection Platform]
"NoGenTicket"=dword:00000001
</pre>

* Activate
<pre>
cd "\Program Files\Microsoft Office\Office16"
cd "\Program Files (x86)\Microsoft Office\Office16"
cscript ospp.vbs /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript ospp.vbs /sethst:kms.example.com
cscript ospp.vbs /act
cscript ospp.vbs /dstatusall
</pre>

= Office 2021 ProPlus Retail =

* Assicurarsi di aver installato la 2021 ProPlus (non professional) Retail

* Usare lo script
<pre>
@echo off
echo Change kms.example.com to KMS Server IP or Host
pause
REM Change ProgramFiles to ProgramFiles(x86) If install x86 version . Default are x64

Title Converter Office 2021 Retail to Volume And Activate Through KMS Server

set LICPATH=%ProgramFiles%\Microsoft Office\root\Licenses16
set LICPATH1=%ProgramFiles%\Microsoft Office\Office16

cd C:\Windows\System32

cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-bridge-office.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root-bridge-test.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-stil.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\pkeyconfig-office.xrm-ms"
cscript slmgr.vbs /ipk FXYTK-NJJ8C-GB6DW-3DYQT-6F7TH

cscript "%LICPATH1%\ospp.vbs" /sethst:kms.example.com
cscript "%LICPATH1%\ospp.vbs" /act

echo.
echo Finished.
echo.
pause
</pre>

=Riferimenti=

*[https://www.ilsoftware.it/articoli.asp?tag=KMS-cos-e-e-come-funziona-l-attivazione-di-Windows-in-rete-locale_23680 KMS, cos'è e come funziona l'attivazione di Windows in rete locale - IlSoftware.it]
*[https://github.com/Py-KMS-Organization/py-kms Py-KMS-Organization/py-kms: KMS Server Emulator written in Python]
*[https://github.com/FuryGreenwood/FuryKMS FuryGreenwood/FuryKMS: Microsoft Windows and Office KMS Activator]
*[https://github.com/massgravel/Microsoft-Activation-Scripts massgravel/Microsoft-Activation-Scripts: A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, fewer antivirus detection and user-friendliness.]
*[https://massgrave.dev/ index]
*[https://theitbros.com/activate-windows-with-kms-server/ How to Activate Windows with your KMS Server - KMS License Key List]
*[http://blog.51sec.org/2020/05/create-kms-docker-and-use-kms-to.html#point3 Activate Windows/Office (Run KMS Docker / Install KMS) - Cybersecurity Memo]

Attivazione di prodotti Microsoft con KMS

2026-01-16T11:03:31Z

Gabriele.vivinetto: /* Installazione da ISO Evaluation */

=Installazione server KMS con docker=

* https://wind4.github.io/vlmcsd/

<pre>
cat > docker-compose.yml <<EOFile
version: '3'
services:
app:
container_name: vlmcsd
image: mikolatero/vlmcsd
restart: unless-stopped
ports:
- '1688:1688'
EOFile
</pre>

docker compose up

= Attivazione WIN 10/11 PRO, WIN2K8R2 STD, WIN7 PRO=

* Comandi comuni

cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

* Windows 10-11

cscript.exe //NoLogo slmgr.vbs -ipk W269N-WFGWX-YVC9B-4J6C9-T83GX

* Windows 2008R2 Standard

cscript.exe //NoLogo slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC

* Windows Seven Pro
cscript.exe //NoLogo slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

* Proseguire

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Riferimenti ===
* https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/get-started/kms-client-activation-keys.md
* [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Key Management Services (KMS) client activation and product keys for Windows Server and Windows | Microsoft Learn]

=Attivazione Windows Server=

=== Installazione da ISO Evaluation ===

* We need to use DISM to change the product version/edition

* Open an elevated command prompt
* Get a list of available version upgrade paths by typing:

DISM.exe /Online /Get-TargetEditions

* Then upgrade to the listed edition by typing:

DISM /Online /Set-Edition:<TargetEdition> /ProductKey:<Product Key from Below Table> /AcceptEula

=== Installazione da ISO Retail ===
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

cscript.exe //NoLogo slmgr.vbs -ipk <Product Key from Below Table>

=== [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Product Key Table] ===
<pre>
LICENZA CD-KEY
Windows Server 2025 Standard TVRH6-WHNXV-R9WG3-9XRFY-MY832
Windows Server 2025 Datacenter D764K-2NDRG-47T6Q-P8T8W-YP6DF
Windows Server 2025 Datacenter Azure Edition XGN3F-F394H-FD2MY-PP6FD-8MCRC
Windows Server 2022 Standard VDYBN-27WPP-V4HQT-9VMD4-VMK7H
Windows Server 2022 Datacenter WX4NM-KYWYW-QJJR4-XV3QB-6VM33
Windows Server 2022 Datacenter Azure Edition NTBV8-9K7Q8-V27C6-M2BTV-KHMXV
Windows Server 2019 Standard (SAC v1809) N2KJX-J94YW-TQVFB-DG9YT-724CC
Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C
Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Datacenter (SAC v1809) 6NMRW-2C8FM-D24W7-TQWMY-CWH2D
Windows Server 2019 Azure Core FDNH6-VW9RW-BXPJ7-4XTYG-239TB
Windows Server 2019 ARM64 GRFBW-QNDC4-6QBHG-CCK3B-2PR88
Windows Server 2016 Standard WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2016 Standard (SAC v1803) PTXN8-JFHJM-4WC78-MPCBR-9W4KR
Windows Server 2016 Standard (SAC v1709) DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4
Windows Server 2016 Essentials JCKRF-N37P4-C2D82-9YXRT-4M63B
Windows Server 2016 Datacenter (SAC v1803) 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG
Windows Server 2016 Datacenter (SAC v1709) 6Y6KB-N82V8-D8CQV-23MJW-BWTG6
Windows Server 2016 Datacenter CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Cloud Storage QN4C6-GBJD2-FB422-GHWJK-GJG2R
Windows Server 2016 Azure Core VP34G-4NPPG-79JTQ-864T4-R3MQX
Windows Server 2016 ARM64 K9FYF-G6NCK-73M32-XMVPY-F9DRR

</pre>

=== Parte comune ===
*Proseguire
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Troubleshooting ===
If an error occurred while activating Windows Server:
Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F069' to display the error text.

The reason is that I have an evaluation version of Windows Server 2022 installed. First, you need to convert it to a Standard version according to this article:

dism /online /set-edition:serverstandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula

Then I can activate my Windows instance on the KMS host.

=== Riferimenti ===
* [https://www.aidenwebb.com/posts/how-to-fix-server-2019-activation-error-run-slui.exe-0x2a-0xc004f069/ How to Fix Server 2019 Activation Error: Run “slui.exe 0x2a 0xC004F069” | Aiden Arnkels-Webb]

=Attivazione Office 2019 Pro Plus =

* https://github.com/Wind4/vlmcsd/issues/20

I have one that works for office 2019. But I do NOT know why it works.
cscript "%ProgramFiles(x86)%\Microsoft Office\Office16\ospp.vbs" /dstatus
with the following output

LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 1601-01-01
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004F040 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights.
REMAINING GRACE: 179 days (259199 minute(s) before expiring)

* install volume licensing SKUs for office 2019

<pre>
@echo off
:ADMIN
openfiles >nul 2>nul ||(
echo CreateObject^("Shell.Application"^).ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs"
"%temp%\getadmin.vbs" >nul 2>&1
goto:eof
)
del /f /q "%temp%\getadmin.vbs" >nul 2>nul

for /f "tokens=6 delims=[]. " %%G in ('ver') do set win=%%G

setlocal

pushd "%~dp0"
Title Office 2019 Retail to Volume License Converter

rem SET OfficePath=%ProgramFiles%\Microsoft Office
SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" (
echo Could not find the license files for Office 2019!
pause
goto :eof
)

echo Press Enter to start VL-Conversion...
echo.
pause
echo.
cd /D "%SystemRoot%\System32"

if %win% GEQ 9200 (
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)
if %win% LSS 9200 (
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)

cscript "%OfficePath%\Office16\ospp.vbs" /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript "%OfficePath%\Office16\ospp.vbs" /act

echo.
echo Retail to Volume License conversion finished.
echo.
pause
</pre>

* Turn off KMS Client Online AVS Valdation
<pre>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Software Protection Platform]
"NoGenTicket"=dword:00000001
</pre>

* Activate
<pre>
cd "\Program Files\Microsoft Office\Office16"
cd "\Program Files (x86)\Microsoft Office\Office16"
cscript ospp.vbs /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript ospp.vbs /sethst:kms.example.com
cscript ospp.vbs /act
cscript ospp.vbs /dstatusall
</pre>

= Office 2021 ProPlus Retail =

* Assicurarsi di aver installato la 2021 ProPlus (non professional) Retail

* Usare lo script
<pre>
@echo off
echo Change kms.example.com to KMS Server IP or Host
pause
REM Change ProgramFiles to ProgramFiles(x86) If install x86 version . Default are x64

Title Converter Office 2021 Retail to Volume And Activate Through KMS Server

set LICPATH=%ProgramFiles%\Microsoft Office\root\Licenses16
set LICPATH1=%ProgramFiles%\Microsoft Office\Office16

cd C:\Windows\System32

cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-bridge-office.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root-bridge-test.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-stil.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\pkeyconfig-office.xrm-ms"
cscript slmgr.vbs /ipk FXYTK-NJJ8C-GB6DW-3DYQT-6F7TH

cscript "%LICPATH1%\ospp.vbs" /sethst:kms.example.com
cscript "%LICPATH1%\ospp.vbs" /act

echo.
echo Finished.
echo.
pause
</pre>

=Riferimenti=

*[https://www.ilsoftware.it/articoli.asp?tag=KMS-cos-e-e-come-funziona-l-attivazione-di-Windows-in-rete-locale_23680 KMS, cos'è e come funziona l'attivazione di Windows in rete locale - IlSoftware.it]
*[https://github.com/Py-KMS-Organization/py-kms Py-KMS-Organization/py-kms: KMS Server Emulator written in Python]
*[https://github.com/FuryGreenwood/FuryKMS FuryGreenwood/FuryKMS: Microsoft Windows and Office KMS Activator]
*[https://github.com/massgravel/Microsoft-Activation-Scripts massgravel/Microsoft-Activation-Scripts: A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, fewer antivirus detection and user-friendliness.]
*[https://massgrave.dev/ index]
*[https://theitbros.com/activate-windows-with-kms-server/ How to Activate Windows with your KMS Server - KMS License Key List]
*[http://blog.51sec.org/2020/05/create-kms-docker-and-use-kms-to.html#point3 Activate Windows/Office (Run KMS Docker / Install KMS) - Cybersecurity Memo]

Attivazione di prodotti Microsoft con KMS

2026-01-16T11:01:46Z

Gabriele.vivinetto: /* Installazione da ISO Evaluation */

=Installazione server KMS con docker=

* https://wind4.github.io/vlmcsd/

<pre>
cat > docker-compose.yml <<EOFile
version: '3'
services:
app:
container_name: vlmcsd
image: mikolatero/vlmcsd
restart: unless-stopped
ports:
- '1688:1688'
EOFile
</pre>

docker compose up

= Attivazione WIN 10/11 PRO, WIN2K8R2 STD, WIN7 PRO=

* Comandi comuni

cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

* Windows 10-11

cscript.exe //NoLogo slmgr.vbs -ipk W269N-WFGWX-YVC9B-4J6C9-T83GX

* Windows 2008R2 Standard

cscript.exe //NoLogo slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC

* Windows Seven Pro
cscript.exe //NoLogo slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

* Proseguire

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Riferimenti ===
* https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/get-started/kms-client-activation-keys.md
* [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Key Management Services (KMS) client activation and product keys for Windows Server and Windows | Microsoft Learn]

=Attivazione Windows Server=

=== Installazione da ISO Evaluation ===

* We need to use DISM to change the product version/edition

* Open an elevated command prompt

* Get a list of available version upgrade paths by typing:

DISM.exe /Online /Get-TargetEditions

* Then upgrade to the listed edition by typing:

DISM /Online /Set-Edition:<TargetEdition> /ProductKey:<Product Key from Below Table> /AcceptEula

=== Installazione da ISO Retail ===
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

cscript.exe //NoLogo slmgr.vbs -ipk <Product Key from Below Table>

=== [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Product Key Table] ===
<pre>
LICENZA CD-KEY
Windows Server 2025 Standard TVRH6-WHNXV-R9WG3-9XRFY-MY832
Windows Server 2025 Datacenter D764K-2NDRG-47T6Q-P8T8W-YP6DF
Windows Server 2025 Datacenter Azure Edition XGN3F-F394H-FD2MY-PP6FD-8MCRC
Windows Server 2022 Standard VDYBN-27WPP-V4HQT-9VMD4-VMK7H
Windows Server 2022 Datacenter WX4NM-KYWYW-QJJR4-XV3QB-6VM33
Windows Server 2022 Datacenter Azure Edition NTBV8-9K7Q8-V27C6-M2BTV-KHMXV
Windows Server 2019 Standard (SAC v1809) N2KJX-J94YW-TQVFB-DG9YT-724CC
Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C
Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Datacenter (SAC v1809) 6NMRW-2C8FM-D24W7-TQWMY-CWH2D
Windows Server 2019 Azure Core FDNH6-VW9RW-BXPJ7-4XTYG-239TB
Windows Server 2019 ARM64 GRFBW-QNDC4-6QBHG-CCK3B-2PR88
Windows Server 2016 Standard WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2016 Standard (SAC v1803) PTXN8-JFHJM-4WC78-MPCBR-9W4KR
Windows Server 2016 Standard (SAC v1709) DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4
Windows Server 2016 Essentials JCKRF-N37P4-C2D82-9YXRT-4M63B
Windows Server 2016 Datacenter (SAC v1803) 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG
Windows Server 2016 Datacenter (SAC v1709) 6Y6KB-N82V8-D8CQV-23MJW-BWTG6
Windows Server 2016 Datacenter CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Cloud Storage QN4C6-GBJD2-FB422-GHWJK-GJG2R
Windows Server 2016 Azure Core VP34G-4NPPG-79JTQ-864T4-R3MQX
Windows Server 2016 ARM64 K9FYF-G6NCK-73M32-XMVPY-F9DRR

</pre>

=== Parte comune ===
*Proseguire
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Troubleshooting ===
If an error occurred while activating Windows Server:
Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F069' to display the error text.

The reason is that I have an evaluation version of Windows Server 2022 installed. First, you need to convert it to a Standard version according to this article:

dism /online /set-edition:serverstandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula

Then I can activate my Windows instance on the KMS host.

=== Riferimenti ===
* [https://www.aidenwebb.com/posts/how-to-fix-server-2019-activation-error-run-slui.exe-0x2a-0xc004f069/ How to Fix Server 2019 Activation Error: Run “slui.exe 0x2a 0xC004F069” | Aiden Arnkels-Webb]

=Attivazione Office 2019 Pro Plus =

* https://github.com/Wind4/vlmcsd/issues/20

I have one that works for office 2019. But I do NOT know why it works.
cscript "%ProgramFiles(x86)%\Microsoft Office\Office16\ospp.vbs" /dstatus
with the following output

LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 1601-01-01
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004F040 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights.
REMAINING GRACE: 179 days (259199 minute(s) before expiring)

* install volume licensing SKUs for office 2019

<pre>
@echo off
:ADMIN
openfiles >nul 2>nul ||(
echo CreateObject^("Shell.Application"^).ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs"
"%temp%\getadmin.vbs" >nul 2>&1
goto:eof
)
del /f /q "%temp%\getadmin.vbs" >nul 2>nul

for /f "tokens=6 delims=[]. " %%G in ('ver') do set win=%%G

setlocal

pushd "%~dp0"
Title Office 2019 Retail to Volume License Converter

rem SET OfficePath=%ProgramFiles%\Microsoft Office
SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" (
echo Could not find the license files for Office 2019!
pause
goto :eof
)

echo Press Enter to start VL-Conversion...
echo.
pause
echo.
cd /D "%SystemRoot%\System32"

if %win% GEQ 9200 (
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)
if %win% LSS 9200 (
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)

cscript "%OfficePath%\Office16\ospp.vbs" /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript "%OfficePath%\Office16\ospp.vbs" /act

echo.
echo Retail to Volume License conversion finished.
echo.
pause
</pre>

* Turn off KMS Client Online AVS Valdation
<pre>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Software Protection Platform]
"NoGenTicket"=dword:00000001
</pre>

* Activate
<pre>
cd "\Program Files\Microsoft Office\Office16"
cd "\Program Files (x86)\Microsoft Office\Office16"
cscript ospp.vbs /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript ospp.vbs /sethst:kms.example.com
cscript ospp.vbs /act
cscript ospp.vbs /dstatusall
</pre>

= Office 2021 ProPlus Retail =

* Assicurarsi di aver installato la 2021 ProPlus (non professional) Retail

* Usare lo script
<pre>
@echo off
echo Change kms.example.com to KMS Server IP or Host
pause
REM Change ProgramFiles to ProgramFiles(x86) If install x86 version . Default are x64

Title Converter Office 2021 Retail to Volume And Activate Through KMS Server

set LICPATH=%ProgramFiles%\Microsoft Office\root\Licenses16
set LICPATH1=%ProgramFiles%\Microsoft Office\Office16

cd C:\Windows\System32

cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-bridge-office.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root-bridge-test.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-stil.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\pkeyconfig-office.xrm-ms"
cscript slmgr.vbs /ipk FXYTK-NJJ8C-GB6DW-3DYQT-6F7TH

cscript "%LICPATH1%\ospp.vbs" /sethst:kms.example.com
cscript "%LICPATH1%\ospp.vbs" /act

echo.
echo Finished.
echo.
pause
</pre>

=Riferimenti=

*[https://www.ilsoftware.it/articoli.asp?tag=KMS-cos-e-e-come-funziona-l-attivazione-di-Windows-in-rete-locale_23680 KMS, cos'è e come funziona l'attivazione di Windows in rete locale - IlSoftware.it]
*[https://github.com/Py-KMS-Organization/py-kms Py-KMS-Organization/py-kms: KMS Server Emulator written in Python]
*[https://github.com/FuryGreenwood/FuryKMS FuryGreenwood/FuryKMS: Microsoft Windows and Office KMS Activator]
*[https://github.com/massgravel/Microsoft-Activation-Scripts massgravel/Microsoft-Activation-Scripts: A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, fewer antivirus detection and user-friendliness.]
*[https://massgrave.dev/ index]
*[https://theitbros.com/activate-windows-with-kms-server/ How to Activate Windows with your KMS Server - KMS License Key List]
*[http://blog.51sec.org/2020/05/create-kms-docker-and-use-kms-to.html#point3 Activate Windows/Office (Run KMS Docker / Install KMS) - Cybersecurity Memo]

Attivazione di prodotti Microsoft con KMS

2026-01-16T11:01:11Z

Gabriele.vivinetto: /* Product Key Table */

=Installazione server KMS con docker=

* https://wind4.github.io/vlmcsd/

<pre>
cat > docker-compose.yml <<EOFile
version: '3'
services:
app:
container_name: vlmcsd
image: mikolatero/vlmcsd
restart: unless-stopped
ports:
- '1688:1688'
EOFile
</pre>

docker compose up

= Attivazione WIN 10/11 PRO, WIN2K8R2 STD, WIN7 PRO=

* Comandi comuni

cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

* Windows 10-11

cscript.exe //NoLogo slmgr.vbs -ipk W269N-WFGWX-YVC9B-4J6C9-T83GX

* Windows 2008R2 Standard

cscript.exe //NoLogo slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC

* Windows Seven Pro
cscript.exe //NoLogo slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

* Proseguire

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Riferimenti ===
* https://github.com/MicrosoftDocs/windowsserverdocs/blob/main/WindowsServerDocs/get-started/kms-client-activation-keys.md
* [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Key Management Services (KMS) client activation and product keys for Windows Server and Windows | Microsoft Learn]

=Attivazione Windows Server=

=== Installazione da ISO Evaluation ===

* We need to use DISM to change the product version/edition

* Open an elevated command prompt

* Get a list of available version upgrade paths by typing:

 DISM.exe /Online /Get-TargetEditions

* Then upgrade to the listed edition by typing:

 DISM /Online /Set-Edition:<TargetEdition> /ProductKey:<Product Key from Below Table> /AcceptEula

=== Installazione da ISO Retail ===
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -upk

cscript.exe //NoLogo slmgr.vbs -ipk <Product Key from Below Table>

=== [https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys Product Key Table] ===
<pre>
LICENZA CD-KEY
Windows Server 2025 Standard TVRH6-WHNXV-R9WG3-9XRFY-MY832
Windows Server 2025 Datacenter D764K-2NDRG-47T6Q-P8T8W-YP6DF
Windows Server 2025 Datacenter Azure Edition XGN3F-F394H-FD2MY-PP6FD-8MCRC
Windows Server 2022 Standard VDYBN-27WPP-V4HQT-9VMD4-VMK7H
Windows Server 2022 Datacenter WX4NM-KYWYW-QJJR4-XV3QB-6VM33
Windows Server 2022 Datacenter Azure Edition NTBV8-9K7Q8-V27C6-M2BTV-KHMXV
Windows Server 2019 Standard (SAC v1809) N2KJX-J94YW-TQVFB-DG9YT-724CC
Windows Server 2019 Standard N69G4-B89J2-4G8F4-WWYCC-J464C
Windows Server 2019 Essentials WVDHN-86M7X-466P6-VHXV7-YY726
Windows Server 2019 Datacenter WMDGN-G9PQG-XVVXX-R3X43-63DFG
Windows Server 2019 Datacenter (SAC v1809) 6NMRW-2C8FM-D24W7-TQWMY-CWH2D
Windows Server 2019 Azure Core FDNH6-VW9RW-BXPJ7-4XTYG-239TB
Windows Server 2019 ARM64 GRFBW-QNDC4-6QBHG-CCK3B-2PR88
Windows Server 2016 Standard WC2BQ-8NRM3-FDDYY-2BFGV-KHKQY
Windows Server 2016 Standard (SAC v1803) PTXN8-JFHJM-4WC78-MPCBR-9W4KR
Windows Server 2016 Standard (SAC v1709) DPCNP-XQFKJ-BJF7R-FRC8D-GF6G4
Windows Server 2016 Essentials JCKRF-N37P4-C2D82-9YXRT-4M63B
Windows Server 2016 Datacenter (SAC v1803) 2HXDN-KRXHB-GPYC7-YCKFJ-7FVDG
Windows Server 2016 Datacenter (SAC v1709) 6Y6KB-N82V8-D8CQV-23MJW-BWTG6
Windows Server 2016 Datacenter CB7KF-BWN84-R7R2Y-793K2-8XDDG
Windows Server 2016 Cloud Storage QN4C6-GBJD2-FB422-GHWJK-GJG2R
Windows Server 2016 Azure Core VP34G-4NPPG-79JTQ-864T4-R3MQX
Windows Server 2016 ARM64 K9FYF-G6NCK-73M32-XMVPY-F9DRR

</pre>

=== Parte comune ===
*Proseguire
cd %SYSTEMROOT%\System32

cscript.exe //NoLogo slmgr.vbs -skms kms.example.com

cscript.exe //NoLogo slmgr.vbs -ato

cscript.exe //NoLogo slmgr.vbs -dlv

=== Troubleshooting ===
If an error occurred while activating Windows Server:
Error: 0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F069' to display the error text.

The reason is that I have an evaluation version of Windows Server 2022 installed. First, you need to convert it to a Standard version according to this article:

dism /online /set-edition:serverstandard /productkey:VDYBN-27WPP-V4HQT-9VMD4-VMK7H /accepteula

Then I can activate my Windows instance on the KMS host.

=== Riferimenti ===
* [https://www.aidenwebb.com/posts/how-to-fix-server-2019-activation-error-run-slui.exe-0x2a-0xc004f069/ How to Fix Server 2019 Activation Error: Run “slui.exe 0x2a 0xC004F069” | Aiden Arnkels-Webb]

=Attivazione Office 2019 Pro Plus =

* https://github.com/Wind4/vlmcsd/issues/20

I have one that works for office 2019. But I do NOT know why it works.
cscript "%ProgramFiles(x86)%\Microsoft Office\Office16\ospp.vbs" /dstatus
with the following output

LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition
LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel
BETA EXPIRATION: 1601-01-01
LICENSE STATUS: ---LICENSED---
ERROR CODE: 0x4004F040 (for information purposes only as the status is licensed)
ERROR DESCRIPTION: The Software Licensing Service reported that the product was activated but the owner should verify the Product Use Rights.
REMAINING GRACE: 179 days (259199 minute(s) before expiring)

* install volume licensing SKUs for office 2019

<pre>
@echo off
:ADMIN
openfiles >nul 2>nul ||(
echo CreateObject^("Shell.Application"^).ShellExecute "%~s0", "", "", "runas", 1 >> "%temp%\getadmin.vbs"
"%temp%\getadmin.vbs" >nul 2>&1
goto:eof
)
del /f /q "%temp%\getadmin.vbs" >nul 2>nul

for /f "tokens=6 delims=[]. " %%G in ('ver') do set win=%%G

setlocal

pushd "%~dp0"
Title Office 2019 Retail to Volume License Converter

rem SET OfficePath=%ProgramFiles%\Microsoft Office
SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" SET OfficePath=%ProgramFiles(x86)%\Microsoft Office
if not exist "%OfficePath%\root\Licenses16" (
echo Could not find the license files for Office 2019!
pause
goto :eof
)

echo Press Enter to start VL-Conversion...
echo.
pause
echo.
cd /D "%SystemRoot%\System32"

if %win% GEQ 9200 (
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript slmgr.vbs /ilc "%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)
if %win% LSS 9200 (
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ppd.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul.xrm-ms"
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\ProPlus2019VL_KMS_Client_AE-ul-oob.xrm-ms"

cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-bridge-office.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-root-bridge-test.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-stil.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\client-issuance-ul-oob.xrm-ms
cscript "%OfficePath%\Office16\ospp.vbs" /inslic:"%OfficePath%\root\Licenses16\pkeyconfig-office.xrm-ms
)

cscript "%OfficePath%\Office16\ospp.vbs" /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript "%OfficePath%\Office16\ospp.vbs" /act

echo.
echo Retail to Volume License conversion finished.
echo.
pause
</pre>

* Turn off KMS Client Online AVS Valdation
<pre>
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\Software Protection Platform]
"NoGenTicket"=dword:00000001
</pre>

* Activate
<pre>
cd "\Program Files\Microsoft Office\Office16"
cd "\Program Files (x86)\Microsoft Office\Office16"
cscript ospp.vbs /inpkey:NMMKJ-6RK4F-KMJVX-8D9MJ-6MWKP
cscript ospp.vbs /sethst:kms.example.com
cscript ospp.vbs /act
cscript ospp.vbs /dstatusall
</pre>

= Office 2021 ProPlus Retail =

* Assicurarsi di aver installato la 2021 ProPlus (non professional) Retail

* Usare lo script
<pre>
@echo off
echo Change kms.example.com to KMS Server IP or Host
pause
REM Change ProgramFiles to ProgramFiles(x86) If install x86 version . Default are x64

Title Converter Office 2021 Retail to Volume And Activate Through KMS Server

set LICPATH=%ProgramFiles%\Microsoft Office\root\Licenses16
set LICPATH1=%ProgramFiles%\Microsoft Office\Office16

cd C:\Windows\System32

cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ppd.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\ProPlusVL_KMS_Client-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-bridge-office.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-root-bridge-test.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-stil.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\client-issuance-ul-oob.xrm-ms"
cscript slmgr.vbs /ilc "%LICPATH%\pkeyconfig-office.xrm-ms"
cscript slmgr.vbs /ipk FXYTK-NJJ8C-GB6DW-3DYQT-6F7TH

cscript "%LICPATH1%\ospp.vbs" /sethst:kms.example.com
cscript "%LICPATH1%\ospp.vbs" /act

echo.
echo Finished.
echo.
pause
</pre>

=Riferimenti=

*[https://www.ilsoftware.it/articoli.asp?tag=KMS-cos-e-e-come-funziona-l-attivazione-di-Windows-in-rete-locale_23680 KMS, cos'è e come funziona l'attivazione di Windows in rete locale - IlSoftware.it]
*[https://github.com/Py-KMS-Organization/py-kms Py-KMS-Organization/py-kms: KMS Server Emulator written in Python]
*[https://github.com/FuryGreenwood/FuryKMS FuryGreenwood/FuryKMS: Microsoft Windows and Office KMS Activator]
*[https://github.com/massgravel/Microsoft-Activation-Scripts massgravel/Microsoft-Activation-Scripts: A collection of scripts for activating Microsoft products using HWID / KMS38 / Online KMS activation methods with a focus on open-source code, fewer antivirus detection and user-friendliness.]
*[https://massgrave.dev/ index]
*[https://theitbros.com/activate-windows-with-kms-server/ How to Activate Windows with your KMS Server - KMS License Key List]
*[http://blog.51sec.org/2020/05/create-kms-docker-and-use-kms-to.html#point3 Activate Windows/Office (Run KMS Docker / Install KMS) - Cybersecurity Memo]

Proxmox Backup Server non completa il Garbage Collection

2026-01-15T16:48:54Z

Gabriele.vivinetto: Created page with "Se quando si lancia un GC, non si recupera spazio e nella riga del GC Job rimangono dei dati come Pending Data Significa che ci sono dei chunk più vecchi di 25 ore, che di default non pulisce. Per forzarlo, impostare in Options / Tuning Options / GC Access-Time cutoff: 1 Rieseguire il GC == Riferimenti == * [https://forum.proxmox.com/threads/force-delete-of-pending-removals.112316/page-4#post-782781 SOLVED - Force delete of "Pending removals" | Page 4 | Proxmox..."

Se quando si lancia un GC, non si recupera spazio e nella riga del GC Job rimangono dei dati come

Pending Data

Significa che ci sono dei chunk più vecchi di 25 ore, che di default non pulisce.

Per forzarlo, impostare in

Options / Tuning Options / GC Access-Time cutoff: 1

Rieseguire il GC

== Riferimenti ==

* [https://forum.proxmox.com/threads/force-delete-of-pending-removals.112316/page-4#post-782781 SOLVED - Force delete of "Pending removals" | Page 4 | Proxmox Support Forum]

Proxmox Backup Server

2026-01-15T16:45:13Z

Gabriele.vivinetto:

Correggere l'errore the listen ... http2 directive is deprecated, use the http2 directive instead in nginx proxy manager

2026-01-12T11:52:04Z

Gabriele.vivinetto: Created page with "Se all'avvio si vede nei log: nginx-app | nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/12.conf:19 eseguire:<pre> docker compose exec nginx.crodocker01.croalliance.priv-app \ /bin/bash -c " cd /data/nginx/proxy_host && sed -i 's/listen 443 ssl http2;/listen 443 ssl;\nhttp2 on;/g' *.conf && sed -i '/^listen \[::\]:443 ssl http2;/s/ http2//' *.conf " \ | tee -a update.log </pre>In prat..."

Se all'avvio si vede nei log:
nginx-app | nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/12.conf:19
eseguire:<pre>
docker compose exec nginx.crodocker01.croalliance.priv-app \
/bin/bash -c "
cd /data/nginx/proxy_host &&
sed -i 's/listen 443 ssl http2;/listen 443 ssl;\nhttp2 on;/g' *.conf &&
sed -i '/^listen \[::\]:443 ssl http2;/s/ http2//' *.conf " \
| tee -a update.log
</pre>In pratica cambia:<pre>
listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443 ssl http2;
</pre>in:<pre>
listen 80;
listen [::]:80;

listen 443 ssl;
http2 on;
listen [::]:443 ssl;
</pre>

== Riferimenti ==

* [https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4060 use the "http2" directive instead warning · Issue #4060 · NginxProxyManager/nginx-proxy-manager]