Gregory Candido

I create a PS script that won't run on my workstation, nothing happens.  After investigation the script download the EXE file but the installation next runs or executes.
Not sure if this is permission issue or a scripting error?  Please help me.  Below is my current script
 
# Silent Install Dropbox 
# Download URL: https://vbc-downloads.vonage.com/win/VonageBusinessSetup.exe
# Path for the workdir
$workdir = "c:\temp\Vonage"
# Check if work directory exists if not create it
If (Test-Path -Path $workdir -PathType Container)
{ Write-Host "$workdir already exists" -ForegroundColor Red}
ELSE
{ New-Item -Path $workdir  -ItemType directory }
# Download the installer
$source = "https://vbc-downloads.vonage.com/win/VonageBusinessSetup.exe"
$destination = "$workdir\VonageBusinessSetup.exe"
Invoke-WebRequest $source -OutFile $destination
# Wait 60 Seconds for the installer to download
Start-Sleep -s 60

# Start the installation
Start-Process -FilePath "$workdir\VonageBusinessSetup.exe" -ArgumentList "/S"
# Wait XX Seconds for the installation to finish
Start-Sleep -s 60
 

Would this be correct?  I would assume if they come 22H2 in the future we would need to create a global rule for that as well.
Since this is a global rule this means it will apply to all my tenant's machines?
 
Greg

Would this be correct?  I would assume if they come 22H2 in the future we would need to create a global rule for that as well.
Since this is a global rule this means it will apply to all my tenant's machines?
 
Greg

I'm trying to start an application that will start via PS script.
I create pulseway script using Windows Powershell to run this command but I can't get the application to start.
 
$env:Path += "C:\Program Files (x86)\NetDocuments\ndOffice\ndOffice.exe" 
& "C:\Program Files (x86)\NetDocuments\ndOffice\ndOffice.exe"
 
However if I go to the remote computer, open Windows Powershell and run these commands the application opens as desired.
All my other scripts I have work on this computer, so I'm executing it correctly.
 
Please advise.
 
Greg
 

Get rid of your script.
Just patch the Host and set the VMs to shutdown instead of saved state - if no patches are applied the the VMs won't be shut down.
If you leave the VMs in saved state they can in rare circumstances get corrupt vmrs files and Hyper V will be broken, it's an easy fix by replacing the vrms files with new ones,  its a rare occurrence though