Exporting/Importing Time Zone settings using VMware UEM – IVANDEMES

My Top 3 Favorite/Informative UEM Community Forum Discussions – June 2017 – IVANDEMES

My Top 3 Favorite/Informative UEM Community Forum Discussions – July 2017 – IVANDEMES

There are some situations in which you need to trace an issue, resolve a conflict, deploy in a predictable manner, or you have to respond quickly to changes in customer requirements and technology. These situations are often unpredictable and stressful. You may suddenly find yourself fixing the same issues again and again. In a blog post series we will try to identify what struggles you may face while working with vRO and how to address them with less effort and for less time.

Struggle 1: You think you have fixed an issue and it suddenly shows up again. Later, it turns out that someone else, in a good will, has changed the same workflow fixing another issue but overriding your changes.

Struggle 2: A colleague leaves the company and now you have to support his workflow. You have no idea what this workflow is about and how it works. You spend a lot of time trying to understand it and still have some troubles with it. And on top of that, you receive a request from the customer to add a new feature or a bug fix to it.

Struggle 3: You wrote a workflow 2 years ago and now you want to extend its functionality while keeping the old features working. You do the change and send it for testing, everything is fine. A week later, the QA comes with a report and tells you about a use case scenario that does not work any more.

Struggle 4: A solution works flawlessly in your development vRO environment but it does not work in staging. So, you go through each workflow and try to find why. It is like Spot 10 Differences but instead of comparing two pictures you compare two environments, and it takes a lot of time.

Struggle 5: You have to prepare a release package, but every time you miss an action or a resource element and you try to deploy to the staging environment, the package does not work. Or you pull everything from one environment and move it to another, and you are ready 2 weeks before the release. But one feature is still not working as it turns out to be more complex than you originally thought.

If you have ever experienced any of the situations above, you will find this blog post series extremely useful. We will show you how to address these problems by using different techniques and tools. We will focus on the DevOps toolchain phases from Code to Continuous Delivery, we will not discuss how you plan what to do or how you operate the solution.

Once you set up and configure your development environment, it will be really easy to follow the development process, as most of its steps are actually automated. In most cases, you will only interact with your development environment and when ready, you will push the changes to a source code control system, get an approval, and the fix or feature will go to production with no human intervention.

Here are some of the topics we will cover in this blog post series:

1. Setting up Development environment and Source code control system
2. Setting up Continuous Integration and Dependency management
3. Setting up Continuous Delivery
4. What principles to follow in architecting your solution and how the tools will support you
5. Why you should write in Javascript and how to do it properly

Stay tuned!

Create a simple stateless desktop for testing using VMware Workstation – IVANDEMES

Live Search VMware UEM Community Templates – IVANDEMES

PowerCLI を楽しむべく、プロンプト文字列を工夫してみようと思います。

以前、下記のような投稿をしましたが・・・

PowerCLI のプロンプト文字列「PowerCLI>」について。

これを応用して、vCenter / ESXi への接続状態によって「PowerCLI」の色を変更してみます。

ということで、

まず下記のような PowerShell スクリプト「set_powercli_prompt.ps1」を

適当なフォルダ（「ドキュメント」配下など、今後も配置しておける場所）に作成しておきます。

ドット スペース「. 」からはじまる1 行目は、通常 PowerCLI が起動時に読み込むスクリプトを読み込んでいます。

そして、$global:DefaultVIServers 変数をもとに、接続している（IsConnected が Trueである）vCenter / ESXi が

1台でもあれば、プロンプトの文字列色を Green に、それ以外の場合は DarkCyan にします。

set_powercli_prompt.ps1

. "C:\Program Files (x86)\VMware\Infrastructure\PowerCLI\Scripts\Initialize-PowerCLIEnvironment.ps1"

Clear-Host

 

function prompt{

    $vc_all = $global:DefaultVIServers

    $vc_connected = $vc_all | where {$_.IsConnected -eq $True}

    if($vc_connected.Count -ge 1){

        $prompt_color = "Green"

    }else{

        $prompt_color = "DarkCyan"

    }

    Write-Host "PowerCLI" -NoNewLine -ForegroundColor $prompt_color

    Write-Host ">" -NoNewLine -ForegroundColor "Gray"

    return " "

}

そして、下記のスクリプトを読み込んで PowerShell を起動するショートカットを作成します。

今回は下記のスクリプトで、デスクトップに「PowerCLI」というショートカットを作成しました。

このスクリプトは上記のものと同じフォルダに配置して、実行します。

create_powercli_shortcut.ps1

$tool_name = "PowerCLI"

$profile_script_name = "set_powercli_prompt.ps1"

 

$shortcut_dir = Join-Path $HOME "Desktop"

$shortcut_path = Join-Path $shortcut_dir ($tool_name + ".lnk")

 

$tool_work_dir = (ls $PSCommandPath).DirectoryName

$profile_path = Join-Path $tool_work_dir $profile_script_name

 

$ps = "powershell"

$ps_argument = ("-NoExit", "-File",  $profile_path) -join " "

 

$wsh = New-Object -ComObject WScript.Shell

$shortcut = $wsh.CreateShortcut($shortcut_path)

$shortcut.TargetPath = $ps

$shortcut.Arguments = $ps_argument

$shortcut.WorkingDirectory = (ls $profile_path).DirectoryName

$shortcut.Save()

上記の「create_powercli_shortcut.ps1」スクリプトを実行すると、

デスクトップに PowerCLI ショートカットが作成されます。

このショートカットは、powershell.exe を下記2つのオプションで起動するだけのものです。

• -NoExit
• -File ～\set_powercli_prompt.ps1  ※プロンプトを変更するスクリプトを指定する。

このショートカットを起動すると、プロンプトが「PowerCLI>」となった PowerShell が起動されます。

そして、Connect-VIServer で vCenter / ESXi に接続すると、プロンプトの色が変わります。

今回の例だと、vCenter 接続中だけ「PowerCLI」が Green になっています。

さらに工夫すれば、接続先の vCenter / ESXi の情報をプロンプトに反映したりすることもできます。

（しかしその分レスポンスに影響するので、やりすぎ注意・・・）

なお今回は、Windows 10 + PowerCLI 6.5 R1 の環境でしか動作を試してません。

以上、PowerCLI のプロンプトを工夫してみる話でした。

PowerNSX を楽しむべく、NSX Manager と vCenter の接続状態をもとに

プロンプト文字列の色を変更してみようと思います。

PowerCLI + vCenter 接続のケースはこちらもどうぞ。

PowerCLI プロンプト文字列に vCenter への接続状態を反映してみる。

今回は、下記の前提です。

• PowerCLI はインストール済み。
• PowerNSX はインストール済み。
• Windows 10 環境で実行。

ということで、

まず下記のような PowerShell スクリプト「set_powernsx_prompt.ps1」を

適当なフォルダ（「ドキュメント」配下など、今後も配置しておける場所）に作成しておきます。

vCenter と NSX Manager の接続状態が自動格納される変数である

$global:DefaultVIServer と $DefaultNSXConnection をもとに、下記のようにプロンプトの色を変更します。

• NSX Manager と vCenter 両方に接続できていたら Cyan
• NSX Manager が連携している vCenter と、接続している vCenter が違ったら怪しいので Red
• NSX Manger だけに接続できていたら DarkCyan
• vCenter だけに接続できていたら Green
• 未接続は Gray

残念ながら、複数台の vCenter に同時接続するケースにはちゃんと対応してません。

set_powernsx_prompt.ps1

$module_list = @(

    "VMware.VimAutomation.Core",

    "VMware.VimAutomation.Vds",

    "PowerNSX"

)

Import-Module $module_list

 

$window_width  = 120

$window_height = 40

$window_buffer = 3000

 

$pshost = Get-Host

$pswindow = $pshost.ui.rawui

 

$pswindow.WindowTitle = "PowerNSX"

 

$newsize = $pswindow.buffersize 

$newsize.height = $window_buffer

$newsize.width = $window_width 

$pswindow.buffersize = $newsize 

 

$newsize = $pswindow.windowsize 

$newsize.height = $window_height 

$newsize.width = $window_width 

$pswindow.windowsize = $newsize

 

Clear-Host

$module = Get-Module -Name PowerNSX

 

Write-Host ""

Write-Host "Welcome to " -NoNewLine

Write-Host $module.Name -foregroundcolor Cyan

Write-Host $module.ProjectUri

Write-Host ""

Write-Host $module.Copyright

Write-Host ""

Write-Host $module.Description

Write-Host ""

(Get-Module $module_list | ft -AutoSize  Name,Version -HideTableHeaders | Out-String).trim()

Write-Host ""

Write-Host "Log in to a vCenter Server and NSX Mnager: "

Write-Host "  Connect-NsxServer -vCenterServer <vCenter Server>" -foregroundcolor yellow

Write-Host ""

 

function prompt{

    $vc = $global:DefaultVIServer

    $nsx = $DefaultNSXConnection

    if(($vc.IsConnected -eq $True) -and ($nsx.Server -ne $null)){

        $prompt_color = "Cyan"

        if($vc.Name -ne $nsx.VIConnection){

            $prompt_color = "Red"

        }

    }

    elseif(($vc.IsConnected -ne $True) -and ($nsx.Server -ne $null)){

        $prompt_color = "DarkCyan"

    }

    elseif(($vc.IsConnected -eq $True) -and ($nsx.Server -eq $null)){

        $prompt_color = "Green"

    }

    else{

        $prompt_color = "Gray"

    }   

    Write-Host "PowerNSX" -NoNewLine -ForegroundColor $prompt_color

    Write-Host ">" -NoNewline

    return " "

}

ついでに、set_powernsx_prompt.ps1 を読み込んで PowerShell を起動するショートカットを作成します。

今回は下記のスクリプトで、デスクトップに「PowerNSX」というショートカットを作成しました。

このスクリプトは上記のスクリプトと同じフォルダに配置して、実行します。

実行するとき、PowerShell の ExecutionPolicy は

スクリプト実行できる設定（RemoteSigned など）にしておきます。

# デスクトップに PowerNSX のショートカットを作成する。

 

$tool_name = "PowerNSX"

$profile_script_name = "set_powernsx_prompt.ps1"

 

$shortcut_dir = Join-Path $HOME "Desktop"

$shortcut_path = Join-Path $shortcut_dir ($tool_name + ".lnk")

 

$tool_work_dir = (ls $PSCommandPath).DirectoryName

$profile_path = Join-Path $tool_work_dir $profile_script_name

 

$ps = "powershell"

$ps_argument = ("-NoExit", "-File",  $profile_path) -join " "

 

$wsh = New-Object -ComObject WScript.Shell

$shortcut = $wsh.CreateShortcut($shortcut_path)

$shortcut.TargetPath = $ps

$shortcut.Arguments = $ps_argument

$shortcut.WorkingDirectory = (ls $profile_path).DirectoryName

$shortcut.Save()

作成した PowerNSX ショートカットをダブルクリックすると、下記のような感じになると思います。

ためしにインストールされた PowerNSX / PowerCLI についての情報も表示してみました。

これで、Connect-NsxServer で接続すると、冒頭のスクリーンショットのようにプロンプト色がかわります。

ラボ環境の NSX などでお楽しみいただければと思います・・・

以上、PowerNSX のプロンプトを工夫してみる話でした。

By design, vRealize Orchestrator (vRO) is an IT process automation tool that makes IT operations faster and less error-prone. However, to get the best out of vRO, you need to know how to overcome the most common challenges you may come across. In this blog, we will focus on how to properly set up your development environment and source code control system (SCCS) to gain full traceability of your development process and be able to resolve conflicts.

As with any type of software development, it all starts with an integrated development environment (IDE) and a SCCS. With vRO, the easiest way is not to change the vRO client with another IDE for developing workflows and actions, but just integrate a SCCS with it and define their interaction.

Depending on how much control you want to have over what you are doing, the interaction between the SCCS and vRO can be manual, semi-automated, and automated. The more manual the interaction is, the more control you will have; and you will be able to use all features of the SCCS. The more automated the interaction is, the more limited you will be on what you can do, especially if you use the fully automated one button approach.

In this post, we will focus on the manual, full-control approach, because if you are doing something serious, which as a reader of this blog I believe you do, the best is to have full control over your source code.

So, let's get started. You have to create a vRO package and put it under version control.

Initial project setup

Create an initial vRO package and store it on your file system

To create an initial vRO package, you need a vRO server and a vRO client.

1. In the Orchestrator client, create a package and add the initial content to the package. See Create a Package in the vRO official documentation.
   
2. Right-click the package and select Expand package to folder.
3. Choose a folder where you want to store your project files. It can be local or remote.
4. Uncheck Export version history.

Although this feature may sounds useful, the expanded package cannot be build with the version history. So, it will just add more unnecessary files.

   5.  Click Save.

        The vRO client generates a pom.xml file.

Now, you have to modify the generated pom.xml file to generate your package from the initial project files.

Modify the generated pom.xml file

1. Navigate to your project folder.
   The folder structure will look like this:
   
2. Open the generated pom.xml.

        The pom.xml will look like this:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">  <modelVersion>4.0.0</modelVersion>  <!--  Maybe you'd like to change this to point to your organization's groupId-->  <groupId>workflow-designer-exported</groupId>  <artifactId>com.vmware.pscoe.demo</artifactId>  <packaging>package</packaging>  <version>1.0.0-SNAPSHOT</version>  <properties>    <keystoreLocation>--Specify me--</keystoreLocation>    <keystorePassword>--Specify me--</keystorePassword>    <vco.version>7.3.0.5481809</vco.version>    <!-- change to vf for releases: it will lock the workflows -->    <allowedMask>vef</allowedMask>  </properties>  <repositories>    <repository>      <id>added-by-archetype</id>      <name>This repo was added by the 'Expand to file system'</name>      <url>https://172.16.202.131:8281/vco-repo</url>    </repository>  </repositories>  <pluginRepositories>    <pluginRepository>      <id>added-by-archetype</id>      <name>This repo was added by the 'Expand to file system'</name>      <url>https://172.16.202.131:8281/vco-repo</url>    </pluginRepository>  </pluginRepositories>  <build>    <plugins>      <plugin>        <groupId>com.vmware.o11n.mojo.pkg</groupId>        <artifactId>maven-o11n-package-plugin</artifactId>        <version>${vco.version}</version>        <extensions>true</extensions>        <configuration>          <packageName>com.vmware.pscoe.demo</packageName>          <!-- Set the local path to the *.vmokeystore file used to sign the content -->          <keystoreLocation>${keystoreLocation}</keystoreLocation>          <keystorePassword>${keystorePassword}</keystorePassword>          <includes>            <include>**/*.element_info.xml</include>          </includes>          <packageFileName>${project.artifactId}-${project.version}</packageFileName>          <allowedMask>${allowedMask}</allowedMask>          <exportVersionHistory>false</exportVersionHistory>        </configuration>      </plugin>    </plugins>  </build></project>

  3.   Modify the Keystore location and password.

        The keystone contains the certificate used to sign the package when creating it. In this case, generate an example self-signed certificate in a keystone following the procedure.

1. Generate the keystore.

   keytool -genkey -keyalg RSA -alias_DunesRSA_Alias_ -keystore example.keystore -storepass password123 -validity 3650 -keysize 2048

2. Answer the questions.
3. Modify the pom.xml

   <keystoreLocation>example.keystore</keystoreLocation> <keystorePassword>password123</keystorePassword>

For production usage, use real certificates.

  4.  Modify the vRO Version.

       The vRO version is used as a version of the vRO maven plug-in and it needs to correspond to the version of the artifact in the maven repository. In this case, we are using vRO as a maven repository.

1. Replace the IP address with the hostname/IP address of your server in the URL - https://172.16.202.131:8281/vco-repo/com/vmware/o11n/mojo/pkg/maven-o11n-package-plugin/.
2. Go to the URL and check the plug-in version. In this case, it shows 7.3.0:
   

          c.  Change the version in the pom.xml to 7.3.0.

Build the vRO package

Build the package from the project sources using mvn. Navigate to your project folder and run the command:

If you use vRO as a repository, you have to change the self-signed certificates on the vRO server. Otherwise, use the -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true parameters.

Verify the build

Verify that the command has produced a package in the target folder. 

Put the vRO content under source control

In theory, you can use any kind of SCCS, but here is used Github.

Create new repository

Push the changes

Now you are ready to push changes to your Github repository. This is just an example on how to do it:

Continuous Development

Once you have set up your project and added everything under source control, follow this procedure to do incremental changes to your project:

1. Create a branch in Git.
2. Checkout the branch using SourceTree or Git cli, or any other Git client.
3. Build the package and import it in vRO.
4. Fix an issue or implement a new feature.
5. "Expand" the package to your file system over the newly checkout branch.
6. Commit changes to your local branch. (Might do several commits, repeat the steps 5 and 6).
7. Push the branch to Git.
8. Create a Pull Request:
   1. Inspect the automatically generated diff;
   2. Add reviewers.
9. Reviewers inspect the diff and provide comments.
10. (Optional) Adopt the reviewers suggestions by making new commits with their changes.
11. Merge the Pull Request.
    
    

And there you have it!

Integrating your development environment and source code control system is the first step to proper software development in vRO. Adopting CI/CD will enable you to realize the full potential of agile development and delivery of use cases that fit better to the customers real needs. Following this series of blog posts will help you make it seamless and successful.

Stay tuned!

CloudCred VMworld Hands-On Labs Challenge

The time is drawing near!

Join the CloudCredibility.com team as we partner again with the experts in Hands-On Labs to bring you:

CloudCred VMworld Hands-On Labs Challenge

Beginning on *SUNDAY*, August 28, in the VMworld Hands-On Labs World at CloudCredibility.com, and in the Hands-On Labs Connect Area at VMworld Las Vegas, find:

Over 70 brand-new Self-Paced Hands-On Labs Tasks, including Challenge Labs

Expert-Led Workshops

Exciting Prizes!

~ The GREAT Echo Giveaway ~

Did you know that an Amazon Echo can control a VM?

At this year’s Hackathon, participants will learn how to configure an Echo Dot to do this very thing!

Whether or not you can attend the Hackathon, the source & instructions can be found at code.vmware.com  - {Code}  - the official VMware program for developers.

Or, learn how by completing tasks in the Hands-On Labs Dev-Ops badge at CloudCredibility.com – which will take you step-by-step through this cool process.

To make sure EVERYONE has a chance to take home an Amazon Echo Dot, we are giving away 75 Echo Dots in the Hands-On Labs Venue at EACH VMworld this year.

That’s seventy-five Amazon Echo Dots, or about 15 a day for 5 days!

Winners will be selected by Expert-Led Workshop proctors, and at-random in the Self-Paced Labs room each afternoon.

PLUS

Daily Points Raffle

Monday, Tuesday, Wednesday, Thursday

Players earning enough points to land in the Top 10 spots on the CloudCred, VMworld Hands-On Labs World Leaderboard will be entered into the Daily Points Raffle.

GoPro Hero 3 Cameras

1 Winner Daily

+++

Badge Completions – Grand Prizes

Drawings to take place Wednesday afternoon

Players earning any of the four Contest Badges will be entered into Wednesday’s Badge Raffles.

DevOps Badge

Roku 4K

+++

Experts Badge

Hands-On Labs Earbuds

+++

Solutions Badge

GoPro Hero 3 Camera

+++

Overall Badge

DJI Spark Drone

So make sure your schedule includes time in the Hands-On Labs –

and playing CloudCred.

You could take home any one of these great prizes, plus ...

Labs Tee-shirts for tweeting with #VMworldHOL

CloudCred Tee-shirts for new users

Hands-On Labs earbuds for the attendee who completes the 10,000^th lab taken

**Hands-On Labs will be OPEN on Sunday for early-attenders! Beat the crowds & visit on this first day.**

Players must complete Task 4601 & agree to contest terms & conditions.

Employees of VMware are not eligible for contest prizes. Players must be present to win. Players winning multiple prizes will be at the discretion of CloudCred staff.

今年も vExpert NSX 2017 Award を受賞できました！

vExpert NSX 2017 Award Announcement - VMTN Blog - VMware Blogs

ということで、記念に自宅 NSX を最新版 6.3.3 にアップデートしてみました。

そして PowerNSX でバージョン確認してみようと思います。

今回は権限の都合により、vCenter に接続したあと 2行目で NSX Manager に admin ユーザでログインしています。

PowerNSX> Connect-NsxServer -vCenterServer vc-sv02.go-lab.jp

PowerNSX> Connect-NsxServer -NsxServer nsxmgr01.go-lab.jp -DisableVIAutoConnect

まず NSX Manger です。

PowerNSX> Get-NsxManagerSystemSummary | select hostName,@{n="Version";E={$_.versionInfo | %{($_.majorVersion,$_.minorVersion,$_.patchVersion) -join "."}}},@{N="Build";E={$_.versionInfo.buildNumber}}

 

hostName Version Build

-------- ------- -----

nsxmgr01 6.3.3   6276725

 

NSX Controller です。

PowerNSX> Get-NsxController | select name,id,@{N="vmId";E={$_.virtualMachineInfo.objectId}},version,status,upgradeStatus | sort name | ft -AutoSize

 

name     id           vmId   version     status  upgradeStatus

----     --           ----   -------     ------  -------------

nsxctl01 controller-7 vm-483 6.3.6235594 RUNNING UPGRADED

nsxctl02 controller-6 vm-482 6.3.6235594 RUNNING UPGRADED

nsxctl03 controller-5 vm-481 6.3.6235594 RUNNING UPGRADED

 

NSX Edge （Edge Service Gateway）です。

小さい環境なので NSX Edge は ESG / DLR それぞれ 1台しかいません。

PowerNSX> Get-NsxEdge | select name,id,type,status,@{N="BuildInfo";E={$_.edgeSummary.appliancesSummary.vmBuildInfo}} | ft -AutoSize

 

name     id     type            status   BuildInfo

----     --     ----            ------   ---------

nsxesg01 edge-1 gatewayServices deployed 6.3.3-6144198

 

NSX Edge （DLR Control VM）です。

PowerNSX> Get-NsxLogicalRouter | select name,id,type,status,@{N="BuildInfo";E={$_.edgeSummary.appliancesSummary.vmBuildInfo}} | ft -AutoSize

 

name     id     type              status   BuildInfo

----     --     ----              ------   ---------

nsxdlr01 edge-5 distributedRouter deployed 6.3.3-6144198

 

NSX インストールずみクラスタの状態も見てみました。

PowerNSX> Get-NsxClusterStatus (Get-Cluster -Name nsx-cluster-01) | where {$_.installed -eq "true"} | select featureId,featureVersion,enabled,status,updateAvailable | ft -AutoSize

 

featureId                                featureVersion enabled status updateAvailable

---------                                -------------- ------- ------ ---------------

com.vmware.vshield.firewall              5.5            true    GREEN  false

com.vmware.vshield.vsm.messagingInfra                   true    GREEN  false

com.vmware.vshield.vsm.vxlan             5.5            true    GREEN  false

com.vmware.vshield.vsm.nwfabric.hostPrep 6.3.3.6276725  true    GREEN  false

 

ESXi の esx-nsxv VIB のバージョンです。

ちなみに 6.3.3 では ESXi ホストをメンテナンスモードにするだけで VIB のアップデートが完了します。

PowerNSX> Get-Cluster -Name nsx-cluster-01 | Get-VMHost | select Parent,Name,ConnectionState,@{N="esx-nsxv";E={($_|Get-EsxCli -V2).software.vib.get.Invoke(@{vibname="esx-nsxv"}).Version}},@{N="RebootRequired";E={$_.ExtensionData.Summary.RebootRequired}} | sort Parent,Name | ft -AutoSize

 

Parent         Name             ConnectionState esx-nsxv          RebootRequired

------         ----             --------------- --------          --------------

nsx-cluster-01 hv-n01.go-lab.jp       Connected 6.5.0-0.0.6244264          False

nsx-cluster-01 hv-n02.go-lab.jp       Connected 6.5.0-0.0.6244264          False

nsx-cluster-01 hv-n03.go-lab.jp       Connected 6.5.0-0.0.6244264          False

 

今年も趣味の NSX にとりくんでいきたいと思います。どこかでお役に立てればうれしいです。

以上、vExpert NSX 受賞記念の投稿でした。

Yes, hello, world. This will begin a series of blog posts for all to see and use.

Are you developing the next coolest vRA blueprint ever? Does it maybe involve NSX components? How about software blueprints? As with many efforts that don't quite succeed the first try, so to do issues occur within software during the development process. What happens in vRealize Automation when you try but fail? If you're reading this, you probably know:  it deletes the entire deployment. Not always helpful, especially when writing software components. Fortunately, there's an easy way to fix that. In your blueprint, add the custom property to your deployment called "_debug_deployment" and set the value to "true".

Now when you request that same item, instead of saying "Failed" and vRA blowing the whole thing up before you've had a chance to figure out what went wrong, the deployment will hang around out there. It'll say "Partially Successful" in your requests so you can distinguish between something that would have failed and when you finally see those successful ones.

Remove the property once you've got everything working properly. This will preserve some of your hair (if you still have any at all) and make the development process a little easier on you.

Power BI for Mobile is a touch-optimized Windows 8 app for a tablet. By using this app, you can view any workbook saved to Office 365.

Preparing a workbook for mobile viewing

Power BI for Mobile does not display a workbook in the same way that SharePoint Online does. Instead, it displays a workbook as a set of related pages with one item to a page. An item is a Power View report, a PivotTable, a chart, a PivotChart, or a table. A named range is also an item that is displayed on a separate page, except that other items appearing within the range appear on the same page. You determine which items are displayed online by opening the File tab in Excel, selecting Info, and then clicking Browser View Options. In the Browser View Options dialog box, you can select Sheets or Items in the drop-down list. If you choose Sheets, you can choose to display only Power View reports.

The only control you have over the sequencing of pages is to use a naming convention. Power BI for Mobile displays all items except Power View reports alphabetically by name. Then it displays the Power View reports in the order in which they appear in the workbook.

Important To be visible in the POWER BI for Mobile app, your workbook item or sheet must be based on the Excel Data Model in a workbook hosted in Office 365, a Windows Azure SQL Database, or an O Data feed. An item or sheet based on any other type of data source will be displayed as a blank page.

Using Power BI for Mobile

When you open the Power BI for Mobile app, swipe up to display the app bar, tap Browse, and then, on the Locations page, swipe up to show the app bar. In the box, type the URL for your SharePoint Online site, and then tap the Go arrow to the right of the URL. You must provide a user name and password to browse your workbooks. Navigate to Shared Documents, and then tap a report. Once a report is open, you can swipe up at any time to access the app bar, where you can tag a report as a favorite or use the Reset To Original button to restore the report to its original state and refresh the data. In addition, you can see thumbnail images of the report, as shown in Figure 5.8, so that you can easily jump to a different page.

FIGURE 5.8 : A Power View report and thumbnails of workbook pages in the Power BI for Mobile app.

The Power BI for Mobile app is designed for an interactive touch experience with the following features in mind for Power View:

Highlight In a Power View sheet, tap a chart element such as a bar, column, or legend item to bring the selected DATA into view. The other data is displayed with a more subdued hue to help you see the ratio between the two subsets of data. Clear the selection by tapping the chart background. You can select multiple items for highlighting by tapping the icon with three bars in the upper-right corner of the chart.

Filter For any item that has a filter defined, tap the filter icon in the upper-right corner to open the filter pane. You can change filter values and clear the filters, but you cannot add or delete a filter.

Zoom You can pinch and expand your fingers on the tablet’s surface to zoom out or in, respectively. However, this technique currently works only on Excel items and not on Power View sheets.

Sort a table column To sort, tap the column heading in an Excel item. Swipe labels on the horizontal axis of a Power View column chart or the vertical axis on a bar chart.

Drill You can double-click a field to drill down to the next level of a hierarchy (if one is defined in the data model). Click the Drill Up arrow to return to the previous level.

As long as you leave the Power BI for Mobile app open, the filter and sort selections you have applied remain intact. However, when you close the app, the filter and sort selections are removed.

Sharing a report from Power BI for Mobile

To share a report that you are viewing in the Power BI for Mobile app, swipe from the right, click Share, and then type the email recipient’s address. The app sends an email message containing a link to the report rather than the page you are viewing. The recipient can use one of two links to view the report, but only if the recipient already has permissions to view the report in SharePoint Online. The MOBILEBI link connects the user to the report in the Power BI for Mobile app, and the HTTPS link opens the report in a browser window using the Excel Web App.

Power BI Administration

Power BI is a collection of features and services to help you display content like Excel workbooks, charts and reports through a different UI, if you wish, but also gives you some other options such as scheduled data refreshes, access to on-premises data, and the ability to create, and manage connections to data sources to help ensure everyone uses the same data source for reporting.

POWER BI FOR OFFICE 365 includes an administrative infrastructure that you manage through the Power BI Admin Center. To access the Power BI Admin Center, if you are a member of the Admin group, click the Power BI Admin Center link on the Tools menu (gear icon) in the upper-right corner of a Power BI site. From a standard SharePoint Online site, click the Power BI link on the Admin menu in the upper-right corner. This centralized portal for administrative tasks allows you to perform the following tasks:

Monitor system health The system_health session is an Extended Events session that is included by default with SQL SERVER. This session starts automatically when the SQL Server Database Engine starts, and runs without any noticeable performance effects.

Use the Gateway page to review a list of existing gateways and their current status. A gateway is the mechanism that securely connects Power BI to an on-premises data source and runs as a client agent on an on-premises computer. When you use this page to set up a new gateway, you download the gateway client, install it locally, and then register the gateway with a key provided in the Power BI Admin Center. You can also use this page to regenerate the key for an existing gateway or to enable the cloud credential store for the gateway so that you can quickly restore the gateway on another computer if the current gateway fails.

Configure data sources The data source can be a user data source or a system data source.

Use the Data Sources page to review a list of existing on-premises data sources and their current status. You can edit, delete, or test the connection for an existing data source. When you edit the data source, you specify whether it is enabled for cloud access, which means workbooks with this data source can be refreshed in SharePoint Online, and whether it is enabled as an O Data feed that users can access by using Power Query. You also use the Data Sources page to add a new data source, optionally enable it for cloud access or an O Data feed, assign it to a gateway, and specify the connection properties or provide a connection string. Currently, only SQL Server and Oracle are supported as data source types.

Define security for administrative roles Use the Role Management page to add members to the Admin group, which grants permission to access the Power BI Admin Center, or to the Data Steward group, which grants permission to certify queries for use in Power Query.

Specify settings for Power BI Use the Settings page to configure general settings such as whether to display top users in the usage analytics dashboard or to enable Windows authentication for O Data when it feeds the Microsoft Online Directory

Synchronization Tool is configured. You can also define the recipients of email notifications and specify whether any of the following events trigger a notification: the expiration of a gateway, the release of a new version of the Data Management Gateway client, or an indexing failure for an O Data feed.

Source: https://mindmajix.com/sql-server/how-to-share-reports-in-power-bi-for-mobile

Logging is a pretty important thing these days (well, almost all days), and being able to implement that into your CMP is equally as important. VMware's Log Insight solution is a fantastic platform for aggregating, analyzing, and searching for logs which offers the best integration with other VMware products on the market. Log Insight can consume logs from a variety of sources over several protocols. It also has an agent which can be installed in Windows and Linux and, with server-side configurations, is able to send file-based logs back to the Log Insight system/cluster. Well, today I bring to the community two new blueprints which automate the installation of this agent into workloads deployed from vRealize Automation. Simply import the .zip file into vRA using the API or the CloudClient, and drag-and-drop onto a blueprint. The nice thing about both of these blueprints is the agent is streamed directly from the Log Insight system--no need to pre-stage the agent package on a file server. Check the links on VMware Code if you're interested in checking these out:

Log Insight Agent for Linux

Log Insight Agent for Windows

Scenario , Windows based vcenter server with external PSC (appliances)

When click any component by using administrator@vsphere.local

Error:- Do not have permission to look this object

Work around:-

1. Shut down the vCenter Server services
2. Shut down the PSCs services
3. Started up PSC services then verified they were all running
4. Started up vCenter services then verified those services

SDDC, Cloud, Converged, and Virtual Fundamental Server Storage I/O Tradecraft

Over the past several months I have posted, commenting, presenting and discussing more about Data Infrastructures and my new book (my 4th solo project) officially announced today, Software Defined Data Infrastructure Essentials (CRC Press). Software Defined Data Infrastructure (SDDI) Essentials is now generally available at various global venues in hardcopy, hardback print as well as various electronic versions including via  Amazon and CRC  Press among others. For those attending VMworld 2017 in Las Vegas, I will be doing a book signing, meet and greet at 1PM Tuesday August 29 in the VMworld book store, as well as presenting at various other fall industry events.

Software Defined Data Infrastructure (SDDI) Announcement

(Via Businesswire) Stillwater,  Minnesota – August 23, 2017  – Server StorageIO, a leading  independent IT industry advisory and consultancy firm, in conjunction with  publisher CRC Press, a Taylor and Francis imprint, announced the release and general availability of “Software-Defined  Data Infrastructure Essentials,” a new book by Greg Schulz, noted author  and Server StorageIO founder.

The Software Defined Data Infrastructure Essentials book covers physical, cloud, converged (and hyper-converged), container,  and virtual server storage I/O networking technologies, revealing trends,  tools, techniques, and tradecraft skills.

Various IT and Cloud Infrastructure Layers including Data Infrastructures

From cloud web scale to enterprise and small environments, IoT  to database, software-defined data center (SDDC) to converged and container  servers, flash solid state devices (SSD) to storage and I/O networking,, the  book helps develop or refine hardware, software, services and management experiences,  providing real-world examples for  those involved with or looking to expand  their data infrastructure education knowledge and tradecraft skills.

Software Defined Data Infrastructure Essentials book topics include:

• Cloud, Converged, Container, and Virtual Server Storage I/O networking
• Data protection (archive, availability, backup, BC/DR, snapshot, security)
• Block,  file, object, structured, unstructured and data value
• Analytics, monitoring, reporting, and management metrics
• Industry  trends, tools, techniques, decision making
• Local,  remote server, storage and network I/O troubleshooting
• Performance,  availability, capacity and  economics (PACE)

What People Are Saying About Software Defined Data Infrastructure Essentials Book

“From CIOs to operations, sales to engineering, this  book is a comprehensive reference, a must-read for IT infrastructure professionals, beginners to seasoned experts,” said Tom  Becchetti, advisory systems engineer.

"We had a front row seat watching Greg present live in our education workshop seminar sessions for ITC professionals in the Netherlands material that is in this book. We recommend this amazing book to expand your converged and data infrastructure knowledge from beginners to industry veterans."
 
Gert and Frank Brouwer - Brouwer Storage Consultancy

"Software-Defined Data Infrastructures provides the foundational building blocks to improve your craft in several areas including applications, clouds, legacy, and more.  IT professionals, as well as sales professionals and support personal, stand to gain a great deal by reading this book."
   
Mark McSherry- Oracle Regional Sales Manager

"Greg Schulz has provided a complete ‘toolkit’ for storage management along with the background and framework for the storage or data infrastructure professional (or those aspiring to become one)."
  Greg Brunton – Experienced Storage and Data Management Professional

“Software-defined data infrastructures are  where hardware, software, server, storage, I/O networking and related services converge  inside data centers or clouds to protect, preserve, secure and serve  applications and data,” said Schulz.   “Both readers who are new  to data infrastructures and seasoned pros will find this indispensable for  gaining and expanding their knowledge.”

More About Software Defined Data Infrastructure Essentials
    Software Defined Data Infrastructures (SDDI) Essentials provides fundamental coverage of physical, cloud, converged, and virtual server storage I/O networking technologies, trends, tools, techniques, and tradecraft skills. From webscale, software-defined, containers, database, key-value store, cloud, and enterprise to small or medium-size business, the book is filled with techniques, and tips to help develop or refine your server storage I/O hardware, software, Software Defined Data Centers (SDDC), Software Data Infrastructures (SDI) or Software Defined Anything (SDx) and services skills. Whether you are new to data infrastructures or a seasoned pro, you will find this comprehensive reference indispensable for gaining as well as expanding experience with technologies, tools, techniques, and trends.

This book is the definitive source providing comprehensive coverage about IT and cloud Data Infrastructures for experienced industry experts to beginners. Coverage of topics spans from higher level applications down to components (hardware, software, networks, and services) that get defined to create data infrastructures that support business, web, and other information services. This includes Servers, Storage, I/O Networks, Hardware, Software, Management Tools, Physical, Software Defined Virtual, Cloud, Docker, Containers (Docker and others) as well as Bulk, Block, File, Object, Cloud, Virtual and software defined storage.

Additional topics include Data protection (Availability, Archiving, Resiliency, HA, BC, BR, DR, Backup), Performance and Capacity Planning, Converged Infrastructure (CI), Hyper-Converged, NVM and NVMe Flash SSD, Storage Class Memory (SCM), NVMe over Fabrics, Benchmarking (including metrics matter along with tools), Performance Capacity Planning and much more including whos doing what, how things work, what to use when, where, why along with current and emerging trends.

Book Features

ISBN-13: 978-1498738156
      ISBN-10: 149873815X
      Hardcover: 672 pages
      (Available in Kindle and other electronic formats)
      Over 200 illustrations and 70 plus tables
      Frequently asked Questions (and answers) along with many tips
      Various learning exercises, extensive glossary and appendices
      Publisher: Auerbach/CRC Press Publications; 1 edition (June 19, 2017)
Language: English

Where To Learn More

Learn  more about  related technology,  trends, tools, techniques, and tips with the following links.

• Whats a data infrastructure? (Via NetworkWorld)
• Software Defined Data Infrastructure Essentials (CRC Press) book companion page (includes various images, sample figures and added content)
• Click here to view (PDF) table of contents (TOC)
• Click here to view (PDF) Preface, who should read, how organized and related material
• Search and see whats inside Software Defined Data Infrastructure Essentials using this link to Google Books
• Do you have an IT trade craft skills gap? (Via NetworkWorld)
• Ensure your data infrastructure remains available and resilient (Via NetworkWorld)
• Data Infrastructure Primer and Overview (Its Whats Inside The Data Center)
• Data Infrastructure Server Storage I/O Tradecraft Trends
• Data Infrastructure Server Storage I/O related Tradecraft Overview
• Some server storage I/O benchmark workload scripts (Part I)
• Server Storage I/O Benchmarking Performance Resource Tools
• Server Storage I/O Converged (CI) Hyper-converged (HCI) overview
• Data Infrastructure industry links page - Various Data Infrastructure related links
• Welcome to the Data Protection Diaries - Data protection related topics
• Time to restore your backups, do you know where is your data is?
• Object and Cloud Storage Center (www.objectstoragecenter.com)
• www.thessdplace.com - NVM, flash, SSD, SCM and related topics
• www.thenvmeplace.com - NVM Express (NVMe) related topics
• Cloud and Virtual Data Storage Networking (CRC Press) "Intel Recommended Reading" book companion page
• The Green and Virtual Data Center (CRC Press) "Intel Recommended Reading" book companion page
• Resilient Storage Networks - Designing Flexible Scalable Data Infrastructures (Elsevier) book companion page
• Other books, articles, tips, blog posts, news, events, webinars, videos by Greg Schulz and Server StorageIO (portfolio page)

  Various IT and Cloud Infrastructure Layers including Data Infrastructures

What This All Means

Data Infrastructures exist to protect, preserve, secure and serve information along with the applications and data they depend on. With more data being created at a faster rate, along with the size of data becoming larger, increased application functionality to transform data into information means more demands on data infrastructures and their underlying resources.

Software-Defined Data Infrastructure Essentials: Cloud, Converged, and Virtual Fundamental Server Storage I/O Tradecraft is for people who are currently involved with or looking to expand their knowledge and tradecraft skills (experience) of data infrastructures. Software-defined data centers (SDDC), software data infrastructures (SDI), software-defined data infrastructure (SDDI) and traditional data infrastructures are made up of software, hardware, services, and best practices and tools spanning servers, I/O networking, and storage from physical to software-defined virtual, container, and clouds. The role of data infrastructures is to enable and support information technology (IT) and organizational information applications.

Everything is not the same in business, organizations, IT, and in particular servers, storage, and I/O. This means that there are different audiences who will benefit from reading this book. Because everything and everybody is not the same when it comes to server and storage I/O along with associated IT environments and applications, different readers may want to focus on various sections or chapters of this book.

If you are looking to expand your knowledge into an adjacent area or to understand whats under the hood, from converged, hyper-converged to traditional data infrastructures topics, this book is for you. For experienced storage, server, and networking professionals, this book connects the dots as well as provides coverage of virtualization, cloud, and other convergence themes and topics.

This book is also for those who are new or need to learn more about data infrastructure, server, storage, I/O networking, hardware, software, and services. Another audience for this book is experienced IT professionals who are now responsible for or working with data infrastructure components, technologies, tools, and techniques.

Learn more here about Software Defined Data Infrastructure (SDDI) Essentials book along with cloud, converged, and virtual fundamental server storage I/O tradecraft topics, order your copy from Amazon.com or CRC Press here, and thank you in advance for learning more about SDDI and related topics.

Ok, nuff said, for now.
Gs

After upgrade PSC u1 to u2 PSC disjoin from domain , and user got this error.

com.vmware.identity.idm.server.provider.vmwdirectory.VMwareDirectoryProvider]

[2017-08-18T13:23:14.779-05:00 bba76607-42b4-4a15-a3c2-7542f427d12c WARN ] [ActiveDirectoryProvider] There may be a domain join status change since native AD is configured. ActiveDirectoryProvider can function properly only when machine is properly joined

Tried to join domain  but got (Idm client exception: Error trying to join AD, error code [31])

It was because of smb was disabled on PSC (appliances)

run this command

/opt/likewise/bin/lwregshell list_values '[HKEY_THIS_MACHINE\Services\lwio\Parameters\Drivers\rdr]'

if value is zero of smb  then run this command

1. /opt/likewise/bin/lwregshell set_value '[HKEY_THIS_MACHINE\Services\lwio\Parameters\Drivers\rdr]' Smb2Enabled 1
2. /opt/likewise/bin/lwsm restart lwio
3. service-controll --stop --all
4. service-control --start -all
5. restart web client on vcenter server
6. then logon psc and try to add PSC in domain
7. If you have secondary PSC , it will take some time for showing domain user.

PowerCLI には、vSAN に対応したコマンドも含まれています。

VMware Hands-on Labs （HOL）のラボを利用して PowerCLI で vSAN の情報を見てみます。

今回は 「vSAN 6.5 の新機能」（HOL-1731-SDC-1 ）のシナリオを利用します。

このラボには PowerCLI で vSAN を操作するシナリオ（モジュール 4）も含まれていますが、

今回は モジュール1 での vSphere Web Client での情報確認を PowerCLI で代用してみます。

下記の「HOL-1731-SDC-1 - vSAN v6.5: What's New」です。

VMware Learning Platform

まず「レッスン 3：vSAN クラスターの準備」のシナリオを進めて vSAN クラスタを構成しておきます。

デスクトップにある PowerCLI のアイコンをダブルクリック起動して、vCenter に接続します。

PowerCLI> Connect-VIServer vcsa-01a.corp.local

PowerCLI コマンドラインは、HOL の「テキストの送信」を利用します。

vSAN クラスタの設定を確認してみます。

PowerCLI> Get-Cluster | where {$_.VsanEnabled -eq $True} | Get-VsanClusterConfiguration | select Cluster, VsanEnabled, VsanDiskClaimMode, SpaceEfficiencyEnabled | ft -AutoSize

ディスクグループの情報を確認してみます。

IsCacheDisk が True のものがキャッシュ ディスクで、False のものがキャパシティ ディスクです。

PowerCLI> Get-Cluster | where {$_.VsanEnabled -eq $True} | Get-VsanDiskGroup | sort VMHost | select VMHost, DiskGroupType, DiskFormatVersion, @{N="CacheDisk"; E={($_ | Get-VsanDisk | where {$_.IsCacheDisk -eq $true}).Count}}, @{N="CapacityDisk"; E={($_ | Get-VsanDisk | where {$_.IsCacheDisk -ne $true}).Count}}, Uuid | ft -AutoSize

デフォルトのウインドウ幅だと表示しきれないので、必要に応じて変更します。

たとえば、下記でウィンドウ幅を 120 に拡張できます。

$window_width = 120

$pswindow = (Get-Host).ui.rawui

$newsize = $pswindow.buffersize; $newsize.width = $window_width; $pswindow.buffersize = $newsize

$newsize = $pswindow.windowsize; $newsize.width = $window_width; $pswindow.windowsize = $newsize

vSAN ディスクを確認してみます。

PowerCLI> Get-Cluster | where {$_.VsanEnabled -eq $True} | Get-VsanDiskGroup | % {$hv = $_.VMHost; $_ | Get-VsanDisk | % {$path = $_.DevicePath; $_| select @{N="ESXi"; E={$hv.Name}},Uuid, IsCacheDisk, IsSSD, CanonicalName, @{N="CapacityGB"; E={($hv | Get-VMHostDisk | where {$_.DeviceName -eq $path }).ScsiLun.CapacityGB}}}} | ft -AutoSize

vSAN データストアの容量情報を確認してみます。

PowerCLI> Get-Datastore | where {$_.Type -eq "vsan"} | select Name, Type, CapacityGB, FreeSpaceGB, @{N="ProvisionedSpaceGB"; E={($_.CapacityGB - $_.FreeSpaceGB) + ($_.ExtensionData.Summary.Uncommitted / 1GB)}} | ft -AutoSize

各 ESXi ホストのストレージ プロバイダ の情報を見てみます。

PowerCLI> Get-VasaProvider | where {$_.Namespace -eq "VSAN"} | sort Name | select Status, Name, ProviderId | ft -AutoSize

アクティブなプロバイダは下記でわかります。

PowerCLI> Get-VasaStorageArray | where {$_.ModelId -eq "VSAN"} | select @{N="Datastore"; E={$Id = "ds:///vmfs/volumes/" + $_.Id + "/"; (Get-Datastore | where {$_.ExtensionData.Info.Url -eq $Id}).Name}}, Provider, Id | ft -AutoSize

デフォルトのストレージ ポリシー「Virtual SAN Default Storage Policy」のルールを確認してみます。

PowerCLI> Get-SpbmStoragePolicy -Name "Virtual SAN Default Storage Policy" | select -ExpandProperty AnyOfRuleSets | %{$name = $_.Name; $_ | select -ExpandProperty AllOfRules | select @{N="RuleName"; E={$Name}}, Capability, Value} | ft -AutoSize

HOL のシナリオを「レッスン 4： VSAN クラスター キャパシティのスケール アウト」まで進めると、

下記のように vSAN が拡張された様子が確認できます。

vSAN クラスタに、ディスクグループが追加されています。

追加したディスクグループの、キャッシュ ディスクとキャパシティディスクです。

vSAN データストア容量も追加されてます。

このように、vSphere Web Client で確認できる情報と同様のものが、PowerCLI でも確認することができます。

vSAN の構成情報をレポートとして残したい場合などに利用すると便利かもしれません。

以上、PowerCLI で vSAN の情報を見てみる話でした。

Hi,

Visit the below link to get the solution of Title issue.

http://vmwarediary.com/Tips/2017/8/5799801/Vmware-Tools64-msi-missing-during-uninstallation-and-Setup-exe-c-switch-does-…

Share more get more.

Thanks