I don't see the options for this in the admin UI. Also when I unassign or assign an App Stack to a logged in user nothing happens until a log out/log in.
It would be nice to get a feature comparison between 3.0 and 2.10.
NO YOU CAN NOT. Please do not do this. You will corrupt the unified console and break everything. Only use it for writable management and logs that's it. Anything else will break AV3.
Why is it there if you can't use it?
This release has been a cluster so far. In the unified console you can't deploy a writable volume with out an application, the dashboard is useless, and the getting started wizard says things are required when they are not. Why have a unified console if when 1/2 of the "unified" features are in beta? The unified console should be beta because it is not feature complete. I appreciate all the work that has gone into this to get it to an appliance and trying to reduce the number of management consoles but this product is far from release ready. Where is the documentation about using the legacy UI for Writable management?
there isn't. I'm telling you because this is the communities page and trying to give a little more info. The supported way is to not use it at all... And yes it is not all there but we are working hard to get it there.
Jason - I really appreciate the posts you've made on this forum, as they've proven far far more helpful than the documentation. However, how did AV3 make it to GA in this state?
Missing functionality I can handle to an extent, but the amount of bugs and ways to break AV3 is staggering. Why has the ability to do something that will corrupt an install been left in? Why not have a cut down version of the old console with only the relevant parts available? Why isn't any of this properly documented? I'm sure lots of folk who don't read these forums have been tearing their hair out with AV3 more than we have (and I'm nearly bald).
I know VMware will get AV right again in future updates, but I'm seriously shocked that this was released as is. It's quite possibly the most disappointing major release from VMware that I can remember.
I'd like to echo the same concern as well as "alsmk2". I'm new to appvolumes but was somewhat familiar with the old interface as I played/demo'd around with it last years and really liked it. We're now trying to do POC with a small subset of our company with AV3 but this version seems to be a step backward from what I tested last year. Performance seems worse and I'm about to open my 3rd ticket with VMware. On AV2.9 I never had to do that or had the performance issue. Also quite surprised that VMware would put this out in GA. Is there any timetable on the first update for AV3. I feel I'm going to go back to 2.9 for now until that comes out.
IMO AV3 should be treated as a tech preview. I would have enjoyed it if I had understood I was trying it out to see what was coming. Instead I was extremely frustrated with trying to figure it out by trial and error thinking it was a true release. I have given up on it until there is a real release product in the future.
My imagination says that VMWare rushed this out to score some points somehow. Perhaps to beat Unidesk's 4.0 tech preview release... or something else similar. No way to really know this. Just my guess. I imagine development people and support people at VMware are thinking "Oh Crap!".
Not quite sure if this was noted for everyone else but i was well aware that this was a tech preview and should not be put into production in any way.
I even received a warning message when downloading the software in the My VMWare portal that this product should not be put into production.
That being said. I do believe they have their work cut out for them There are too many issues in the AV3 version that need to be fixed before it is even a bit production ready. Not only is configuration quite tedious you will need to have a migrate path form 2.x (which will be implemented as said on the forums). I do hope they change their view regarding writable volumes. The "old" way did fit much better to be honest because you would like to make that decision on a per user base, not a per application base. Looking at Appstacks, it's a different approach and you may or may not like it but it does do the job.
Well, I can't see anything on the product page or the announcement blog that hints that this is anything but good to go. I don't remember clearly that warning you refer to... but I don't doubt you. I expect I glossed over that. I still think VMware could (should!) be more transparent about the true status. I agree with your other observations.