Although vSphere 5.5 has a scheduled task to create Snapshots, it appears to be missing a scheduled task to remove them.
I had to find a way of automating the removal of the Snapshots for specific Virtual Machines at a specific time (ie not during business hours).
To do this required 3 things, a Scheduled Task and a PowerShell script using the VMWare Snapin and a TXT document with the hostname of the Virtual Machine that needs the Snapshot to be removed.
This script is quite simple – it connects to the vSphere server, checks for a VM name under a TXT document that people add their servers to and then when the scheduled task runs it removes the Snapshot for that VM and clears the TXT document ready for the next day.
App-V applications, usually store their data locally if they are not streamed. Sometimes an Application will have problems, either hasn’t been downloaded or some other reason.
One of the solutions that can be ran is to clear the App-V package store of a workstation, allowing you to reevaluate and download the packages back to the affected computer.
This script is pretty simple and something I made a year ago for some colleagues experiencing App-V application cache issues so decided to share it here. This requires the App-VClient PowerShell module – usually installed by default as part of the App-V client.
Some ‘server based’ applications require to be logged into into a service account to allow an Application or service to run, These applications usually require manual intervention by systems administrators to login to the account manually after a server restart.
There are many ways to setup Automatic Logon, using “control userpasswords2” via the Run Prompt, using Third Party utilities like LogonExpert or simply using RegEdit and setting them manually.
I have created a PowerShell script for editing the registry to set this manually in a standardized way and could be ran remotely. It is pretty simple and only requires version 1 of PowerShell.
In Server 2008 and Server 2008 R2, Disk Cleanup is Disabled by default. This is how you can enable disk cleanup in Windows Server 2008 R2 – 64bit.
You can enable the Desktop Experience role (which requires a restart to complete) but the easiest way is to copy the files from the WinSXS directory to the relevant directories – as mentioned below
|Windows Server 2008 R2||C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe|
|Windows Server 2008 R2||C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui|
One of the problems with Hyper-V 2012 R2 on an Intel NUC – NUC5i7RYH was because of the ‘Client’ network card chipset. Windows Server 2012 would not install the Ethernet Adapter for the Server operating system.
Once I made the manual adjustments to the Network drivers to get this going, I then slipstreamed the drivers and Server 2012 R2 updates (as of Feb 2016) into a Hyper-V 2012 R2 ISO which can then be made bootable for future Hyper-V installations.
7-Zip or WinRAR will be needed to extract the EXE to a folder location. In these examples, I am using 7-Zip.
With monthly server patching, the process is currently manual due to the number of clusters and very application specific servers that is patched – including an issue with failed updates caused by Trend Officescan – and an issue that has been done manually for months.
It was time to automate this process – and without Orchestrator or SMA I had to use what I already had – a SCCM 2012 R2 Infrastructure, and the use of the Task Sequence and PowerShell.
Importing drivers into System Center Configuration Manager R2 (SCCM) is a task I do at least once a month as new models are introduced into my work environment.
In this guide I am going to guide you through a step by step method of exporting drivers from an already existing build (ie vendor supplied, OEM) or from a driver package supplied for operating system deployment purposes from a vendor, such as Hewlett Packard.
As part of being an IT Engineer at my place of employment – I work with operating system deployment and management – part of this is using the Windows DISM toolset for adding packages or drivers directly into a Windows OS WIM or boot WIM.
Here are a few useful DISM commands I have gathered and use on a monthly basis with WIM management and updates.
The following procedures will outline the installation instructions of third party Antivirus and Anti-malware tools that do include Rootkit scanning and removal. The Trend Micro utilities should be run first and if possible a virus sample collected and sent to Trend Micro. The following utilities are included in this: AVG Antivirus Free, CCleaner, ClamWin Antivirus, CWShredder, HijackThis, Malwarebytes Anti-malware, Microsoft Security Essentials, Rootkit Revealer, Spybot Search & Destroy.
I have just configured ESXi on my new Intel NUC – NUC5i7RYH (Intel NUC i7-5557U 3.1GHz 16GB 256GB SSD).
Due to incompatibility with ESXi-Customizer on Windows 10 – I used the now recommended: ESXi-Customizer-PS Power CLI script.
Following the instructions at the ESXi-Customizer website: http://www.v-front.de/p/esxi-customizer-ps.html with installing the VMWare Power CLI PowerShell dependencies onto my workstation (you need a register My VMWare account to download this directly from VMware).
I was able to use the following command from the directory where the PowerShell script was saved:
.\ESXi-Customizer-PS-v2.4.ps1 -v60 -vft -load sata-xahci,net55-r8168
This will make the script connect to the V-Front Online Depot and add the sata-xahci and net55-r8168 packages from there to the latest ESXi 6.0 Imageprofile.
Entirely with no user interaction it was able to download the latest v6 ESXi release and slipstream the sata-xahci drivers leaving a clean ISO I was then able to use Rufus with the default settings to deploy the ISO to my USB Flash drive which was then used to install on the Intel NUC successfully.