Casey,
I have uploaded the log files to you.
I have uploaded the log files to you.
- Welcome to Support Forum: Get Support for Patch My PC Products and Services.
Patch My PC Support
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.
Pages1
#1
Support and General Questions (Enterprises Using ConfigMgr and Intune) / Re: Very slow performance and fluctuating memory issues PMPC (Enterprise Plus)
July 23, 2024, 05:38:10 AM #2
Support and General Questions (Enterprises Using ConfigMgr and Intune) / Very slow performance and fluctuating memory issues PMPC (Enterprise Plus)
July 19, 2024, 02:10:52 PM
We are running the MSP licensed EnterPrise Plus multi-tenant version of PatchMyPC, and I am beginning to onboard our clients (Intune). Running it on a Windows 10 Enterprise LTSC VM with 12GB of RAM.
As I have begun adding clients and their patches, the Publisher app has gotten slower and slower. At the moment, the PatchMyPC-Service is taking nearly 1.2GB of RAM running in the background, but when working with it, it has gone far higher. I just tried to do a repair install because the program has stopped showing its settings window and just run it in the background. During that time, the service took 8-10GB of RAM. After running the repair, I tried opening it again, and the Settings app RAM in use just keeps rising and the program took several minutes to open (it is still in a (Not Responding) state and is going up and down in RAM usage from 6-10GB for the Settings app). I upped the memory in the VM to 16GB to give Windows room to breathe. Using the app however, especially when applying changes or switching between tenants or right-clicking in a tenant slows things to a crawl.
How much RAM should the application use, and what can I do to improve performance?
As I have begun adding clients and their patches, the Publisher app has gotten slower and slower. At the moment, the PatchMyPC-Service is taking nearly 1.2GB of RAM running in the background, but when working with it, it has gone far higher. I just tried to do a repair install because the program has stopped showing its settings window and just run it in the background. During that time, the service took 8-10GB of RAM. After running the repair, I tried opening it again, and the Settings app RAM in use just keeps rising and the program took several minutes to open (it is still in a (Not Responding) state and is going up and down in RAM usage from 6-10GB for the Settings app). I upped the memory in the VM to 16GB to give Windows room to breathe. Using the app however, especially when applying changes or switching between tenants or right-clicking in a tenant slows things to a crawl.
How much RAM should the application use, and what can I do to improve performance?
#3
Support and General Questions (Enterprises Using ConfigMgr and Intune) / Report shows unassigned patches (Intune)
June 07, 2024, 02:18:40 PM
So, I'm running the PowerBI report used for showing, well, trying to show clients what is going on with their patching (we are an MSP with the MSP license). We are dogfooding using ourselves first.
I have everything configured, but when I run this report based on our Intune updates, I see a large number of Unassigned patches. Our intune device group here has all of our Windows PCs, and I have Intune updates set up (and am only using updates, including when I export the CSV for the report data). I'm unsure why patches aren't assigned, and any client would ask us "why the red number seems so high and what it means".
The only thing I can think of is that we retain the current update and one back for each product (in case of a need to go back one revision). Could it be that the report is reflecting the older revision of updates? Or is there something I need to do to ensure these are assigned? How do I clearly find what is assigned and what is not?
I have everything configured, but when I run this report based on our Intune updates, I see a large number of Unassigned patches. Our intune device group here has all of our Windows PCs, and I have Intune updates set up (and am only using updates, including when I export the CSV for the report data). I'm unsure why patches aren't assigned, and any client would ask us "why the red number seems so high and what it means".
The only thing I can think of is that we retain the current update and one back for each product (in case of a need to go back one revision). Could it be that the report is reflecting the older revision of updates? Or is there something I need to do to ensure these are assigned? How do I clearly find what is assigned and what is not?
Pages1