Page 2 of 2

Re: Unsure what is going wrong

Posted: Wed Sep 05, 2018 3:51 pm
by jmaxwell
We are using the URL scenario. This still needs a network share location set up correct??
We copied the ISO manually since it was quicker and in our testing environment.
As for the rest of the files:
1. See attached for the file path C:\Windows\LTSvc\PatchRemedy Is this the correct path? Correct files downloaded?
prupgrade1.PNG
prupgrade1.PNG (12.88 KiB) Viewed 11701 times
2. See attached. Is this all the files needed?
prupgrade2.PNG
prupgrade2.PNG (31.95 KiB) Viewed 11701 times
3. Per previous response, the only thing we can determine if the set up ran was the "Windows Installer" process was in the process section of task manager. Would this be the place to look for the setup.exe? Other

Would this be the correct command(s) in the script? See attached.

Also, line 507 is the message we get then line 510 message occurs as in last screenshot of my previous post.
Which command do I need to copy and run in command prompt exactly? Do we know the name of the update app that would be consuming alot of cpu?

Thanks again for support and patience with me.

Re: Unsure what is going wrong

Posted: Wed Sep 05, 2018 3:51 pm
by jmaxwell
prupgrade4.PNG
prupgrade4.PNG (54.49 KiB) Viewed 11700 times

Re: Unsure what is going wrong

Posted: Thu Sep 06, 2018 2:14 pm
by Cubert
This is the command we run here. Run this command while monitoring the Windows Processes to see what get launched during the setup.
Capture.PNG
Capture.PNG (3.7 KiB) Viewed 11683 times

Re: Unsure what is going wrong

Posted: Thu Sep 06, 2018 8:20 pm
by jmaxwell
Ok tried to run the command as instructed. Here are the results.
commandline1.PNG
commandline1.PNG (174.33 KiB) Viewed 11673 times
C:\Windows\LTSvc\PatchRemedy\windows10UG\sources is where that .dll is found out.

Let me know if I incorrectly ran it. Or need additional information.

Re: Unsure what is going wrong

Posted: Fri Sep 07, 2018 12:54 pm
by Cubert
Yeap that was correct, the last command with full path...

And we got an error, The files that were extracted are corrupt. so lets step back a bit and test re-extracting the files from ISO.

In powershell run, change @ISO_Path@ to actual path of ISO

Code: Select all

$mountResult = Mount-DiskImage -ImagePath @ISO_Path@ -Passthru
($mountResult | Get-Volume).DriveLetter
Next take drive letter returned and execute, change @MountDriveLetter@ with actual drive letter returned above and replace %ltsvcdir% with correct true path. Make sure to delete all files from directory first so robo copy copies fresh.

Code: Select all

robocopy @mountDriveLetter@:\ %ltsvcdir%\PatchRemedy\windows10UG\  /e /r:1 /w:1

Once copy completes, (Note how long copy takes) rerun previous install command on setup.exe. Do you get same error?

If not, try setting plugin config setting to copy ISO locally to agent . It maybe that the LTagent script service times out during the copy. it only allows us like 10 or 15 minutes per command.

Re: Unsure what is going wrong

Posted: Wed Sep 12, 2018 3:32 pm
by jmaxwell
I tried running the first command on two machines. Here is the results.
powershell2.jpg
powershell2.jpg (958.59 KiB) Viewed 11617 times
powershell1.jpg
powershell1.jpg (966.46 KiB) Viewed 11617 times
Do i need the entire path of the iso including the .iso file or just the folder path where the iso is located? Please advise.

Re: Unsure what is going wrong

Posted: Thu Sep 13, 2018 2:28 pm
by Cubert
Nope your requesting it fine, the issue is your getting "Permission Denied" for the user executing the powershell console.

That is a typical issue that can be resolved by placing ISO on a basic open network share. Shares inside a domain environment must have permissions allowing a user and or the LT agent service user the ability to access files.