JHT_Seattle's Posts

Can you outline your process?  I feel like I'm overthinking how complicated this would be, considering you said it only took you a half hour
So you're saying that when I update an existing stack it will automatically inject the updated snapvol.cfg file from the latest uploaded template, etc into the stack?  That's not what I've been l... See more...
So you're saying that when I update an existing stack it will automatically inject the updated snapvol.cfg file from the latest uploaded template, etc into the stack?  That's not what I've been led to believe...
I have this exact same issue since we updated managers to 2.12 awhile back.  I have a SR open for it, but have not received a hotfix... instead my logs were sent to engineering.  Can you give me ... See more...
I have this exact same issue since we updated managers to 2.12 awhile back.  I have a SR open for it, but have not received a hotfix... instead my logs were sent to engineering.  Can you give me your SR number so I can send it to my support engineer?
I had the issue with updating the templates when we updated to 2.12.  I ended up specifying a second datastore as the template store instead. As for updating existing stacks, there is a way ma... See more...
I had the issue with updating the templates when we updated to 2.12.  I ended up specifying a second datastore as the template store instead. As for updating existing stacks, there is a way manually, but it's tedious and probably a bit risky.  So, yes, the only proper way to update a stack is to recreate it at this time.  I've seen one other note here in the forums, and I've seen it myself, that recreating stacks with the latest template *does* improve load time vs older template versions.  One of the more frustrating things to me is that nowhere in the existing stacks is anything to indicate what version of the template was used.
So, 4 months from the 2.12 release (both of them), and nothing in resolved items about the major printer regression bug, except a note in Known Issues that says printing on Windows 10 might be an... See more...
So, 4 months from the 2.12 release (both of them), and nothing in resolved items about the major printer regression bug, except a note in Known Issues that says printing on Windows 10 might be an issue?  Forum chatter indicates so far that it's not fixed. WTH, App Volumes?
Hey Ray - I ran into a problem with an older stack of mine this last week and ended up resolving it by mounting an "update" of the vmdk to a VM without the appvol agent installed and copying f... See more...
Hey Ray - I ran into a problem with an older stack of mine this last week and ended up resolving it by mounting an "update" of the vmdk to a VM without the appvol agent installed and copying files from the latest template into the screwy app stack.  Long story short, and to tie it to this thread, it also noticeably sped up mount/logon. I remember asking Jason Marshall a long time ago for a true "upgrade" function in the GUI to insert these newer files into existing stacks, when I was thinking of versioning for stacks being integrated.  I could swear he said that was something they were working on, but I never saw it materialize. Unfortunately, it's not possible (so far as I know) to see easily what version of a template was used for each stack.  I only see what agent version was used. Just throwing this out there, since in an earlier reply you noted that you have several older stacks.  With 2.12.1 just around the corner, though, I'm going to wait until that template is available to do anything further (since it includes the virtual printer fix).
Just wanted to quickly say that when we switched from ethereal port groups (which is still the documented recommendation) for our linked clone VMs to static port groups, almost alllllll of our "A... See more...
Just wanted to quickly say that when we switched from ethereal port groups (which is still the documented recommendation) for our linked clone VMs to static port groups, almost alllllll of our "Agent Unreachable" woes disappeared overnight.  Take that for what you will, but if you're not set to static, you might give that a shot.
Hi Ray! Long time... I'm seeing this issue in my env as well under 2.12.  We have a few stacks with virtual printers (Adobe Acrobat X, Bullzip PDF, CutePDF) and all (including the XPS printer ... See more...
Hi Ray! Long time... I'm seeing this issue in my env as well under 2.12.  We have a few stacks with virtual printers (Adobe Acrobat X, Bullzip PDF, CutePDF) and all (including the XPS printer on the image itself) are missing with stacks successfully attached (any stack).  Most of my stacks were built with the 2.11 agent/template, but even after updating a stack to 2.12 it persists. Downgrading the AppVol agent to 2.11 resolves the issue.  Here's how it breaks down: 2.11 Agent + 2.11 stack w/virtual printer = all printers present (incl XPS from parent image) 2.11 Agent + 2.12 stack w/virtual printer = only 2.12 stack printer present (none from parent image) 2.12 Agent + 2.11 stack w/virtual printer = no printers present 2.12 Agent + 2.12 stack w/virtual printer = no printers present Between this and the requirement for capture VMs to be domain joined this is another great example of 2 steps forward, 1 back from the App Volumes dev team.  At least this is manageable, but I guess those "30-50%" decreased login times are a result of not actually attaching everything in the stacks.  Good job, guys.
VMware App Volumes 2.11 Release Notes
Opened a SR, got this response.  Release is due out this quarter.
No, nothing.  Development seems to have been focused on making the necessary changes to fit into the unified Astro UI future, to the detriment of every App Volumes 2.x admin with a production dep... See more...
No, nothing.  Development seems to have been focused on making the necessary changes to fit into the unified Astro UI future, to the detriment of every App Volumes 2.x admin with a production deployment.  VMware overall seems to be missing the boat when it comes to operationalizing all of these great technologies.  Most of my issues these days either have NO solution, or I have to dig into command lines and databases that aren't officially supported, or I just have to wait for Dev to come through in some future release.  Why App Volumes had to be the first technology in the Horizon stack to be released for the future model when it SO CLEARLY IS NOT READY is beyond me.  So now we have an unusable 3.0 release (for prod environments, and if you can get it to fully work in test, more power to you), and a lapsed 2.x branch that isn't fully compatible with the Horizon 7 release. I get no sense of urgency or duty to the customer (us) from VMware.  Just a few sympathetic shrugs and nothing else.
No change. System Messages log has these messages related to trying to attach stacks: Failed to reconfigure VM "cp-parent-db697967-d78b-4954-a2fc-fb5ddb3dd88f" (502b5222-1ba7-93b7-6405-846b... See more...
No change. System Messages log has these messages related to trying to attach stacks: Failed to reconfigure VM "cp-parent-db697967-d78b-4954-a2fc-fb5ddb3dd88f" (502b5222-1ba7-93b7-6405-846ba3884cd6): Fault: Unspecified (InvalidState) I suspect that App Volumes is not looking at the instant clone, but rather the parent of the instant clone to attach stacks to.  Given the nature of the parent, however, it's simply not possible.  Even though it's new, I haven't read anyone else having any issues, and it's hard for me to believe that this wouldn't have been tested by VMware prior to release as both Instant Clone and App Volumes are the highly-touted next-gen combination of technologies in the VDI space.  If it's not just me and this is truly how these two operate today then 2.10.1 or 2.11.0 had better come soon...
Anyone else have this issue?  I can't seem to attach stacks in a 2.10.0 environment to my test pool of H7 instant clones.  The same image I've always used, just replaced the agent option to use c... See more...
Anyone else have this issue?  I can't seem to attach stacks in a 2.10.0 environment to my test pool of H7 instant clones.  The same image I've always used, just replaced the agent option to use composer with instant clone tech.  I opened a SR for it, but have yet to be able to sync up with the SE.
Okay, after playing with the HTML5 vCenter Fling today, revisited my AppVol 3.0 appliance.  I created an IP Pool for the subnet I deployed it to and associated it with the port group the applianc... See more...
Okay, after playing with the HTML5 vCenter Fling today, revisited my AppVol 3.0 appliance.  I created an IP Pool for the subnet I deployed it to and associated it with the port group the appliance is on.  Tried to register vCenter again, SUCCESS first try.  Tried vROps, still no good.  Maybe it's just randomness?
I did note that I disabled cert checks... made no difference. 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, a... See more...
I did note that I disabled cert checks... made no difference. 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.  vCenter is more important, obviously, and it can't connect to that either.  I'm pretty sure it's some issue in the appliance (perhaps the firewall), but I'm not about to go digging through this.  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.  For 3.x to succeed it needs to provide some additional value over what we can do with the 2.10.0 release.  Currently, there is none which is why everyone is advising to stay on the 2.10.0 release.
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 (Wi... See more...
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. I opened a case for it, I'll reply back here if/when anything improves.  Awaiting 3.0.1...
I can't get through the basic config wizard.  Using the same credentials/info as a working 2.10.0 environment, the 3.0 appliance just reports connection failures.  Logged into the appliance conso... See more...
I can't get through the basic config wizard.  Using the same credentials/info as a working 2.10.0 environment, the 3.0 appliance just reports connection failures.  Logged into the appliance console and it can ping everything successfully.  Anyone else out there having any luck?
We're only using user assignments here, no machine assignments.  Turns out that's a good thing because machine assignments aren't supported at all in 3.0!  Don't know if that'll change down the r... See more...
We're only using user assignments here, no machine assignments.  Turns out that's a good thing because machine assignments aren't supported at all in 3.0!  Don't know if that'll change down the road or not. I've got the 3.0 OVA downloaded, but not deployed yet.  Too busy trying to put v7 through its paces... if I can just get this Instant Clone functionality to work a little more smoothly (and get stacks to attach) maybe I'll be motivated to.  So far I like some of the new v7 functionality, but overall I'm still mixed.  VMware is still adding functions without any attention to operational details.  Take the Instant Cloning, for example - no CLI support (so I can't script publishing a new image), and images aren't treated as top-level objects so you have to go into each pool to make a change.  For now there are fun things to play with, but it's just not really usable/scalable.  Sad   Of the laundry list of bugs and feature requests I gave to VMware 2 years ago, which prompted in person meetings with VPs, etc, I think probably less than 10% have been implemented.  Basic stuff like sort orders (session lengths), multi-select session logoff, tracking client versions - nothing!
Following up, opened a SR. Seeing in App Vol Manager system messages "failed to mount [stack]", but not much more than that. Did I miss a release note that said App Volumes doesn't work wit... See more...
Following up, opened a SR. Seeing in App Vol Manager system messages "failed to mount [stack]", but not much more than that. Did I miss a release note that said App Volumes doesn't work with Horizon Instant Clones?
I took a working VM we've used for our linked clone pools, updated the agent and made the change to instant clone, nothing else, and now no stacks attach at login (user based assignments, 2.10.0)... See more...
I took a working VM we've used for our linked clone pools, updated the agent and made the change to instant clone, nothing else, and now no stacks attach at login (user based assignments, 2.10.0). As a final test I removed the AppVol agent, Horizon agent and VM tools, rebooting after each, reinstalled them all in the reverse order, rebooting after each, recomposed (published) and no change - no stacks attach. Anyone else?