<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Andr3201110141 Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>Andr3201110141 Tracker</description>
    <pubDate>Wed, 15 Nov 2023 10:32:06 GMT</pubDate>
    <dc:date>2023-11-15T10:32:06Z</dc:date>
    <item>
      <title>Create and upload certificates to vCenter Server Virtual Appliance</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Create-and-upload-certificates-to-vCenter-Server-Virtual/ta-p/2795711</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The script is started without any input so you can just download and launch it. Although the main aim was to create certificates on the VCSA, it can also be used to create just a CA or other certificates for your web servers. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Certificator_vCenterServer.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/55591i9EF637FCB18E63E5/image-size/large?v=v2&amp;amp;px=999" role="button" title="Certificator_vCenterServer.png" alt="Certificator_vCenterServer.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refer to my blog for detail on how the script works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://vmwarenotes.blogspot.com/" style="font-size: 10pt; line-height: 1.5em;" title="http://vmwarenotes.blogspot.com/"&gt;http://vmwarenotes.blogspot.com/&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Oct 2014 15:47:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Documents/Create-and-upload-certificates-to-vCenter-Server-Virtual/ta-p/2795711</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2014-10-10T15:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: Week long headache with CA signed certificates on VCSA 5.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Week-long-headache-with-CA-signed-certificates-on-VCSA-5-5/m-p/2166243#M71676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I realized that there are a number of things that I missed, so I wrote a script to automate the entire process. Testers wanted!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://vmwarenotes.blogspot.com/2014/10/certificator.html" title="http://vmwarenotes.blogspot.com/2014/10/certificator.html"&gt;Andre's VMware Notes: Certificator&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andre Combrinck&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Oct 2014 04:28:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Week-long-headache-with-CA-signed-certificates-on-VCSA-5-5/m-p/2166243#M71676</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2014-10-02T04:28:56Z</dc:date>
    </item>
    <item>
      <title>Re: Week long headache with CA signed certificates on VCSA 5.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Week-long-headache-with-CA-signed-certificates-on-VCSA-5-5/m-p/2166242#M71675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just some more information about where the issue seems to be. None of the below made a difference but I add it for the record. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Going through the &lt;SPAN style="color: #666666; font-family: Calibri, sans-serif; font-size: 14px;"&gt;&lt;SPAN&gt;02-inventoryservice script, it reaches a point where it calls the vi_regtool, which is a Java application. When you get the message "Initializing registration provider" and "Getting SSL certificates for &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://"&gt;https://&lt;/A&gt;&lt;SPAN&gt;...", it is within in this Java application. More precisely, it is when it runs the command 'exec -a vi_regtool $JAVA_BIN "$LOG4J_CONF" $JAVA_OPTS -jar "$VI_REGTOOL_JAR" "$@"'.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since Java has its own certificate store, I added my self-signed certificate into the Java cacerts store. I even created an intermediate CA to sign the server certs with and added this cert into the store too. On vCSA the Java JRE home is at /usr/java/jre-vmware. To add the CA to the Java store, run this command while withing the JRE HOME folder: bin/keytool -import -trustcacerts -alias MyRootCA -file RootCA.crt -keystore lib/security/cacerts. This adds the cert successfully, and even after rebooting the appliance, I still cannot run &lt;SPAN style="color: #666666; font-family: Calibri, sans-serif; font-size: 14px;"&gt;02-inventoryservice to completion.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I get: server certificate assertion not verified and thumbprint not matched.&lt;/P&gt;&lt;P&gt;Return code is: SSLHandshakeFailed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andre&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Sep 2014 08:39:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Week-long-headache-with-CA-signed-certificates-on-VCSA-5-5/m-p/2166242#M71675</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2014-09-04T08:39:10Z</dc:date>
    </item>
    <item>
      <title>Re: Week long headache with CA signed certificates on VCSA 5.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Week-long-headache-with-CA-signed-certificates-on-VCSA-5-5/m-p/2166241#M71674</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As it always goes, I made progress right after my last post.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;After getting the error, it seems that the certificate is put in place, because if you browse to &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://vcenter:7444/lookupservice/sdk"&gt;https://vcenter:7444/lookupservice/sdk&lt;/A&gt;&lt;SPAN&gt;, the correct certificate does appear. I then ran OpenSSL s_client to verify that the certificate is valid and this is what I got:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vCenter55:/ # openssl s_client -connect 192.168.33.128:7444 -status &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;### The command I ran the first time&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;CONNECTED(00000003)&lt;/P&gt;&lt;P&gt;OCSP response: no response sent&lt;/P&gt;&lt;P&gt;depth=1 /C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;verify error:num=19:self signed certificate in certificate chain &lt;STRONG style="text-decoration: underline;"&gt;### Seems the appliance doesn't like the self-signed certificate&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;verify return:0&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Certificate chain&lt;/P&gt;&lt;P&gt;0 s:/C=ZA/ST=Gauteng/O=company/OU=VMware vCenter Service Certificate/CN=vCenter55.company.co.za&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; i:/C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;1 s:/C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; i:/C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Server certificate&lt;/P&gt;&lt;P&gt;-----BEGIN CERTIFICATE-----&lt;/P&gt;&lt;P&gt;MIID9jCCAt6gAwIBAgICAS.......FBQAwfjELMAkGA1UEBhMCWkEx&lt;/P&gt;&lt;P&gt;-----END CERTIFICATE-----&lt;/P&gt;&lt;P&gt;subject=/C=ZA/ST=Gauteng/O=company/OU=VMware vCenter Service Certificate/CN=vCenter55.company.co.za&lt;/P&gt;&lt;P&gt;issuer=/C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;No client certificate CA names sent&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;SSL handshake has read 2309 bytes and written 441 bytes&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;New, TLSv1/SSLv3, Cipher is AES256-SHA&lt;/P&gt;&lt;P&gt;Server public key is 2048 bit&lt;/P&gt;&lt;P&gt;Secure Renegotiation IS supported&lt;/P&gt;&lt;P&gt;Compression: NONE&lt;/P&gt;&lt;P&gt;Expansion: NONE&lt;/P&gt;&lt;P&gt;SSL-Session:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Protocol&amp;nbsp; : TLSv1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Cipher&amp;nbsp;&amp;nbsp;&amp;nbsp; : AES256-SHA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Session-ID: 540771BD58058D6BD2F7C0B673A0D5740FC964C9179DC83DDA9EDA0BCAEB06C7&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Session-ID-ctx:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Master-Key: 8BDD035D2FCB5645DECF21B5BB26B6C46C6A964DBD8B5E54EA4CEF1893B75E2D2C2C904E1162B808BA7BBD5CFDDEE22E&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Key-Arg&amp;nbsp;&amp;nbsp; : None&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Start Time: 1409774013&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Timeout&amp;nbsp;&amp;nbsp; : 300 (sec)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Verify return code: 19 (self signed certificate in certificate chain) &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;### The return code 19, as seen above, is and error&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vCenter55:/ # openssl s_client -connect 192.168.33.128:7444 -CApath /etc/ssl/certs &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;### This time I ran it while specifying the folder where my root CA is kept&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;CONNECTED(00000003)&lt;/P&gt;&lt;P&gt;depth=1 /C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;verify return:1 &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;### No error this time.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;depth=0 /C=ZA/ST=Gauteng/O=company/OU=VMware vCenter Service Certificate/CN=vCenter55.company.co.za&lt;/P&gt;&lt;P&gt;verify return:1&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Certificate chain&lt;/P&gt;&lt;P&gt;0 s:/C=ZA/ST=Gauteng/O=company/OU=VMware vCenter Service Certificate/CN=vCenter55.company.co.za&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; i:/C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;1 s:/C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; i:/C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Server certificate&lt;/P&gt;&lt;P&gt;-----BEGIN CERTIFICATE-----&lt;/P&gt;&lt;P&gt;MIID9jCCAt6gAwIBAgI......wfjELMAkGA1UEBhMCWkEx&lt;/P&gt;&lt;P&gt;-----END CERTIFICATE-----&lt;/P&gt;&lt;P&gt;subject=/C=ZA/ST=Gauteng/O=company/OU=VMware vCenter Service Certificate/CN=vCenter55.company.co.za&lt;/P&gt;&lt;P&gt;issuer=/C=ZA/ST=Gauteng/L=Pretoria/O=company/OU=Certificate Authority/CN=company Root CA&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;No client certificate CA names sent&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;SSL handshake has read 2309 bytes and written 465 bytes&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;New, TLSv1/SSLv3, Cipher is AES256-SHA&lt;/P&gt;&lt;P&gt;Server public key is 2048 bit&lt;/P&gt;&lt;P&gt;Secure Renegotiation IS supported&lt;/P&gt;&lt;P&gt;Compression: NONE&lt;/P&gt;&lt;P&gt;Expansion: NONE&lt;/P&gt;&lt;P&gt;SSL-Session:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Protocol&amp;nbsp; : TLSv1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Cipher&amp;nbsp;&amp;nbsp;&amp;nbsp; : AES256-SHA&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Session-ID: 54077230E37AC53541373C907E213A8ED19EA02DF5EAFA47C28BF114DA3D68E1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Session-ID-ctx:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Master-Key: F8226AA2B758500D90B0137632F14752FB617E749577C7B4826CD541B1DE6D8BA8F4C3FA24CE59F734E8D5176D1F43AB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Key-Arg&amp;nbsp;&amp;nbsp; : None&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Start Time: 1409774128&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Timeout&amp;nbsp;&amp;nbsp; : 300 (sec)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Verify return code: 0 (ok) &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;### This time the cert is OK&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Turning my attention to the &lt;SPAN style="font-size: 11.0pt; font-family: 'Calibri','sans-serif';"&gt;02-inventoryservice script...&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Sep 2014 20:08:44 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Week-long-headache-with-CA-signed-certificates-on-VCSA-5-5/m-p/2166241#M71674</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2014-09-03T20:08:44Z</dc:date>
    </item>
    <item>
      <title>Re: Week long headache with CA signed certificates on VCSA 5.5</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/Week-long-headache-with-CA-signed-certificates-on-VCSA-5-5/m-p/2166240#M71673</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am in the same boat as you are. I even posted a question to the editor of the article that after following the steps, I get the same issue. I have to be honest here that I didn't use a Microsoft CA nor a public CA, and ran all the OpenSSL commands directly on the appliance. So, I started by creating a root CA with the key, then I generate the CSRs etc from the appliance. To ensure that the root CA that I created was valid, I copied it to /etc/ssl/certs and ran c_rehash /etc/ssl/certs, which then lists my new CA. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Sep 2014 19:40:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/Week-long-headache-with-CA-signed-certificates-on-VCSA-5-5/m-p/2166240#M71673</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2014-09-03T19:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: Assigning vSphere with Operations Management  licenses to a host</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Assigning-vSphere-with-Operations-Management-licenses-to-a-host/m-p/416797#M1367</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I finally phoned License support and got it solved. I had to downgrade the 6 vCenter Operations Manager licenses in order to see them. My hosts are all on ESX 5.1. The downgrade is done from my.vmware.com --&amp;gt; License Keys --&amp;gt; I want to: Downgrade Licenses. It worked as expected after that. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2014 15:08:17 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Assigning-vSphere-with-Operations-Management-licenses-to-a-host/m-p/416797#M1367</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2014-03-25T15:08:17Z</dc:date>
    </item>
    <item>
      <title>Re: Assigning vSphere with Operations Management  licenses to a host</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Assigning-vSphere-with-Operations-Management-licenses-to-a-host/m-p/416796#M1366</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the replies,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@Gradinka, thanks for the screenshot. I know where to go for the licensing, but...&lt;/P&gt;&lt;P&gt;@markdjones82 ...yes, the problem is that I don't have the option to choose one of the 6 licenses when licensing a host. And yes, the licenses are a mixture of both since we started with the acceleration kit, which came with vCenter Operations Manager and then we topped it up with 12 Standard licenses. I used up the Standard licenses first and now want to start using the other 6.&lt;/P&gt;&lt;P&gt;@markj Thanks for the post. I removed the license that was available from the download site and instead assigned the license with the 6 CPUs to the vCenter Operations Manager. &lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;This is where I am at:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="LicenseHost.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/50840iC0DB8B4E893E5B72/image-size/large?v=v2&amp;amp;px=999" role="button" title="LicenseHost.png" alt="LicenseHost.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;As you can see, the 6 CPU licenses for vCenter Operations Manager are now showing. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any more ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andre&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Mar 2014 09:43:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Assigning-vSphere-with-Operations-Management-licenses-to-a-host/m-p/416796#M1366</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2014-03-25T09:43:52Z</dc:date>
    </item>
    <item>
      <title>Assigning vSphere with Operations Management  licenses to a host</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/Assigning-vSphere-with-Operations-Management-licenses-to-a-host/m-p/416792#M1362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How in the world do I allocate VMware vSphere with Operations Management 5.5 Standard licenses to a host? The implementation was green field so we bought the acceleration kit for vCenter server that comes with 6 licenses of vSphere with Operation Management. I've got Ops Manager working well and itself is licensed and can see all the hosts. We also bought 12 further licenses to have 18 in total, and I can see the other 12 and allocate them to hosts, but cannot see the original 6. I never could.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="License Issue2.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/50820i4F47DBB854D31E8F/image-size/large?v=v2&amp;amp;px=999" role="button" title="License Issue2.png" alt="License Issue2.png" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="License Issue1.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/50812i324A9410F387936D/image-size/large?v=v2&amp;amp;px=999" role="button" title="License Issue1.png" alt="License Issue1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andre&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Mar 2014 11:11:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/Assigning-vSphere-with-Operations-Management-licenses-to-a-host/m-p/416792#M1362</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2014-03-24T11:11:10Z</dc:date>
    </item>
    <item>
      <title>Re: ESXi 4.x vMotion MTU</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872286#M68007</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FC SANs don't use an MTU so you don't need to take that into consideration. MTU and Jumbo Frames are Ethernet concepts. A Jumbo Frame is just frames that are greater than the conventional frames of 1500. As algreco81 said, it is better to have a higher MTU for performance reasons, but it is not a requirement for migrations to work. It only improves VM migrations (copying the running instance of a VM and its active RAM to from one host to another). The storage stays in place.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Oct 2012 15:17:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/ESXi-4-x-vMotion-MTU/m-p/872286#M68007</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2012-10-05T15:17:55Z</dc:date>
    </item>
    <item>
      <title>Re: Afetr deploying Unable to join domain using PowerCLI</title>
      <link>https://communities.vmware.com/t5/Automation-Tools-Discussions/Afetr-deploying-Unable-to-join-domain-using-PowerCLI/m-p/848589#M376</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you expecting that the server auto joins the domain? I see that you are using a static IP address on the VM. Unfortunately, due to the order in which the customization happens, the static IP address is only applied after a second reboot. To autojoin the domain, you would need to use a DHCP server to make sure the machine already has an IP address at the time the domain join procedure happens.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2012 07:24:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Automation-Tools-Discussions/Afetr-deploying-Unable-to-join-domain-using-PowerCLI/m-p/848589#M376</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2012-09-21T07:24:22Z</dc:date>
    </item>
    <item>
      <title>Re: Auto cloning issue - fault.NicSettingMismatch</title>
      <link>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Auto-cloning-issue-fault-NicSettingMismatch/m-p/2209930#M73414</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would recommend the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Get-OSCustomizationNicMapping $s.name | Set-OSCustomizationNicMapping -IpMode UseStaticIP -IpAddress $s.IPAddress -SubnetMask 255.255.255.0 -DefaultGateway 1.1.2.1 -Dns $dns1,$dns2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm a bit late, but I hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andre&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Sep 2012 14:12:09 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/Auto-cloning-issue-fault-NicSettingMismatch/m-p/2209930#M73414</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2012-09-14T14:12:09Z</dc:date>
    </item>
    <item>
      <title>Re: Virtualization for small IBM X3100 M4</title>
      <link>https://communities.vmware.com/t5/Virtualization-Technology/Virtualization-for-small-IBM-X3100-M4/m-p/851111#M4895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Arne,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ESXi is a good starting point and relatively simple to get started and to manage afterwards. What you would end up with is the host standing on its own running some VMs and a client machine on the other end with the vSphere client installed on it. The vSphere client allows you to manage the VMs on the host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Following on from the previous post, make sure the server you are using has all the required hardware and that the hardware is compatible. &lt;A href="http://www.vmware.com/resources/compatibility/search.php?rct=j&amp;amp;q=&amp;amp;esrc=s&amp;amp;frm=1&amp;amp;source=web&amp;amp;cd=1&amp;amp;ved=0CFEQFjAA&amp;amp;url=http://www.vmware.com/go/hcl/&amp;amp;ei=qjH5T6LvG5SChQf-qKXoBg&amp;amp;usg=AFQjCNEFF21anzH7ZKOahz2fqtWZZLQOAw&amp;amp;sig2=EiXLiWgkz77uAo5kQSRLGQ"&gt;http://www.vmware.com/resources/compatibility/search.php?rct=j&amp;amp;q=&amp;amp;esrc=s&amp;amp;frm=1&amp;amp;source=web&amp;amp;cd=1&amp;amp;ved=0CFEQFjAA&amp;amp;url=http://www.vmware.com/go/hcl/&amp;amp;ei=qjH5T6LvG5SChQf-qKXoBg&amp;amp;usg=AFQjCNEFF21anzH7ZKOahz2fqtWZZLQOAw&amp;amp;sig2=EiXLiWgkz77uAo5kQSRLGQ&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andre&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 08 Jul 2012 07:08:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Virtualization-Technology/Virtualization-for-small-IBM-X3100-M4/m-p/851111#M4895</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2012-07-08T07:08:18Z</dc:date>
    </item>
    <item>
      <title>Re: Changing my SC network</title>
      <link>https://communities.vmware.com/t5/Availability-HA-FT-Discussions/Changing-my-SC-network/m-p/2629465#M6692</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have a look at this article. Hope it helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=4309499"&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=4309499&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 04 Feb 2012 15:38:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Availability-HA-FT-Discussions/Changing-my-SC-network/m-p/2629465#M6692</guid>
      <dc:creator>Andr3201110141</dc:creator>
      <dc:date>2012-02-04T15:38:42Z</dc:date>
    </item>
  </channel>
</rss>

