We are experiencing a dramatically increase of the hard disk where WO1 is installed. The main cause is the Cache Folder that occupies over 70 GB (93% of the capacity). This issue was detected two weeks ago with the last Windows Server security-patch updated. We suspected that IIS is not working properly with the pagination of the Device Server of the WO1 (we managed only +2000 devices, so that is not the problem because the server is full of capacity).
By your experience, where would it be the root cause? Does anyone experience something related?
We asked the same question, we have a lot more folder than you too. Support at first said on a call that we could delete them with no issue, then when we asked for it in writing, they came back and said don't delete them and that they would confirm. I then went on leave and they closed the ticket. I haven't had a chance to log another ticket yet so I would be interested to hear what others have to say about it.
I have no idea what is causing the cache folder to fill up or whether you can delete the cache files. I know you can manually delete orphaned file storage blobs (app installers) that would be stored on the configured file storage path. For this, use the PurgeUtility log to determine what is not being purged.
@aaronk I have suggested to support that they first determine if the ACLs on the folders are actually correct. The screenshot I saw had a SID for the user. Also the username configured in the console to impersonate and access the DFS is supposed to be in DOMAIN\Username format. Not sure why the screenshot had UPN.
Thank you for your reply. We have just added size to HD because it was just over 93% and the cache folder is not increasing, it keeps in the same size. We are going to schedule an upgrade of Device Server and Console (the issue is in the Console) to 22.10 version and see if this fix it. I don't know if the root cause is an IIS performance problem in the server but actually the Event Viewer does not show any suspicious in this way.
We are updating a on-prem environment from 22.06 ( for instance in 21.05 version, Java 1.8 was added by the installer) up to 22.09 (without checking version of the Java). The problem is the Windows Server 2016 is installed on a RED-HAT with an openjdk 11+ version.
Could any incompatiblity with this java version for the AWCM service?