gpeck29adv's Posts

We've been able to successfully put SQL Server Management Studio 2014 (as well as Visual Studio 2010 and Visual Studio 2005) into AppStacks. Here's what we found: Use a App Volumes capturing ... See more...
We've been able to successfully put SQL Server Management Studio 2014 (as well as Visual Studio 2010 and Visual Studio 2005) into AppStacks. Here's what we found: Use a App Volumes capturing machine that is the SAME version as the image used for the base image. To clarify, we have the base image for our pool with a number of Snapshots. At one point we fought with this, and even though the provisioning machine was a clone of the base image, it was not the same snapshot. The provisioning machine was version 1.1 while the pool was using version 1.4 of snapshots. I didn't think this would matter....but it did. I rebuilt our provisioning machine(s) with the same version as the current pool, and the AppStack worked. I then tested with deploying a new snapshot to the pool, and the AppStack worked. Lesson learned: Just because it's a clone, make sure the install is done on the SAME snapshot version as the pool. The pool can be progressed from that point. DON'T CHANGE THE SID! We were deploying 4 provisioning machines so that 2 people could deploy 2 AppStacks at a time. Things tested fine, and even though we were on the same snapshot version, we still got license not valid messages once we added the AppStack to a pool desktop. Ugh! Then we realized that morning to deploy 4 of the systems, we used the Windows 7 customization with the box checked to change the SID. Once I redeployed and manually renamed the machines without changing the SID, and recaptured the AppStack...things worked. Best I can figure is that SQL Server Management Studio 2014 (and VS2005 and VS2010) use the SID and sum date/time value to create the license in the software. If they don't match, you get the license messages. This is what has worked for us repeatedly. We are using App Volumes 2.9. FYI: VS2010 needs to be at SP1 if you are going to put it together with SQL Server Manager 2014.
I updated my App Volumes capture machines and redeployed Visual Studio 2010 and it worked without any license errors. Thank You! Guess this shows the importance of keeping the App Volume Build ma... See more...
I updated my App Volumes capture machines and redeployed Visual Studio 2010 and it worked without any license errors. Thank You! Guess this shows the importance of keeping the App Volume Build machines at the same level as the base image.
We currently are capturing on what is the base image. Maybe I'll rebuild my capture machines off the base image JUST to make sure. I was thinking there might be registry entries that don't get ca... See more...
We currently are capturing on what is the base image. Maybe I'll rebuild my capture machines off the base image JUST to make sure. I was thinking there might be registry entries that don't get captured during the process is this a possibility?
Stefan, You most likely will need some sort of profile management. We are using AppVolumes with non-persistent VM's that refresh after log off. Our Lync is installed, not in an AppStack, but in ... See more...
Stefan, You most likely will need some sort of profile management. We are using AppVolumes with non-persistent VM's that refresh after log off. Our Lync is installed, not in an AppStack, but in the base image with Office, but the refresh of the desktop will cause the reconfiguration. We overcome that with Liquidware Labs ProfileUnity.
We are attempting to put Visual Studio 2005 and Visual Studio 2010 into an AppStack. All works with the original install and the program opens fine. Close up the AppStack and assign to a new user... See more...
We are attempting to put Visual Studio 2005 and Visual Studio 2010 into an AppStack. All works with the original install and the program opens fine. Close up the AppStack and assign to a new user for testing and both version open a pop up message stating "Invalid License Data. Reinstall is required". Has anybody overcame this issue?
We are currently updating our implemenation of AppVolumes and have successfully virtualized FileZilla in our department appstack for IT. Upon installation I mounted the stack and tested filezil... See more...
We are currently updating our implemenation of AppVolumes and have successfully virtualized FileZilla in our department appstack for IT. Upon installation I mounted the stack and tested filezilla to the ftpsite.vmware.com address and was able to connect with no issues. We are currently still on AppVolumes 2.9 with plans to move to 2.10 in January.  Nothing special was done for FileZilla to work. I did install all apps with "Run as administrator".
Trying to configure App Volumes in a multiple domain environment, where the domain (DOMAIN1) that the App Volumes Managers are installed has a 2 way direct trust with the other domain (DOMAIN2). ... See more...
Trying to configure App Volumes in a multiple domain environment, where the domain (DOMAIN1) that the App Volumes Managers are installed has a 2 way direct trust with the other domain (DOMAIN2). Issue that we are having is when a user in DOMAIN2 logs into View, the AppStack isn't mounted. Setup AppStack (BASE_Applications_v1.0) is created and works for local users AppStack Group (G_APPVOL_Base_Apps) is created in DOMAIN1 AppStack is assigned to DOMAIN1\G_APPVOL_Base_Apps DOMAIN1\User1 added to the G_APPVOL_Base_Apps) group DOMAIN2\User2 added to the G_APPVOL_Base_Apps) group Domain1\User1 logs in without issue and gets AppStack loaded Domain2\User2 lobs in and AppStack is NOT loaded. MODIFIED SETUP Save as above, except: AppStack is assigned to DOMAIN2\User2 In Modified Setup, DOMAIN2\User2 gets the AppStack The goal is 1 group assignment, and users/groups added to that 1 group for AppStack assignment without regard to the domain of the user or group added to the group. LOG Information for User2 login in original setup: 2015-07-13 14:57:25 UTC] P2892R3496  INFO Started GET "/user-login?name=svservice&uuid=423a7f6e-d0e5-0628-a47e-45b1b0506998&status=0&osver=6.1.7601&sp=1.0&suite=256&product=1&arch=9&proc=2&agentver=2.9.0.839U&username=User2&domain=DOMAIN1&userdomain=DOMAIN2&workstation=COETEST002&machinesid=S-1-5-21-2519256555-1071686382-2677787016" for 127.0.0.1 at 2015-07-13 10:57:25 -0400 [2015-07-13 14:57:25 UTC] P2892R3496  INFO (NTLM) Authenticating URL "/user-login" [2015-07-13 14:57:25 UTC] P2892R3496  INFO (NTLM) Received NTLM authentication to /user-login (type 3) [2015-07-13 14:57:25 UTC] P2892R3496  INFO (NTLM) User: "User2" [2015-07-13 14:57:25 UTC] P2892R3496  INFO (NTLM) Workstation: "COETEST002" [2015-07-13 14:57:25 UTC] P2892R3496  INFO (NTLM) Domain: "DOMAIN2" [2015-07-13 14:57:25 UTC] P2892R3496  INFO (NTLM) Authenticating user User2 on domain DOMAIN2 [2015-07-13 14:57:25 UTC] P2892R3496  INFO      RADIR: Connection to AD domain2.com succeeded - Took 109ms [2015-07-13 14:57:25 UTC] P2892R3496  INFO Processing by Agent::UsersController#login as HTML [2015-07-13 14:57:25 UTC] P2892R3496  INFO   Parameters: {"name"=>"svservice", "uuid"=>"423a7f6e-d0e5-0628-a47e-45b1b0506998", "status"=>"0", "osver"=>"6.1.7601", "sp"=>"1.0", "suite"=>"256", "product"=>"1", "arch"=>"9", "proc"=>"2", "agentver"=>"2.9.0.839U", "username"=>"User2", "domain"=>"DOMAIN1", "userdomain"=>"DOMAIN2", "workstation"=>"COETEST002", "machinesid"=>"S-1-5-21-2519256555-1071686382-2677787016"} [2015-07-13 14:57:25 UTC] P2892R3496  INFO        Cvo: Manager version: "2.9.0.23" - Running as “SRVAPPVOL01$@DOMAIN1" [2015-07-13 14:57:25 UTC] P2892R3496  INFO    Manager: User Login: upn=DOMAIN2\User2 account=User2 (domain) [2015-07-13 14:57:25 UTC] P2892R3496  INFO        Cvo: Loaded existing record for "Computer <DOMAIN1\COETEST002$>" [2015-07-13 14:57:25 UTC] P2892R3496  INFO        Cvo: Found existing user "User <DOMAIN2\User2>" [2015-07-13 14:57:25 UTC] P2892R3496  INFO        Cvo: Re-using "#<Cvo::Hypervisor::VcentersAdapter:0x517d1d8>" - 435806 secs old - Not yet connected [2015-07-13 14:57:25 UTC] P2892R3496  INFO   RvSphere: Error while pinging VMware connection to root@esx_host1.DOMAIN1.local: end of file reached [2015-07-13 14:57:25 UTC] P2892R3496  INFO        Cvo: Unable to ping "#<Cvo::Hypervisor::EsxAdapter:0x50c14e0>" - 7249 secs old - Ping took 31ms [2015-07-13 14:57:25 UTC] P2892R3496  INFO        Cvo: Connecting directly to "esx_host1.DOMAIN1.local" for "Machine <coetest002> (503a4f5e-8c77-9c64-e6e9-4e883bea7bba)" [2015-07-13 14:57:25 UTC] P2892R3496  INFO   RvSphere: Connection to VMware root@esx_host1.DOMAIN1.local succeeded - Took 94ms [2015-07-13 14:57:25 UTC] P2892R3496  INFO        Cvo: Preparing for login of "User <DOMAIN2\User2>" - previous logins: 3, last login: 2015-07-10 15:37:27 UTC [2015-07-13 14:57:25 UTC] P2892R3496  INFO        Cvo: Saved login of "User <DOMAIN2\User2>" into "Computer <DOMAIN1\COETEST002$>" [2015-07-13 14:57:26 UTC] P2892R3496  INFO        Cvo: Attaching 0 volumes for "User <DOMAIN2\User2>" [2015-07-13 14:57:26 UTC] P2892R3496  INFO   Rendered text template (0.0ms) [2015-07-13 14:57:26 UTC] P2892R3496  INFO Completed 200 OK in 514.8ms (Views: 0.0ms | ActiveRecord: 109.2ms) [2015-07-13 14:57:26 UTC] P2892R3496  INFO Log Info from Modified Setup [2015-07-13 16:14:31 UTC] P2364R3585  INFO Started GET "/view_broker/sessions/start?vcenter_url=https://vcenter_server.DOMAIN1.local:443/sdk&server_dn=cn=934b3370-c149-4d1a-8787-a2bca71c0bd6,ou=servers,dc=vdi,dc=vmware,dc=int&server_dns_name=coetest003.DOMAIN1.local&rdsh=false&vm_ref=vm-7004&username=User2&user_domain=DOMAIN2&guid=a5619084-92f2-4159-a1f7-c0860295f994&av_broker_version=2.6.0.6" for 127.0.0.1 at 2015-07-13 12:14:31 -0400 [2015-07-13 16:14:31 UTC] P2364R3585  INFO Processing by ViewBroker::SessionsController#start as HTML [2015-07-13 16:14:31 UTC] P2364R3585  INFO   Parameters: {"vcenter_url"=>"https://vcenter_server.DOMAIN1.local:443/sdk", "server_dn"=>"cn=934b3370-c149-4d1a-8787-a2bca71c0bd6,ou=servers,dc=vdi,dc=vmware,dc=int", "server_dns_name"=>"coetest003.DOMAIN1.local", "rdsh"=>"false", "vm_ref"=>"vm-7004", "username"=>"User2", "user_domain"=>"DOMAIN2", "guid"=>"a5619084-92f2-4159-a1f7-c0860295f994", "av_broker_version"=>"2.6.0.6"} [2015-07-13 16:14:31 UTC] P2364R3585  INFO        Cvo: Manager version: "2.9.0.23" - Running as "APPVOL01$@DOMAIN1" [2015-07-13 16:14:31 UTC] P2364R3585  INFO    Manager: ViewBroker Session Start: vCenterURL: https://vcenter_server.DOMAIN1.local:443/sdk [2015-07-13 16:14:31 UTC] P2364R3585  INFO    Manager: Requested by true [2015-07-13 16:14:31 UTC] P2364R3585  INFO   RvSphere: Connection to VMware svc_vcenter_account@DOMAIN1.local@vcenter_server.DOMAIN1.local succeeded - Took 250ms [2015-07-13 16:14:31 UTC] P2364R3585  INFO        Cvo: Eliminating old session found during Session Start: [2015-07-13 16:14:31 UTC] P2364R3585  INFO        Cvo: ViewBroker <2dd20929-a03e-477e-8c80-cf8e330485e9> "" on "Computer <DOMAIN1\coetest003$>" (pending) [2015-07-13 16:14:31 UTC] P2364R3585  INFO        Cvo: Configuration has changed, disconnecting cached AD adapter from [2015-07-13 16:14:31 UTC] P2364R3585  INFO      RADIR: Connection to AD DOMAIN1.local succeeded - Took 109ms [2015-07-13 16:14:31 UTC] P2364R3585  INFO        Cvo: Found existing user "User <DOMAIN2\User2>" [2015-07-13 16:14:31 UTC] P2364R3585  INFO        Cvo: Using trust account “trust_user” to connect to "domain2.com" for "domain2.com" [2015-07-13 16:14:32 UTC] P2364R3585  INFO      RADIR: Connection to AD domain2.com succeeded - Took 109ms [2015-07-13 16:14:32 UTC] P2364R3585  INFO        Cvo: Re-using "#<Cvo::Hypervisor::VcentersAdapter:0x756ffa8>" - 504 secs old - Not yet connected [2015-07-13 16:14:32 UTC] P2364R3585  INFO   RvSphere: Connection to VMware svc_vcenter_account@DOMAIN1.local@vcenter_server.DOMAIN1.local succeeded - Took 250ms [2015-07-13 16:14:32 UTC] P2364R3585  INFO        Cvo: Attaching 1 volumes for "User <DOMAIN2\User2>" [2015-07-13 16:14:32 UTC] P2364R3585  INFO        Cvo: Mounting volumes for "User <DOMAIN2\User2>" to "Computer <DOMAIN1\coetest003$>" on "Windows Desktop OS" [2015-07-13 16:14:32 UTC] P2364R3585  INFO   RvSphere: Connection to VMware svc_vcenter_account@DOMAIN1.local@vcenter_server.DOMAIN1.local succeeded - Took 265ms [2015-07-13 16:14:33 UTC] P2364R3585  INFO        Cvo: Acquiring mount lock for "Machine <coetest003> (503a1d13-b431-0d6c-b5c5-2de1f5d13670)" - Currently: available [2015-07-13 16:14:33 UTC] P2364R3585  INFO   RvSphere: Connection to VMware svc_vcenter_account@DOMAIN1.local@vcenter_server.DOMAIN1.local succeeded - Took 265ms [2015-07-13 16:14:33 UTC] P2364R3585  INFO   RvSphere: Mounting 1 volume(s) in VM "coetest003" (503a1d13-b431-0d6c-b5c5-2de1f5d13670) on VMware "svc_vcenter_account@DOMAIN1.local@vcenter_server.DOMAIN1.local" [2015-07-13 16:14:33 UTC] P2364R3585  INFO   RvSphere: Attaching read-only volume "[appvol01] cloudvolumes/apps/Applications_Base_v1.1.vmdk" to VM "coetest003" [2015-07-13 16:14:33 UTC] P2364R3585  INFO   RvSphere: Preparing to reconfigure VM  coetest003" (503a1d13-b431-0d6c-b5c5-2de1f5d13670) <running> [2015-07-13 16:14:35 UTC] P2364R3585  INFO        Cvo: Volume "Applications_Base_v1.1" now has 1 current attachment(s) and 5 total attachment(s) [2015-07-13 16:14:35 UTC] P2364R3585  INFO        Cvo: Successful mount actions for 1 volume(s) appended to response [2015-07-13 16:14:35 UTC] P2364R3585  INFO   Rendered text template (0.0ms) [2015-07-13 16:14:35 UTC] P2364R3585  INFO Completed 200 OK in 4040.5ms (Views: 0.0ms | ActiveRecord: 358.8ms)
I appreciate that a fix is coming; however, a month has past and I'm wondering...probably like others. When is this fix coming? You may think this isn't really necessary; but when you tie App ... See more...
I appreciate that a fix is coming; however, a month has past and I'm wondering...probably like others. When is this fix coming? You may think this isn't really necessary; but when you tie App Volumes writable disks and personal Management tools like ProfileUnity, it might be a bit more necessary. Currently I'm possibly experiencing both things running at the same time, and since the user installed apps volume (set for UIA and Profile) isn't there, the other tools is erroring out. It works fine when I don't save the profile on the UIA disk...but who wants to sit through a Windows local profile creation on every logon? Any updates would be great!
We are trying to assign App Volumes to users that are in an OU with an Asterisk in the name. When we do, the App Volume isn't mounted. I need to do further testing, but this seems like the issue.... See more...
We are trying to assign App Volumes to users that are in an OU with an Asterisk in the name. When we do, the App Volume isn't mounted. I need to do further testing, but this seems like the issue. I thought the AD was incorrect in using an asterisk in the name of an OU, but according to MS KB909264 the OU name is valid. OU names Allowed characters All characters are allowed, even extended characters. Is this an issue with App Volumes.
Jason, We are getting the attached heidi error. Agreed this needs to be put in the base image. I'm unfamiliar with the install, and the person that is working with me that is familiar with the i... See more...
Jason, We are getting the attached heidi error. Agreed this needs to be put in the base image. I'm unfamiliar with the install, and the person that is working with me that is familiar with the installs is also unfamiliar on how to de-couple the heidi install from the main product installation. Is there any documentation on how to install the heidi driver in the base image. We are looking at installing multiple versions of AutoCAD 12, 13, & 14. Is the suggested approach to this to put them into separate AppStacks or just use one stack? The users that get AutoCAD will get all three versions. Greg
Has anybody put AutoCAD in an app stack. It seems to work if I launch AutoCAD with the /nohardware option. The HEIDI drivers for the video card are causing an issue. Looking to if anybody has ove... See more...
Has anybody put AutoCAD in an app stack. It seems to work if I launch AutoCAD with the /nohardware option. The HEIDI drivers for the video card are causing an issue. Looking to if anybody has overcome this issue. I'm assuming that we need to install these drivers in the base image.