Automation Folder Package Is Not Recreated Automatically During Deployment in Ghost Solution Suite 3.3 RU13

Products

• Ghost Solution Suite

Issue/Introduction

After upgrading Ghost Solution Suite (GSS) to version 3.3 RU13, triggering the Install Automation Folder task from the GSS Console deploys an existing, outdated package. Even after updating the configuration settings (such as network share credentials) in the Boot Disk Creator, the deployment engine does not automatically rebuild the package executable before pushing it to the target client machine.

Environment

 

Ghost Solution Suite (GSS) 3.3 RU13

Boot Disk Creator (BDC)

Windows Preinstallation Environment (WinPE) Automation Folders

 

Cause

In Ghost Solution Suite 3.3 RU12, selecting Install Automation Folder automatically evaluated the underlying Boot Disk Creator configuration, deleted the existing executable, recreated an updated AF_Automation Folder.exe package with a new timestamp, and deployed it.

Beginning in GSS 3.3 RU13, the automated package recreation logic during the deployment action no longer triggers if a package executable already exists. The GSS Console deploys the pre-existing executable stored on the server regardless of configuration edits, resulting in failed network connections or outdated settings on the target endpoint unless the executable package is refreshed manually or deleted.

The GSS 3.3 RU13 Console engine skips the background package generation routine during the Install Automation Folder execution if AF_Automation Folder.exe is already present in the package directory. It defaults to pushing the pre-existing file rather than checking for configuration updates or rebuilding the package dynamically.

Behavior Aspect	GSS 3.3 RU12 (Previous)	GSS 3.3 RU13 (Current)
Console Status Output	Displays "Creating Windows Automation Folder package" before push.	Immediately starts pushing the existing package file.
Package Executable Timestamp	Updated dynamically upon launching the installation task.	Remains unchanged from the initial creation date/time.
Configuration Updates	Automatically compiled into the deployed executable.	Ignored during deployment unless manually compiled/cleared.

Resolution

This issue has been reported to our Broadcom Engineering team. Currently targeted to our GSS 3.3.14 release.

Diagnostics

To verify whether your environment is affected by this behavior, check the timestamps of the compiled package executable on the GSS Server before and after making configuration updates.

1. Open the Ghost Solution Suite Console (v3.3.13).
2. Open Boot Disk Creator (under Tools > Boot Disk Creator) and navigate to Edit Configuration for the Automation Folder.
3. Proceed through the configuration wizard to Step 5 of 8 (Network Connection) and update the credentials (e.g., changes the password for accessing the server share).
4. Finish the wizard to save the configuration changes.
5. Right-click a target machine in the console, select Advanced, and click Install Automation Folder.
6. Select the modified Automation Folder pre-boot configuration and click OK.
7. Result: The system deploys the existing AF_Automation Folder.exe package without updating or recreating it (the timestamp on the .exe file in Program Files (x86)\Altiris\eXpress\Deployment Server\AutoFolderPkgs\Automation folder\x64 remains unchanged).

Workarounds

To ensure updated configurations are properly deployed to client endpoints in GSS 3.3 RU13, use one of the following resolution workarounds.

Option 1: Manually Recompile the Executable in Boot Disk Creator

1. In RU13, open Boot Disk Creator and right-click Automation Folder under Configurations.
2. Select Create Automation Folder Installer... and clicks through the wizard.
3. When prompted that AF_Automation Folder.exe already exists, clicks Yes to manually overwrite/replace it.

Option 2: Remove the Existing Executable Package File

Deleting the old executable forces the GSS Console to automatically rebuild a new package using the latest configuration parameters upon the next deployment attempt.

1. On the GSS Server, open File Explorer and navigate to: C:\Program Files (x86)\Altiris\eXpress\Deployment Server\AutoFolderPkgs\Automation folder\
2. Open the appropriate architecture subfolder (\x64\ or \x86\).
3. Delete the existing file: AF_Automation Folder.exe.
4. In the GSS Console, right-click the target endpoint and select Advanced > Install Automation Folder.
5. Select the modified configuration and click OK.

Note: The GSS Console will detect the missing file, re-run the package creation routine dynamically, generate a new AF_Automation Folder.exe file, and deploy it to the endpoint.

Verification

1. To confirm that the updated package was deployed:
2. Verify that AF_Automation Folder.exe in C:\Program Files (x86)\Altiris\eXpress\Deployment Server\AutoFolderPkgs\Automation folder\x64\ shows a current Date modified timestamp.
3. Confirm the target client machine successfully completes the Automation Folder installation and uses the updated parameters (e.g., validates network share connection under the newly configured credentials).