• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Kelemvor

#31
Yeah, i know that already.  But when we have multiple people running the same EXE file from a network share, the log file is useless since we have no idea what goes with who.  That's why we need it to store locally on each machine.

But it appears that the .settings file still does work so we put in a local path in that file and it now has all machines recording the log file to their C drive and it's openable.  However, please don't make the .settings file stop working even if it's not officially supported any more.  :)
#32
Looks like 4.0.0.5 and opening the log file from %localappdata%\temp\patchmypc.log.

Since the .settings file isn't used for us to redirect where the log file goes, that's the only place we could find that stores it local to each PC.  When I open the file on our network share, that one opens normally but contains a jumble of info from multiple computers and I have no way of knowing which section goes with which machine.
#33
Everyone in my office who has opened it up has it look like the attached file.  No line returns are showing up at all.  This only started within the last week.

On a side not, it would be great if a line could be added about what version of each program was detected and what version is the latest so we can tell how far behind people were when they ran it.
#34
Howdy,

Prior to the latest version or two, Notepad worked just fine to open the Log file.  As of yesterday, the log file just shows up as one giant block of text that is horrible to read.  If I use somethign more advanced like notepad++ works, but not everyone has that.

Any chance the log file could be encoded differently?

While we're on that topic, could you maybe put in a line of ****************'s or something to divide each time the program is run?  Currently there's no line break between when one run ends and another one starts which also makes it harder to read.

Thanks!
#35
Thanks.  Tested it and it worked great.
#36
Report Bugs and Issues (Free Home Updater) / Handbrake
February 22, 2018, 07:26:33 AM
This has been failing for a week or two.

2/22/2018 8:20:53 AM - Download URL: https://download.handbrake.fr/releases/1.0.7/HandBrake-1.0.7-i686-Win_GUI.exe
2/22/2018 8:20:53 AM - Failed to get download information for HandBrake 1.0.7 (x86) Download URL: https://download.handbrake.fr/releases/1.0.7/HandBrake-1.0.7-i686-Win_GUI.exe


If I go to https://download.handbrake.fr/releases/1.0.7/HandBrake-1.0.7-i686-Win_GUI.exe manually, it does give me a file download so dunno why PMPC isn't working.
#37
We had tried giving explicit permissions to the folder but it didn't help.  So, we decided to just make the GPO as a User GPO so it will run as the user logged in.  That seems to be working fine.

The one problem we're having now is that we modified the .settings file to force the Log file to go into a folder on each person's C drive.  However, when someone runs the program with the /s flag, the First time it doesn't put the log file where we told it to.  Then if they run it again, the Second time it does put the log file where we specified.  I don't know if it's reading in the settings and running the scan at the same time so the settings don't take effect the first run or if it's a bug or what.

We're going to try running it the first time in Download Only mode to see if that works, and then run it the second time in regular mode so we can capture what each machine is doing.
#38
OK.  Some more info.

No matter what we do, we can't get it to run as System, from a network drive.  Maybe it's a permissions thing or something.  No idea.

So, as a work around, I modified my GPO to now copy the patchmypc.exe, patchmypc.ini, defailtapps.settings, and patchmypc.settings files to the local C drive.  The Scheduled Task then runs it from that location.  This work.  Everything runs and the software gets updated.

However, this doesn't seem to work when told to use the Cache folder out on our network.  The log shows that it downloaded the updates from the internet instead of pulling them from the cache.

When I ran the program manually, it does have the path to the cache folder listed in options but it just seemed to ignore that settings.

Ideally what I'd like to happen is this:

  • PC runs PMP.exe /s based on the scheduled task.
    If it finds something out of date, it will look to our network share to see if the file it needs is already out there.  If it finds it, it will install the update.
    If it looks to the network share but doesn't find what it needs, I want it to go online and download the file and then put the installer into the cache folder for the next person.

Maybe it just can't do what we want and we'll jsut deal with having everyone have to download the files every time but just thought I'd check back in.

#39
Two things:

1) Any chance the log file location could be modified to be stores in the Settings file like all the other settings?  If we are running Patchmypc.exe from a network share, each individual user will never run the program manually to set a location.  We want each computer to keep its own log so if we have to research something, we can do so.  If it just stores in the same folder as the EXE, then we'll just have one gigantic log file with 100 machine's information in it which won't be helpful at all.

2) When I run the program from a scheduled Task under the System account from my own machine, it seems to work fine.  But I've run the program manually so not sure if that would have changed something.  I had a different person just run the scheduled task, without having ever run the program manually, and he's getting what I got last week.  It shows up in Task Manager but just sits there forever and never does anything.

I had the person try copying the files to their local machine and running patchmypc.exe /s from an admin command prompt.  It ran for a few seconds and then just went away.

This is all that was in the log file:

2/19/2018 9:26:24 AM - Patch My PC Started
2/19/2018 9:26:24 AM - Patch My PC running with command line option: /s
2/19/2018 9:26:24 AM - Performing scan of installed applications
2/19/2018 9:26:25 AM - 7-Zip 16.04 (x64 edition)  -  16.04.00.0
2/19/2018 9:26:29 AM - Scan completed
2/19/2018 9:26:29 AM - Starting to perform updates automatically in silent mode
2/19/2018 9:26:33 AM - Patch My PC 4.0.0.0 | Definitions: 19-Feb-2018 | 2/19/2018 9:26:33 AM

2/19/2018 9:26:33 AM - Run With /S Switch
2/19/2018 9:26:33 AM - Operating System: Microsoft Windows 10 Enterprise x64

2/19/2018 9:26:33 AM - Operating System: 6.2.9200.0


They are a local admin of their machine as well.  No idea what the problem might be.
#40
I am running it now at home and it seems to be working fine.  I'll try again on Monday when I'm back in the office and see how it goes.
#41
Quote from: Admin - Justin on February 16, 2018, 11:16:41 AM
You can but that setting is saved locally on the machine from the options menu.

I tried running the Beta version via a Scheduled Task that runs as the SYSTEM account and it doesn't seem to work.  It's been running in Task Manager for a couple hours already.  THe only thing in the log file is:
2/16/2018 9:11:59 AM - Patch My PC Started
2/16/2018 9:11:59 AM - Patch My PC running with command line option: /s

The Beta is v3.9 so I can wait until v4 next week and try again.
#42
We are testing to run it from a shared drive using the caching option.  It'd be great if we could specify to have the log file get stored on each PC somewhere instead of putting it in the folder with the EXE since that would probably make for an ugly mess if multiple people run it at the same time.

Thanks
#43
Quote from: Admin - Justin on February 16, 2018, 12:24:37 AM
You could try the latest beta if you want.

Just installed the Beta ad am giving it a whirl.  Can you tell me where the log file would be stored if it's running as the "System" user?  Also, does the log file get updated as it runs so I can follow along and see if it's doing anything, or does it only get updated when it's done?

Thanks.
#44
Thanks for the response.  If you think to reply here when the new version is out, that'd be great.  I'll give it a try right away.
#45
I was able to get it to work if I set it up under User configuration instead of Computer configuration.  However, we have some machines that we don't necessarily want it to run on so I'm told I can look into Loopback Processing within Group Policy to maybe gain some finer controls...