Labels

3300 (1) 3PAR (1) Active Directory (1) ADFS (1) Admin Share (1) Auto-Sync (2) Auto-Sync locked (1) AWS (3) AzCopy (1) Azure (3) Backups (2) Broadcom (1) Call Forwarding (1) CLI (2) cmd (1) Compatibility View (1) Dameware MRC (1) Databases (1) DFS (1) DNS (1) Domain Admin (1) domain controller (1) Enterprise Mode (1) ESXi 5.0 (1) ESXi 5.1 (5) ESXi 5.5 (3) Exchange (3) Exchange 2010 (5) Extreme (1) ExtremeXOS (1) Federation (1) File Share (1) FSMO (1) GPO (1) Group Policy (1) Group Policy Client (1) Hardware Acceleration (1) Helpdesk (1) HP-UX (1) Hyper-V (2) IAM (1) IE10 (1) IE11 (1) IP conflict (1) Kayako (3) LDAP (1) Licence (1) Links (9) local groups (1) LUN lock (1) LUN number (1) MAC address (1) Microsoft Teams (1) Mitel (1) Namespaces (1) Networking (6) Nexenta (6) NMC (1) Office 365 (4) OneDrive (1) Outlook 2003 (1) Outlook 2013 (1) PC (1) Physical (1) PowerCLI (10) Powershell (10) promoted links (2) Public Folders (1) RDP (1) RDS (1) Recovery Services (1) RedShift (1) Registry (3) Reports (1) Resolve (2) Restart (1) RSA (1) Run As (1) SAML (1) SAN (1) Scavenging (1) script (10) Server 2003 (3) Server 2008 R2 (1) Server 2012 R2 (2) Servers (2) sharepoint 2013 (3) SMTP (3) Snapshot (2) SRM (1) SSH (5) SSL Certificate (2) Temporary profile (1) Terminal Server (3) Troubleshooting (5) Ubuntu (1) Update Manager (1) Useful Apps (1) VAAI (1) vCenter Server Appliance (1) VDI (1) VDP (1) Veeam Backup and Replication (2) VM (1) VM Error (1) vmdk (1) VMFS (1) vMotion (2) VMware (20) VoiP (1) vSphere 5.5 (4) vSphere 6.0 (2) vSphere 6.5 (1) vUM (1) webpart (1) Windows (3) Windows 10 (1) Windows 7 (2)

Wednesday, 30 December 2015

Find VM Attached RDM By WWN

In order to find an existing VM attached RDM by WWN use the script below;
Get-VM | Get-HardDisk -DiskType "RawPhysical","RawVirtual" | where {$_.ScsiCanonicalName -like "*WWN*"} | Select Parent, Name, DiskType, ScsiCanonicalName, DeviceName | fl
The output will look similar to the below if an RDM is found;

Parent                          : SERVER-NAME.domain
Name                            : Hard disk x
DiskType                     : RawVirtual
ScsiCanonicalName   : naa.WWN

DeviceName                : vml.DeviceName

Find VM Datastore By WWN

In order to find any existing VM datastore by WWN use the script below;
Get-Datastore | where {$_.extensiondata.info.vmfs.extent.diskname -like "*WWN*"}
The output will look similar to the below if a datastore is found;

Name                                       FreeSpaceGB      CapacityGB
----                                            -----------                 ----------
san01-lun01                            339.047                 499.750
san01-lun01                            339.045                 499.750

Wednesday, 23 December 2015

Check If A .VMDK Is Attached To A VM

Another quick PowerCLI script to check if a .vmdk file is associated with a VM
Get-VM | Get-HardDisk | Where {$_.Filename -like '*vmdk-name*'} | Select Parent, Filename
If the disk is in use you should get a response similar to

Parent                                                Filename
------                                                    --------
VMName                                             [SAN] VMName/vmdk-name.vmdk
VMName                                             [SAN] VMName/vmdk-name_1.vmdk
VMName                                             [SAN] VMName/vmdk-name_2.vmdk

Monday, 21 December 2015

Check To See If Folder Or File Is Present On A Remote Server

I needed to check for an installed program on a number of remote servers without having to log in to each one individually. Unfortunately, whilst the program is listed in Control Panel > Add / Remove Programs, it does not get returned via Powershell when running;

Get-WMIObject Win32_Product

Running the following script allowed me to import a list of servers then search for a file or folder on those servers. Following the search the server name and result of the search is outputted to the screen;

#Import list of servers
$cns = Get-Content "C:\Users\LangridgeJ\Desktop\list-of-servers.txt"
#Scan for selected file or folder
foreach ($cn in $cns)
{$path = Test-Path "\\$cn\C$\Path\To\Folder\Or\File"
#Write output to screen
If ($path -eq $true ) { Write-Host $cn 'Files or folders are present' }   
        Else { Write-Host $cn 'No files or folders are present' } }

Friday, 18 December 2015

No "Continue To This Website" Option On HTTPS Site

I recently had an issue with an internal website with no certificate. When trying to access the site via IE10 I was not being given an option to "Continue to this website". This was due to a change Microsoft made blocking the use of RSA certificates with keys less than 1024 bits long.

Microsoft's Security Advisory bulletin can be found here: https://support.microsoft.com/en-us/kb/2661254

To fix this, run CMD as administrator and submit the following command;

certutil -setreg chain\MinRSAPubKeyBitLength 512

Then refresh the page. The "Continue to this website" option should be available again.

Wednesday, 16 December 2015

AWS RedShift Cluster Can Only Be Launched In Default VPC

When trying to launch a RedShift cluster in AWS I found I was only able to select the default VPC - unfortunately not the VPC that my Production workloads were running in.

In order to allow the creation of RedShift clusters in VPCs other than your default you need to create a new Cluster Subnet Group. To do this follow the steps below;

1. Login to AWS console and select RedShift
2. In the RedShift console go to "Security" and select "Subnet Groups" from the tabs at the top
3. Click "Create Cluster Subnet Group"
4. Give the group a name and description and pick the VPC you want to run the Cluster in. Then choose your Subnet IDs from the Availability Zones available.
5. Click "Create". Now when you try to launch a RedShift cluster you will be able to choose the VPC you want to run the Cluster in, and your newly created Subnet Group.