<?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>topic Re: AppVolumes 3.0 - does anyone have it working? in App Volumes</title>
    <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951927#M566</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did note that I disabled cert checks... made no difference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do understand that vROps is optional, but if I'm opting to connect to my existing vROps instance it should be able to connect, and it isn't.&amp;nbsp; vCenter is more important, obviously, and it can't connect to that either.&amp;nbsp; I'm pretty sure it's some issue in the appliance (perhaps the firewall), but I'm not about to go digging through this.&amp;nbsp; It appears that enough people have issues with this first release that I'm opening the case and letting VMware dig through it so that by the time we get a release where migration is an option the appliance will be stable and a viable option for upgrade.&amp;nbsp; For 3.x to succeed it needs to provide some additional value over what we can do with the 2.10.0 release.&amp;nbsp; Currently, there is none which is why everyone is advising to stay on the 2.10.0 release.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 28 Mar 2016 18:45:53 GMT</pubDate>
    <dc:creator>JHT_Seattle</dc:creator>
    <dc:date>2016-03-28T18:45:53Z</dc:date>
    <item>
      <title>AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951922#M561</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I can't get through the basic config wizard.&amp;nbsp; Using the same credentials/info as a working 2.10.0 environment, the 3.0 appliance just reports connection failures.&amp;nbsp; Logged into the appliance console and it can ping everything successfully.&amp;nbsp; Anyone else out there having any luck?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 21:35:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951922#M561</guid>
      <dc:creator>JHT_Seattle</dc:creator>
      <dc:date>2016-03-25T21:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951923#M562</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;No.&amp;nbsp; Similar experience to yours.&amp;nbsp; Although I don't think the 2.10 creds are relevant.&amp;nbsp; I installed the appliance using the ova.&amp;nbsp; I can log on to it at the console (root/123), change the password, check networking... all good.&amp;nbsp; But cannot get any response from &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://" rel="nofollow"&gt;http://&lt;/A&gt;&lt;SPAN&gt;&amp;lt;applianceip&amp;gt;/horizonadmin.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 22:04:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951923#M562</guid>
      <dc:creator>dray11</dc:creator>
      <dc:date>2016-03-25T22:04:00Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951924#M563</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm stuck as well. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First issue was with static IP.&amp;nbsp; The appliance booted but got stuck waiting for DHCP so I added registration to DHCP and rebooted appliance.&amp;nbsp; When it came up there was a problem with the AD configure button.&amp;nbsp; I redeployed the OVA and made sure to configure DHCP with new MAC before booting.&amp;nbsp; That worked and the config button allowed me to add AD and Admin group.&amp;nbsp; I'm stuck at the vROPS config.&amp;nbsp; Documentation says that vROPS is optional even thought the app volumes config wizard shows it as required.&amp;nbsp; I'm going to move on the vCenter registration and see if the config finishes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What step are you stuck on?&amp;nbsp; You may need to add the appropriate certificates to the app volumes appliance cacert.pem file.&amp;nbsp; I added our internal AD CA, public CA root and intermediate certs, etc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 22:10:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951924#M563</guid>
      <dc:creator>cmbwml1</dc:creator>
      <dc:date>2016-03-25T22:10:47Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951925#M564</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've tried selecting the option to accept any cert, and I've tried disabling cert checks in the appliance, neither has resulted in me being able to establish a connection to either my vCenter (Windows-based, not the VCSA) or my vROps instance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I opened a case for it, I'll reply back here if/when anything improves.&amp;nbsp; Awaiting 3.0.1...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2016 22:50:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951925#M564</guid>
      <dc:creator>JHT_Seattle</dc:creator>
      <dc:date>2016-03-25T22:50:37Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951926#M565</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you might need to have certs disable to test&lt;/P&gt;&lt;P&gt;/etc/wemi/utils/disable_ssl_validation.sh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the setup and usage is definitely different than 2.10, no computer assignment, no longer has option to assign/de-assign stack on the fly, file share requirement, do see some of these options better suited for stability and easier to integrated different deployments (example multiple vcenter, etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vROps is optional&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when you install agent, take note that it install vrops, uem, and appv components.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Mar 2016 21:11:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951926#M565</guid>
      <dc:creator>chulerico</dc:creator>
      <dc:date>2016-03-26T21:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951927#M566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I did note that I disabled cert checks... made no difference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do understand that vROps is optional, but if I'm opting to connect to my existing vROps instance it should be able to connect, and it isn't.&amp;nbsp; vCenter is more important, obviously, and it can't connect to that either.&amp;nbsp; I'm pretty sure it's some issue in the appliance (perhaps the firewall), but I'm not about to go digging through this.&amp;nbsp; It appears that enough people have issues with this first release that I'm opening the case and letting VMware dig through it so that by the time we get a release where migration is an option the appliance will be stable and a viable option for upgrade.&amp;nbsp; For 3.x to succeed it needs to provide some additional value over what we can do with the 2.10.0 release.&amp;nbsp; Currently, there is none which is why everyone is advising to stay on the 2.10.0 release.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2016 18:45:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951927#M566</guid>
      <dc:creator>JHT_Seattle</dc:creator>
      <dc:date>2016-03-28T18:45:53Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951928#M567</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think I was having the same problem as you.&amp;nbsp; I got it working finally... but not sure what if anything I did.&amp;nbsp; I reinstalled the Appliance three times.&amp;nbsp; The third time it worked.&amp;nbsp; Fortunately the install is pretty quick.&lt;/P&gt;&lt;P&gt;The first time I installed it with the old J# vSphere console.&amp;nbsp; Felt like it went ok but like you, it seemed like the networking did not work.&amp;nbsp; &lt;/P&gt;&lt;P&gt;Decided to try again in case I accidentally did something wrong.&amp;nbsp; This time I used the web console.&amp;nbsp; Seemed to go about the same.&amp;nbsp; Again, networking did not work.&amp;nbsp; This time I was determined to figure it out.&amp;nbsp; I am no Linux expert but I can get around.&amp;nbsp; I figured out that I could only ping my local network from the appliance.&amp;nbsp; Nothing could ping the appliance... not even machines on the local VLAN.&amp;nbsp; I checked everything... it seemed anyway... must have missed something.&amp;nbsp; Certainly confirmed all the eth0 interface settings.&lt;/P&gt;&lt;P&gt;So... I finally decided to try again.&amp;nbsp; Deleted the appliance and installed again... from the web console.&amp;nbsp; This time it worked.&amp;nbsp;&amp;nbsp; ???&lt;/P&gt;&lt;P&gt;I can't make any sense of this.&amp;nbsp; Probably something about me or my environment... but that makes this feel a lot more like a finicky tech preview and less like a GA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2016 20:55:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951928#M567</guid>
      <dc:creator>dray11</dc:creator>
      <dc:date>2016-03-28T20:55:49Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951929#M568</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay, after playing with the HTML5 vCenter Fling today, revisited my AppVol 3.0 appliance.&amp;nbsp; I created an IP Pool for the subnet I deployed it to and associated it with the port group the appliance is on.&amp;nbsp; Tried to register vCenter again, SUCCESS first try.&amp;nbsp; Tried vROps, still no good.&amp;nbsp; Maybe it's just randomness?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Mar 2016 23:56:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951929#M568</guid>
      <dc:creator>JHT_Seattle</dc:creator>
      <dc:date>2016-03-28T23:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951930#M569</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for me the configurations steps all work, but I'm stuck when scanning the file share for new apps. I get this in the logs and the no new app appears!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[2016-03-29 07:59:34 UTC] P2103R14230 ERROR Unable to detect an ESX hostname for "#&amp;lt;Xms::Vcenter:0x00000007a6f098&amp;gt;"&lt;/P&gt;&lt;P&gt;[2016-03-29 07:59:34 UTC] P2103R14230 INFO Completed 400 Bad Request in 296.3ms (Views: 0.2ms | ActiveRecord: 1.3ms)&lt;/P&gt;&lt;P&gt;[2016-03-29 07:59:34 UTC] P2103R14230 INFO&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cristiano&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2016 08:04:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951930#M569</guid>
      <dc:creator>sappomannoz</dc:creator>
      <dc:date>2016-03-29T08:04:10Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951931#M570</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It works now. Datastore prefix is case sensitive, but to fix it I had to redeploy the ova, so maybe there where also other errors.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2016 09:43:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951931#M570</guid>
      <dc:creator>sappomannoz</dc:creator>
      <dc:date>2016-03-29T09:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951932#M571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I feel like I am on a different problem track and should stop making noise here... but wanted to followup on my previous comments for anyone else who comes along.&lt;/P&gt;&lt;P&gt;I figured out that the appliance firewall blocks ICMP.&amp;nbsp; Therefore do not expect it to respond to pings unless you disable the firewall (/etc/wemi/utils/disable_firewall.sh).&amp;nbsp; It is fine to have the firewall on unless you need ICMP it for testing (I think).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The console gave me confusing results because it would work in Chrome but not in IE... only I didn't notice the pattern for a while.&amp;nbsp; Turns out I needed TLS 1.1 enabled in IE (IE 10... why wasn't it enabled already?&amp;nbsp; I dunno.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, I suspect if I had not focused on pinging and had tried Chrome first I would have connected to my first install.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I have successfully AppCapture'd, Assign'ed and Agent'ed to get a simple app on my test client.&amp;nbsp; Modest success.&amp;nbsp; Now can do real testing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 29 Mar 2016 14:32:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951932#M571</guid>
      <dc:creator>dray11</dc:creator>
      <dc:date>2016-03-29T14:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951933#M572</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone been able to remove apps from appvols 3??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Apr 2016 15:37:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951933#M572</guid>
      <dc:creator>Hayes_marc</dc:creator>
      <dc:date>2016-04-06T15:37:22Z</dc:date>
    </item>
    <item>
      <title>Re: AppVolumes 3.0 - does anyone have it working?</title>
      <link>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951934#M573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately, there is no way to remove apps from inventory built-in; release notes indicate to contact VMware Support to remove them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Apr 2016 16:56:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/App-Volumes/AppVolumes-3-0-does-anyone-have-it-working/m-p/951934#M573</guid>
      <dc:creator>eeg3</dc:creator>
      <dc:date>2016-04-06T16:56:00Z</dc:date>
    </item>
  </channel>
</rss>

