- 15
- 3
- 3
Good day all,
I have an issue which is extremely weird. In our environment , we have some sites that likes to PXE boot to rebuild a pc without removing the name from SCCM and AD. I do not like this process but it is not my call.
Scenario :
Workstation with name PC123 is already a working pc but need to get reloaded. PC gets PXE booted and gets an IP and starts - No issues here
Issue is, in our DHCP Scope PC123 got IP 1.1.1.1, but a previous computer that was PXE booted , PC789 also had IP 1.1.1.1 ( DHCP lease is only 1 day BTW).
During the process of PXE, PC123 gets joined to the domain with name PC789 and not it current name PC123, which is a problem as each pc has an Asset tag with its name.
Hope the above make some kind of sense.
Questions I have :
1. Why did it get renamed with a new name instead of the one it already had?
2. Does PXE get the name from DNS when reloading a pc that has not been removed from SCCM and AD?
Thanks and regards
I have an issue which is extremely weird. In our environment , we have some sites that likes to PXE boot to rebuild a pc without removing the name from SCCM and AD. I do not like this process but it is not my call.
Scenario :
Workstation with name PC123 is already a working pc but need to get reloaded. PC gets PXE booted and gets an IP and starts - No issues here
Issue is, in our DHCP Scope PC123 got IP 1.1.1.1, but a previous computer that was PXE booted , PC789 also had IP 1.1.1.1 ( DHCP lease is only 1 day BTW).
During the process of PXE, PC123 gets joined to the domain with name PC789 and not it current name PC123, which is a problem as each pc has an Asset tag with its name.
Hope the above make some kind of sense.
Questions I have :
1. Why did it get renamed with a new name instead of the one it already had?
2. Does PXE get the name from DNS when reloading a pc that has not been removed from SCCM and AD?
Thanks and regards