You are correct about the error code meaning: Insufficient system resources exist to complete the requested service.
I've not seen this before, but maybe it's related to anti-virus? Have you implemented the exclusions for UEM?
They are described here:
I already added exclusions for the FlexEngine.exe process, but haven't added any of the UEM-related shares to the exclusions.
Our AV (Bitdefender Enterprise Security) is set to scan network shares only for application files, but I went ahead and added the shares to the exclusions. We'll see how it goes.
Unfortunately, it still didn't do anything to prevent the error 1450.
'insufficient system resources exist to complete the requested service' while importing is a strange error.
UEM copies the content from the archive (.ZIP) to the correct folder inside the user profile in that case.
Anything that could interfere with that? Anti virus is the logical one, but you say the exclusions are in place.
Anything else on the system? Do you use encryption, App-V, etc.?
What configuration do your VM's have? Do they have a single vCPU and minimum RAM?
How do you offer the SMB shares for UEM? Regular Windows Server OS or from a NAS/SAN device?
Also, could you run this command from an elevated command prompt and post the output?
This gives you a list of filter drivers installed on the system. Maybe something is interfering with the files.
Antivirus running is Bitdefender. Only file scanning module is enabled as we had issues with App Volumes when behavior detection module was enabled.
No encryptions or App-V/ThinApp, but we do have App Volumes (2.12) running on our desktops presenting appstacks+writable volumes
Desktops are running 2 vCPU and 4GB RAM. Running Windows 8.1 and Windows 10 LTSB 2016 (build 1607).
SMB share is from a NAS device. Supports up to SMB 2.1.
Here's the fltmc result ran from Windows 10 desktop:
PS C:\Windows\system32> .\fltMC.exe
Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
wcnfs 0 409900 0
immflex 7 385910 0
gzflt 7 320820 0
avc3 7 320780 0
trufos 6 320770 0
storqosflt 0 244000 0
svdriver 4 190000 0
wcifs 0 189900 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
FileInfo 7 45000 0
Wof 6 40700 0
gzflt, avc3, trufos filter drivers are from Bitdefender AV.
svdriver is, of course, from App Volumes.
wcnfs and wcifs are related to Windows container feature new to Windows 10 build 1607 (not being used or enabled, but the filter drivers are installed by default nonetheless).
immflex is obviously from UEM.
Everything else are basically Windows stuff.
What template do you use for your writable volumes? UIA only or UIA+profile?
I think the proces of elimination would be the next step to see if we can pinpoint the issue.
I would try these things in this order:
- remove Bitdefender completely. the fact that it installs 3 filter drivers makes me think it might be doing a little bit more then just on-acces file scanning
- host the SMB shares on a regular Windows Server (2008R2 or newer)
- remove App Volumes agent