This post is more than 5 years old
3 Posts
0
2381
January 12th, 2011 09:00
AD GPO Deployment and x64 support?
I'm reading from The Getting Started Guide, version 1.0.0.
Section 8 : Appendix 1 says:
For Windows, there are 32-bit and 64-bit MSI packages that can be installed locally on desktops, and there are also versions that can be installed on a network server and then launched remotely on the user desktops.
and the Section 8.2 : Deploying the local VDI Assessment Agent with AD GPO heading on p.39 says
This section describes how to use Group Policy to automatically distribute the locally installed VDI Assessment Agents to a large number of desktop machines.
but later in the section at the end of Step Three: Deploy the Software on p.46 it says
Disable the "Make this 32-bit x86 application available to Win64 machines" checkbox.
Is x64 client support available for AD GPO deployment? If not what is the recommended deploy mechanism for large numbers of x64 clients?
Thanks!
jasmine11
38 Posts
1
January 13th, 2011 08:00
Hi Jay
Thanks for your interests in Quest VDI Assessment solutions and pointing out above misleading information to us. x64 client support is avialable for AD GPO deployment. Currently there is only one msi package and the checkbox in question doesn't need to be disabled.
Thanks again
jasmine
jaywinks11
3 Posts
0
January 13th, 2011 14:00
Hey that is GREAT news. While we're on the subject, right there in that section of the doc, a few pages seem out-of-order. I don't have it right in front of me but I noticed some frames seemed out-of-sequence. If you folks are planning a rev. 1.1 of the document or tool you might want to review there and note both these things.
THANKS!
jaywinks11
3 Posts
0
February 3rd, 2011 13:00
Page 45, first caption (Enable Always Wait for Network at Computer Startup and Logon) and accompanying screenshot is right in the middle of the properties of the Software Installation Settings portion of the GPO. Possibly fine to put both settings in the same GPO, but the order of this caption/frame should be outside the current context. Picky, I know, but that's what makes good technical documentation : sadistic pedantry.
DELL-Hugh M
14 Posts
0
February 3rd, 2011 13:00
Hello Jay,
Yes, we'll be doing a v1.1 at some point and will be reviewing the docs. If you have a chance to confirm which frames are out of order, we'll make a note.
Thanks,
Hugh
Product Manager, VDI Assessment