Random Strange DHCP Issue

[ITGURU]

I'm running SPECOPS GPupdate which integrated with AD which i use to bulk WOL machines on the network.

Been working perfect for years.

However, recently bought some refurb desktops and discovered a strange issue.

All machines setup in exactly the same way, but issue is as follows:

 

when the machine is switched on by hand it registers in DHCP and DNS as the correct name i.e TEACHERPC.domain.local pings ok work ok etc.

When the machine is shutdown, the DHCP lease is gone by the machines proper network/AD name and is replaced with some other DNS name i.e pc0875.domain.suffix.com presumably where the machines came from.

 

When this happens, Specops Gpupdate will not boot the machine, because it says 'computer not found in DHCP'

However, if i manually boot the machine, then run it again, it will show the machine is already runny.

 

I am unable to find anything in the BIOS that represents this old machine name.

 

The odd thing is If i select all the refurb machines, the majority will boot as the names show correct in DHCP but the odd ones won't boot because of the name mismatch/change in DHCP.

 

Anyone seen this before?

[Guest Guest]

I'm running SPECOPS GPupdate which integrated with AD which i use to bulk WOL machines on the network.

Been working perfect for years.

However, recently bought some refurb desktops and discovered a strange issue.

All machines setup in exactly the same way, but issue is as follows:

 

when the machine is switched on by hand it registers in DHCP and DNS as the correct name i.e TEACHERPC.domain.local pings ok work ok etc.

When the machine is shutdown, the DHCP lease is gone by the machines proper network/AD name and is replaced with some other DNS name i.e pc0875.domain.suffix.com presumably where the machines came from.

 

When this happens, Specops Gpupdate will not boot the machine, because it says 'computer not found in DHCP'

However, if i manually boot the machine, then run it again, it will show the machine is already runny.

 

I am unable to find anything in the BIOS that represents this old machine name.

 

The odd thing is If i select all the refurb machines, the majority will boot as the names show correct in DHCP but the odd ones won't boot because of the name mismatch/change in DHCP.

 

Anyone seen this before?

Is vPro enabled? You can set device names within that which would explain why the name is correct until it's shutdown

[ITGURU]

Is vPro enabled? You can set device names within that which would explain why the name is correct until it's shutdown

 

I did wonder if that was part of the issue - just haven't worked out where to find the settings yet! They were obviously not all reset in the same way.

[ITGURU]

All sorted now! Managed to do a ME reset through the BIOS!