It sounds like that can be created by copying a config.xml from a user profile that is set up the way you want, but I can’t find how to set the plugin folder in the Notepad++ settings GUI, either. Other posts have mentioned a, where the plugin folder could be managed at deployment time, but I haven’t found the setting that moves the plugin folder.
I also am not a fan of portable installations they’re much more difficult to manage (for both installs and reporting) as a sysadmin than system-wide applications. A few posts have mentioned installing Notepad++ to ProgramData instead as a workaround, but I’d rather not put installs in there. It appears Notepad++ by default uses Program Files for both (with some things in the users %AppData%). Program Files is restricted to admins, but ProgramData can be accessed by users. It’s my understanding that Program Files should hold the static program files, and ProgramData is where user settings and files (like plugins) should go. I’m currently distributing Notepad++ using the exe installer with a /S this works fine for install, but it turns out users can’t install plugins because they live in Program Files. I’ve seen several posts that have pieces of the answer, but I haven’t found one that’s satisfactory (to me) yet.
I’m one of the Intune admins for my company, and I’m trying to determine if there’s a way to allow my users to install plugins.
0 kommentar(er)
