Issue with Profiles after scripted install

[aninterestingconcept]

I have a script that identifies the GUID's of any installed openvpn application and removes them one at a time with a 30 second delay between loops using msiexec /x {GUID} /qn.
It then searches 4 key directories for *.ovpn files and deletes them if the exist.
C:\Users
C:\Program Files
C:\Program Files (x86)
C:\Windows\System32\config\systemprofile\appdata\

After that it installs the current bundled MSI from the server for the 3.2 client (openvpn-connect-3.2.0.1064_signed.msi) that I've already downloaded and installs using misexec /i C:\{path to my file}

My problem is that the bundled profile from the MSI installer does not come through and I get some previous profile on my new install.

What am I missing? How is that possible when I've already removed all clients and profiles from the system. Is there a different file type I'm missing? A registry entry (I searched and didn't find any) After the whole thing the only profiles I find are for the new server, but despite that, I still see the old profile and not the new one in my final install. According to the config.json in my test profiles appdata roaming directory it's in my appdata\roamin\openvpn Connect\profiles folder but when I look there are no profiles there...

Essentially I want to remove an old installer/profile msi from one server and replace it with a new installer/profile from a different open VPN server. I just keep getting the previous profile in the new install even after removing all the profiles... it makes no sense...

[Pippin]

Your topic moved because it's not about the Open Source Community version.

[aninterestingconcept]

Your topic moved because it's not about the Open Source Community version.

It does't fit that topic though, it's about scripting.
Also it is client side not server side.

[Pippin]

I agree but openvpn-connect-3.2.0.1064 is not open source.
However, since there is not really a better fit under the Commercial version it was put here.