So here is the situation I have run into,
I tried capturing an image using the automation partition. The computer was off of the domain when this happened. When the automation partition loaded, somehow it failed/crashed and rebooted the machine into windows. Now when windows comes up I get a 169.254.***.*** ip address which acts like it cant see the DHCP server.
I know the cable is working and I know the NIC is working (it works fine if i set a static IP)
I have rebooted the computer probably 50 times, removed the automation partition, flusheddns, (cant renew or release IP because there is not a dhcp server contacted)
I contacted Support and I spoke with one person who told me several times that it does not use any kind of 169 address. He also had another person on the call tell me the same thing,
My question is has anyone else had this issue regarding the automation partition? I have contacted Symantec and they dont think it has anything to do with their automation partition (but they said it doesnt work very well and that I should use the PXE Server) I know the Automation partition uses some kind of 169.254 addressing as you can see it when it loads up.
Attached is a picture of the automation partition when it is loading up with the 169. address.
One additional thing, I know that the automation partition is connecting with the Ghost server as I can pull images and send them,
Anyone have any thoughts or experienced this?
