'Insufficient resources to write file' error with almost all packages when deployed

Comments

9 comments

  • Matthew Waite

    I am having a similar problem. I am getting the insufficient resources error with almost every package when deployed.  For example, I just tried the latest Adobe Shockwave, Reader DC and Java 8 u40 updates. All received that error on every machine I targeted.

    I'm an Enterprise user running PDQ Deploy 6 Beta 3, from a Windows 7 SP1 64-bit host, to Windows 7 SP1 64-bit targets. Rebooting host or targets has no effect.

    Some advice would be greatly appreciated.

    Thanks.

    0
    Comment actions Permalink
  • Kynan Wallace

    Greetings Matthew, in an effort to keep plugging away fixing this issue I finally resolved it and figured out the culprit. We use a program called Clean Slate (similar to DeepFreeze) on all our general lab computers in our school and it was that particular program running (whether a user was logged in or at CTRL ALT DEL screen) preventing PDQ deploy from actually deploying and resulting in this particular issue. I tested it by uninstalling cleanslate on a test computer and was able to 100% deploy entire nested package of all my wanted updates.

    Hope this helps you, I am currently poking around to see if there's an exemption I can make either inside cleanslate or contact their support in getting this working together with PDQ deploy.

    0
    Comment actions Permalink
  • Matthew Waite

    Kynan, thanks for the update! I'm sure not coincidentally, we are also using Clean Slate. Go figure.

    0
    Comment actions Permalink
  • Kynan Wallace

    Matthew, I got a response from FortressGrand as follows:

     

    You can plug in the settings below for PDQ, which should allow it to push down the installs without interference from Clean Slate.  You can also update the build to the last build released for Clean Slate v6.5 too at some point if you so desire.  The attached instructions will provide the instructions for doing so. 

     

    Please go to Allowed File & Registry Operations>Exempt Applications and create this item from the All Groups Baseline Security tab with Use Baseline Security for this Group selected  (enter items just as shown with + symbol in lieu of colon after drive letter -  items can be copied and pasted in).

     

    C+\WINDOWS\SYSTEM32\LSASS.EXE

     

    Click on Apply.

     

    Next, please go to Allowed File & Registry Operations>Writable Folders & Files and create these items from the All Groups Baseline Security tab with Use Baseline Security for this Group selected (enter item just as shown with + symbol in lieu of colon after drive letter -  items can be copied and pasted in):

     

    C+\WINDOWS\ADMINARSENAL\

     

    Click on Apply, then go to File>Save the changes

    I am not sure if PDQ uses the system or administrator profile credentials to deploy software, but most system management tools are set to do so as system.  Clean Slate applies security to both with the properties Clean Slate Security Applied to Administrative Threads and Clean Slate Security Applied to System Threads, which are both found under Allowed File & Registry Operations.   One or both of these may need to be disabled also if the above setting doesn't work by itself. 

    If you should have any issues that only occur when Clean Slate is enabled, then I can take a look at a Details Report from Diagnostics, which should shed some light on the issue. Clean Slate can easily be disabled to test to see if the problem occurs when security is disabled.  To disable, please click on the menu File and place a checkmark next to Disable All Security On this Computer.  Remove the check mark to re-enable. 

     

    To get a Clean Slate Details Report from Diagnostics, please logon as a user with Clean Slate's security enabled and access the Fortres Security Interface (FSI), which can be done by holding down Ctrl+Shift+F.  From within the FSI, please go to Diagnostics, click on the button Record, minimize the FSI, and duplicate the issue immediately thereafter.  After the issue has occurred, please maximize the FSI, click on the button Refresh, then click on the button Details Report.  At the top of the Details Report, please click on the Save button in the upper left of the report next to the Print button, and save that .rtf file.  If there are multiple issues, please click on the button Clear, click on the button Record, run the next test as before, and save the new Details Report as before.  Do this for each issue and attach each for review.

     

    Haven't had a chance to test it but will update when I do. Hope it helps!

    0
    Comment actions Permalink
  • Kynan Wallace

    Update:

    Following all the instructions provided in the earlier email, I am yielding the same results as before where it will not allow PDQDeploy to install properly. I did find something very interesting that I hope you can shed some light on.

    1. Workstation sitting at the CTRL+ALT+DEL screen awaiting login results in PDQDeploy not able to install packages properly.
    2. Workstation logged in as a local administrator (CleanSlate is disabled due to Basic Settings>Clean Slate for Administrators being disabled)results in PDQDeploy not able to install packages properly.
    3. Workstation logged in as domain administrator (CleanSlate is disabled due to Basic Settings>Clean Slate for Administrators being disabled) results in PDQDeploy not able to install packages properly.
    4. Workstation logged in as Domain User (CleanSlate is enabled) results in PDQDeploy SUCCESSFULLY installing packages properly.
    5. Workstation logged in as Domain Administrator (CleanSlate setting changed to Enabled for administrators in Basic Settings) PDQDeploy SUCCESSFULLY installing packages.

    So it appears that whenever CleanSlate is disabled for whatever reason (at CTRL+ALT+DEL or logged in as an administrator) It will not allow PDQDeploy to work successfully in a disabled state. But the packaged installation from PDQDeploy works if clean slate is in an Enabled state, whether logged in as regular user, local admin, domain admin or at the CTRL+ALT+DEL screen.

     

    Just submitted another ticket to clean slate in regards to this, I asked them if anything can be done to leave clean slate disabled for admins.

    I guess my routing now is to enable it for admins, but disable it for admin threads which should allow installations through in accordance with the above post of mines changes. 

     

    Hope this helps Matthew!

    0
    Comment actions Permalink
  • Kynan Wallace

    I take that back, even at CTRL+ALT+DEL with clean slate enabled I still get insufficient resources error. Going to ask Fortress Grand about it, will report back.

    0
    Comment actions Permalink
  • Kynan Wallace

    So after talking with their support, it looks like the issue is that PDQ Deploy will only work if clean slate is at an ENABLED state. This can be circumvented with allowing installs of software by allowing admin and system threads in the settings.

    Version 7 of clean slate is the only one with an option to enable or disable security at the login screen. Hope this helps anyone!

    0
    Comment actions Permalink
  • Matthew Waite

    Kynan, thanks again for the updates.

    I was able to get it working using the above steps when logged in with security enabled. But still not having any luck installing at the CTRL+ALT+DEL screen. We have Clean Slate 7, and I tried the enable security at log on screen option. Didn't make a difference unfortunately. I'm playing with it presently, if I figure out anything else, I'll be sure to update the thread.

    0
    Comment actions Permalink
  • Kynan Wallace

    No problem happy to help! If I remember correctly security at login should be disabled, try that! Hope it works!

    0
    Comment actions Permalink

Please sign in to leave a comment.