How can I set up OBS Studio and Stream Deck on one PC for multiple Windows users?

[Silly OBS Guy]

I want to distribute OBS Studio and Stream Deck, including their presets (the scenes created in OBS Studio, the Stream Deck profile file with scene switching, and the OBS plugin for Stream Deck), across multiple Windows profiles managed in the Active Directory. It's crucial that OBS Studio, Stream Deck, and their presets are installed on only one computer—the video conferencing machine (VC). These programs should not appear on the office computers of the Windows users, only on the VC machine. When a Windows user logs into the VC PC, OBS Studio should open automatically.

Why I want to distribute OBS Studio & Stream Deck with the preferences to the Windows profiles:

If I want to configure all the settings locally on the VC computer, I have to ask the Windows users for their passwords to gain access to their respective Windows profiles. It's understandable that not everyone wants to share their password for privacy reasons.

Here's everything I did at the local facility:

1. First, I imported the scene file into OBS Studio. After the import, all scene settings are displayed.
2. Next, I imported the profile file with the created scene transitions into Stream Deck. I also need to log into my Elgato account to download the OBS Studio plugin. Then the scene switching works on the Stream Deck terminal.

Is there an easier way?

I think you can set up software distribution using group policies. Is it also possible to program it in PowerShell? If so, please include PowerShell code in your replies.

Overview:

I know that's a lot of information. Here's an overview:

• OBS Studio (software + scene file) and Stream Deck (software + profile file + OBS plugin) should be accessible to every Windows user on the VC computer.
• OBS Studio and Stream Deck should not appear on the office computers, but only on the VC PC.
• OBS Studio should start automatically on the VC PC.

 

[koala]

OBS Studio isn't designed for a managed environment. There is no support for automated import and export of configurations, for example for a command line to automatically import some exported scene into the current configuration.

You can try to do do this yourself. Create a master config you adapt for every user by changing the configured user specific paths to the current user's paths.
All the config is in %appdata%\obs-studio. It's ascii text files, ini and json file format, and all paths within are absolute paths with "c:/users/<username>/...".
You can enumerate the master files and read them with the corresponding reader library in Powershell (ini file format, json format), modify any paths, and write the modified files to the user profile. You can do this in a login script when the user is logging in to your VC PC. Login scripts can be assigned to users and computers with group policy.