Remove one or more PXE servers from the PXE Configuration Utility UI
search cancel

Remove one or more PXE servers from the PXE Configuration Utility UI

book

Article ID: 421144

calendar_today

Updated On:

Products

Ghost Solution Suite

Issue/Introduction

If a PXE server installed for Ghost Solution Suite is no longer used or needed, how can it be uninstalled and removed from the PXE Configuration Utility 'Servers' list in the GSS Console?

Environment

Ghost Solution Suite 3.3.x

Cause

There are no options in the PXE configuration utility UI to remove old PXE server entries from the 'Status' tab

Resolution

Step 1: If the 'Altiris PXE Server' component is still installed on the PXE server that needs to be removed from the PXE Configuration Utility, first log in to the PXE server with an administrator account and uninstall 'Altiris PXE Server' from 'Programs and Features'. If this is already uninstalled, continue to step 2.

Step 2: Log in to the GSS server with an administrator account or an account that has full rights to the eXpress share

Step 3: Stop all GSS related 'Altiris' services (Altiris PXE components, Altiris eXpress Server, Altiris DB Management service)

Step 4: Open File Explorer and navigate to the root of the eXpress share. By default the share is mapped to 'C:\Program Files (x86)\Altiris\eXpress\Deployment Server'

Step 5: Make a backup of 'default.cfg' file located in the eXpress share and save it in a different directory

Step 6: Open 'default.cfg' with a text editor (may need to run a text editor as administrator, then open the file)

Step 7: Scroll to the bottom of the .cfg file and find the section labeled '[PXEServers]'

Step 8: Remove unused servers by deleting the entry. Once desired entries are deleted, remove any blank lines left behind. Keep each PXE server entry on a separate line. Save and close the .cfg file

Step 9: Start GSS server services

Step 10: Open the PXE Configuration Utility and confirm the desired PXE server is removed from the 'Status' tab

If the steps above do not resolve the issue, follow additional steps documented in the KB below:

https://knowledge.broadcom.com/external/article?articleId=154088