Invalid configuration for device ‘1’ or ‘0’

I had a tons of errors in vCenter in the recent tasks list when recomposing a pool:

Invalid configuration for device ‘0’
Invalid configuration for device ‘1’

After calls to Vmware support, which they couldn’t pinpoint the error, I sat and watched my VMs being created by composer.

My templates kept showing AppStack vdmks being added during the recompose process, and the pool would fail to publish.

I checked the AppVolumes assignments, and I guess name filtering wasn’t applied correct and was assigning the AppStacks to all the VMs in the OU. ┬áReassigning the AppStack with name filtering turned on resolved the issue.

Error on login either ‘-r’ or ‘-s’ must be specified


We recently upgraded to VMWare App Volumes 2.11 and had an issue on login to a Windows 7 VDI system where users were getting the following message:

“Error on login either ‘-r’ or ‘-s’ must be specified”

After submitting a ticket to VMware, the issue was with UEM 9.0 and the App Volumes 2.11 template file.


There is a switched built into the AppStacks script allvolattached_shellstart.bat. The call in the script is to use FlexEngine.exe -ra which is not used in UEM 9.0. You will need to adjust that to read FlexEngine.exe -UEMRefreshShortcuts for UEM 9.0.

For the existing AppStacks you can update the AppStack and make the changes during provisioning mode.

In Windows change to show hidden folders and hidden system folders. Browse to C:\SnapVolumesTemp\MountedDevices\ Open allvolattached_shellstart.bat with notepad and look for FlexEngine.exe -ra Change from -ra to -UEMRefreshShortcuts

Hope this helps you ­čÖé