UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0

Steps to reproduce the problem:
1. Spin up linked clone
2. Assign Chrome AppVolume (packaged separately from the OS)
3. Login
4. Open Chrome
5. Install Extension
6. "COULD_NOT_GET_TEMP_DIRECTORY" error appears

What is the expected behavior?
Installation of extension without complaining.

What went wrong?
This is similar to the following: https://bugs.chromium.org/p/chromium/issues/detail?id=413889

At this point application layering is gaining a lot of traction in business, so the need to be able to "roam Chrome" is becoming a must. I realize you can use an authenticated account and roam these things through Google, but in an effort to simplify user configuration within the model of application virtualization, this needs to be a setting that we can configure as engineers.

As it stands currently, because Chrome downloads/unpackages to the TMP defined variable, in an environment that is virtualized at application layer, in addition to OS layer, I cannot release Chrome as a managed application to our end users. 

Is there any way to modify this somehow? This creates a much larger management point for this application, as it would need to be part of the base image to not be affected by this.

WebStore page: 

Did this work before? No 

Chrome version: 50.0.2661.87 m  Channel: stable
OS Version: 10.0
Flash Version: 22.0.0.192

Virtualization is evolving. This needs to catch up.