sw-deploy wrote: ↑July 15th, 2024, 8:05 am
Thanks for the quick response.
In the past, all worked fine.
But software changes, so is it.
We installed rainmeter in the program files to ensure, that no user could modify the skins / layout.
And that rainmeter is working when a new user logged in.
If the normal installation will place the files in the users appdata (not tested yet), how could we get this two points covered?
First, Rainmeter is intentionally and by design made for the exact opposite of what you want. It's meant to "give control to the user" to design his desktop as desired. It's also not a software with security features meant to restrict the user ability to change his skins or layout. In other words, if you're looking for this, such a solution must come from outside Rainmeter.
In my opinion, one way to solve your 2nd point could be to duplicate the settings folder (C:\Users\[User]\AppData\Roaming\Rainmeter) and the parent of the skins folder (C:\Users\[User]\Documents\Rainmeter) for every user account, so that the same layout and skins (even though technically different files) would be used / loaded irrespective of the user being logged in. By the way, the skins folder can actually be changed / relocated by editing the Rainmeter.ini file.
As for your 1st point, that's more difficult. Apart from designing a Windows policy or using some other software to write protect the relevant Rainmeter folders / files and your startup sequence to prevent modification and ensure that no user can modify the skins / layout or avoid loading them at startup, I personally don't see many other possibilities (if any) to achieve what you want. I might be wrong, of course, but it's unlikely.
As a rather "extreme" and probably unfeasible measure, if you're proficient in C++, you could just fork Rainmeter from GitHub and set the relevant folders as desired, for your 2nd point. That being said, if you try to approach your 1st point in a similar manner, you'd still need some way to "block" the modification of skin or layout files by the user...