I’m using your version of the script. It’s working really well for me and I’ve made my own additions for our environment. The only piece I can’t get to work is the vmkernel creation (I had to remove this piece to test the rest).

If I don’t modify the script, I get this error:
[vSphere PowerCLI] > .\copyportgroups_tmp.ps1
Unexpected token ‘What’ in expression or statement.
At D:\copyportgroups_tmp.ps1:39 char:28
+ $MotionIP = Read-Host “What <<< .\copyportgroups_tmp.ps1
Unexpected token ‘Creating’ in expression or statement.
At D:\copyportgroups_tmp.ps1:43 char:21
+ Write-Host “Creating <<<< $($vmk) on $($NewHost).”
+ CategoryInfo : ParserError: (Creating:String) [], ParseException
+ FullyQualifiedErrorId : UnexpectedToken

Thanks for the help.

script did prompt me for VI server and source/destination and it generate this error after accepting the infomation. I will try again as you mentioned. thanks heaps
Ajay

That has nothing to do with ESXi or ESX. That command is trying to connect to your vCenter server.

In the command:

$VISRV = Connect-VIServer # or ask (Read-Host “Please enter the name of your VI SERVER”)

the “#” is a commentor, meaning everything after that is ignored. So, put the FQDN of your vCenter server just before the “#” or remove the “# or ask” part and it will ask when you run the script.

Hope that helps…

Mike

I am trying this script from 1 esxi to another esxi and both are 4.0 U2 and geting this error!! help if you guys can
Connect-VIServer : A positional parameter cannot be found that accepts argument
‘$null’.
At line:1 char:26

Use this in a testing area first, or use it for ideas. Full credit to Al as this is still mainly his work that I merely tweaked. I am NOT a programmer and someone will likely hate the way I do things. No worries.

function AskEm {
$caption = “Select:”;
$message = “Add item $element to the new list?”;
$yes = new-Object System.Management.Automation.Host.ChoiceDescription “&Yes”,”help”;
$no = new-Object System.Management.Automation.Host.ChoiceDescription “&No”,”help”;
$choices = [System.Management.Automation.Host.ChoiceDescription[]]($yes,$no);
$answer = $host.ui.PromptForChoice($caption,$message,$choices,0)
switch ($answer){
0 {$Global:NewList += @($element)}
1 {continue}
}
}
# initialize a variable
$Global:NewList = $null

$VISRV = Connect-VIServer # or ask (Read-Host “Please enter the name of your VI SERVER”)
$BASEHost = Get-VMHost -Name (Read-Host “Please enter the name of your existing server as seen in the VI Client:”)
$NEWHost = Get-VMHost -Name (Read-Host “Please enter the name of the server to configure as seen in the VI Client:”)

# get the switches for the base host
$MySwitches = $BASEHost |Get-VirtualSwitch

# ask the user to select what switches to look at and copy
foreach ($element in $MySwitches) {
Askem
}

#go thru each switch selected above
foreach ($switch in $NewList) {
# check to see if the switch already exists on the new host – if so don’t create it.
If (($NEWHost |Get-VirtualSwitch -Name $switch.Name -ErrorAction SilentlyContinue)-eq $null){
# if not, create it…
Write-Host “Creating Virtual Switch $($switch.Name) on $($NEWHost).”
$NewSwitch = $NEWHost |New-VirtualSwitch -Name $switch.Name -NumPorts $switch.NumPorts -Mtu $switch.Mtu
}
Else {Write-Host “Vswitch $($switch.name) already exists on $($NEWHost). Checking port groups on this switch.”}

If ($switch.Name -eq “vSwitch0″) {
$MotionIP = Read-Host “What is the IP for the VMotion Network?”
$MyVMKs = $BASEHost | Get-VMHostNetworkAdapter -VMKernel
foreach ($vmk in $MyVMKs) {
if (($NEWHost | Get-VMHostNetworkAdapter -VMKernel).devicename -ne $vmk.DeviceName) {
Write-Host “Creating $($vmk) on $($NewHost).”
$vmkpg = Get-VirtualPortGroup -Name $vmk.portgroupname -VMHost $BASEhost
if ($vmk.PortGroupName -eq “VMkernel-VMotion”) {
$NewVMK = $NEWHost | New-VMHostNetworkAdapter -PortGroup $vmk.portgroupname -SubnetMask $vmk.subnetmask -VMotionEnabled $vmk.vmotionenabled -VirtualSwitch $vmkpg.virtualswitchname -IP $MotionIP}
else {$NewVMK = $NEWHost | New-VMHostNetworkAdapter -PortGroup $vmk.portgroupname -SubnetMask $vmk.subnetmask -VMotionEnabled $vmk.vmotionenabled -VirtualSwitch $vmkpg.virtualswitchname}
get-virtualportgroup -VMHost $NEWHost -Name $vmk.portgroupname | Set-VirtualPortGroup -VLanId $vmkpg.vlanid
}
}
}
Else {
$MyPGs = $switch | Get-VirtualPortGroup
foreach ($Pg in $MyPGs) {
If (($NEWHost |Get-VirtualPortGroup -Name $PG.Name-ErrorAction SilentlyContinue)-eq $null){
Write-Host “Creating Portgroup $($PG.Name) on $($switch)”
$NewPortGroup = $NEWHost |Get-VirtualSwitch -Name $switch |New-VirtualPortGroup -Name $PG.Name -VLanId $PG.VLanID
}
}
}

}

Hope this helps…

The part ESXi didn’t seem to like was the fact that the VMkernel ports are vmk0, vmk1, etc. instead of looking a bit like ESX portgroups. Still things to look at in “my” version before it is ready to use in Production.