File Copy with MSI push - not working
Dan Hoffmann
I am pushing a software phone client but I also need to update a config file after the install.
I have both steps in the package but the config file copy didn't work. it did copy over, but the program didn't work until I re-copied the file manually. (related or not? I'm not sure)
How do the steps work? All at once, or step 1 finishes, then kicks off step 2?
Can I set a delay, or should I not have the config copy in the same package?
Thanks!
Dan
0
Comments
Hi Dan,
Is the original config file that you're copying to the target created during the installation or after the program is launched?
The original config is created as part of the install.
You said that the file copy worked but you had to recopy it over. Did something happen to the config file you copied originally or did it get overwritten? Are you using the file copy step in Deploy and did you check the box to overwrite existing files?
Not to be the powershell guy, but I'm gonna be the powershell guy:
Start-Process "msiexec.exe" -ArgumentList '/i', 'installer.msi', 'any', 'other', 'switches'
Copy-Item -Path /source/here -Destination /path/here -Force
Create a new package with the ps1 file attached to it, and have the config file in the same location as the ps1 file you want to run on the target machine. I think that'll do it.
ALTERNATIVELY;
Create a two-step package. First Step: Install your package using whatever arguments you need to pass it
Step Two: File-Copy. Place a config file from a known working installation in the same directory you placed the installer file in your PDQ Repo. Make sure you have "Overwrite Existing files" checked on the File-Copy step.
That ought to do it.
Yes, I am using the file copy step as my Step2.
My 'issue' may not even be related to this, but I don't know how the steps work which is why I posted that question part.
Once the client is installed, when you try to login, it connects to the server through the config settings. The default config does not have the server info listed.In my test deployment, I was unable to connect to the server. I recopied the config and got right in.
Sorry - yes I marked the file to overwrite.
Sure. Sorry for the confusion then! Steps work as you would expect. Step 1 runs, if all goes well, it moves to step 2, and so on and so forth until it either A) completes, or B) errors.
May I ask, what Run As option are you running?
Great. Run as Deploy User - which is a network admin account
If the steps wait, then I may have run into a fluke then with my login.