Invoke-Command not working for remote installation

spiceuser-c1jq1 · 2022-01-27T16:17:34.000Z

I am currently trying to uninstall Office 2010 and install Office 2016 (Yes, 2016) on hundreds of computers. I have gone through the process of setting up an MSP and using a script someone made a while ago to auto install on a list of computers supplied. However, I can’t for the life of me get the invoke-command of calling the setup.exe and it actually work. If I check the targeted computer’s processes, Microsoft Setup Bootstrapper is there, but does nothing, I’ve tried leaving it for extended periods of time and nothing happens.

I am copying the files to the local computer in a temporary folder so it’s not a double hop issue. The files copy over without an issue and if I call the setup.exe /adminfile from the targeted computer itself, the setup begins.

Any ideas?

#Get computers to install office on
$Computers = Get-Content -Path "\\server\Office2016\ComputerNames.txt"
ForEach ($Computer in $Computers)
{
	Write-Host "Working on $Computer" -ForegroundColor White
	
	Write-Host "Testing access to $Computer" -ForegroundColor White
	$HostUp = Test-Connection -ComputerName $Computer -BufferSize 12 -Count 1 -quiet
	If (!($HostUp))
	{
		Write-Warning -Message "Remote Host is not accessible!"	}
	Else
	{
		Write-Host "Success!" -ForegroundColor Green
		$items = Get-Item -Path "\\server\Office2016\*"
		Write-Host "Creating Transfer folder on $Computer" -ForegroundColor Yellow
		New-Item -Path \\$computer\c$\Transfer -ItemType Directory -ErrorAction SilentlyContinue | Out-Null
		foreach ($item in $items)
		{
			Write-Host "Copying $Item over to $Computer\c$\Transfer\" -ForegroundColor Yellow
			Copy-Item -Path $item -Destination \\$Computer\C$\Transfer\ -Force -Recurse
		}
		Write-Host "Starting setup on $Computer" -ForegroundColor White
		
		Invoke-Command -ComputerName $Computer -ScriptBlock {
			$installer = 'C:\Transfer\setup.exe'
			$adminfile = '/adminfile officesetup.msp'
			
			Start-Process -Wait -FilePath $installer -ArgumentList $adminfile
		} -AsJob -ErrorAction Stop
		
	}
}
Get-Job | Format-Table

Neally · 2022-01-27T16:19:41.000Z

Without looking at the script, tough to say…

If you post code, please use the ‘Insert Code’ button. Please and thank you!

PLEASE READ BEFORE POSTING! Read if you're new to the PowerShell forum! Programming & Development

Hi, and welcome to the PowerShell forum! Don’t apologize for being a “noob” or “newbie” or “n00b.” There’s just no need – nobody will think you’re stupid, and the forums are all about asking questions. Just ask! Use a descriptive subject. Don’t say “Need help” or “PowerShell Help”, actually summarize what the problem is. It helps the rest of us keep track of which problem is which. Don’t post massive scripts. We’re all volunteers and we don’t have time to read all that, nor will we copy…

192033ab-bb8f-4032-88a5-8e2313af0344-codebutton_small.png

spiceuser-c1jq1 · 2022-01-27T16:21:04.000Z

I inserted, but it didn’t go through for some reason. It’s added now

Neally · 2022-01-27T16:36:33.000Z

does it have some interactive component?

‘-asjob’ might put it in the background and something can not get acknowledged?

spiceuser-c1jq1 · 2022-01-27T16:44:42.000Z

If I call it locally, I have to press OK once. Not ideal, but I can probably figure out how to get past that if I can get it working in the first place.

I took out -AsJob, but still the same thing. The setup bootstrapper sits there in processes but nothing is actually happening.

Neally · 2022-01-27T16:53:08.000Z

spiceuser-c1jq1:

If I call it locally, I have to press OK once. Not ideal, but I can probably figure out how to get past that if I can get it working in the first place.

I took out -AsJob, but still the same thing. The setup bootstrapper sits there in processes but nothing is actually happening.

yeah eitherway, invoke-command will run it as a different context, the user would not see the prompt.

spiceuser-c1jq1 · 2022-01-27T16:55:10.000Z

What do you mean? Do you have any idea how to get this working?

Neally · 2022-01-27T17:06:44.000Z

spiceuser-c1jq1:

What do you mean? Do you have any idea how to get this working?

I mean, if you need to interactively click ok , that will not work.

have you looked into the Office Deployment Tool (ODT)

how does your msp file look like? you need it to install without prompts.

spiceuser-c1jq1 · 2022-01-27T17:14:33.000Z

I’ve also tried creating a bat file and that doesn’t work either.

So if I type in CMD or PS on the targeted computer

C:\Transfer\Setup.exe /adminfile officesetup.msp

It works fine, but if I put that same code in a bat file and try to invoke-command that bat file remotely, it doesn’t work.

ODT is for 2019 / 365 to my understanding so I am using the older Office Customization Tool.

027c6c46-5b73-4230-b285-6b42c1f0a182-Capture.PNG800×461 123 KB

dwendel · 2022-01-27T18:00:01.000Z

As Nealy said, how does your msp file look like? you need it to configure it to not prompt.

Our bat file script worked fine but the msp file was setup for no prompts.

Files also copied local 1st then,

Start C:\tech\installs\Office2016ProPlus_32bit\setup.exe /adminfile C:\tech\installs\Office2016ProPlus_32bit\Office2016ProPlus_32bit.MSP

spiceuser-c1jq1 · 2022-01-27T18:36:03.000Z

I reconfigured the MSP to have 0 prompts and it works. Thank you for the help you two!

spiceuser-c1jq1 · 2022-01-27T18:40:40.000Z

I’m not seeing the option to choose “Best Answer” and resolve this post