cancel
Showing results for 
Search instead for 
Did you mean: 

ePO Endpoint Deployment Kit 9.6.1 - Enterprise Edition

UPDATE:

Version 9.6.1 - 08/08/2016

Inhibited entry of comma in description field due to a ePO bug that splits it into 2 packages.

Fixed issue with overwriting of package if it already exists.

UPDATE:

Version 9.6.0.

Updated to .NET 4.5.

Removed third-party DotNetZip Library, replaced with native .NET 4.5 functions.

Removed third-party HTTPUploadHelper for MultipartFormData processing, replaced with native .NET 4.5 functions.

Changed background color of dialogs.

UPDATE:

Version 9.2.5.  Updated error handling for product detecion key parsing.

UPDATE:

Version 9.2.4.  This version set default values for the product detection key and product detection value.

I am very pleased to post the Community Edition of the ePO Endpoint Deployment Kit (EEDK).  This tool is designed to allow ePO  users to build and deploy their own custom software packages using ePO. This can included other software, hotfixes, scripts etc.  Inside the attached .zip files we have included a Product Guide along with  examples of building your own software packages.  If you have any question please use this community site for support.

UPDATE:

Version 9.4.  This version adds Windows 8 and Windows 2012 platform support.

UPDATE:

Version 9.5.2  This version adds Windows 10 platform support.

UPDATE:

Providing Enterprise Edition to the community. This will be the only version maintained going forward.

Labels (2)
Tags (1)
Attachments
Comments

Hi Andre,

Thanks for the recommendation.  Unfortunately, this didn't help with the issue.  It's still not running my script.

Thanks again!

Kevin

Thanks eelsasser for the information. It makes a lot more sense on how eposign function works. I would say leave as is. The issue that I originally had with this that I would get an eposign error but it didn't have any information on why it thew an error. I agree with ThomasN regarding a notification that the two DLL's are required for the eposign function to work.

As always this is a great tool and it just keeps getting better!

Erik

Thank you for all the hard work on maintaining EEDK!  I think there is a small bug in the 9.6 version.  When I go to build a package, if the package does not exist EEDK works as expected.  However, if the package already exists, EEDK will prompt to overwrite.  If you say "yes" then EEDK will display an error saying the package already exists. It is easily remediated by deleting the package in the build folder.
overwrite.jpgerror.jpg

Unfortunately, my permissions to edit/upload content to communities has been restricted. I can't post any version updates here.

Therefore, I have posted 9.6.1 to here:

ePOEndpointDeploymentKit - Box

Version 9.6.1 - 08/08/2016

Inhibited entry of comma in description field due to a ePO bug that splits it into 2 packages.

Fixed issue with overwriting of package if it already exists.

Let me know if this works for you.

Awesome.   Thank you.  I can confirm that 9.6.1 works as expected, and that I cant put comma's in the description field. 

Has anyone seen the following error message when attempting to build a package using EDK?  Thanks!

build error message.JPG

I tried but couldnt do anything to recreate you error.  Can you post the contents of EEDK.log, it may help track down the issue.

Hi Brinkn,

Here is the content of the log file:

[8/9/2016 3:31 PM] ePO Endpoint Deployment Kit: 9.6.0 (Enterprise Edition)

[8/9/2016 3:31 PM] Form Loaded from parameters.

[8/9/2016 3:31 PM] Populating eedkSettings.

[8/9/2016 3:31 PM] -Build:"" does not exist.

[8/9/2016 3:31 PM] Form Closing

[8/9/2016 3:31 PM] Exit (1)

Thanks in advance!

This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.
This widget could not be displayed.