Hello,
It seems that is it is not possible to assign appstacks to users when there are already appstacks assigned to the computer a user is logging on to.
This is what the System Messages log is showing:
Skipping volumes for "User" because "Computer" already has volumes.
Is this correct and is this a limitation of Appvolumes? Will this be changed in a future version?
This is actually a safety catch. The reason it is done is because of a user writable volume. These volumes must be attached first and as part of a login process. So if there is a machine based volume it will behave in ways similair to a writable volume and there is potential for unexpected behavior. This safety check will be refined over time to allow for that use case. It is not a technical limitation it that it can work but is limited to protect the user from themselves ![]()
This is actually a safety catch. The reason it is done is because of a user writable volume. These volumes must be attached first and as part of a login process. So if there is a machine based volume it will behave in ways similair to a writable volume and there is potential for unexpected behavior. This safety check will be refined over time to allow for that use case. It is not a technical limitation it that it can work but is limited to protect the user from themselves ![]()
