We are putting Windows 10 on our developer boxes, but for some reason, Harvest maps the user location to someplace on the network, which causes Harvest not to work. 

This can be mitigated by changing the following lines in the config.ini file in C:\Program Files\CA\SCM\configuration\ 

[email protected]/.cascm/configuration 
[email protected]/.cascm/workspace 

While logged in as admin, these correctly go to the C:\Users\<<username>> directory, but while logged in as a normal user, they go off to the network. 

I can hardcode these locations as such: 

osgi.configuration.area=C:/Projects/harvest/.cascm/configuration 
osgi.instance.area.default=C:/Projects/harvest/.cascm/workspace 

And it works. However, this means every user uses the same workspace, which isn’t ideal. 

I’ve tried to use the following instructions for Eclipse to code a variable in there, but I’m having issues: 

The Eclipse runtime options 

I end up with something like osgi.configuration.area= $LOCALAPPDATA$/.cascm/configuration, but when I open Harvest, it doesn’t substitute the $LOCALAPPDATA$ with the Windows environmental variable. 

What is the best way to resolve this?

CA Harvest SCM client v12.x and up
Windows platform

Something you can do to make the .cascm folder appear in an alternate location, specific for each user, is override the settings in the config.ini and workbench.ini files from the command prompt. So, for example, if you went to the "Properties" window for the Workbench shortcut on the desktop and replaced 

"C:\Program Files\CA\SCM\workbench.exe" 

with 

"C:\Program Files\CA\SCM\workbench.exe"-data c:/temp/%USERNAME%/.cascm/workspace -configuration c:/temp/%USERNAME%/.cascm/configuration -eclipse.keyring c:/temp/%USERNAME%/.cascm/keyring.txt

the .cascm folders for your users would wind up in the C:\Temp\<their userid> folder instead of C:\Users\<their userid> 
 
 

More information on command line options for Eclipse-based applications can be found here: The Eclipse runtime options