How to generate PackageInfo.txt ?

[RiD3R07]

Hi all,

First of all thanks for this amazing tool.

I just started a new job and inherited the current SCCM infrastructure and they previous guy was using AutoIT to package all the apps.

I am trying to reverse engineer all the stuff he's done, because he didn't leave behind any documentation or sample scripts.  All deleted and gone.

I have managed to create some from scratch, like running basic MSI and EXE.

But now, I see a folder called PackageInfo.txt and it contacts all the switches and purpose and background information.  I was wondering, how did he create that? Or how would one go ahead and create/automate that with all the information?

Thanks,

[Subz]

This appears to be installer options for Office 365, I don't believe they would have use this to script as it would be difficult to read (script wise).

[RiD3R07]

26 minutes ago, Subz said:

This appears to be installer options for Office 365, I don't believe they would have use this to script as it would be difficult to read (script wise).

This was an example.  That file is there in all the apps.

[Subz]

As I mentioned the text above appears to be just instructions, if it was xml or ini format then that would make sense as you could reference that information from a script.  They may have just added the instructions to each of the packages/applications we use a similar process, while we package majority of packages, if we're overwhelmed we will send a package out to a third party with these type of instructions, we don't expect the vendor to use AutoIt, they may use PowerShell, vbscript or some other language so we make the packaging document quite general, i.e. which switches we use, any customizations we would like to have included, e.g. registry, file changes etc...

Just my 2 cents.