In the future, I will code this so it will add to the XML instead of merely over-writing and modifying some existing XML nodes. This isn't THE most robust thing out there yet - for example, if a person wanted to add an account to an already existing Pidgin setup, this script will remove any prior settings from other Pidgin IM providers (i.e. Note that you may need to enable these manually - unless you've configured it already and it has been stored in prefs.xml. the script copies this file into the user's account folder and makes it a framework by which to work with for the rest of the script.Ĭopy any plugins you wish to deploy to the client (defaults to Pidgin path\plugins) into the 'plugins' subfolder where your script resides. This will be used if Pidgin is installed but no XMPP account has been set up yet - i.e. NOTE that you will want to clean up the accounts.xml file before using it as a template. **** Clean up your accounts.xml template file **** x:\scriptfolder\files\prefs.xml, x:\scriptfolder\files\accounts.xml purple folder, copy 'prefs.xml' and 'accounts.xml' to the 'files' folder underneath where your script resides. you should now see x:\scriptfolder\files\certificatesįrom the main. purple folder and copy the 'certificates' folder to the 'files' subfolder where your script resides. **** Copy the connection certificates from your profile location to your scriptfolder ****įrom a working system that has already been set up with Pidgin and your XMPP server, you will want to find the certificates folder from your profile.īrowse into the. The general account setup is saved in 'accounts.xml.' Overall client preferences are stored in 'prefs.xml.'
Windows Vista/7: C:\Users\username\appdata\Roaming\.purple Windows XP: c:\documents and settings\username\application data\.purple NOTE: Where the Pidgin account profile is stored: Note that this script doesn't yet copy over custom (non-native installed) emoticons, sounds, themes, etc. Select the plugins you wish to use, configure settings etc.
On a workstation, install and configure Pidgin as you would for your users. **** Making the account template XML **** In the same folder where this script (we'll call it "scriptfolder") is stored, mimic the following structure * sConnectionSecurity: the authentication encryption scheme for the connection. * iPort: the connection port for the chat server * sDomain: the XMPP domain of your chat server * sFileTransferProxy: the FQN or IP address of the server acting as your file transfer proxy * sServerName: the FQN or IP address of your XMPP server VBS file extension.Įdit the script, adjust the variables to reflect your server and connection settings. This has been fully tested with Pidgin 2.10 - but I suspect it would work with some prior (but recent) versions as well.Ĭopy the script text into a new file in your favorite text editor, save with a. * The 'Resource' for the connection will be set to their computer name. * Logon account name will be the same as their Windows logon account. The script will configure the following options: * You have a plugin or two that you wish to deploy to your clients at the time of account creation
* You use Pidgin in your environment and need a way to silently set up an account for your users without any interaction * You have a Windows domain and are using LDAP to authenticate your users Just make sure Pidgin is closed when this is run. You can use this script to execute after the Pidgin install (or at Windows logon to configure an XMPP account for a local server. This script is intended to help automate account setups for Openfire (XMPP) chat server + Pidgin implementations in a corporate network using Windows LDAP authentication.