Documentation discrepancy about Windows and SQL supported versions

[caddo]

Hi,

I'm writing documentation for a customer about supported scenarios with App Volumes but there are some gray areas and they are not minor ones.

In the VMware Horizon View App Volumes Deployment Guide it's clearly stated that the following are supported:

App Volumes Manager database: SQL 2008 R2 or 2012 standard and above for production

App Volumes agent: Windows 7

The User Guide states:

Important: You must install a VMware App Volumes Agent in a Windows 7 64 or 32 bit, Windows 8, or Windows Server 2008 R2 virtual machine. Please refer to Critical Initial Configuration for more information.

SQL Express 2008 (local)

SQL Server 2008 (remote)

The release notes states:

Windows 7 32/64-bit for VDI

Windows 2008 R2 for Published Applications

Windows 2008 R2 for Server VDI

I have to say that I am VERY confused about what platforms are supported and what not in all when it comes to SQL support and OS supported for the Agent.

Can someone please make a semi-official statement to help me out?

Thank you

[VUTiger]

I phrased this exact same question with exact same sources to support.

My primary goal was SQL 2012 and Server 2012 R2 as the platforms of choice for App Volumes.

As of 2.6 both SQL 2012 and Server 2012 R2 are supported platforms for App Volumes Manager

Past documentation states SQL 2008 and Server 2008 as supported platforms.

As for as Agent install it looks like Windows 7 (32/64) and Server 2008 R2 for VDI and RDSH.

As per latest Documentation: https://www.vmware.com/pdf/app-volumes-26-users-guide.pdf

or

https://www.vmware.com/support/appvolumes/doc/app-volumes-26-release-notes.html

Any other OS outside of that should be taken up with VMware support (WIndows 8 or 8.1, etc.).

[caddo]

VUTiger,

thank you for your reply.

I checked the docs again but even in version 2.6 I can't find any mention about SQL 2012 or 2012 R2, it actually still states that only SQL 2008 is supported.

Event the 2.6 release notes talk only about SQL 2008.

Can you point me where you foind this information? Or did it come from the support?

[Ray_handels]

Just for the record. We did install the database on an SQL 2012 R2 database and installed Appvolumes Manager on a 2012R2 server and works like a charm.

[caddo]

As far as my testing environment goes I did the same and I know that it works, just like I can tell you that it work well with Windows 8.1 too (didn't test Writable Volumes).

One thing is what works and another is what VMware supports.

Thank you for your contribution anyway.

[R_Scheer]

Here is an excerpt from a support mail:

Hello Ronald,

Thank you for your support request.

I can see that you are having problems with App Volumes after upgrading to version 2.6

...

Also, on another note, you mention that you are using SQL 2012 SP2.

As per the Vmware App Volumes 2.6 Release notes, I can see that this version of SQL is not supported.

https://www.vmware.com/support/appvolumes/doc/app-volumes-26-release-notes.html

Only SQL Server / Express 2008 is listed as supported.

...

[JaceJ]

We also have our App Volumes setup on SQL server 2012 and it works though we haven't updated to 2.6 quite yet as I'm waiting for some firewall rules to be updated for a second load balanced server.

Can the vmware guys comment when this will be supported officially?

[VUTiger]

https://www.vmware.com/pdf/app-volumes-26-users-guide.pdf

Page 10 it clearly states for App Volumes Manager Windows 2012 R2 is listed supported OS.

http://www.vmware.com/files/pdf/techpaper/vmware-horizon-view-app-volumes-deployment-guide.pdf

Page 16 states:

App Volumes Manager database •

SQL Express 2008 R2 supported for testing/non-production •

SQL 2008 R2 or 2012 standard and above for production

[JaceJ]

Problem is this is still a documentation discrepancy as the first document you linked only shows SQL 2008 as supported and no mention of SQL 2012

[VUTiger]

Sure, we all acknowledge that.

I was pointing him to semi-official documentation on SQL 2012 and Server 2012 Support published via VMware.

We are deployed and using it and it works, there are cobbled together pieces of official VMware documentation stating its supported.

VMware needs to publish official statement about that, until then its "technically" supported and working in multiple environments on 2012.

I think this is answered and take a ways are acknowledged