Category: Windows Server 2012
-
Resolving Windows Server 2012 Failover Cluster Kerberos Security Issue – Invalid DNS Error
I’ve been running Windows Server 2012 Failover Cluster for about a year and it’s been stable up until now. Recently, I encountered an issue where Live migration of VMs failed across all hosts in the cluster. In addition, the Failover Cluster Manager started displaying the following error: Cluster network name resource ‘Cluster Name’ failed registration…
-
Renaming AD User Object Surname Property.
The following script renames the Surname property of an Active Directory User Object. The script requires PowerShell 3.0. The only edit required is the organizational Exchange Server name specified in the New-PSSession cmdlet. The script accepts the Given Name, Surname and new Surname parameters’ input from the console,executes the rename of the Active Directory object…
-
Configuring multiple ISCSI Connections for Multipath IO using PowerShell.
This post will be focused mainly on the ISCSI Initiator host and configuring multipath IO paths to an ISCSI Target. The ISCSI Target portal has already been configured with 2 network paths for ISCSI. The ISCSI Service by default is in a ‘Stopped’ state. So, we’ll begin by starting the service: [hyperv00]: PS C:\Users\admin\Documents> Start-Service…
-
Configuring Hyper-v Host Network Adapters for ISCSI Storage Connectivity with Powershell .
Windows Server 2012 R2 with PowerShell 4.0 has hugely expanded support for configuring multiple NICs on a Cluster/ISCSI Initiator node via command line. After deploying multiple Network Interface Cards on my Hyper-v host, it took me a while to figure out how to properly configure the NICS with PowerShell . Prior to Windows Server 2012,…
-
PowerShell 3.0 Script creates AD user and Exchange Mailbox.
This interactive script requires PowerShell 3.0 . It creates an Active Directory user and their corresponding mailbox using a remote session at the same time. It should work out of the box, but specific variables will have to be edited to reflect the Active Directory configuration of the organization in question. function New-Employee { Param…
-
PowerShell script utilizes “Using” scope modifier to create VM from existing .vhdx file.
The following interactive PowerShell 3.0 script creates a new virtual machine. It utilizes the ‘Using’ scope modifier to pass local variables to remote machines with the invoke-command cmdlet. An existing .vhdx file is copied to a new location and renamed . Same file is used to create the virtual machine. The script assumes the VM…
-
How to promote Windows Server 2012 to a Domain Controller
Originally posted on Exchange Times: Microsoft has done away with dcpromo when it comes to Windows Server 2012. We’ve been so accustomed to using dcpromo that I actually struggled a bit to promote a 2012 server to a DC in one of my labs. This short video shows how to install the Active Directory Directory…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 4
Here we go over my steps for the actual cluster creation, cluster and node validation, quorum setup and cluster shared volume configuration.We have by running a cluster validation on each node. This can be achieved with the following cmdlets: Test-Cluster -Node hyperv01 Test-Cluster -Node hyperv03 In this case, the test passed. The process basically gives…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 3
In the next part of the series, we will create a simple 1GB iSCSI virtual disk, assign it to the already configured target and verify the disk is visible to the iSCSI initiators. New-IscsiVirtualDisk -Description “Witness Disk” -Path g:\iscsivirtualdisks\Witness00.vhd -Size 1GB -ComputerName labtarget -Verbose (Create the 1GB iSCSI virtual disk) Add-IscsiVirtualDiskTargetMapping -TargetName Target00 -Path g:\iscsivirtualdisks\Witness00.vhd…
-
Configuring Windows Server 2012 as an iSCSI Target SAN in a Two Host Failover Cluster Part 2
In this part of the series, we will configure two hosts as iSCSI initiators. The hosts have already been defined at the Target and ready to log on. Both hosts are running WS 2012 Hyper-v Core and I made sure to install the Failover Clustering and Hyper-v windows features. Following is a snapshot of the cmdlets available…