Created a new appstack, hit provision and selected my provisioning machine. I don't get the popup letting me know to begin. The log seems like everything goes fine, but I do see what may be errors with "failed to create metafile directory"
[2019-01-31 21:29:30.667 UTC] [svservice:P1368:T2176] "\\?\Volume{4e05e36a-0000-0000-0000-100000000000}\" mounted at "\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\"
[2019-01-31 21:29:30.667 UTC] [svservice:P1368:T2176] Detected volume for provisioning. Path: \Device\HarddiskVolume3 GUID: {4e05e36a-0000-0000-0000-100000000000}
[2019-01-31 21:29:30.667 UTC] [svservice:P1368:T2176] Checking if disk size has changed for volume \\?\Volume{4e05e36a-0000-0000-0000-100000000000}
[2019-01-31 21:29:30.667 UTC] [svservice:P1368:T2176] Volume "{4e05e36a-0000-0000-0000-100000000000}" partition 21471690752 bytes, disk size 21474836480 bytes (delta 3145728)
[2019-01-31 21:29:30.667 UTC] [svservice:P1368:T2176] Checking if profile C:\Users\username for SID S-1-5-21-823518204-1788223648-1177238915-35190 should be deleted
[2019-01-31 21:29:30.667 UTC] [svservice:P1368:T2176] WorkerShouldDeleteLocalProfile returned FALSE
[2019-01-31 21:29:30.667 UTC] [svservice:P1368:T2176] PreCheckVolume: Volume \Device\HarddiskVolume3 checking
[2019-01-31 21:29:30.667 UTC] [svservice:P1368:T2176] PreCheckVolume: Volume free space is 21344546816 bytes and total space is 21471686656 bytes
[2019-01-31 21:29:30.683 UTC] [svservice:P1368:T2176] Read registry value VolAttachMessageOn (value is 0)
[2019-01-31 21:29:30.683 UTC] [svservice:P1368:T2176] HttpQueryNewPolicyFiles: called
[2019-01-31 21:29:30.683 UTC] [svservice:P1368:T2176] Checking new policy files
[2019-01-31 21:29:30.683 UTC] [svservice:P1368:T2176] Initializing HTTP connection
[2019-01-31 21:29:30.683 UTC] [svservice:P1368:T2176] Choosing a manager out of 1 configured manager(s)
[2019-01-31 21:29:30.683 UTC] [svservice:P1368:T2176] IsDomainJoinedComputer: NetGetJoinInformation() success, domain name REDACTED and type is 3
[2019-01-31 21:29:30.683 UTC] [svservice:P1368:T2176] QueryNewPolicyFiles URL: /update-volume-files?name=svservice&status=0&uuid=42086d9e-3b1b-feb3-dbdf-62ce53279c89&osver=10.0.17134&sp=0.0&suite=256&product=1&arch=9&proc=4&agentver=2.15.0.23U&domain=REDACTED&workstation=VCAPT-A001&volver=2.15.0.56&freebytes=21344546816&totalbytes=21471686656&ip=10.150.34.16&time=2019-01-31%2021:29:30.683%20UTC&machinesid=S-1-5-21-235881110-1711006267-1648827422
[2019-01-31 21:29:30.683 UTC] [svservice:P1368:T2176] [0] Connecting to serverfqdn:443 using HTTPS (attempt 1)
[2019-01-31 21:29:30.839 UTC] [svservice:P1368:T2176] WinHttpSendRequestWithSSLCertValidation: SSL Certificate validation succeeded.
[2019-01-31 21:29:30.839 UTC] [svservice:P1368:T2176] HttpReadAllAvailableData: Error 0 in WinHttpQueryDataAvailable: dwSize 0
[2019-01-31 21:29:30.839 UTC] [svservice:P1368:T2176] Manager status 200
[2019-01-31 21:29:30.839 UTC] [svservice:P1368:T2176] HttpQueryNewPolicyFiles: HttpInitializeRequest succeded. Manager status code = 200
[2019-01-31 21:29:30.839 UTC] [svservice:P1368:T2176] HttpQueryNewPolicyFilesManager returned empty response
.[2019-01-31 21:29:30.839 UTC] [svservice:P1368:T2176] HttpQueryNewPolicyFiles: succeeded
[2019-01-31 21:29:30.839 UTC] [svservice:P1368:T2176] CollectBaseImageInfo: %systemdrive%="C:"
[2019-01-31 21:29:30.902 UTC] [svservice:P1368:T2176] Unable to create directory "\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\METADATA": error 19
[2019-01-31 21:29:30.902 UTC] [svservice:P1368:T2176] PreAnalysisIconsLinks: failed to create metafile directory "\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\METADATA" error 2!
[2019-01-31 21:29:30.902 UTC] [svservice:P1368:T2176] Unable to create directory "\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\METADATA": error 19
[2019-01-31 21:29:30.902 UTC] [svservice:P1368:T2176] PreAnalysisInstalledApps: failed to create metafile directory "\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\METADATA" error 2!
[2019-01-31 21:29:30.902 UTC] [svservice:P1368:T2176] Checking for scripts on "\Device\HarddiskVolume3" (event prestartup)
[2019-01-31 21:29:30.902 UTC] [svservice:P1368:T2176] RunScript: Launching "\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\prestartup.bat" (event prestartup, CreationFlag 0x08000020, wait -1 ms)
[2019-01-31 21:29:30.917 UTC] [svservice:P1368:T2176] Successfully launched: \SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\prestartup.bat (wait -1 ms)
[2019-01-31 21:29:31.027 UTC] [svservice:P1368:T2176] Finished waiting for "\SnapVolumesTemp\MountPoints\{4e05e36a-0000-0000-0000-100000000000}\prestartup.bat" (WaitStatus 0, ExitCode 1)
[2019-01-31 21:29:31.027 UTC] [svservice:P1368:T2176] All volumes attached, processing...
[2019-01-31 21:29:31.027 UTC] [svservice:P1368:T2176] Sending reply to SVCMD_ID_NEW_VOLUME_PRE (Message 35, Size 24)
The user doing the provisioning does it have local admin rights? Does it happen just with this new one, or can you update older ones?
I have admin rights, and this is a new environment with 2.14 and this is the first appstack.
are you using domain accounts or local accounts?
Domain, per the logs you will see that.
Try creating a local user, and add it to the local administrators group, using domain users causes problems. I
Nope. I'm pretty sure the idea is to have this on the domain and installing it as close to a true VDI as possible though, so I've always done it with my desktop admin account.
If you use a domain account, that can get captured in app stacks sometimes, and when your logged in you will see. Look at this
App Volumes – Blocking user logon while waiting | Virtually Virtuoso
its why its a good idea to use local accounts, or at least one that is dedicated for provisioning that won't be logged in.
I've made probably a few hundred of these over the last couple years, and almost always the reason the provisioning message doesn't come up is because the provision user doesn't have local admin rights. What I do is copy the parent image uninstall all vdi agents other then the appvolumes agent, add a local admin, add the local admin user to the local administrators group and thats it. Your getting alot of "unable to create directory" messages in the log as well, which suggest the user doesn't have permission.
Giving it a try right now with a brand new local admin.
Same error message. I'm going to open a ticket with support on this one, I can't wrap my head around it.
I did this just find in 2.13, had a little under 30 app stacks. Can't wrap my head around this.
Did you try readding the template disk? It might be a corrupt template disk that is holding you back from creating a new appstack.
When you updated to 2.14 did you upload the template disks, I'm Ray_Handels may be on to something. I'd try uploading them again to see if that helps
I'll try it, but they were deployed during install, I see the templates there, and if I add a drive letter to the template mounted to the VM I can see all the files intact, so I did not suspect anything was wrong with the templates.
No luck for me guys, will continue to hack at this.