- PXE MANAGER FOR SYMANTEC GHOST 3.1 NOT WORKING FULL
- PXE MANAGER FOR SYMANTEC GHOST 3.1 NOT WORKING SOFTWARE
This will prompt for a reboot, which is needed for these changes to take place.Īfter reinstallation of PXE is complete you will want to go back into msconfig and re-enable all of the services and startup programs that were previously disabled, and then reboot the server one last time. Then go to the Startup tab and click on Disable All. Go to the Services tab, check the box that says Hide all Microsoft services, and then click on Disable All. This can be done by running Start > Run, type in "msconfig".
PXE MANAGER FOR SYMANTEC GHOST 3.1 NOT WORKING SOFTWARE
You can remove any possible other software conflicts by first completely un-installing PXE Manager and PXE Server (as per the above knowledgebase article), but then before reinstalling disabling all other software temporarily. In this case it was found that other software on the system was conflicting with the install.
PXE MANAGER FOR SYMANTEC GHOST 3.1 NOT WORKING FULL
In some cases even after a full and complete reinstall the issue can persist. When this occurs you will generally need to reinstall the PXE Manager and PXE server. When the above steps do not resolve the issue, and the PXE Manager log file does not show any failures or errors, then the installation most likely was corrupted or not completed successfully. Once the PXE Configuration Utility opens successfully, choose the Data Logs tab and disable logging. (See the linked article 19228.) This utility will show if the keys are matching or not, and it can also regenerate the MMAccessKey.ini file if they are not matching.ĭelete the PxeLog_Manager.Txt file on the Deployment Server before trying to open the PXE Configuration Utility. You can also verify that this is the cause with the PXE key match utility. If in the PXE Manager log file (which can be enabled in the PXEManager.ini file) it shows "failure" after an authentication, then this is most likely the cause. ini file and find the entry "DSServerPort." Change this value to equal the value of the " TCP Port" in the Altiris Deployment Server Control Panel applet.įirst you need to determine if the problem is truly being caused by the MMAccessKey not authenticating correctly with the Deployment Server. This will avoid any timeout issues from occurring after restarting the services.
If the " Connection" options are used to allow or block any IP's or subnets they check to make sure that the DS is allowed, not blocked or rejected based on subnet or IP address this will cause PXE Manager to not fully function.Ĭause 3: The MMAccessKey (Middle Man Access Key) is not correctly authenticating to the Deployment Server security key.
The Altiris PXE Manager service requires a connection to the Deployment Server axengine on TCP port 402.
This can also be caused by timeout issues when the two services take an excessive amount of time to connect.Ĭause 2: The port that the Axengine uses to accept communications has been changed from the default of 402, and the PXE Manager is still trying to connect to the server on port 402. This communication issue can be caused by the "Allow encrypted sessions" being disabled in the Deployment Server Control Panel applet. Cause 1: The Altiris PXE Manager service is not able to communicate with the Altiris Deployment Server DB Management service.