Master/Golden image is running on Windows 2012 / Windows 2016 servers, VDA version 7.15 LTSR CU5 and Static IP assigned to it. We have deployed clone machines using this Master image. Servers were working fine from past 2years and DHCP has 30% free IP's available in the same VLAN. Suddenly from past 1 month Clone servers started getting dual IP's - 1 IP same as Master (Master and Clones get same IP address) and other one is APIPA IP on updating Machine Catalogs, both clone and Master has different MAC addresses. I logged into clone machine using local admin and noticed the NIC settings are same as Master (Static IP), if i change the NIC setting to Dynamic, clone server started working normally until it is rebooted. The only changes made on the Master server was installing MS security Patches. It is not related to OS specific as the same issue noticed on both Windows 2012 and 2016, not related to DHCP as issue noticed in multiple DHCP VLAN's.
1. Is there any article / recommendation like Master server should have DHCP alone enabled IP.
2. Is there any Microsoft patch which links to this issue.
3. We tried to remove the NIC card from clone machine and add new NIC from same DHCP but the same issue.
4. Created new Master image (with Static IP) and deployed new Clone servers, same issue.
Question
Arun Kumar K R
Hi All,
Master/Golden image is running on Windows 2012 / Windows 2016 servers, VDA version 7.15 LTSR CU5 and Static IP assigned to it. We have deployed clone machines using this Master image. Servers were working fine from past 2years and DHCP has 30% free IP's available in the same VLAN. Suddenly from past 1 month Clone servers started getting dual IP's - 1 IP same as Master (Master and Clones get same IP address) and other one is APIPA IP on updating Machine Catalogs, both clone and Master has different MAC addresses. I logged into clone machine using local admin and noticed the NIC settings are same as Master (Static IP), if i change the NIC setting to Dynamic, clone server started working normally until it is rebooted. The only changes made on the Master server was installing MS security Patches. It is not related to OS specific as the same issue noticed on both Windows 2012 and 2016, not related to DHCP as issue noticed in multiple DHCP VLAN's.
1. Is there any article / recommendation like Master server should have DHCP alone enabled IP.
2. Is there any Microsoft patch which links to this issue.
3. We tried to remove the NIC card from clone machine and add new NIC from same DHCP but the same issue.
4. Created new Master image (with Static IP) and deployed new Clone servers, same issue.
Anyone please guide me on this please.
Link to comment
1 answer to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now