Howdy V,
I have not previously done exactly what you are asking, but have done some similar tasks.
We use VIPM Pro and a local repository to distribute packages not found in the public repositories; not only our internally developed packages.
First, using VI Package Builder's Destinations and Source File Settings pages you can easily include the file and specify where it is installed. Second, using the Custom Actions you can specify a VI to run Before or After the package install. Use the Generate VI button to create a template VI and save into your package project; I create a Custom Actions folder when needed. Edit this template VI to launch your package configuration file; I typically rename so I know its purpose without viewing. You can use the System Exec.vi and create a constant for the command line that will include the exact install path to the .vipc file location. And, if you're not comfortable with command lines, using Open a Document on Disk.vi is another option.
I'm uncertain of whether VIPM will have any issues launching a package configuration before or after a package install. However, testing this will be simple and you can include instructions for the end-users if the automation is unsuccessful.
NOTE: My suggestions are based upon a Windows OS install and will need modifications for MAC or Linux
Best wishes with finding a solution.
James