Wylie Bayes

Here is a function to fix windows unquoted service path enumeration vulnerabilities automatically with powershell! Cheers! function fix-servicepath { $hosts = get-content C:\Users\*****\Documents\WindowsPowershell\Servers.txt foreach ($box in $hosts) {     $services = $null     $services = get-wmiobject win32_service -computername $box     foreach ($service in $services){ $Displayname = $service.DisplayName        if (($service.PathName -like "* *") -and ($service.Pathname -notlike '"*"*') -and ($service.PathName -like '*.exe')) {         $box         $service.PathName         write-host "Changing Path to be quoted:"         $NewPath = $service.Pathname         $newservicepath…

Here is a custom script I made to check HP Onboard Administrators, Netapp Controllers, and vCenter servers for health issues in Powershell. Cheers! This relies on a few things first: VMWare PowerCLI 5.5+ Netapp DataOnTap 4.0 modules HP OA Powershell Cmdlets to function properly. If you want to capture VM Snapshot alarms you must create an alarm in your vCenters called “VMSnapshot Running” . I personally set mine to if the snapshot is 2GB or larger, trigger the alarm.…

So playing with Hyper-V the past few weeks quite a bit and noticed that when creating a vSwitch, no matter if External and bridged to a real NIC on the host or not, it will create a NIC on the Windows host machine correlating to the vSwitch in Hyper-v. If you create a virtual machine, and attach it to the vSwitch, and this virtual machine is running a DHCP server, your HOST NIC for that vSwitch will pull a DHCP…

Hey everyone! Just thought I’d post up a quick set of instructions to take a VMware formatted OVA file, extract out the .VMDK file and then convert it to a VHD or VHDX with Powershell. First, you will need the Microsoft Virtual Machine Converter package, and installed it. You can download it here: title Next, fire up powershell as administrator, and run this command to import the virtual machine converter powershell Cmdlets: Import-Module "C:\Program Files\Microsoft Virtual…

Just thought I would put this out here for anyone monitoring a large Vmware environment. Cheers! You would need to change $ss to a remote location you wish the report to be stored, our putting a local location would be fine as well, but then would have to local copies on C:, and wherever you specify. function vmware-provisioning { $viservers = "vcenter1", "vcenter2" $cred = get-credential $date = (Get-Date).tostring("yyyyMMdd") Add-PSSnapin Vmware.VIMAutomation.Core | Out-Null set-PowerCLIConfiguration -invalidCertificateAction…