MCCFL_MLA Absent Member.
Absent Member.
1592 views

ZPM Agent Windows Temp Folder

I think I may be missing something,

ZCM 11.3.2 FR 1

I have had a couple Win7x64 workstations recently have a full C:\ Drive. When digging in I see the Windows \ Temp folder has ballooned to over 100GB+ in size. The temp folders appear to be related to ZPM.

Am I missing some sort of setting to tell the agent to clean up patch temp data? Or what is the best solution?

I pretty much run 2 main Policy's that would change somewhat often.

1 - MS Critical
2 - MS Recommened
Labels (2)
Tags (2)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: ZPM Agent Windows Temp Folder

MCCFL,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Forums Team
http://forums.novell.com


0 Likes
Knowledge Partner
Knowledge Partner

Re: ZPM Agent Windows Temp Folder

MCCFL_MLA;2409407 wrote:
I think I may be missing something,

ZCM 11.3.2 FR 1

I have had a couple Win7x64 workstations recently have a full C:\ Drive. When digging in I see the Windows \ Temp folder has ballooned to over 100GB+ in size. The temp folders appear to be related to ZPM.

Am I missing some sort of setting to tell the agent to clean up patch temp data? Or what is the best solution?

I pretty much run 2 main Policy's that would change somewhat often.

1 - MS Critical
2 - MS Recommened


It's supposed to clean up the temp stuff once the patch is installed (and the policy is completed).

But I forget exactly when the cleanup happens.

It does show in a log somewhere, I can't remember if it's in the Event Viewer -> Application log (filter for WUS types).

More or less the ZPM stuff passes along the .exe/patches to WUS and WUS does the patching and then cleanup.

But again I don't recall if the cleanup happens after the patch is installed successfully, or after the entire policy is finished running and/or the PC rebooted.

I vaguely recall seeing some cleanup operation in the Event logs, but it may also be patch dependent.

--Kevin
0 Likes
sreinhart Absent Member.
Absent Member.

Re: ZPM Agent Windows Temp Folder

MCCFL_MLA;2409407 wrote:
I think I may be missing something,

ZCM 11.3.2 FR 1

I have had a couple Win7x64 workstations recently have a full C:\ Drive. When digging in I see the Windows \ Temp folder has ballooned to over 100GB+ in size. The temp folders appear to be related to ZPM.

Am I missing some sort of setting to tell the agent to clean up patch temp data? Or what is the best solution?

I pretty much run 2 main Policy's that would change somewhat often.

1 - MS Critical
2 - MS Recommened


I've bumped into this as well... This is most likely caused by a CbsPersist_*.log located in "C:\Windows\Logs\CBS" and which has grown to a size of over 2GB. This usually happens on machines that don't get rebooted all that often and have longer periods of uptime. These log files normally get compressed by makecab.exe but that fails with files over 2 GB in size, leaving all later CbsPersist-Files uncompressed as well. What's worse, for every failed compression attempt (several times per hour), it leaves a "Cab_*"-File in the C:\Windows\Temp folder which can easily be up to 100 MB per file. The only solution I know, is to delete the oversized file (or all CbsPersist-Files) as well as all the Cab_* from the temp folder.

It's noteworthy that this has nothing to do with ZPM or Patch Policies per se. Since the cause is with makecab.exe and overall questionable design in Windows, it most likely happens with WSUS or other mechanisms as well.

Hope this helps,

Steffen
0 Likes
MCCFL_MLA Absent Member.
Absent Member.

Re: ZPM Agent Windows Temp Folder

sreinhart;2410310 wrote:
I've bumped into this as well... This is most likely caused by a CbsPersist_*.log located in "C:\Windows\Logs\CBS" and which has grown to a size of over 2GB. This usually happens on machines that don't get rebooted all that often and have longer periods of uptime. These log files normally get compressed by makecab.exe but that fails with files over 2 GB in size, leaving all later CbsPersist-Files uncompressed as well. What's worse, for every failed compression attempt (several times per hour), it leaves a "Cab_*"-File in the C:\Windows\Temp folder which can easily be up to 100 MB per file. The only solution I know, is to delete the oversized file (or all CbsPersist-Files) as well as all the Cab_* from the temp folder.

It's noteworthy that this has nothing to do with ZPM or Patch Policies per se. Since the cause is with makecab.exe and overall questionable design in Windows, it most likely happens with WSUS or other mechanisms as well.

Hope this helps,

Steffen


Thanks for the info, I will dig in a bit more, but yes, I saw many many 100+ mb files attached to the current full install of Java 8. For some reason the Patch Full install for this is always failing, I have not had it be successful. I need to dig in on this as well. I had Many older workstations that ran out of disk space due to having over 60GB of TMP Files due to failures...(My bad for not paying attention to the updaters)

In the time being, I have brought up a WSUS Server. I have moved about 50 workstations off the ZCM / ZPM Patching for windows. I am continuing on these 50 to run all other 3rd Party updates using ZCM/ZPM.

Thanks!
patrick
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.