Latest imported feed items on VMware Blogs https://blogs.vmware.com <![CDATA[Part 3: Create shorter Microsoft Powershell WPF automated clean script]]> http://vcloud-lab.com/entries/powershell/part-3-create-shorter-microsoft-powershell-wpf-automated-clean-script http://vcloud-lab.com/entries/powershell/part-3-create-shorter-microsoft-powershell-wpf-automated-clean-script Sun, 22 Apr 2018 18:12:00 +0000 Currently I am working on rewriting all my VBscript and Powershell GUI script using WPF (Windows presentation platform). When building a graphical xaml forms on Visual studio as shown earlier on Part 1: Create WPF XAML powershell GUI form with Visual studio, I had to remove many elements manually by finding them, and every time it is not productive at all, if I missed removing any unwanted element, it was causing errors. To illustrate it, earlier I was removing lots of stuff from XAML form, But in this demo I will remove only 2 Lines 'x:Class="WPFapplication2.MainWindow"' and 'mc:Ignorable="d"'. This is one time process.

Microsoft windows Powershell presentation frameworks, wpf visual studio XAML xml code, script for cleaner

Line 24 and 25 are same earlier shown article Part 2: Powershell and WPF: Build GUI applications tutorial, Next line 28 is important one. Once XAML form is parsed by finding nodes and shows the list of allcontrols. Using Foreach-Object I can create a variable for each control so it can be used to perform actions. I don't have to worry about adding new FindName method everytime, it is automated now.

$xaml.SelectNodes("//*[@*[contains(translate(name(.),'n','N'),'Name')]]").Name

Powershell wpf gui tutorial Microsoft Powershell  system.xml.xmlnodereader xaml, windows.markup.xamlreader load file selectnodes from xml new variable name.png

Below is the gif animation of the script, it is working perfectly and my code is very much shorter now, and if I add new control in the XAML 

Microsoft Powershell GUI, graphical user interface windows powershell wpf tutorial, xaml, windows presentation frameworks, logical partitions disk list

Download script here, this is also available on GitHub.com.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
#Load required libraries
Add-Type -AssemblyName PresentationFramework, PresentationCore, WindowsBase, System.Windows.Forms, System.Drawing 

[xml]$xaml = @"

        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:WpfApplication2"

        Title="MainWindow" Height="300" Width="364">
    
        
        
        

Userful Articles
Part 1: Create WPF XAML powershell GUI form with Visual studio
Part 2: Powershell and WPF: Build GUI applications tutorial
COOL POWERSHELL FREE ONLINE GUI GENERATOR TOOL, POSHGUI
Generate random password GUI using powershell

]]>
Currently I am working on rewriting all my VBscript and Powershell GUI script using WPF (Windows presentation platform). When building a graphical xaml forms on Visual studio as shown earlier on Part 1: Create WPF XAML powershell GUI form with Visual studio, I had to remove many elements manually by finding them, and every time it is not productive at all, if I missed removing any unwanted element, it was causing errors. To illustrate it, earlier I was removing lots of stuff from XAML form, But in this demo I will remove only 2 Lines 'x:Class="WPFapplication2.MainWindow"' and 'mc:Ignorable="d"'. This is one time process.

Microsoft windows Powershell presentation frameworks, wpf visual studio XAML xml code, script for cleaner

Line 24 and 25 are same earlier shown article Part 2: Powershell and WPF: Build GUI applications tutorial, Next line 28 is important one. Once XAML form is parsed by finding nodes and shows the list of allcontrols. Using Foreach-Object I can create a variable for each control so it can be used to perform actions. I don't have to worry about adding new FindName method everytime, it is automated now.

$xaml.SelectNodes("//*[@*[contains(translate(name(.),'n','N'),'Name')]]").Name

Powershell wpf gui tutorial Microsoft Powershell  system.xml.xmlnodereader xaml, windows.markup.xamlreader load file selectnodes from xml new variable name.png

Below is the gif animation of the script, it is working perfectly and my code is very much shorter now, and if I add new control in the XAML 

Microsoft Powershell GUI, graphical user interface windows powershell wpf tutorial, xaml, windows presentation frameworks, logical partitions disk list

Download script here, this is also available on GitHub.com.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
#Load required libraries
Add-Type -AssemblyName PresentationFramework, PresentationCore, WindowsBase, System.Windows.Forms, System.Drawing 

[xml]$xaml = @"

        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:WpfApplication2"

        Title="MainWindow" Height="300" Width="364">
    
        
        
        

Userful Articles
Part 1: Create WPF XAML powershell GUI form with Visual studio
Part 2: Powershell and WPF: Build GUI applications tutorial
COOL POWERSHELL FREE ONLINE GUI GENERATOR TOOL, POSHGUI
Generate random password GUI using powershell

]]>
Virtual Geek
<![CDATA[VMware Product Interoperability Matrices for VMware vSphere Hypervisor (ESXi)]]> https://tinkertry.com/articles/vsphere-upgrade-matrix https://tinkertry.com/articles/vsphere-upgrade-matrix Sun, 22 Apr 2018 17:08:00 +0000

I haven't spotted this table out there recently, with all the vSphere 6.7 discussion these past few days since launch on Tue Apr 17 2018. So I figured I'd give it some visibility, since you may not have read these three documents carefully enough:

  1. Important information before upgrading to vSphere 6.7 (53704)

    Purpose
    This article provides important documentation and upgrade information that must be reviewed before upgrading to vSphere 6.7.
    ...

  2. Update sequence for vSphere 6.7 and its compatible VMware products (53710)
    kb.vmware.com/s/article/53710

    Product                   |  Starting Version  |  Recommended Action for Upgrade
    vCenter Server Appliance  |  6.5 Update 1b     |  Upgrade to 6.7
    vSphere ESXi              |  6.5 Update 1b     |  Upgrade to 6.7
    VMware vSAN               |  6.6.1             |  Upgrade to 6.7

    Hmm, what is vSphere ESXi 6.5 Update 1b? Is that a typo? Does that include last month's version of ESXi such as 6.5U1 Build 7967591 (for Spectre mitigation)? I'll revisit that question below, as we inspect a table of releases.

  3. vSphere 6.7 Release Notes

    ...
    ESXi and vCenter Server Version Compatibility
    The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server.
    ...

but you may have forgotten to actually click on that highlighted link above.

VMware Product Interoperability Matrices

Visit this direct link to view, for a visual of valid ESXi 6.7 upgrade paths:

VMware-Product-Interoperability-Matrices-table-for-ESXi-screenshot-on-2018-04-22--TinkerTry
Here's how the the ESXi upgrade matrix looks on Apr 22 2018.

From the main page, I already clicked on Upgrade Path, then selected VMware vSphere Hypervisor (ESXi) from the drop-down menu for you, then shared the above direct URL to the results. Note that you can hover your mouse over the grey i badges to get more details.

What's missing

What I notied is that you won't find in the table below is the aforementioned ESXi 6.5 Update 1b:

  • Build numbers and versions of VMware ESXi/ESX (2143832)
    kb.vmware.com/s/article/2143832

    Version                    | Release Date | Build Number | Install Build Number
    ESXi 6.7 GA                  2018-04-17     8169922        N/A
    ESXi 6.5 U1g                 2018-03-20     7967591        N/A
    ESXi 6.5 Patch 02            2017-12-19     7388607        N/A
    ESXi 6.5 U1 Express Patch 4  2017-10-05     6765664        N/A
    ESXi 6.5 U1                  2017-07-27     5969303        N/A
    ESXi 6.5.0d                  2017-04-18     5310538        N/A
    ESXi 6.5. Express Patch 1a   2017-03-28     5224529        N/A
    ESXi 6.5. Patch 01           2017-03-09     5146846        5146843
    ESXi 6.5.0 a                 2017-02-02     4887370        N/A
    ESXi 6.5 GA                  2016-11-15     4564106        N/A

I have reached out to try to get to the bottom of being absolutely sure about whether it is supported to upgrade directly from any 6.5x version to 6.7, whether or not vSAN is in use, since I'm seeing some differing opinions on the valid upgrade paths, see examples in the See Also below. I also heard a brief mention on the recent vForum Online Spring 2018 as well, I'll be circling back and looking into that. I hope to post updates below this article, once I know more.

Whether or not the various upgrade methods allow you to proceed, even if it unsupported to do so, is really a different matter. Some methods do no validation checking, such as the ESXCLI method popular with folks kicking the tires with the free hypervisor.

Disclaimer/Disclosure - I cannot feasibly provide support for your upgrade, especially given the variety of unsupported hardware out there, see full disclaimer at below-left. This article is focused mostly on small home labs, was voluntarily authored, and not associated with my employment at VMware. It is not official documentation. I work in the storage division, separate from the group developing and supporting the hypervisor.


See also at TinkerTry

All vSphere 6.7 articles.


See also

important-information-to-know-before-upgrading-to-vsphere-6-7

vmware-vsphere-esxi-6-7-new-features-installing-and-upgrading
]]>

I haven't spotted this table out there recently, with all the vSphere 6.7 discussion these past few days since launch on Tue Apr 17 2018. So I figured I'd give it some visibility, since you may not have read these three documents carefully enough:

  1. Important information before upgrading to vSphere 6.7 (53704)

    Purpose
    This article provides important documentation and upgrade information that must be reviewed before upgrading to vSphere 6.7.
    ...

  2. Update sequence for vSphere 6.7 and its compatible VMware products (53710)
    kb.vmware.com/s/article/53710

    Product                   |  Starting Version  |  Recommended Action for Upgrade
    vCenter Server Appliance  |  6.5 Update 1b     |  Upgrade to 6.7
    vSphere ESXi              |  6.5 Update 1b     |  Upgrade to 6.7
    VMware vSAN               |  6.6.1             |  Upgrade to 6.7

    Hmm, what is vSphere ESXi 6.5 Update 1b? Is that a typo? Does that include last month's version of ESXi such as 6.5U1 Build 7967591 (for Spectre mitigation)? I'll revisit that question below, as we inspect a table of releases.

  3. vSphere 6.7 Release Notes

    ...
    ESXi and vCenter Server Version Compatibility
    The VMware Product Interoperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, including ESXi, VMware vCenter Server, and optional VMware products. Check the VMware Product Interoperability Matrix also for information about supported management and backup agents before you install ESXi or vCenter Server.
    ...

but you may have forgotten to actually click on that highlighted link above.

VMware Product Interoperability Matrices

Visit this direct link to view, for a visual of valid ESXi 6.7 upgrade paths:

VMware-Product-Interoperability-Matrices-table-for-ESXi-screenshot-on-2018-04-22--TinkerTry
Here's how the the ESXi upgrade matrix looks on Apr 22 2018.

From the main page, I already clicked on Upgrade Path, then selected VMware vSphere Hypervisor (ESXi) from the drop-down menu for you, then shared the above direct URL to the results. Note that you can hover your mouse over the grey i badges to get more details.

What's missing

What I notied is that you won't find in the table below is the aforementioned ESXi 6.5 Update 1b:

  • Build numbers and versions of VMware ESXi/ESX (2143832)
    kb.vmware.com/s/article/2143832

    Version                    | Release Date | Build Number | Install Build Number
    ESXi 6.7 GA                  2018-04-17     8169922        N/A
    ESXi 6.5 U1g                 2018-03-20     7967591        N/A
    ESXi 6.5 Patch 02            2017-12-19     7388607        N/A
    ESXi 6.5 U1 Express Patch 4  2017-10-05     6765664        N/A
    ESXi 6.5 U1                  2017-07-27     5969303        N/A
    ESXi 6.5.0d                  2017-04-18     5310538        N/A
    ESXi 6.5. Express Patch 1a   2017-03-28     5224529        N/A
    ESXi 6.5. Patch 01           2017-03-09     5146846        5146843
    ESXi 6.5.0 a                 2017-02-02     4887370        N/A
    ESXi 6.5 GA                  2016-11-15     4564106        N/A

I have reached out to try to get to the bottom of being absolutely sure about whether it is supported to upgrade directly from any 6.5x version to 6.7, whether or not vSAN is in use, since I'm seeing some differing opinions on the valid upgrade paths, see examples in the See Also below. I also heard a brief mention on the recent vForum Online Spring 2018 as well, I'll be circling back and looking into that. I hope to post updates below this article, once I know more.

Whether or not the various upgrade methods allow you to proceed, even if it unsupported to do so, is really a different matter. Some methods do no validation checking, such as the ESXCLI method popular with folks kicking the tires with the free hypervisor.

Disclaimer/Disclosure - I cannot feasibly provide support for your upgrade, especially given the variety of unsupported hardware out there, see full disclaimer at below-left. This article is focused mostly on small home labs, was voluntarily authored, and not associated with my employment at VMware. It is not official documentation. I work in the storage division, separate from the group developing and supporting the hypervisor.


See also at TinkerTry

All vSphere 6.7 articles.


See also

important-information-to-know-before-upgrading-to-vsphere-6-7

vmware-vsphere-esxi-6-7-new-features-installing-and-upgrading
]]>
TinkerTry IT @ home | Author: Paul Braren
<![CDATA[vSphere 6.7 Announced: What’s New]]> https://www.myvirtualjourney.com/vsphere-6-7-announced-whats-new/ https://www.myvirtualjourney.com/vsphere-6-7-announced-whats-new/ Sun, 22 Apr 2018 10:47:25 +0000 Read more]]> Read more]]> My Virtual Journey <![CDATA[VMware vSphere 6.7 scalability]]> https://vinfrastructure.it/2018/04/vmware-vsphere-6-7-scalability/ https://vinfrastructure.it/2018/04/vmware-vsphere-6-7-scalability/ Sun, 22 Apr 2018 05:34:04 +0000 The new VMware vSphere 6.7, recently available in GA, increase all configuration maximums to new limits (compared to the v6.5 and previous versions). Maybe we can say with no limit, or at least, to be serious, with really huge numbers compared to the actual needs and the existing compunting power. Those new limits are both for scalability aspect, but also to fit with possible performance requirements, considering that a bigger number of business critical applications are going in the virtual environment. For more information see the new official site: VMware Configuration Maximum. Host ESXi 6.7 Limits remains quite […]

The post VMware vSphere 6.7 scalability appeared first on vInfrastructure Blog.

]]>
The new VMware vSphere 6.7, recently available in GA, increase all configuration maximums to new limits (compared to the v6.5 and previous versions). Maybe we can say with no limit, or at least, to be serious, with really huge numbers compared to the actual needs and the existing compunting power. Those new limits are both for scalability aspect, but also to fit with possible performance requirements, considering that a bigger number of business critical applications are going in the virtual environment. For more information see the new official site: VMware Configuration Maximum. Host ESXi 6.7 Limits remains quite […]

The post VMware vSphere 6.7 scalability appeared first on vInfrastructure Blog.

]]>
vInfrastructure Blog
<![CDATA[PowerCLI から Nested ESXi の esxcli を実行してみる。(GuestProcessManager)]]> https://communities.vmware.com/people/gowatana/blog/2018/04/21/powercli-nested-esxcli https://communities.vmware.com/people/gowatana/blog/2018/04/21/powercli-nested-esxcli Sun, 22 Apr 2018 03:29:27 +0000

ESXi 上の VM に ESXi をインストールする「Nested ESXi」と呼ばれる使用方法があり、

検証環境や、vSAN Witness Appliance などで利用されています。

Running Nested VMs

 

Nested ESXi は物理マシンへのインストールと同様に DCUI からの設定作業ができるため

通常は、VM コンソールから設定をすることになります。

nested-esxi-vm.png

 

しかし VM であり、しかも最近の ESXi 6.x ではデフォルトで VMware Tools がインストールされます。

そのため Nested ESXi では、ネットワーク設定前であっても

vSphere のレイヤから直接での設定投入ができます。

 

通常、PowerCLI からゲスト OS の設定を変更する場合は Invoke-VMScript を使用しますが、

ScriptType で指定できるインタープリタは PowerShell、Bat、Bash だけなので

ESXi ではスクリプト(コマンド)が実行できません。

 

Invoke-VMScript

https://code.vmware.com/doc/preview?id=6330#/doc/Invoke-VMScript.html

 

そこで、ためしに vSphere Web Services API の GuestOperationsManager にある

GuestProcessManager を利用して esxcli コマンドを実行してみました。

 

GuestProcessManager

https://code.vmware.com/apis/358/vsphere?h=GuestOperationsManager#/doc/vim.vm.guest.ProcessManager.html

 

今回は、下記のようなサンプル スクリプトを作成してみました。

エラー制御などは、あえて一切いれていないので、

実行してみる場合はお好みで改造していただければと・・・

invoke_nested-esxcli.ps1 · GitHub

 

スクリプトの内容は下記のようになっています。

param($ESXiVM, $ESXiUser, $ESXiPass)

 

# 最初に変数設定。

$vm_name = $ESXiVM

$esxi_user = $ESXiUser

$esxi_pass = $ESXiPass

$esxcli_args = $args

 

$vm = Get-VM $vm_name | select -First 1

$vm_id = $vm.Id

$vc_name = $vm.Uid  -replace "^.*@|:.*$",""

$vc = $global:DefaultVIServers | where {$_.Name -eq $vc_name}

 

"ESXi VM Name:" + $vm.Name

"esxcli args: " + $esxcli_args

 

# ESXi の認証情報をセット。

$cred = New-Object VMware.Vim.NamePasswordAuthentication

$cred.Username = $esxi_user

$cred.Password = $esxi_pass

 

# esxcli コマンドをフルパスで指定。

$gps = New-Object VMware.Vim.GuestProgramSpec

$gps.WorkingDirectory = "/tmp"

$gps.ProgramPath = "/bin/esxcli"

$gps.Arguments = $esxcli_args

 

# ここでコマンド実行。

$gom = Get-View $vc.ExtensionData.Content.GuestOperationsManager

$pm = Get-View $gom.ProcessManager

$gos_pid = $pm.StartProgramInGuest($vm_Id, $cred, $gps)

$pm.ListProcessesInGuest($vm_Id, $cred, $gos_pid)

 

実行するときには、まず Nested VM を管理している vCenter に接続しておきます。

PowerCLI> Connect-VIServer

 

このスクリプトでは、esxcli のオプションを通常どおり指定しやすいように工夫しています。

実行方法は、下記のような感じです。

PowerCLI> .invoke_nested-esxcli.ps1 -ESXiVM: -ESXiUser: -ESXiPass:

 

もしくは・・・

PowerCLI> .invoke_nested-esxcli.ps1 -ESXiVM: -ESXiUser: -ESXiPass:

 

たとえば「esxcli system hostname set --host ~ --domain ~」の実行は

下記のようになります。

PowerCLI> .invoke_nested-esxcli.ps1 system hostname set --host hv-n23w --domain go-lab.jp -ESXiVM:hv-n23w -ESXiUser:root -ESXiPass:VMware1!

ESXi VM Name:hv-n23w

esxcli args: system hostname set --host hv-n23w --domain go-lab.jp

 

Name      : esxcli

Pid       : 2278253

Owner     : root

CmdLine   : "/bin/esxcli" system hostname set --host hv-n23w --domain go-lab.jp

StartTime : 2018/04/22 2:52:18

EndTime   :

ExitCode  :

 

 

これだとコマンドの出力結果は取得できないのですが、

Nested ESXi をネットワーク設定して vCenter に登録してしまえば

vCenter 経由で ESXi の設定確認ができるので、うちでは設定投入するだけの利用をしています。

 

ちなみに、今回の環境では下記でした。

  • 物理環境: vCenter 6.5 U1 / ESXi 6.5 U1
  • Nested ESXi: ESXi 6.7
  • PowerCLI 10.0.0 / PowerShell 5.1 / Windows 10

 

以上、PowerCLI から Nested ESXi の esxcli を実行してみる話でした。

]]>

ESXi 上の VM に ESXi をインストールする「Nested ESXi」と呼ばれる使用方法があり、

検証環境や、vSAN Witness Appliance などで利用されています。

Running Nested VMs

 

Nested ESXi は物理マシンへのインストールと同様に DCUI からの設定作業ができるため

通常は、VM コンソールから設定をすることになります。

nested-esxi-vm.png

 

しかし VM であり、しかも最近の ESXi 6.x ではデフォルトで VMware Tools がインストールされます。

そのため Nested ESXi では、ネットワーク設定前であっても

vSphere のレイヤから直接での設定投入ができます。

 

通常、PowerCLI からゲスト OS の設定を変更する場合は Invoke-VMScript を使用しますが、

ScriptType で指定できるインタープリタは PowerShell、Bat、Bash だけなので

ESXi ではスクリプト(コマンド)が実行できません。

 

Invoke-VMScript

https://code.vmware.com/doc/preview?id=6330#/doc/Invoke-VMScript.html

 

そこで、ためしに vSphere Web Services API の GuestOperationsManager にある

GuestProcessManager を利用して esxcli コマンドを実行してみました。

 

GuestProcessManager

https://code.vmware.com/apis/358/vsphere?h=GuestOperationsManager#/doc/vim.vm.guest.ProcessManager.html

 

今回は、下記のようなサンプル スクリプトを作成してみました。

エラー制御などは、あえて一切いれていないので、

実行してみる場合はお好みで改造していただければと・・・

invoke_nested-esxcli.ps1 · GitHub

 

スクリプトの内容は下記のようになっています。

param($ESXiVM, $ESXiUser, $ESXiPass)

 

# 最初に変数設定。

$vm_name = $ESXiVM

$esxi_user = $ESXiUser

$esxi_pass = $ESXiPass

$esxcli_args = $args

 

$vm = Get-VM $vm_name | select -First 1

$vm_id = $vm.Id

$vc_name = $vm.Uid  -replace "^.*@|:.*$",""

$vc = $global:DefaultVIServers | where {$_.Name -eq $vc_name}

 

"ESXi VM Name:" + $vm.Name

"esxcli args: " + $esxcli_args

 

# ESXi の認証情報をセット。

$cred = New-Object VMware.Vim.NamePasswordAuthentication

$cred.Username = $esxi_user

$cred.Password = $esxi_pass

 

# esxcli コマンドをフルパスで指定。

$gps = New-Object VMware.Vim.GuestProgramSpec

$gps.WorkingDirectory = "/tmp"

$gps.ProgramPath = "/bin/esxcli"

$gps.Arguments = $esxcli_args

 

# ここでコマンド実行。

$gom = Get-View $vc.ExtensionData.Content.GuestOperationsManager

$pm = Get-View $gom.ProcessManager

$gos_pid = $pm.StartProgramInGuest($vm_Id, $cred, $gps)

$pm.ListProcessesInGuest($vm_Id, $cred, $gos_pid)

 

実行するときには、まず Nested VM を管理している vCenter に接続しておきます。

PowerCLI> Connect-VIServer

 

このスクリプトでは、esxcli のオプションを通常どおり指定しやすいように工夫しています。

実行方法は、下記のような感じです。

PowerCLI> .invoke_nested-esxcli.ps1 -ESXiVM: -ESXiUser: -ESXiPass:

 

もしくは・・・

PowerCLI> .invoke_nested-esxcli.ps1 -ESXiVM: -ESXiUser: -ESXiPass:

 

たとえば「esxcli system hostname set --host ~ --domain ~」の実行は

下記のようになります。

PowerCLI> .invoke_nested-esxcli.ps1 system hostname set --host hv-n23w --domain go-lab.jp -ESXiVM:hv-n23w -ESXiUser:root -ESXiPass:VMware1!

ESXi VM Name:hv-n23w

esxcli args: system hostname set --host hv-n23w --domain go-lab.jp

 

Name      : esxcli

Pid       : 2278253

Owner     : root

CmdLine   : "/bin/esxcli" system hostname set --host hv-n23w --domain go-lab.jp

StartTime : 2018/04/22 2:52:18

EndTime   :

ExitCode  :

 

 

これだとコマンドの出力結果は取得できないのですが、

Nested ESXi をネットワーク設定して vCenter に登録してしまえば

vCenter 経由で ESXi の設定確認ができるので、うちでは設定投入するだけの利用をしています。

 

ちなみに、今回の環境では下記でした。

  • 物理環境: vCenter 6.5 U1 / ESXi 6.5 U1
  • Nested ESXi: ESXi 6.7
  • PowerCLI 10.0.0 / PowerShell 5.1 / Windows 10

 

以上、PowerCLI から Nested ESXi の esxcli を実行してみる話でした。

]]>
Gowatana Blog
<![CDATA[VMware vSphere 6.5 Upgrade – Path Finder]]> https://www.unixarena.com/2018/04/vmware-vsphere-6-5-upgrade-path-finder.html https://www.unixarena.com/2018/04/vmware-vsphere-6-5-upgrade-path-finder.html Sat, 21 Apr 2018 08:02:52 +0000 VMware vSphere 6.5 has released last year but still many of the environments are running with vSphere 5.5 or vSphere 6.0. This article will try to provide more information about VMware vSphere 6.5 upgrade resources and other available utilities in the market to simplify the upgrade work plan and execution. This article also covers the …

The post VMware vSphere 6.5 Upgrade – Path Finder appeared first on UnixArena.

]]>
VMware vSphere 6.5 has released last year but still many of the environments are running with vSphere 5.5 or vSphere 6.0. This article will try to provide more information about VMware vSphere 6.5 upgrade resources and other available utilities in the market to simplify the upgrade work plan and execution. This article also covers the …

The post VMware vSphere 6.5 Upgrade – Path Finder appeared first on UnixArena.

]]>
UnixArena
<![CDATA[Microsoft Powershell GUI: Change Internet Options connections Lan settings proxy server grayed out]]> http://vcloud-lab.com/entries/powershell/microsoft-powershell-gui-change-internet-options-connections-lan-settings-proxy-server-grayed-out http://vcloud-lab.com/entries/powershell/microsoft-powershell-gui-change-internet-options-connections-lan-settings-proxy-server-grayed-out Sat, 21 Apr 2018 07:46:00 +0000 Powershell winform wpf mix gui, graphical interface, change registry proxy settings hack internet option connections tab enable proxy

One of my friend wanted a small proxy settings hack tool which I created using Powershell script, it is very small tool and helps to change proxy server settings, It can changed when Internet Options >> Connections tab is either missing or Lan settings button is disabled, and you still want to change proxy settings. Basically this graphical powershell script make changes in the Registry. So registry modification must be enabled for this.

microsoft windows Powershell Internet Options Connections tab, Lab Settings, Proxy Server, VPN connection, lan proxy address.png

After launching script looks like below. It shows the current proxy configuration, Settings can be changed via typing new proxy server and proxy port and pressing Change Proxy button. Once Setting is refreshed, you can see the results. To build this GUI, I have used Powershell Studio.

microsoft powershell wpf forms change internet proxy settings, connection tab enable hack, powershell hack, registry

Basically this script Enable or Disable and changes proxy server dword values under registry path  HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings. Below dword values need to change the behavior of Lan settings >> proxy.

ProxyEnable = 1  #1 = enabled & 0 = Disabled
ProxyServer = 'OldProxyServer:808'

This script can be downloaded from here, It is also available on github.com.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
<#
    .NOTES
    --------------------------------------------------------------------------------
     Code generated by:  Visual Studio 2015
     Created on:         4/19/2018 4:57 AM
     Generated by:       http://vcloud-lab.com
     Written by:         Kunal Udapi
     Tested on:          Windows 10
                         Windows 2016 Server
    --------------------------------------------------------------------------------
    .DESCRIPTION
        GUI script generated using Visual Studio 2015
#>

Add-Type -AssemblyName PresentationFramework

$RawXamlForm = @"

        Title="Configure Proxy Server" Height="201" Width="525" ResizeMode="NoResize" Topmost="True" WindowStyle="none">
    
        
            
            
        
    
    
        
        
        
        
        
        

Useful Tools
COOL POWERSHELL FREE ONLINE GUI GENERATOR TOOL, POSHGUI
Generate random password GUI using powershell
Part 1: Create WPF XAML powershell GUI form with Visual studio
Powershell PoshGUI: Convert user to SID and vice versa using

]]>
Powershell winform wpf mix gui, graphical interface, change registry proxy settings hack internet option connections tab enable proxy

One of my friend wanted a small proxy settings hack tool which I created using Powershell script, it is very small tool and helps to change proxy server settings, It can changed when Internet Options >> Connections tab is either missing or Lan settings button is disabled, and you still want to change proxy settings. Basically this graphical powershell script make changes in the Registry. So registry modification must be enabled for this.

microsoft windows Powershell Internet Options Connections tab, Lab Settings, Proxy Server, VPN connection, lan proxy address.png

After launching script looks like below. It shows the current proxy configuration, Settings can be changed via typing new proxy server and proxy port and pressing Change Proxy button. Once Setting is refreshed, you can see the results. To build this GUI, I have used Powershell Studio.

microsoft powershell wpf forms change internet proxy settings, connection tab enable hack, powershell hack, registry

Basically this script Enable or Disable and changes proxy server dword values under registry path  HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionInternet Settings. Below dword values need to change the behavior of Lan settings >> proxy.

ProxyEnable = 1  #1 = enabled & 0 = Disabled
ProxyServer = 'OldProxyServer:808'

This script can be downloaded from here, It is also available on github.com.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
<#
    .NOTES
    --------------------------------------------------------------------------------
     Code generated by:  Visual Studio 2015
     Created on:         4/19/2018 4:57 AM
     Generated by:       http://vcloud-lab.com
     Written by:         Kunal Udapi
     Tested on:          Windows 10
                         Windows 2016 Server
    --------------------------------------------------------------------------------
    .DESCRIPTION
        GUI script generated using Visual Studio 2015
#>

Add-Type -AssemblyName PresentationFramework

$RawXamlForm = @"

        Title="Configure Proxy Server" Height="201" Width="525" ResizeMode="NoResize" Topmost="True" WindowStyle="none">
    
        
            
            
        
    
    
        
        
        
        
        
        

Useful Tools
COOL POWERSHELL FREE ONLINE GUI GENERATOR TOOL, POSHGUI
Generate random password GUI using powershell
Part 1: Create WPF XAML powershell GUI form with Visual studio
Powershell PoshGUI: Convert user to SID and vice versa using

]]>
Virtual Geek
<![CDATA[FlashArray vSphere Web Client now supports vSphere 6.7]]> https://www.codyhosterman.com/2018/04/flasharray-vsphere-web-client-now-supports-vsphere-6-7/ https://www.codyhosterman.com/2018/04/flasharray-vsphere-web-client-now-supports-vsphere-6-7/ Fri, 20 Apr 2018 23:00:56 +0000 Continue reading FlashArray vSphere Web Client now supports vSphere 6.7 ]]> Continue reading FlashArray vSphere Web Client now supports vSphere 6.7 ]]> Cody Hosterman <![CDATA[vCenter 6.7 upgrade walkthrough]]> https://vwannabe.com/2018/04/20/vcenter-6-7-upgrade-walkthrough/ https://vwannabe.com/2018/04/20/vcenter-6-7-upgrade-walkthrough/ Fri, 20 Apr 2018 19:26:54 +0000 Continue reading vCenter 6.7 upgrade walkthrough]]> Continue reading vCenter 6.7 upgrade walkthrough]]> vWannabe <![CDATA[What’s New in Core Storage in vSphere 6.7 Part IV: NVMe Controller In-Guest UNMAP Support]]> https://www.codyhosterman.com/2018/04/whats-new-in-core-storage-in-vsphere-6-7-part-iv-nvme-controller-in-guest-unmap-support/ https://www.codyhosterman.com/2018/04/whats-new-in-core-storage-in-vsphere-6-7-part-iv-nvme-controller-in-guest-unmap-support/ Fri, 20 Apr 2018 18:42:42 +0000 Continue reading What’s New in Core Storage in vSphere 6.7 Part IV: NVMe Controller In-Guest UNMAP Support ]]> Continue reading What’s New in Core Storage in vSphere 6.7 Part IV: NVMe Controller In-Guest UNMAP Support ]]> Cody Hosterman