In a past post I talked about deploying 3cx windows client and customizing it via scripts. Mainly to have things like chat window pop up and other settings the same across all users. See thread here for that https://www.3cx.com/community/threa...ze-provision-and-deploy-the-3cx-client.47499/ One thing that was an issue was how do you get the .3cxconfig files to automatically deploy it without having to manually go through the console and click the "Config+" and save it. What if you had 300 users? Not possible right? Well below are the steps to automate it. There are some certain things that have to be done manually, but the bulk work is done via scripts or other. 1. Get the .3cxconfig files for all your users. To do this download Test Mail Server Tool at http://www.toolheap.com/test-mail-server-tool/ Run it on a pc on the same network of your 3cx server. Go into the 3cx server and change the SMTP server to that pc's IP address. Select the folder in Test Mail Server Tool you want the emails saved in. Go into the 3cx Console and select every extn and send that Welcome Email. You will get all those welcome emails in .eml format from the server tool. The good news is the extension number for each welcome email is the last 4 characters of the file. So 3cxProv_******_1100.eml is for extension 1100. So you have the Welcome Emails, now you need those config files. Go get UUD32win http://www.marks-lab.com/ This program extracts the config file as a .htm file. Once you have the .htm files, you need to rename them to end in .3cxconfig. If you want to deploy them using scripts and need them to be named the users login name, below is how I did it all at once. Basically used excel to make a big cmd that renamed all the files in the folder to the (username).3xcxconfig The interesting part was matching the extension with the username, again done in excel with the VLOOKUP function. Below are the main functions. If your not comfortable using excel, then this might not be for you. I'm sure you can script this another way, but this is how I did it. To get a list of the files to start with do "dir > files.txt" in the command prompt. Copy the file list and paste into excel Export your extensions from 3cx console so you have a list of everyone. I'd delete everything out of the spreadsheet but the usernames (their emails minus the @***) and their exten numbers. Now you just have to create a vlookup and match the username/ext with the file name based on the last 4 digits in the .html file. Then use the CONCATENATE function to modify the name and add the "ren" to the beginning so you can copy it all and run it as a cmd to rename all the files. Some functions and what i used them for in excel are remove junk in file name except exten.htm =RIGHT get rid of .htm =LEFT get the current file name and name I want it to be in a REN cmd =CONCATENATE("ren ",CHAR(34),E1,CHAR(34)," ",CHAR(34),D1,F1,CHAR(34)) And the main one Vlookup. This compares your column with exten and users you pulled out of 3cx to your column of file names from the welcome email. It then makes a new column you can reference of users names that are lined up with the extensions from the welcome email. A few CONCATENATE functions then get you to the command to rename the files to matching usernames based on extension. =VLOOKUP(A1,$B$1:$C$86,2,FALSE) example Now you have a bunch of (username).3xconfig files after renaming them using command prompt and pasting in the text you get from excel. Obviously secure these files, they contain 3cx login information for all your users. Put those in a shared path and now you can run scripts to automatically provision every pc on your network with the 3cx client. If a user has logged into the PC in the past and has a C:\Users\(username) folder, you can drop the proper 3cx files into their folder so when you login, 3cx launches with their extension, even if they never opened the Welcome Email on that pc before. I've made some changes to the script I originally used, the new one is below and is better. I had some issues with the past one in some situations and it wasn't as fast.