Site Server fails to finish an Image Job - Stays at Winpe screen
I am having an issue with two our remote sites where we send an image job to a machine and it boots to winpe and images the machine but will not do the driver management and then boot back to production.
I rebuilt the site server recently in an attempt to rule it out as the cause. I don't believe it is the site server causing this. There is a breakdown in communication from the site server to the client in the winpe environment that is not processing the job completely.
On our main campus we have two site servers and they work fine, with imaging clients. This only happens with our site servers that are in remote citys.
What command line tools can I use to examine where it is getting a job and or examine ports that it is is using.
What ports is winpe using in communication with task/package server to process the Drivers and sending the client back to production once the PECAgent is done processing.
Any assistance would be greatly appreciated.