Script Extracts and Examples (PowerCLI) - Revision history

Sstrutt: Typo fix

2016-10-04T15:36:10Z

Typo fix

← Older revision		Revision as of 15:36, 4 October 2016
Line 1:		Line 1:
	#REDIRECT [[~~:Category~~:Category:PowerCLI]]		#REDIRECT [[:Category:PowerCLI]]

Sstrutt: Deleted page contents, redirect to Category

2016-10-04T15:35:52Z

Deleted page contents, redirect to Category

Show changes

Sstrutt: Added link to ESX/HBA.NIC driver script for incoming external link

2012-05-22T06:35:49Z

Added link to ESX/HBA.NIC driver script for incoming external link

← Older revision		Revision as of 06:35, 22 May 2012
Line 1:		Line 1:
	'''Looking for examples of how to launch from command line or scheduler - see [[Getting_Started_(PowerCLI)#Scheduling\|Getting_Started_(PowerCLI) > Scheduling]]'''		* '''Looking for examples of how to launch from command line or scheduler - see [[Getting_Started_(PowerCLI)#Scheduling\|Getting_Started_(PowerCLI) > Scheduling]]'''
			* '''Looking for script to get ESX BIOS version - see [[ESX_Script_Extracts_and_Examples#ESX_BIOS,_NIC_and_HBA_Driver_Versions\|ESX_BIOS,_NIC_and_HBA_Driver_Versions]]'''

	{{Depreciated\|category=PowerCLI}}		{{Depreciated\|category=PowerCLI}}

Sstrutt: Added Depreciated template

2012-04-20T11:31:39Z

Added Depreciated template

← Older revision		Revision as of 11:31, 20 April 2012
Line 1:		Line 1:
	~~__NOINDEX__~~

	'''Looking for examples of how to launch from command line or scheduler - see [[Getting_Started_(PowerCLI)#Scheduling\|Getting_Started_(PowerCLI) > Scheduling]]'''		'''Looking for examples of how to launch from command line or scheduler - see [[Getting_Started_(PowerCLI)#Scheduling\|Getting_Started_(PowerCLI) > Scheduling]]'''

	~~'''This page is now depreciated as it was getting too large, the content will not be removed, but not be updated. New pages have been created that cover this content - see [[:Category:~~PowerCLI~~]]'''~~		{{Depreciated\|category=PowerCLI}}

	== Virtual Machine ==		== Virtual Machine ==
Line 1,408:		Line 1,406:
	}		}
	</source>		</source>

	~~[[Category:PowerCLI]]~~
	~~[[Category:Virtual Machine]]~~
	~~[[Category:ESX]]~~
	~~[[Category:Storage]]~~

Sstrutt: /* VM's Recently Created */ Typo correction

2012-01-30T20:00:19Z

VM's Recently Created: Typo correction

← Older revision		Revision as of 20:00, 30 January 2012
Line 356:		Line 356:
	$VC_List = "ESX-Check.csv"		$VC_List = "ESX-Check.csv"
	$EmailTo = "you@domain.com"		$EmailTo = "you@domain.com"
			$MailServer = "mail.domain.com"
	$days = 2		$days = 2
	$NotFoundText = "Not found/gone?"		$NotFoundText = "Not found/gone?"
Line 527:		Line 528:

	# Send email		# Send email
	$smtp = New-Object Net.Mail.SmtpClient -arg ~~"mailrelay.uk.michaelpage.local"~~		$smtp = New-Object Net.Mail.SmtpClient -arg $MailServer
	$msg = New-Object Net.Mail.MailMessage		$msg = New-Object Net.Mail.MailMessage

Sstrutt: Added NoIndex tag and depreciated note

2012-01-20T11:56:34Z

Added NoIndex tag and depreciated note

← Older revision		Revision as of 11:56, 20 January 2012
Line 1:		Line 1:
			__NOINDEX__

	'''Looking for examples of how to launch from command line or scheduler - see [[Getting_Started_(PowerCLI)#Scheduling\|Getting_Started_(PowerCLI) > Scheduling]]'''		'''Looking for examples of how to launch from command line or scheduler - see [[Getting_Started_(PowerCLI)#Scheduling\|Getting_Started_(PowerCLI) > Scheduling]]'''

			'''This page is now depreciated as it was getting too large, the content will not be removed, but not be updated. New pages have been created that cover this content - see [[:Category:PowerCLI]]'''

	== Virtual Machine ==		== Virtual Machine ==

Sstrutt: /* Migrate VMs Between vCentres */ Another typo

2012-01-20T09:23:22Z

Migrate VMs Between vCentres: Another typo

← Older revision		Revision as of 09:23, 20 January 2012
Line 781:		Line 781:
	Disconnect-VIServer -Server $VCconn -Confirm:$false		Disconnect-VIServer -Server $VCconn -Confirm:$false
	Stop-Transcript		Stop-Transcript
	<source>		</source>

	== ESX ==		== ESX ==

Sstrutt: /* Migrate VMs Between vCentres */ Typo

2012-01-20T09:22:47Z

Migrate VMs Between vCentres: Typo

← Older revision		Revision as of 09:22, 20 January 2012
Line 695:		Line 695:
	========================================================================================================================================#>		========================================================================================================================================#>

	$SourceVC = "~~uka-sr-vcent-10~~"		$SourceVC = "vcentreA"
	$SourceVapp = "~~GBR 4 Labs~~"		$SourceVapp = "vApp"

	$DestVC = "~~ukb-sr-vcent-10~~"		$DestVC = "vcentreB"
	$DestCluster = "~~UKA_LabManager~~"		$DestCluster = "Cluster"
	$DestFolder = "~~PSC 3.5.5~~"		$DestFolder = "Folder"

	$UserFile = "User.fil"		$UserFile = "User.fil"

Sstrutt: /* Virtual Machine */ Added "Migrate VMs Between vCentres"

2012-01-20T09:21:32Z

Virtual Machine: Added "Migrate VMs Between vCentres"

@@ Line 677: / Line 677: @@
 Stop-Transcript
 </source>
 == ESX ==

Sstrutt: /* Add Attributes to VMs from CSV */ Forgot to end source

2012-01-16T14:41:27Z

Add Attributes to VMs from CSV: Forgot to end source

← Older revision		Revision as of 14:41, 16 January 2012
Line 538:		Line 538:

	=== Add Attributes to VMs from CSV ===		=== Add Attributes to VMs from CSV ===
	You have the option in vCentre to create your own custom attributes to any of the standard objects. This can be incredibly useful if you have a sprawling estate of VM's to manage for various different parts of your company, as you can record information like Owning Dept., Product Family etc against your VM's. The only problem is that you then have fields that have to be manually updated (that and the fact that the info is only held in a VM's vCentre database records, not its VMX, so if you have to re-add a machine to vCentre, you'll lose the custom attributes you populated.		You have the option in vCentre to create your own custom attributes to any of the standard objects. This can be incredibly useful if you have a sprawling estate of VM's to manage for various different parts of your company, as you can record information like Owning Dept., Product Family etc against your VM's.

			The only problem is that you then have fields that have to be manually updated (that and the fact that the info is only held in a VM's vCentre database records, not its VMX, so if you have to re-add a machine to vCentre, you'll lose the custom attributes you populated.

	The following script allows you to update VM attributes from a CSV file (which can be very convenient if you've just deployed 20 VM's for a project).		The following script allows you to update VM attributes from a CSV file (which can be very convenient if you've just deployed 20 VM's for a project).
Line 674:		Line 676:
	}		}
	Stop-Transcript		Stop-Transcript
			</source>

	== ESX ==		== ESX ==

← Older revision		Revision as of 06:35, 22 May 2012
Line 1:		Line 1:
	'''Looking for examples of how to launch from command line or scheduler - see [[Getting_Started_(PowerCLI)#Scheduling\|Getting_Started_(PowerCLI) > Scheduling]]'''		* '''Looking for examples of how to launch from command line or scheduler - see [[Getting_Started_(PowerCLI)#Scheduling\|Getting_Started_(PowerCLI) > Scheduling]]'''
			* '''Looking for script to get ESX BIOS version - see [[ESX_Script_Extracts_and_Examples#ESX_BIOS,_NIC_and_HBA_Driver_Versions\|ESX_BIOS,_NIC_and_HBA_Driver_Versions]]'''

	{{Depreciated\|category=PowerCLI}}		{{Depreciated\|category=PowerCLI}}