Perhaps one of you know about my little problem,
it愀 not really MSI related but it愀 about deploying
msi packages via active directory software deployment.
I just want to know if there ist a possibility to take
a clear view inside an .aas file, which is generated by
the GPO if you are using the software deployment feature
of the AD.
I don愒 want to change anything inside the file(now, perhaps
later ;-), but I惴 just curios and would like to take a look
inside. By using the editor it愀 like open an .exe with edit.
THIA,
Mark
--
Mark Heitbrink - MVP Windows Server
Homepage: www.gruppenrichtlinien.de
W2K FAQ : http://w2k-faq.ebend.de
PM: Vorname@Homepage, Versende-Adresse wird nicht abgerufen.
Meaning, I've been able to view aas files using Notepad, and see advertising
information such as the working directory of a shortcut, the installation
source, and items like the ProductCode and PackageCode.
Perhaps instead of editing the file, you could use the function
"MsiAdvertiseProduct" to generate a new ".aas" file. I've created a VB
program to help automatically create a new software package object in a GPO,
and have used this function successfully to create the "aas" file.
Hope this helps!
Curtis Sawin
"Mark Heitbrink [MVP]" wrote:
> Hi,
>
> Perhaps one of you know about my little problem,
> it´s not really MSI related but it´s about deploying
> msi packages via active directory software deployment.
>
> I just want to know if there ist a possibility to take
> a clear view inside an .aas file, which is generated by
> the GPO if you are using the software deployment feature
> of the AD.
>
> I don´t want to change anything inside the file(now, perhaps
> later ;-), but I´m just curios and would like to take a look
> inside. By using the editor it´s like open an .exe with edit.
> One can open an ".aas" file in a text editor, but this won't give a
> completely "clear" view.
>
> Meaning, I've been able to view aas files using Notepad, and see advertising
> information such as the working directory of a shortcut, the installation
> source, and items like the ProductCode and PackageCode.
>
> Perhaps instead of editing the file, you could use the function
> "MsiAdvertiseProduct" to generate a new ".aas" file. I've created a VB
> program to help automatically create a new software package object in a GPO,
> and have used this function successfully to create the "aas" file.
>
> Hope this helps!
This script would be really interesting to see! Are you able to share it?
Cheers,
Kenny.