Hi,
it takes care of the potential warning message from the connect-viserver command and the two last lines create the numeric increment to be added to the VM-prefix.

thanks

could you please explain the line 45 ,46 and 47

-WarningAction 0
1..$vm_count | foreach {
$y=”{0:D2}” -f $_

Regards,
Nitesh

Hi,
haven’t tested this but start with changing line 30 to only TEST, change row 12 to be 67 and then change row 38 so the first number is 33.

thanks

Hi,
are you looking at importing VM names or why do you need the CSV file?

//Magnus

Hi,
take a look at this, http://magander.se/2014/02/25/create-multiple-vms-from-existing-vsphere-vm-using-powercli/ post and see if it provides what you are looking for.

//Magnus

The script works in my new 6.0 ESXi enviorment. I don’t think that is what fixed it though. I think I just figured out over time and learning what I was looking at.
Is there an option to build a vm from a template?

Hi,
do you start the script in a powercli window?

thanks

PS C:\PowerShellScripts\VMBuildAutomation> C:\PowerShellScripts\VMBuildAutomation\VmBuilder.ps1
Connecting to vCenter Server vm-vcs.wolfpack.local
Connect-viserver : The term ‘Connect-viserver’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or
if a path was included, verify that the path is correct and try again.
At C:\PowerShellScripts\VMBuildAutomation\VmBuilder.ps1:44 char:1
+ Connect-viserver $vCenter -user $vCenterUser -password $vCenterUserPassword -War …
+ ~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Connect-viserver:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

Hi,
for the versions i tested the script i had zero failures. What versions are you running, what do you have to 1-2 days to see if it fails when you can just start the scrip manually and what failure do you get?

//Magnus

depends on what Linux Guest OS you will install.

//Magnus