1 Reply Latest reply on Apr 12, 2018 10:00 AM by treed

    Java 8 161 Update - Sun Folder

    promen Rookie

      We pushed the Java 161 update from SCCM and the install is creating a Sun folder at the root of the C: drive on our computers.  The folder contents contains a deployment.properties file which we already have in our environment in a Sun folder that we create in C:\Windows\Sun.


      Why is this C:\Sun folder getting creating?  If we simply install 161 from the standalone file the folder is not being created.  It is only created when pushed from SCCM with the published update.


      Is anyone else seeing this?





        • 1. Re: Java 8 161 Update - Sun Folder
          treed SupportEmployee



          This is a bit of an oversimplification of our product but Ivanti Patch for SCCM is simply an add-on to SCCM that allows you to publish 3rd party updates. We get these updates directly from the vendor sites with URL's they provide, we then publish those updates for deployment. After publishing and syncing to the WSUS our software is no longer involved in the processes moving forward. SCCM will package and deploy the software, and the OS will install the update similarly to if you would execute it manually.


          Most likely the file is being generated by either the update itself or part of the packaging SCCM does. However, I am unable to replicate the issue you are seeing in my testing environment and I was unable to find any past cases of this particular issue. Its also possible it's a temp file that is simply not deleted after the installation. As mentioned, this is happening far outside the parameters of our software, but I hope the information provided is helpful and leads you to solution.