delta file of vmware snapshot,delete vmware snapshot on production server disaster

https://www.computerweekly.com/tip/VMware-snapshot-best-practices

f a VM file has three snapshots, deleting all will cause the changes from the third delta file to be copied to the second file. Data from the second delta file will be copied to the first and from the first to the original VM. The delta files are deleted only after the commit process is complete.

If each delta file size is 50 GB, an additional 150 GB storage space would be required to accommodate the growing size of delta files. The commit process for a 100 GB snapshot typically takes three to five hours. This process will therefore put an additional performance overhead on the original VMs and the virtual server infrastructure. A degraded system and application performance, especially in a production environment would be unacceptable.

http://www.vmwarearena.com/deep-dive-the-ultimate-guide-to-master-vmware-snapshot/

Virtual Machine Snapshot Files

Virtual machine snapshot consists of multiple files. Virtual Machine snapshot mainly includes the following:

Settings state : Virtual machine’s settings (.nvram & .vmx) and power state

Disk State: state of the virtual machine’s associated disks

Memory state: Contents of virtual machine’s memory (Only if memory snapshot is selected)

Below are the some of the files which comprise of snapshot:

VM_name.vmsd

VM_name-snasphot#.vmsn

VM_name-00000#.vmdk

VM_name-00000#-delta.vmdk

VM_name-snapshot#.vmem

Below is the comparison of  Virtual machine files in the virtual machine directory before and after creating the first snapshot of the virtual machine.

Microsoft Message Analyzer , backup software list to-be-test

https://www.microsoft.com/en-us/download/details.aspx?id=44226

https://www.macrium.com/reflectfree

v3700 ibm

https://www.ibm.com/support/knowledgecenter/STLM5A/com.ibm.storwize.v3700.710.doc/tbrd_endcapleds_9842pj.html




http://www.chinastor.com/a/devices/cipan/01121X142016.html

20、V3500和V3700前面左耳面板3个LED指示灯的意义？


1） 绿色电源标志指示灯，指明主电源是否可用，若指示灯闪烁则说明处于待机模式。
2） 蓝色灯塔标志灯，用来认出存储。
3） 叹号报错灯，亮起时说明存储上某个部件出现硬件故障。
转自中国存储网，原文链接：http://www.chinastor.com/a/devices/cipan/01121X142016.html

check disk space automation

1. Netwrix Disk Space Monitor Freeware Edition (Version 1.2)

2. https://gallery.technet.microsoft.com/scriptcenter/Disk-Space-Report-Reports-98e64d65

Disk Space Report - Reports only disks that are below a threshold - HTML output
Download CheckDiskSpace_post.ps1

Run in Powershell
https://stackoverflow.com/questions/4037939/powershell-says-execution-of-scripts-is-disabled-on-this-system

i  had a similar issue and noted that the default cmd on Windows Server 2012, was running the x64 one.

For Windows 7, Windows 8, Windows Server 2008 R2 or Windows Server 2012, run the following commands as Administrator:


x64 (64 bit)
Open C:\Windows\system32\cmd.exe
Run the command powershell Set-ExecutionPolicy RemoteSigned

You can check mode using

In CMD: echo %PROCESSOR_ARCHITECTURE%
In Powershell: [Environment]::Is64BitProcess
References:
MSDN - Windows PowerShell execution policies
Windows - 32bit vs 64bit directory explanation

vmware esxi 5.5 build 1746974 for dell r310

https://www.virten.net/vmware/esxi-release-build-number-history/

ESXi 5.5 Update 2	ESXi550-update2	2014-09-09	2068190
ESXi 5.5 Update 2 (Security Only)	ESXi550-update2	2014-09-09	1980513
ESXi 5.5 Patch 2	ESXi550-201407001	2014-07-01	1892794
ESXi 5.5 Patch 2 (Security Only)	ESXi550-201407001	2014-07-01	1892623
ESXi 5.5 Express Patch 4	ESXi550-201406001	2014-06-10	1881737
ESXi 5.5 Express Patch 3	ESXi550-201404020	2014-04-19	1746974

https://www.dell.com/support/home/hk/zh/hkdhs1/drivers/driversdetails?driverid=y5w35

可用的格式

檔案格式：ISO Image

檔案名稱：VMware-VMvisor-Installer-5.5.0-1746974.x86_64-Dell_Customized_A04.iso

下載類型：HTTP

檔案大小：327 MB

格式說明:此檔案內含用於建立 CD-ROM 的 ISO 影像。將檔案下載到硬碟上的資料夾，然後使用慣用的 CD 燒錄軟體建立 CD。

 下載檔案

acronis backup and recovery 11 cannot connect to localhost

https://kb.acronis.com/content/32750
\

1) restart all acronis service

2) if still cannot connect after , then restart , acronis remote agent service.

3) open application again

create Windows 10 custom layout (Pin after sysprep will lost the Pin ? not happen more)

https://blogs.technet.microsoft.com/deploymentguys/2016/03/07/windows-10-start-layout-customization/

Export the Start Layout

When you have the Start screen layout that you want your users to see, use the Export-StartLayout cmdlet in Windows PowerShell to export the Start screen to an .xml file.

1. From Start, open Windows PowerShell.
2. At the Windows PowerShell command prompt, enter the following command:

Export-StartLayout –path <path><file name>.xml

Figure 3. Export-StartLayout cmdlet

PowerShell

When you have the Start screen layout exported, use the Import-StartLayout cmdlet in Windows PowerShell to manually import the .xml file into the system.

1. From Start, open Windows PowerShell.
2. At the Windows PowerShell command prompt, enter the following command:

Import-StartLayout –LayoutPath <path><file name>.xml –MountPath %systemdrive%

Copy Profile 

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/customize-the-default-user-profile-by-using-copyprofile

BTW , unlock how many time of sysprep

https://social.technet.microsoft.com/Forums/en-US/ff505760-bc2c-4d5a-ae84-0f82ed9b574b/trying-to-understand-how-many-times-sysprep-has-been-run?forum=win10itprosetup

https://system-center.me/miscellaneous/sysprep-your-windows-os-for-more-then-3-times/

Sysprep your Windows OS for more than 3 times

Posted on November 8, 2010 by sharon

It can happen, the need of re-syspreping an already syspreped machine, why ? maybe you lost your Image master. so.. you running the setup process, adding the changes you want, relocating the XML answerfile, running the sysprep with /generalize switch.. the process is running for few seconds and then the sysprep window is disappeared. well.. open the sysprep log file under \sysprep\Panther … there you will find setup error log, if the logfile contains this line :

Date Time, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn’t update the recorded state, dwRet = 31

then Microsoft say… “Hey dude, bummer…, re-create the whole image“.

well… it’s not so true… this error indicates that you syspreped the machine more then 3 times, you cant do that… if the windows system was already activated by pre OEM activation you cant even re-arm the machine.. so you have 2 problems, one – can’t sysprep anymore and probably you can’t re-arm your machine (it wont let you sysprep if you cant re-arm..).

so, first check if you can re-arm by runing the slmgr.vbs /dlv and check the re-arm counter, if it set to zero.. you need to do the following : http://support.microsoft.com/kb/929828 (set the <SkipRearm>1</SkipRearm> like in the example, note: this option will make the product key window to appear in the setup process).

you can also try running : slmgr.vbs –rearm, to rearm Windows.

after that, let’s come back to the sysprep process.. for syspreping already syspreped machine we have to change few keys in the registry :

HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\

CleanupState:2
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\

GeneralizationState:7

After done with the registry, do the following :

1. Start -> Run : msdtc -uninstall (wait few seconds)
2. Start -> Run : msdtc -install (wait few seconds)
3. Restart the machine
4. Check the registry for the right registry keys values
5. sysprep with the new XML answerfile.
6. and.. Walla !
7. Have fun.