I create custom packages by mimicking how it works. I create a regular package calling C:\WSUS_PP\CustomUpdateEngine.exe, include my own action file (e.g. vgx.xml) and any other necessary files, then use the parameter "\actionfile=vgx.xml". I've done all my customizations this way. I only use the custom package GUI to figure out the necessary parameters for the XML file. The command line calls the CustomUpdateEngine.exe, as stated above.
That's the strange part. No customupdateengine.log file is created. On machines that the package worked on, it's there. On the Win2012 boxes, the log isn't there. Firewall port issues perhaps?
That's the strange part. No customupdateengine.log file is created. On machines that the package worked on, it's there. On the Win2012 boxes, the log isn't there. Firewall port issues perhaps?
