Rainmeter is by design not "secure" enough to be used in that environment. The file is actually a modified zip file, with the addition of certain metadata that is used to verify the integrity of the. The package file is created in the 'Rainmeter Skin Installer' format, with the extension. Just my personal view, but any System Admin in a company that even ALLOWED Rainmeter to be installed on company computers should be frog-marched out by security, clutching their cardboard box with their pitiful personal possessions. The Skin Packager is used to create a 'package' file that contains all of the files needed to install a skin in Rainmeter. You can't ever enforce that any particular skin be run for instance. You simply can't lock down Rainmeter for a particular user. Any user can, and must be able to, change that SkinPath option right back to whatever they want, and can load or unload any skin in the Skins folder. I caution that Rainmeter is not designed, on purpose, to be "locked down" and used in a shared, corporate environment. This folder doesn't have to be writable by any of the users. You simply have to change the SkinPath option in the section of Rainmeter.ini for each and every user, to the new desired path for the skins. The skins on the other hand, can be in any folder, one you might share between users. Any change they make, moving a skin, loading or unloading a skin, changing options like "Keep on screen" etc. This will be true with a "portable" install as well, which will not work well with multiple users. The %APPDATA% folder where Rainmeter.ini and other general files related to Rainmeter MUST be in a "writable" location for the local user running Rainmeter.
0 kommentar(er)
