Yeah I saw that one but from looking at the source code it appeared that it was designed to work with Macintosh DMG, PKG or APP files and prep them for importing into SCCM (lots of references in the code to .dmg/.pkg/.app and no references to .exe or .msi files). Correct me if I overlooked something though.
What I'm looking for is something that will let me take all of the *-win* recipes (autopkg downloads windows installers!) that James & Matt have created and get them prepped as much as possible for importing into SCCM. Wondering how far down the road to take it on the mac side, as we're running AutoPkg (and Aamporter) via Jenkins and we can slave a Windows box running Jenkins to the Mac Jenkins, and have the Jenkins AutoPkg job on the Mac drop it where the Jenkins-PC-Windows slave can access it, have the Mac build job call the PC and finish off importing with Powershell from there. Kinda wanna keep as much as possible in AutoPkg due to the awesomeness of crowd-sourcing and Github pull/fork requests in error remediation! But again, feel free to say "Well you COULD do it that way, but what about..."
I don't do the SCCM side of things, but the guys on that side are learning A LOT from exposure to MacAdmins/Munki/AutoPkg. It's fun to hear them say "Yes, but how do we get it to work like it does on the Mac..."
M@