Server loses fix IP after SEP-Update
We have an issue when updating the SEP-Client on servers. After the Update, we do the mandatory reboot and everything seems to work fine. But after another reboot (which may happen a few months later) the server loses his fixed IP-Address by creating a new network interface and switchting it to DHCP... We have been struggling with this for a few weeks now.
- Only happens on Windows Server 2003
- Happens on both 32 & 64 bit OS
- Virtualised in VMWare
- Happens with the built-in autoupdate of SEPM, as well as manual executing of the installpakage
- There are no open RDP-sessions, no open Shared Files-sessions and no other logged in users during update
- Updating from 11.0.X to 12.1.1000
I was able to reproduce this error:
Network connection before update:
After the completion of the Update, a reboot is requested:
After the reboot is done, SEP is green and looks fine, but the Network connection already changed. Notice that now it's called "Local Area Connection 2". The IP in cmd is still correct though:
Next I reboot again and the server loses it's fix IP. I get the following messages when trying to set the fix IP-address again:
After this the server is back online, but this is kind of ugly.
Any information about why this happens is greatly appreciated.