Due to continual spamming, forum registrations are now by Invitation Only. Hopefully this will be only a temporary measure to combat spammers.
If you want an invitation contact forumapplication @ camstudio . org
Sorry for the inconvenience.
CamStudio 2.7 and corporate environments
2.7 has some great improvements, and I'm glad to see that significant progress is being made.
Unfortunately, it looks like some of the changes make it difficult or impossible to use Camstudio in a corporate network environment.
One change I'm not happy about is the new default save location for videos. Saving documents under program files has been frowned on for years, and in the latest Windows OS versions, especially in a corporate environment, it's very problematic. A limited user trying to record with CamStudio 2.7 sees what looks like a recording session starting up, but nothing actually happens, no video is recorded, and there's no error message to tell the user that there's a problem. It just silently fails to work, which has caused some serious frustration for some of my users until I figured out what was going on.
It's possible to work around this by changing the default location to one the user has access to, but that leads to my second problem: How can I deploy the program with customized default settings? Previously I could just deploy a customized INI file to the program folder. Now the individual users' settings are stored in the user's profile, which is fine, but the default settings they're based on seem to be hard-coded somewhere I can't identify.
Also the settings don't seem to recognize or make use of Windows environment variables. For example, I would expect to be able to use values like %LOCALAPPDATA% or %USERPROFILE% in the configuration, but these aren't recognized.
Am I just missing something? How are others handling these issues?