Sysprep in windows 2008

Con il tool fornito da Microsoft sysprep, che in Windows 2008 è disponibile nella directory C:\Windows\system32\sysprep, si effettua la procedura per il cambio del SID.

Per evitare possibili imprevisti dovuti ad un’errata procedura, gli step raccomandati da seguire sono due:



1. Aprire il Command Prompt con diritti di Administrator
2. Eseguire il comando:


c:\windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /shutdown

Rimuovere download Microsoft Update da Win2008

1. Open Start >> Run or press window key + r

2. Type “services.msc” (without quotes) and Click OK , this will open services window.

3. Right click on Automatic Updates Service and select Stop.

4. After the service is stopped, press window key + r

5. Type “%windir%\SoftwareDistribution” (without quotes) and press enter.

6. Open the Download folder and delete all contents of the Download folder.

7. Close the window, press Window Key + r ( or Open Start >> Run )

8. Type “services.msc” (without quotes) and Click OK

9. Right click on Automatic Updates Service and select Start.

10. That’s it Done

OracleVm re-Register host

Hi Honza,

just tried it:

Before:
# /opt/ovs-agent-latest/utils/repos.py -l
[ * ] b2638dcd-fa49-4646-a7da-83e91e7e26c4 => /dev/hdb1
# du /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4/running_pool
2316896 /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4/running_pool/30_OEL1

Then:
# /opt/ovs-agent-latest/utils/cleanup.py
This is a cleanup script for ovs-agent.
It will try to do the following:

*) stop o2cb heartbeat
*) offline o2cb
*) remove o2cb configuration file
*) umount ovs-agent storage repositories
*) cleanup ovs-agent local database

Would you like to continue? [y/N] y
Cleanup done.

No Repos anymore:
# /opt/ovs-agent-latest/utils/repos.py -l

Create New:
/opt/ovs-agent-latest/utils/repos.py -n /dev/hdb1
[ NEW ] b2638dcd-fa49-4646-a7da-83e91e7e26c4 => /dev/hdb1
/opt/ovs-agent-latest/utils/repos.py -r b2638dcd-fa49-4646-a7da-83e91e7e26c4

Not mounted yet:
# df -k
/dev/hda2 4466156 930456 3305168 22% /
/dev/hda1 101086 45803 50064 48% /boot
tmpfs 296536 0 296536 0% /dev/shm

Initializing:
/opt/ovs-agent-latest/utils/repos.py -i

Mounted!:
# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda2 4466156 930468 3305156 22% /
/dev/hda1 101086 45803 50064 48% /boot
tmpfs 296536 0 296536 0% /dev/shm
/dev/hdb1 33551720 6040232 27511488 19% /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4

And data still there:
# du /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4/running_pool
2316896 /var/ovs/mount/B2638DCDFA494646A7DA83E91E7E26C4/running_pool/30_OEL1

However as noted above: The /OVS link to the /var/ovs/mount point will be created when you register the server with OVM Manager.
All additional data will be left on the device.

Server database Aruba down 20 agosto 2011

I server dei database di Aruba dalle 23 del 19 agosto 2011, sono andati down, o almeno non sono raggiungibili, il problema riguarda solo i server con database, tanto è vero che i siti rispondono, ma viene visualizzato un errore di connessione.

Rimaniamo in attesa di una comunicazione ufficiale da parte di Aruba.

HA initiated a failover action in cluster Vmware

Ho trovato questo messaggio “HA initiated a failover action in cluster your-cluster-name in datacenter your-datacenter-name” sul mio vCenter. Niente è cambiato, le vm non sono state riavviate l'HA continua a funzionare tranquillamente, per risolvere ho usato il seguente metodo:


1. Turn OFF VMware HA on Cluster Feature setting.
2. Enable VMware HA setting again.