Last I encountered some errors while doing a storage VMotion for a couple of VMs during a migration from ESX 3.5 to vSphere 4.1.
When looking in the logs for the CBTMotion errors I found following messages.
CBTMotion: scsi0:1: Clone: failed to start block tracking session on source disk: Change tracking is not active for this disk.
CBTMotion: scsi0:1: failed to clone disk from /vmfs/volumes/694286b5-b7bf1d73/VM01/VM01_1.vmdk to /vmfs/volumes/2b0e242d-40129/VM01/VM01_1.vmdk.
CBTMotion: disk clone failed, aborting Storage VMotion.
Msg_Post: Error
[msg.cbtmotion.disk.clone.failed] Disk clone failed. Canceling Storage vMotion.
To solve this I created a snapshot on the VM and committed it. After this the storage VMotion worked successfully.
Yesterday we were offered the occasion to meet with some people (Greg Taylor & Ross Smith IV) from MS Exchange product team during an exclusive pro-exchange event. Ilse Van Criekinge also joined the party.
Here’s a twitter-style overview of the stuff we discussed.
- ExMon: community member wondered why he couldn’t see the client latency anymore when using exmon
- Somebody else explained a complicated (from the admin side) Public Folder based system for an end-user to be able to manage distribution lists themselves. Additionally this very same customer also used some public folder based contacts to hide recipients in some cases (if I understood the story correctly). Suggestion from the product team was to use ECP for most of this functionality. This would however require a lot of effort in training the end-user.
- MS IT DB Design
- DAG takes care of switching mbx db to another instance, but the default PF store is still hard-coded. So you’re in trouble if that one went down togheter with the active mailbox database. Probably fixed in next roll up, but no guarantee.
- MS IT Storage design: 300mbx/db on a single physical disk containing both the database it selves, the content index and the transaction logs. In case of hard disk failure another copy of the database in the same datacenter is activated. MS IT refreshes hardware every 3 years. During this refresh the mailbox quota is doubled. However they use thin provisioning for their mailboxes, while mailboxes have a 5Gb quota only 3Gb is available for them. When designing their solution they take 10 years of trending into account. PTSs are still allowed at Microsoft because of legal requirements around the Globe. Retention policies do exist but are opt in.
- Archiving in E2K10. Read only access does not exist as such. Suggestion was to use either single item recovery or delegation hold. Quota’s do exist in the dumpster. 20Gb warning & 30Gb error.
- Single Instance Storage: SIS is removed in E2K10. When moving from E2007 to E2010 that should not be an issue as SIS is nowhere taken into account when showing mailbox size. The counter that existed was inaccurate. SIS has been removed in favor IO improvements: search, sort, mailbox move etc. A sort of the inbox takes 1 IO operation as opposed to 7 in previous versions.
- MS IT Backup strategy: Ross discussed the case where they lost 3,5 days worth of email for 8000 users because of a SAN crash. Documented the evolution of the strategy over time.
- Storage calculator. (Ross is the author of this tool).
- CAS HA on VM; multiple CAS or rely on vmotion? MS obviously recommends setting up multiple CAS servers. Use HLB to reduce number of machines required. Aim for 80% CPU. Look at Kemp for cheap hardware load balancers.
- X500 & LegacyExchangeDN: chicken vs. the eg. Kept for backwards compatibility.
- UAG vs. TMG. White paper available. TMG mainly for outbound traffic. UAG for inbound traffic, but built on top of TMG. TMG is the way to go if you only need to publish exchange. If you need/want more than use UAG. However it cannot do certificate based mobile devices!
- Recovering entire folder structures is not possible anymore. Will probably not change.
- Outlook 2007 archiving add-on <=> No date.
- EAS mbx policy difference in RTM vs. SP1: “allow block quarantine” brought to ECP
- Outlook anywhere client certificate authentication. Smart card authentication will be possible when using Outlook 2010 SP1 + Exchange 2010 SP1 + … Will be IPSec based. White paper on the way.
- Vanity domains (as Greg called it): there’s only one common OWA legacy URL however. Use multiple OWA virtual directories or servers.
- Renaming forest with exchange server present. Not supported and never will be. Risky. Also consider SMS, SAP etc.
- Select from address; no plans. Add-ons do exist however. (e.g. http://www.howto-outlook.com/tag/mail-composing)
- HT tries to collapse multiple meeting requests. Think of an original followed up by a number of corrections.
- Operational improvements is E2010: PowerShell, ECP, out of office etc.
- Sent/deleted items in the wrong folder. I personally have a case where I cannot get the steps explained by Ilse to work.
- Recovery database
- Some more storage calculator discussions and a little demo.
Somewhere in between these friendly people from MS were kind enough to answer a number of questions provided to me by some colleagues:
1) Retiring/uninstalling the fist CAS server in a domain/site has effect on the RPCClientAccessServer attribute which can affect/interrupt mailbox access. Are there other issues we can encounter while retiring a/the first CAS or HUB or MBX server?
==> Recommendations is to always create a CASarray even when there’s only one CAS server. Other impact may be PF, OAB generation+distribution, Routing table, arbitration mailboxes, …
2) We would like to separate the traffic between our regions NA – EU (North America – Europe) and the traffic in the regions, (NA= E2K7 and EU = E2K10) is it possible to force the hub transport traffic between those sites over a/2 dedicated hub transport servers as this is easier to troubleshoot. We did it in e2k3 with routing groups.
==> Not possible
3) We want to achieve the pic below… so Outlook/mapi traffic is always connected to CAS1 and CAS2 but not to CAS3 and CAS4 as we want to separate our intern mapi traffic from owapp traffic.
All server are in the same site. CAS1 and CAS2 are in one nlb Cas3 and 4 in another NLB.
The clientaccessarray has the fqdn of the nlb of cas 1 and 2. And rpcclientaccessserver points to the clientaccessarray.
Get-clientaccessarray although gives the 4 Cas servers as members… does this also means that Outlook can connect to cas 3 and 4 as they are NOT in the nlb(which we do not want)?
==> This is possible by proper configuration of DNS aliases and NLB setup. Generally not a good idea however. I CAS2 fails or is in maintenance then CAS1 becomes a single point of failure
Last but not least there were also a number of questions I had of my own. Most of them are coming from discussion with customers in the past. They mostly confirmed my answer, which is always a good thing :-)
- Routing intra exchange org e-mail over the internet? Possible by using Riverbed for instance. Not supported. (Note: most of the comment came from the community, not from MS.)
- “Something” inbetween ISA (DMZ) & CAS (LAN). ==> you could put e.g. Cisco firewalls in front of the ISA but there’s not really any advantage in adding something between ISA & CAS.
- Secondary address resolved to primary in older versions? ==> Has always shown this behavior.
The first version of TDP for Mail supporting Exchange Server 2010 was released during the summer holiday season. A customer was validating functionality offered for restoring individual mails/mailboxes.
Full database backup/restores were working fine and we deployed the mapi toolkit as documented in the IBM Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server Installation and User’s Guide V6.1.2. Didn’t work. The customer subsequently contacts Tivoli support and comes back with the answer “install the CAS role on your MBX servers”.
That let to kind of a “huh?” moment as we used the Exchange Server role based architecture in our deployment. A clever colleague of mine came up with a document confirming that statement:
In order to perform Mailbox Restore (IMR) operations on Exchange Server 2010, the Exchange Server that you are performing the mailbox restore on must have the Mailbox Server Role and the Client Access Server (CAS) Role.
Workaround: Perform the mailbox restore operation on an Exchange server that has the Mailbox Server Role and Client Access Server (CAS) Role.
What we did not find were any “design” guidelines. So a couple of questions remain:
- Do we need to install the CAS role on every MBX server?
- Do we need database copies (we’re talking DAG here) on the server with MBX+CAS roles? Do they need to be active?
- Can we use a “management” server with an empty db, outside of the DAG for this?
- How are we going to shield this CAS from users and applications?
- …
Al lot of questions and few answers in a project that is nearing completion. Hence we recommended the customer to use the recovery database feature and restore-mailbox management shell cmdlet to restore individual items. Worked perfectly.
Anyway, I’m still interested to learn how IBM thinks we should set this up in an environment that does not deploy all roles on a single server. Which is not the type of customers that would pick TSM as there backup software of choice in the first place.
One of the new features in vSphere 4.1 is the ability to configure Host affinity rules for DRS. These enable you to split your vSphere cluster in several groups of hosts and assign assign a subset of your VMs to one of these groups.
There are plenty of use cases for this:
- Netapp Metrocluster
- Applications licensed based on CPUs
- performance sensitive applications
- …
In my case the cluster is spread over 2 sites, one production site and a failover site. The failover site is used to run test & dev servers. Only in case of serious problems on the production site the VMs should be moved to the failover site.
Open the cluster settings and create a “Virtual Machines DRS Group”
I create a group called FailoverSiteVMs which contains the test & dev servers.
A second group is called ProductionSiteVMs which contains the production virtual machines.
Now we need to create 2 “Hosts DRS Groups. One for the FailoverSite.
And another one for the Production site.
An overview of the configured groups
Once all the groups are created you can start creating DRS rules. Select the “Virtual Machines to Hosts” as type, the Cluster Vms Group and the Cluster Hosts Groups.
There are 2 main types of DRS rules:
- Should run on hosts in group
- Must run on hosts in group
- The “Should run on hosts in group” rule keeps the VMs on the configured hosts but HA can violate the DRS rules and start the VMs on the failover hosts.
When the “Must run on hosts in group” type is used HA won’t violate the DRS rules and the VMs won’t be restarted on the failover hosts.
Once the rules are configured the rules dialog looks like this.
VMware just released vSphere 4.1, Site Recovery Manager 4.1 and VMware vCenter Server Heartbeat 6.3.
The downloads can be found at:
Site Recovery Manager 4.1 – Release Notes
vSphere Management Assistant (vMA) 4.1
VMware vCenter Server Heartbeat 6.3 – Release Notes
Both vCenter 4.1 and SRM 4.1 are now only installable on 64-bit host platforms.
Here’s a little slideshow of a bunch of pictures I took during todays ICT on the bike event.
This slideshow requires JavaScript.
Superb weather, a challenging track, a professional organization and some entertaining people. Bottom line; I had a good time. Especially as it has been some time since I rode such a distance (did 100K). My climbing skills need some (a lot actually) but that hardly comes as a surprise.
Alternatively you can peak at some individual images in this gallery (in the correct order):
Earlier on today Symantec tweeted an article comparing archiving features offered by both Symantec Enterprise Vault and Microsoft Exchange Server. They might call it a
Great article
but I’m not sure I agree. From my point of view the article reveals nothing that isn’t known for months. Exchange 2010 is RTM for half a year already. What I really would like to see (and so are others) is a detailed comparison between both Enterprise Vault and Exchange Server. So far I’ve not been able to find such a comparison anywhere on the public internet, so let me have a shot at it myself:
| Microsoft Exchange Server 2010 | Symantec Enterprise Vault 9 | |
| Archiving Targets |
|
|
| Prerequisites |
|
|
| Integration |
|
|
| Offline Archive Support | None | Offline Vault |
| Storage |
|
|
| Legal Position |
|
|
| Migration | Easy (?)
|
Hard (?)
|
| Cost |
|
|
| Conclusion | Low end alternative for pst-files for the first time ever | If you want to archive…
|
Note: This info is preliminary. Both products are in need for E2K10 SP1 before they can be taken seriously. Enterprise Vault 9 is still in beta at the moment and will only support E2010 from SP1 onwards. Exchange Server 2010 will allow separating primary and secondary mailboxes starting with SP1. This highly anticipated Service Pack will probably be released somewhere around Q3 of this year.
Apart from that I’m convinced we’re actually seeing the trusted Microsoft strategy of entering the market with a basic feature set. They feel the temperature and then gain market share gradually. Release after release.
Whether you agree or not, or just want to contribute to the discussion; feel free to comment.
I’ve had the chance to play around with some PowerShell scripting again. A nice occasion to try and include some Comment Based Help I read about in TechNet Magazine a couple of months ago. However I couldn’t get it to work in combination with the standard script header template I tend to use for all of my scripts.
I experimented with commenting out each line on its own:
#header # #help
or using comment blocks
<# header help #>
even
<# header #> <# help #>
and a couple more variations, but no joy. After some “binging” I ended up reading about_Comment_Based_Help;
All of the lines in a comment-based Help topic must be contiguous. If a comment-based Help topic follows a comment that is not part of the Help topic, there must be at least one blank line between the last non-Help comment line and the beginning of the comment-based Help.
It still took some more trial and error to realize that an “empty line” well, needs to be really empty. It cannot contain a comment character either! Call me stupid ;-)
Here’s an example of how it should be done (Ref. line 22):
#========================================================================================================
# AUTHOR
# Koen Vermoesen
# ***.***@***.***
# 2010-05-20
#========================================================================================================
# SCRIPT
# Create custom address lists based on a CSV file
#========================================================================================================
# PREREQUISITES
# /
#========================================================================================================
# CHANGE HISTORY:
# 2010-05-10 Initial version
#========================================================================================================
# TO DO
# /
#========================================================================================================
# COMMENTS
# Parent lists need to proceed child lists in your input csv-file!
#========================================================================================================
#.SYNOPSIS
#Create custom address lists
#
#.DESCRIPTION
#Create custom address lists based on a CSV file called "CreateAddressLists.csv" with these columns
# - Name
# - Container
# - RecipientFilter
#The script will check if the "Container"-field is empty and run de cmdlet with or without "-container" option
#
#.Link
#http://technet.microsoft.com/en-us/library/aa996912.aspx
$Input = "CreateAddressLists.csv"
Import-CSV $Input | Foreach { If ($_.Container -eq "") {New-AddressList -Name $_.Name -RecipientFilter $_.RecipientFilter} else {New-AddressList -Name $_.Name -Container $_.Container -RecipientFilter $_.RecipientFilter}}
For those of you wondering, I have the habit of using scripts not just for bulky or repetitive actions but also as means of documentation and standardization. Additionally these scripts come in handy If you ever need to rebuild some part of the infrastructure. Hence the 35 lines of comment for only 2 lines of code.
Notepad++ supports Powershell from version v5.6 but the VMware PowerCLI cmdlets aren’t included.
So I created PowerCLI Language definition file for syntax highlighting. It contains the cmdlets available in vSphere PowerCLI 4 Update 1 and vCenter Update Manager PowerCLI 4 Update 1.
<NotepadPlus>
<UserLang name="PowerCLI" ext="ps1">
<Settings>
<Global caseIgnored="yes" />
<TreatAsSymbol comment="no" commentLine="no" />
<Prefix words1="yes" words2="yes" words3="no" words4="no" />
</Settings>
<KeywordLists>
<Keywords name="Delimiters">000000</Keywords>
<Keywords name="Folder+"></Keywords>
<Keywords name="Folder-"></Keywords>
<Keywords name="Operators"></Keywords>
<Keywords name="Comment"></Keywords>
<Keywords name="Words1">Add-PassthroughDevice Add-VMHost Add-VmHostNtpServer Apply-DrsRecommendation Apply-VMHostProfile Connect-VIServer Copy-DatastoreItem Copy-HardDisk Copy-VMGuestFile Disconnect-VIServer Dismount-Tools Export-VApp Export-VMHostProfile Get-Annotation Get-CDDrive Get-Cluster Get-CustomAttribute Get-Datacenter Get-Datastore Get-DrsRecommendation Get-DrsRule Get-FloppyDrive Get-Folder Get-HardDisk Get-Inventory Get-IScsiHbaTarget Get-Log Get-LogType Get-NetworkAdapter Get-NicTeamingPolicy Get-OSCustomizationNicMapping Get-OSCustomizationSpec Get-PassthroughDevice Get-PowerCLIConfiguration Get-PowerCLIVersion Get-ResourcePool Get-ScsiLun Get-ScsiLunPath Get-Snapshot Get-Stat Get-StatInterval Get-StatType Get-Task Get-Template Get-UsbDevice Get-VApp Get-VICredentialStoreItem Get-VIEvent Get-View Get-VIObjectByVIView Get-VIPermission Get-VIPrivilege Get-VIRole Get-VirtualPortGroup Get-VirtualSwitch Get-VM Get-VMGuest Get-VMGuestNetworkInterface Get-VMGuestRoute Get-VMHost Get-VMHostAccount Get-VMHostAdvancedConfiguration Get-VMHostAvailableTimeZone Get-VMHostDiagnosticPartition Get-VMHostFirewallDefaultPolicy Get-VMHostFirewallException Get-VMHostFirmware Get-VMHostHba Get-VMHostModule Get-VMHostNetwork Get-VMHostNetworkAdapter Get-VMHostNtpServer Get-VMHostProfile Get-VMHostService Get-VMHostSnmp Get-VMHostStartPolicy Get-VMHostStorage Get-VMHostSysLogServer Get-VMQuestion Get-VMResourceConfiguration Get-VMStartPolicy Import-VApp Import-VMHostProfile Install-VMHostPatch Invoke-VMScript Mount-Tools Move-Cluster Move-Datacenter Move-Folder Move-Inventory Move-ResourcePool Move-Template Move-VM Move-VMHostNew-CDDrive New-ClusterNew-CustomAttribute New-CustomField New-Datacenter New-Datastore New-DrsRule New-FloppyDrive New-Folder New-HardDisk New-IScsiHbaTarget New-NetworkAdapter New-OSCustomizationNicMapping New-OSCustomizationSpec New-ResourcePool New-Snapshot New-StatInterval New-Template New-VApp New-VICredentialStoreItem New-VIPermission New-VIRole New-VirtualPortGroup New-VirtualSwitch New-VM New-VMGuestRoute New-VMHostAccount New-VMHostNetworkAdapter New-VMHostProfile Remove-CDDrive Remove-Cluster Remove-CustomAttribute Remove-CustomField Remove-Datacenter Remove-Datastore Remove-DrsRule Remove-FloppyDrive Remove-Folder Remove-HardDisk Remove-Inventory Remove-IScsiHbaTarget Remove-NetworkAdapter Remove-OSCustomizationNicMap... Remove-OSCustomizationSpec Remove-PassthroughDevice Remove-ResourcePool Remove-Snapshot Remove-StatInterval Remove-Template Remove-UsbDevice Remove-VApp Remove-VICredentialStoreItem Remove-VIPermission Remove-VIRole Remove-VirtualPortGroup Remove-VirtualSwitch Remove-VM Remove-VMGuestRoute Remove-VMHost Remove-VMHostAccount Remove-VMHostNetworkAdapter Remove-VMHostNtpServer Remove-VMHostProfile Restart-VM Restart-VMGuest Restart-VMHost Restart-VMHostService Set-Annotation Set-CDDrive Set-Cluster Set-CustomAttribute Set-CustomField Set-Datacenter Set-Datastore Set-DrsRule Set-FloppyDrive Set-Folder Set-HardDisk Set-IScsiHbaTarget Set-NetworkAdapter Set-NicTeamingPolicy Set-OSCustomizationNicMapping Set-OSCustomizationSpec Set-PowerCLIConfiguration Set-ResourcePool Set-ScsiLun Set-ScsiLunPath Set-Snapshot Set-StatInterval Set-Template Set-VApp Set-VIPermission Set-VIRole Set-VirtualPortGroup Set-VirtualSwitch Set-VM Set-VMGuestNetworkInterface Set-VMGuestRoute Set-VMHost Set-VMHostAccount Set-VMHostAdvancedConfiguration Set-VMHostDiagnosticPartition Set-VMHostFirewallDefaultPolicy Set-VMHostFirewallException Set-VMHostFirmware Set-VMHostHba Set-VMHostModule Set-VMHostNetwork Set-VMHostNetworkAdapter Set-VMHostProfile Set-VMHostService Set-VMHostSnmp Set-VMHostStartPolicy Set-VMHostStorage Set-VMHostSysLogServer Set-VMQuestion Set-VMResourceConfiguration Set-VMStartPolicy Shutdown-VMGuest Start-VApp Start-VM Start-VMHost Start-VMHostService Stop-Task Stop-VApp Stop-VM Stop-VMHost Stop-VMHostService Suspend-VM Suspend-VMGuest Suspend-VMHost Test-VMHostProfileCompliance Test-VMHostSnmp Update-Tools Wait-Task Attach-Baseline Detach-Baseline Download-Patch Get-Baseline Get-Compliance Get-Patch Get-PatchBaseline New-PatchBaseline Remediate-Inventory Remove-Baseline Scan-Inventory Set-PatchBaseline Stage-Patch</Keywords>
<Keywords name="Words2">Answer-VMQuestion Get-ESX Get-PowerCLIDocumentation Get-VC Get-VIServer Get-VIToolkitConfiguration Get-VIToolkitVersion Set-VIToolkitConfiguration</Keywords>
<Keywords name="Words3"></Keywords>
<Keywords name="Words4"></Keywords>
</KeywordLists>
<Styles>
<WordsStyle name="DEFAULT" styleID="11" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="FOLDEROPEN" styleID="12" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="FOLDERCLOSE" styleID="13" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="KEYWORD1" styleID="5" fgColor="0000FF" bgColor="FFFFFF" fontName="" fontStyle="1" />
<WordsStyle name="KEYWORD2" styleID="6" fgColor="8080FF" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="KEYWORD3" styleID="7" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="KEYWORD4" styleID="8" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="COMMENT" styleID="1" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="COMMENT LINE" styleID="2" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="NUMBER" styleID="4" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="OPERATOR" styleID="10" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="DELIMINER1" styleID="14" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="DELIMINER2" styleID="15" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
<WordsStyle name="DELIMINER3" styleID="16" fgColor="000000" bgColor="FFFFFF" fontName="" fontStyle="0" />
</Styles>
</UserLang>
</NotepadPlus>
To add PowerCLI as a user-defined language %APPDATA%\Notepad++\userDefineLang.xml and add the above configuration to this file.
Secondly I created a PowerCLI auto-completion file which contains the same PowerCLI cmdlets. This configuration needs to be added to C:\Program Files\Notepad++\plugins\APIs\PowerCLI.xml. The name of the auto-completion file needs to be the same as defined in the user-defined language definition file.
<NotepadPlus> <AutoComplete> <KeyWord name="Add-PassthroughDevice"/> <KeyWord name="Add-VMHost"/> <KeyWord name="Add-VmHostNtpServer"/> <KeyWord name="Answer-VMQuestion"/> <KeyWord name="Apply-DrsRecommendation"/> <KeyWord name="Apply-VMHostProfile"/> <KeyWord name="Attach-Baseline"/> <KeyWord name="Connect-VIServer"/> <KeyWord name="Copy-DatastoreItem"/> <KeyWord name="Copy-HardDisk"/> <KeyWord name="Copy-VMGuestFile"/> <KeyWord name="Detach-Baseline"/> <KeyWord name="Disconnect-VIServer"/> <KeyWord name="Dismount-Tools"/> <KeyWord name="Download-Patch"/> <KeyWord name="Export-VApp"/> <KeyWord name="Export-VMHostProfile"/> <KeyWord name="Get-Annotation"/> <KeyWord name="Get-Baseline"/> <KeyWord name="Get-CDDrive"/> <KeyWord name="Get-Cluster"/> <KeyWord name="Get-Compliance"/> <KeyWord name="Get-CustomAttribute"/> <KeyWord name="Get-Datacenter"/> <KeyWord name="Get-Datastore"/> <KeyWord name="Get-DrsRecommendation"/> <KeyWord name="Get-DrsRule"/> <KeyWord name="Get-ESX"/> <KeyWord name="Get-FloppyDrive"/> <KeyWord name="Get-Folder"/> <KeyWord name="Get-HardDisk"/> <KeyWord name="Get-IScsiHbaTarget"/> <KeyWord name="Get-Inventory"/> <KeyWord name="Get-Log"/> <KeyWord name="Get-LogType"/> <KeyWord name="Get-NetworkAdapter"/> <KeyWord name="Get-NicTeamingPolicy"/> <KeyWord name="Get-OSCustomizationNicMapping"/> <KeyWord name="Get-OSCustomizationSpec"/> <KeyWord name="Get-PassthroughDevice"/> <KeyWord name="Get-Patch"/> <KeyWord name="Get-PatchBaseline"/> <KeyWord name="Get-PowerCLIConfiguration"/> <KeyWord name="Get-PowerCLIDocumentation"/> <KeyWord name="Get-PowerCLIVersion"/> <KeyWord name="Get-ResourcePool"/> <KeyWord name="Get-ScsiLun"/> <KeyWord name="Get-ScsiLunPath"/> <KeyWord name="Get-Snapshot"/> <KeyWord name="Get-Stat"/> <KeyWord name="Get-StatInterval"/> <KeyWord name="Get-StatType"/> <KeyWord name="Get-Task"/> <KeyWord name="Get-Template"/> <KeyWord name="Get-UsbDevice"/> <KeyWord name="Get-VApp"/> <KeyWord name="Get-VC"/> <KeyWord name="Get-VICredentialStoreItem"/> <KeyWord name="Get-VIEvent"/> <KeyWord name="Get-VIObjectByVIView"/> <KeyWord name="Get-VIPermission"/> <KeyWord name="Get-VIPrivilege"/> <KeyWord name="Get-VIRole"/> <KeyWord name="Get-VIServer"/> <KeyWord name="Get-VIToolkitConfiguration"/> <KeyWord name="Get-VIToolkitVersion"/> <KeyWord name="Get-VM"/> <KeyWord name="Get-VMGuest"/> <KeyWord name="Get-VMGuestNetworkInterface"/> <KeyWord name="Get-VMGuestRoute"/> <KeyWord name="Get-VMHost"/> <KeyWord name="Get-VMHostAccount"/> <KeyWord name="Get-VMHostAdvancedConfiguration"/> <KeyWord name="Get-VMHostAvailableTimeZone"/> <KeyWord name="Get-VMHostDiagnosticPartition"/> <KeyWord name="Get-VMHostFirewallDefaultPolicy"/> <KeyWord name="Get-VMHostFirewallException"/> <KeyWord name="Get-VMHostFirmware"/> <KeyWord name="Get-VMHostHba"/> <KeyWord name="Get-VMHostModule"/> <KeyWord name="Get-VMHostNetwork"/> <KeyWord name="Get-VMHostNetworkAdapter"/> <KeyWord name="Get-VMHostNtpServer"/> <KeyWord name="Get-VMHostProfile"/> <KeyWord name="Get-VMHostService"/> <KeyWord name="Get-VMHostSnmp"/> <KeyWord name="Get-VMHostStartPolicy"/> <KeyWord name="Get-VMHostStorage"/> <KeyWord name="Get-VMHostSysLogServer"/> <KeyWord name="Get-VMQuestion"/> <KeyWord name="Get-VMResourceConfiguration"/> <KeyWord name="Get-VMStartPolicy"/> <KeyWord name="Get-View"/> <KeyWord name="Get-VirtualPortGroup"/> <KeyWord name="Get-VirtualSwitch"/> <KeyWord name="Import-VApp"/> <KeyWord name="Import-VMHostProfile"/> <KeyWord name="Install-VMHostPatch"/> <KeyWord name="Invoke-VMScript"/> <KeyWord name="Mount-Tools"/> <KeyWord name="Move-Cluster"/> <KeyWord name="Move-Datacenter"/> <KeyWord name="Move-Folder"/> <KeyWord name="Move-Inventory"/> <KeyWord name="Move-ResourcePool"/> <KeyWord name="Move-Template"/> <KeyWord name="Move-VM"/> <KeyWord name="Move-VMHost"/> <KeyWord name="New-CDDrive"/> <KeyWord name="New-Cluster"/> <KeyWord name="New-CustomAttribute"/> <KeyWord name="New-CustomField"/> <KeyWord name="New-Datacenter"/> <KeyWord name="New-Datastore"/> <KeyWord name="New-DrsRule"/> <KeyWord name="New-FloppyDrive"/> <KeyWord name="New-Folder"/> <KeyWord name="New-HardDisk"/> <KeyWord name="New-IScsiHbaTarget"/> <KeyWord name="New-NetworkAdapter"/> <KeyWord name="New-OSCustomizationNicMapping"/> <KeyWord name="New-OSCustomizationSpec"/> <KeyWord name="New-PatchBaseline"/> <KeyWord name="New-ResourcePool"/> <KeyWord name="New-Snapshot"/> <KeyWord name="New-StatInterval"/> <KeyWord name="New-Template"/> <KeyWord name="New-VApp"/> <KeyWord name="New-VICredentialStoreItem"/> <KeyWord name="New-VIPermission"/> <KeyWord name="New-VIRole"/> <KeyWord name="New-VM"/> <KeyWord name="New-VMGuestRoute"/> <KeyWord name="New-VMHostAccount"/> <KeyWord name="New-VMHostNetworkAdapter"/> <KeyWord name="New-VMHostProfile"/> <KeyWord name="New-VirtualPortGroup"/> <KeyWord name="New-VirtualSwitch"/> <KeyWord name="Remediate-Inventory"/> <KeyWord name="Remove-Baseline"/> <KeyWord name="Remove-CDDrive"/> <KeyWord name="Remove-Cluster"/> <KeyWord name="Remove-CustomAttribute"/> <KeyWord name="Remove-CustomField"/> <KeyWord name="Remove-Datacenter"/> <KeyWord name="Remove-Datastore"/> <KeyWord name="Remove-DrsRule"/> <KeyWord name="Remove-FloppyDrive"/> <KeyWord name="Remove-Folder"/> <KeyWord name="Remove-HardDisk"/> <KeyWord name="Remove-IScsiHbaTarget"/> <KeyWord name="Remove-Inventory"/> <KeyWord name="Remove-NetworkAdapter"/> <KeyWord name="Remove-OSCustomizationNicMap..."/> <KeyWord name="Remove-OSCustomizationSpec"/> <KeyWord name="Remove-PassthroughDevice"/> <KeyWord name="Remove-ResourcePool"/> <KeyWord name="Remove-Snapshot"/> <KeyWord name="Remove-StatInterval"/> <KeyWord name="Remove-Template"/> <KeyWord name="Remove-UsbDevice"/> <KeyWord name="Remove-VApp"/> <KeyWord name="Remove-VICredentialStoreItem"/> <KeyWord name="Remove-VIPermission"/> <KeyWord name="Remove-VIRole"/> <KeyWord name="Remove-VM"/> <KeyWord name="Remove-VMGuestRoute"/> <KeyWord name="Remove-VMHost"/> <KeyWord name="Remove-VMHostAccount"/> <KeyWord name="Remove-VMHostNetworkAdapter"/> <KeyWord name="Remove-VMHostNtpServer"/> <KeyWord name="Remove-VMHostProfile"/> <KeyWord name="Remove-VirtualPortGroup"/> <KeyWord name="Remove-VirtualSwitch"/> <KeyWord name="Restart-VM"/> <KeyWord name="Restart-VMGuest"/> <KeyWord name="Restart-VMHost"/> <KeyWord name="Restart-VMHostService"/> <KeyWord name="Scan-Inventory"/> <KeyWord name="Set-Annotation"/> <KeyWord name="Set-CDDrive"/> <KeyWord name="Set-Cluster"/> <KeyWord name="Set-CustomAttribute"/> <KeyWord name="Set-CustomField"/> <KeyWord name="Set-Datacenter"/> <KeyWord name="Set-Datastore"/> <KeyWord name="Set-DrsRule"/> <KeyWord name="Set-FloppyDrive"/> <KeyWord name="Set-Folder"/> <KeyWord name="Set-HardDisk"/> <KeyWord name="Set-IScsiHbaTarget"/> <KeyWord name="Set-NetworkAdapter"/> <KeyWord name="Set-NicTeamingPolicy"/> <KeyWord name="Set-OSCustomizationNicMapping"/> <KeyWord name="Set-OSCustomizationSpec"/> <KeyWord name="Set-PatchBaseline"/> <KeyWord name="Set-PowerCLIConfiguration"/> <KeyWord name="Set-ResourcePool"/> <KeyWord name="Set-ScsiLun"/> <KeyWord name="Set-ScsiLunPath"/> <KeyWord name="Set-Snapshot"/> <KeyWord name="Set-StatInterval"/> <KeyWord name="Set-Template"/> <KeyWord name="Set-VApp"/> <KeyWord name="Set-VIPermission"/> <KeyWord name="Set-VIRole"/> <KeyWord name="Set-VM"/> <KeyWord name="Set-VMGuestNetworkInterface"/> <KeyWord name="Set-VMGuestRoute"/> <KeyWord name="Set-VMHost"/> <KeyWord name="Set-VMHostAccount"/> <KeyWord name="Set-VMHostAdvancedConfiguration"/> <KeyWord name="Set-VMHostDiagnosticPartition"/> <KeyWord name="Set-VMHostFirewallDefaultPolicy"/> <KeyWord name="Set-VMHostFirewallException"/> <KeyWord name="Set-VMHostFirmware"/> <KeyWord name="Set-VMHostHba"/> <KeyWord name="Set-VMHostModule"/> <KeyWord name="Set-VMHostNetwork"/> <KeyWord name="Set-VMHostNetworkAdapter"/> <KeyWord name="Set-VMHostProfile"/> <KeyWord name="Set-VMHostService"/> <KeyWord name="Set-VMHostSnmp"/> <KeyWord name="Set-VMHostStartPolicy"/> <KeyWord name="Set-VMHostStorage"/> <KeyWord name="Set-VMHostSysLogServer"/> <KeyWord name="Set-VMQuestion"/> <KeyWord name="Set-VMResourceConfiguration"/> <KeyWord name="Set-VMStartPolicy"/> <KeyWord name="Set-VirtualPortGroup"/> <KeyWord name="Set-VirtualSwitch"/> <KeyWord name="Shutdown-VMGuest"/> <KeyWord name="Stage-Patch"/> <KeyWord name="Start-VApp"/> <KeyWord name="Start-VM"/> <KeyWord name="Start-VMHost"/> <KeyWord name="Start-VMHostService"/> <KeyWord name="Stop-Task"/> <KeyWord name="Stop-VApp"/> <KeyWord name="Stop-VM"/> <KeyWord name="Stop-VMHost"/> <KeyWord name="Stop-VMHostService"/> <KeyWord name="Suspend-VM"/> <KeyWord name="Suspend-VMGuest"/> <KeyWord name="Suspend-VMHost"/> <KeyWord name="Test-VMHostProfileCompliance"/> <KeyWord name="Test-VMHostSnmp"/> <KeyWord name="Update-Tools"/> <KeyWord name="Wait-Task "/> </AutoComplete> </NotepadPlus>



