We have been using Kace to patch our workstations for a couple of years now. We just recently started testing patching on our servers. We have a group of test servers that we've been using the past couple of months to test with. Our servers have very small C: partitions (basically room for the OS), and then everything else usually ends up on separate partitions. It looks like Kace is running the installers from C:\Windows\Temp where multiple directories are being created. Just in the past two months we have been testing that directory is now up to 3GB +. Even though this does not sound like much after last nights patching on these test servers they all went to alarm with low disk space. When I checked my workstations it was also doing the same. It just hasn't been an issue because we have a larger C: on our workstations. 

Is there any setting that I'm overlooking that I'm not seeing? I'm a little hesitant to have a scheduled task to delete the temp directory every month. It seems like it should do it's own cleanup?
Answer Summary:
With the help of support I created an Online Script that will delete the files related to patching. @echo off del "C:\Windows\Temp\*.cab" /S /Q del "C:\Windows\Temp\*.manifest" /S /Q del "C:\Windows\Temp\*.cat" /S /Q del "C:\Windows\Temp\*.mum" /S /Q cd C:\Windows\Temp FOR /D /R %%X IN (amd64_*) DO RD /S /Q "%%X" FOR /D /R %%X IN (msil_*) DO RD /S /Q "%%X" FOR /D /R %%X IN (wow64_*) DO RD /S /Q "%%X" FOR /D /R %%X IN (x86_*) DO RD /S /Q "%%X" REM ######### Delete Empty Directories ########### for /f "tokens=*" %%d in ('dir /ad/b/s ^| sort /R') do rd "%%d"
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

2
With the help of support I created an Online Script that will delete the files related to patching. 

@echo off
del "C:\Windows\Temp\*.cab" /S /Q
del "C:\Windows\Temp\*.manifest" /S /Q
del "C:\Windows\Temp\*.cat" /S /Q
del "C:\Windows\Temp\*.mum" /S /Q

cd C:\Windows\Temp
FOR /D /R %%X IN (amd64_*) DO RD /S /Q "%%X"
FOR /D /R %%X IN (msil_*) DO RD /S /Q "%%X"
FOR /D /R %%X IN (wow64_*) DO RD /S /Q "%%X"
FOR /D /R %%X IN (x86_*) DO RD /S /Q "%%X"

REM ######### Delete Empty Directories ###########

for /f "tokens=*" %%d in ('dir /ad/b/s ^| sort /R') do rd "%%d"

Answered 09/04/2014 by: dugullett
Red Belt

  • Thanks for the update of the temp fix, I guess they are going to fix this properly in a future release?
    • I heard possibly in 6.3. Which for some crazy reason even though we're on 6.0 now 6.3 will be the next release. Try and wrap your mind around that one!
      • LOL
      • Pretty sure the way it was explained to me was like this: K1000 Express is 6.1. The 6.0 service pack will be 6.2, and then 6.3 will be the next full release sometime in 2015.
  • What I have noticed is that it seems to only happen on my 2003 servers that are running Dell OpenManage and have the Kace agent installed.

    Funny thing is I have not turned on the Patching feature from the K1000 yet. It seems to be some sort of interaction between the two.

    I noticed that something about KACE causes the process INVCOL to run and download all the patches, firmware, etc and fail to install them.
Please log in to comment

Answers

0
Hi.  I am seeing the same is and I am on 6.3.314 for the KACE agents.  Is that script the only solution KACE support is providing or is this going to be addressed in the product?  How often are you running that script?
Answered 05/16/2015 by: wmichel23
White Belt

  • It's listed as a known issue in the 6.3 release notes. I would assume that would mean they take care of it soon. For this particular patch schedule we actually run them manually (save and run now). So after I run the schedule and it's complete I then manually run the script.

    For my workstations I have a label for machines for disk capacity is greater than 90%. I then run that script on that label monthly.
Please log in to comment
0
I am see the same thing, looks like a bug we should report. It looks like it started with the 6.0 client on mine.

You are right you do not just want to delete the windows\temp folder since it can then cause a problem with trying to uninstall/repiar/upgrade previously installed programs and patches.

read down to the bottom of this thread

http://superuser.com/questions/418032/emptying-windows-temp-folder-is-a-good-idea
Answered 08/14/2014 by: SMal.tmcc
Red Belt

  • Yeah I was going to put in a ticket with support, but their site seems to be acting up. It's not taking my usual credentials. It also looks like they have updated it recently so I'm not sure if that's related.

    Is anyone else having an issue, or is it just me?
    • Hi Dugullet, I was able to log in to support.kace.com with my expected username/password. I tried it just now.
      • Thanks. I ended up calling them. They had some issues this morning. I guess I just got it at the right time.
Please log in to comment
Answer this question or Comment on this question for clarity

Share