I am a new business customer and am astounded as to why this is still an "idea" and not an implemented solution? I am moving (trying to) 2.5tb to box to transition to more offsite servers for our company. I cannot dump it into box drive to sync as the MacintoshHD is too small. I tried ftp but ftp.box.com is horrifically slow. Box makes it tough for new customers to get up and running.

This limitation should be spelled out in the pre-sales blurb. Right now I will not be adding any more user seats and if there is no actual eta for implementation I will evaluate other options.

What is a realistic eta for this to be implemented in Drive? "not on roadmap" is not a solution.

Why does box support not seem to be aware of this? My ticket received a "we understand your issue and will get back to you" then nothing. Its taken me hours of researching the box forums to find out it cannot be done.

My University is forcing all users to switch from Box Sync to Box Drive. My Mac mini server has a small SSD and a large HDD. It would be really great to place the cache on the HDD!

+1 for adding this feature

+1 for this feature request. This feels like a serious weakness for box that wouldn't be too hard to address. Other competitor products let you do this without a problem.

If this feature were added could it improve performance when working with very large files?
I frequently cannot use Box to store files for ArcMap, where file sizes are often greater than 1GB.

Really? Not on the roadmap? It should be. as more and more users move away from hard disks to SSD's for O/S boot drive, having the Box Drive cache is really going to consume write cycles and lower the lifespan of said SSDs considerably. I only have hard drives in my system at the moment but after reboot the "C" drive is at 100% use for several minutes as Box re-syncs between me and the cloud. I can only imagine the effect on SSD drives. Not to mention the gross inconvenience of having to log out of Box each time I need to search for something on my "C" drive, having the search utility having to pour through every folder mapped to Box is a great waste of time if I don't The only workaround to this is to log out of Box, do my search, then log back in. Again wasting a lot of time. I grant Microsoft has a hand in this by largely forcing everything to default to being put on the "C" drive, but more options should be available, as we're long past the 1990's and much smaller hardware. Thanks for your consideration.

Not on current roadmap? This issue should be one of your priorities as not being able to change this is affecting a wide range of users and is also a security threat. In some organisations the network technicians and admins have the ability to remotely access C: drive without the knowledge of the user. If a user is logged into their personal Box account, their data can be accessed from anywhere within the organisation without their permission or even knowledge. Also in a lot of scenarios the space on C: drive is very limited whether it is because of hard drive space, partitioning or being used by software.
I recently moved to box because I thought that it is a secure platform but in my case any person in the organisation with a bit of knowledge will be able to browse through my data.
Luckly I did not pay for the subscription I was planning on getting.

This is critical. Systems shipping with smaller SSDs I need the ability for large file users (creatives, marketing production staff, etc.) to store their cache on a larger external array.

Changing the mount point does little good. Changing the cache location is key.

I really I need this "Change cache location" function for Box Drive.
I can not migrate from Box Sync to Box Drive without this feature.
I would like to change the cache location to d: drive that has very big space.

Is this ever going to happen? What a joke.

"Unfortunately, this feature is not on our current roadmap."

What. I just installed it on my brand-new Windows 10 machine that has a limited amount of SSD space. I ALWAYS move my sync folders to non-main drives to keep the main one free for software and typical Windows bloat. How is this not even on your roadmap????

Guess I'm not keeping Box Drive on my computer.

With the move to use SSDs for the boot drive, it is really easy for the cache to consume the storage. Being able to move the cache location would be very helpful.

I also want to use box drive on an external drive. It is annoying that it is only available on C:/

This should really really be a priority.

I need this "Change cache location" function, my C: drive is always lack of space,
PLEASE PLEASE PLEASE

This is not on your roadmap? This should have been the very first item in your roadmap!!!!!!!!!!!!!!! It's bad enough that Microsoft fills up my C drive with rubbish. Now I have a 100GB C Drive fighting with Box to store data while my 2TB D Drive is available for it.

Echo, echo, echo... I am constantly chasing space on my C: drive. I am unable to sync large files for offline use because I'm out of space. Please add the capability to maintain cache files on a configurable volume.

Echoing every other user in this thread, it's mind-boggling that Box Drive doesn't support storing data on other drives when EVERY OTHER PLATFORM has this as standard. Again echoing previous comments in this thread, it's quite common to have a smaller SSD for system files and a large HDD for storage, and I can't believe you didn't pick this up as a customer need. It should be on your roadmap, and I don't know why it wouldn't be.

Please add to Box Drive the ability to change where the data is stored. Changing the mount point ('install location') is not enough.

As many others have said in other threads, the need is to have the cached data be stored on a drive other than the User's folder. A typical reason is that there are 1 or more large external drives where the cached data could reside, but the internal SSD with the user's home folder is small.

With small SSD for OS and large files I'd like to save offline, the inability to select the location for Box data makes it unusable.