Yes, a redeploy triggers re-creation of the .AAS file. I came across this when I was trying to manually modify properties of a deployment within the GPC. The problem with a redeploy, which you may have discovered, is that if you have deployed the app to any existing workstations, redeploying it will the cause to be de-installed from those workstations and then re-installed at the next GPO processing cycle. Not always a desirable effect if say, you've already installed the app on several thousand workstations :-).
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Thursday, December 18, 2003 12:03 PM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] GPO Software Distribution I checked the AAS file modification date and it is today at the time I re-deployed the package with the new MST file that I saved as the same name It must recreate that each time you redeploy -----Original Message----- From: Darren Mar-Elia [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 2:45 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] GPO Software Distribution Not sure but I don't think so, because of that AAS file, which doesn't get re-created except at initial deployment, or re-deployment. I guess there's no harm in trying (on a test environment that is :-)) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Thursday, December 18, 2003 11:33 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] GPO Software Distribution What if I modify the existing MST and save it as the same name and then set the policy to redeploy, would that work? -----Original Message----- From: Darren Mar-Elia [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 2:01 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] GPO Software Distribution Justin- Because of the way software installation works in Group Policy, adding MSTs is a one time operation. I believe this is because, as a function of initial deployment of an application, an application advertisement script (.aas) file is created in SYSVOL that includes the definitions of the .mst file, and this file can't be re-created without re-deploying the app. At least, that is my guess. You could try modifying the AD attribute within the GPC that stores what .mst files are associated with the package, but I suspect it won't work unless that .AAS file is re-created. Darren -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Thursday, December 18, 2003 10:19 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] GPO Software Distribution When I created the Software Package I did click on Advanced and was able to put in a MST File, but now I have created a new MST file and want to add that one to the list and remove the other and I can't do it -----Original Message----- From: Steve Shaff [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 1:10 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] GPO Software Distribution I would have to ask the question, did you run assigned or advanced. I have only run into this problem if I don't select the advanced button. Otherwise, it seems that you only have limited functionality of the software policy. Thanks, Steve ***************************************** Steve Shaff Active Directory / Exchange Administrator Corillian Corporation (W) 503.629.3538 (C) 503.807.4797 (F) 503.629.3674 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Thursday, December 18, 2003 9:20 AM To: ActiveDir (E-mail) Subject: [ActiveDir] GPO Software Distribution I have made a change to my MST File and saved it as a new file name. The Software package won't allow me to add a new MST file, all the buttons are grayed out. I have full control being logged in as Administrator. What could be the problem Windows 2000 SP3 Native Mode Justin A. Salandra, MCSE Senior Network Engineer Catholic Healthcare System 212.752.7300 - office 917.455.0110 - cell [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
