Windows Server 2012 Failover Cluster Virtual Fibre Channel Adapter Live Migration Error

I’ve got a multiple  node cluster running Windows Server 2012 with Brocade 415/815 4G/8G FC HBA’s connecting to a VX SAN. I am trying to get the virtual HBA’s working in Hyper-V Guest running Windows 2008 R2 (SQL Cluster). I first created 2 virtual SAN Switches one connected to each port on my physical HBA (each physical port connects to a separate fabric). I add two Virtual HBA’s in my Guest, one to each VSAN Switch. When I go to Zone the HBA’s I only see side A of the virtual HBA’s not both A and B. On each fabric I should see two (A and B) WWPN but I only see one, to solve this you must shut down the Guest OS and twist the address set name (copy Set Address A to  Set Address B  and Set Address B to Set address A) I can add disk and everything works, however when I go to Live migrate I get the following error due to side B not being zoned. Live migration of ‘Virtual Machine Win2012_01’ failed.

Virtual machine migration operation for ‘Win2012_01’ failed at migration destination ‘hv-cl07-c2’. (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

‘Win2012_01’ Synthetic FibreChannel Port: Failed to finish reserving resources with Error ‘Unspecified error’ (0x80004005). (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

‘Win2012_01’ Synthetic FibreChannel Port: Failed to finish reserving resources with Error ‘Unspecified error’ (0x80004005). (Virtual machine ID 2CE90D02-083C-4012-ACA1-BE8D35EFCA33)

To solve this problem, I have done the following:

  • Updated my drivers to the latest version (3.0.2.21)
  • Remember that the Virtual SAN path must be the same, for example when you create 2 paths then the VSAN A should always connect to FiberSwitch 1 and VSAN B should connect 2 Fberswitch 2. This is because when you try to live migrate the guest OS and the VSAN paths are different the fiberSwitch cannot build the connection.
  • My problem was however that I only had created one host on the SAN and configured all the 8 paths under one host, to resolve my problem I created one host for the address set A and one host for the address set B. So I have always one connected and one disconnected host on my SAN and when I am doing a Live migration then the both hosts are online

I hope that this will solve your problem to.

Best Regards,

Pouyan

 

Create FTP user (Powershell GUI)

Here is a small PowerShell script that I have written today, this is a GUI interface script that will help you create a FTP user with folder and will configure the permissions fore IIS:

Well you can use the script to start the GUI both you can also convert this to a EXE file, to convert the script to a EXE you can  download PS2EXE

Now you can run the coede below to confert the PS1 file to a EXE file

  • Start powershell in version 2 (if you are running version 3)
  • Browse to the folder where you unzipt the PS2EXE and run the code

~pouyan

PowerShell – WmiObject and a corrupt repository

If repository is found to be inconsistent, for Vista and newer, run from elevated command prompt:

Note this command will take the content of the inconsistent repository and merge it into the rebuilt repository if it is readable

If the above doesn’t work, then run:

Note this will reset repository to the initial state when the OS was first installed

~pouyan

Using PowerShell as the Shell on Windows Server Core

With PowerShell becoming one of the most important tools in a Windows administrator’s tool bag as well as really becoming the best prompt to use on Windows Server Core, I thought it was about time I documented how to change the command prompt that opens when you log into Server Core with a PowerShell prompt.

To complete this requires two steps:

  1. Enable/Install PowerShell on the Windows 2008 R2 Server Core computer
  2. Update the HKLMSoftwareMicrosoftWindows NTCurrentVersionWinLogonShell registry key replacing cmd.exe with PowerShell.exe

To enable PowerShell run SCONFIG from the command prompt and then select menu options 4 then 2. This will require the computer to be rebooted

Once rebooted login and in the CMD prompt type PowerShell. At the PowerShell prompt type:

Having completed above log off and back on and a powershell prompt will open instead.

~Pouyan

Set Computer Name using PowerShell

Yesterday I faced a problem in which I need to change the computer name using PowerShell. First I was looking for some cmdlet which can do this job for me but there is not any builtin cmdlet for it.
This method is using WMI to do the task.

I am using Get-WMI to give me all the value of Win32_ComputerSystem.

You can see in the Output that the “Name” value contain our Computer name.

After putting the command in to the $computerName variable, you can use the rename method to rename the computer.


The Win32_ComputerSystem WMI class contain the method of .Rename() in which we need to provide a desired computer name in brackets.

~Pouyan

Install the WSUS 3.0 Administration Console

After installing WSUS 3.0 on a server, you can manage WSUS 3.0 from any computer on your network, as long as the domain of that computer has a trust relationship with the domain of the server. You will need to perform a separate installation, from the same downloaded installation package, on every machine from which you want to run the WSUS 3.0 administration console.

Install the console

To install the WSUS 3.0 administration console, use the same installation package you downloaded to install the WSUS server.

Note
The latest version of the WSUS setup executable is available on the WSUS Web site (http://go.microsoft.com/fwlink/?LinkId=74472).

The console-only installation process can be run from the setup UI from the command line. For more information about command-line installation, see Appendix A: Unattended Installations later in this guide.

To install the WSUS 3.0 console only from the UI

  1. Double-click the installer file (WSUSSetup-x86.exe or WSUSSetup-x64.exe).
  2. On the Welcome page, click Next.
  3. On the Installation Mode Selection page, select the Administration Console only check box, and then click Next.
  4. Read the terms of the license agreement carefully. Click I accept the terms of the License Agreement, and then click Next.
  5. The final page of the installation wizard will tell you whether or not the WSUS 3.0 installation was completed successfully. Then click Finish.

To install the WSUS 3.0 console only from the command line

  1. Open a command window.
  2. Navigate to the directory in which you saved the installation executable. (This will be either WSUSSetup-x86.exe or WSUSSetup-x64.exe.)
  3. Type one of the following commands:
  4. This will bring up the Welcome page of the installation UI. Click Next.
  5. Read the terms of the license agreement carefully. Click I accept the terms of the License Agreement, and then click Next.
  6. Wait for the installation process to finish, and then click Finish.

Access the WSUS administration console

You must be a member of the local Administrators group or the WSUS Administrators security group on the computer on which WSUS is installed in order to use all the features of the WSUS console. Members of the WSUS Reporters security group have read-only access to the console.

To open the WSUS administration console

  1. Click Start, point to Control Panel, point to Administrative Tools, and then click Microsoft Windows Server Update Services 3.0.
  2. If you are bringing up the remote console for the first time, you will see only Update Services in the left pane of the console.
  3. To connect to a WSUS server, in the Actions pane click Connect to Server.
  4. In the Connect To Server dialog box, type the name of the WSUS server and the port on which you would like to connect to it.
  5. If you wish to use SSL to communicate with the WSUS server, select the Use Secure Sockets Layer (SSL) to connect to this server check box.
  6. Click Connect to connect to the WSUS server.
  7. You may connect to as many servers as you need to manage through the console.

Fix – FRS Event 13508

To fix the problem, you need to designate a domain controller to be authoritative for the Sysvol replica set.

1. Stop the File Replication service on the PDC emulator FSMO role holder.
2. Use the Registry Editor to navigate to:

3. Double-click the BurFlags Value Name, a REG_DWORD data type, and set the data value to D4, using the Hex radix.
4. Exit the Registry Editor.
5. Start the File Replication service.

Note: If the BurFlags Value Name is set to D4 (authoritative) on more that one replica, conflicts and collisions will occur.

Time Synchronize Domain Servers

In a domain the DC with the PDCEmulator FSMO is the time source for all domain member machines, DC sync with that one and all other domain members sync with an available DC. Therefore make sure no firewall is blocking port 123 UDP on all machines.

Time displayed on the computers are for humans, internally all the client computers/member server/domain controllers will follow UTC Timing conventions.

You should understand the hierarchy.
If possible the PDCEmulator should sync to a NOT domain machine or NTP server, this can be configured with:

With “PEERS” you can set the time source, either DNS name (time.windows.com) or an ip address from a reliable time source.

Here you can find some of them:
 http://www.pool.ntp.org/

To reconfigure the domain members for the domain hierarchie run:

After that run:

Or you should run below command line on problematic system , to reset the time service:

The client part can also be scripted and run as startup script.

Displaying Balloon Tip

Let’s assume your script wants to share status information via a balloon message in the system tray area. Here is a sample:

Note that the code uses the icon of your PowerShell application inside the tray area so the user can associate the message with the application that produced it.

Export thumbnailphoto from AD to jpg for all users

For exporting users thumbnail photo from AD to jpg for all users you can use script below:

~Pouyan