Neither is acceptable, because you'll have to lunger around until the install starts from the right system. Say I provision one system it might install some Unix but it might even install some Windows or try if it could execute phone software written for MIPS. Setting unknown computer support to enabled and then relying on "has to press a key to have the system install" renders any boot and provisioning to something that might work or might not. WinPE would not be loaded and the new resource would never get registered. Since the mac address is not known to sccm it will never react on this dhcp boot request. This would not help: WinPE is loaded by PXE, initiated by dhcp. Before unknown computer support was added in ConfigMgr 2007 R2, this is exactly what we had to do. For this command, you'd have to create a script to register a new resource for the system on-demand. If not, then you'll have to use a pre-start command that runs in WinPE before the task sequence engine is initiated. If not possible via GUI - any commandline tool that could do? I'd like to have a way to change the mac address for clients on sccm. I'd like to only change this mac address and then be all set again!īoth of the other systems booting clients via network allow for such a change. And not by deleting the client and building a new one. I'd like to change this address within client configurations to make sccm match this client again. Sometimes this is virtualized hardware and this mac address changes. But for all of them I could turn off "unknown computer support" making them to react only to those requests to dhcp the servers are made known of.īut now I do have one real problem: sccm does not allow to change, as far as I could find, the mac address. All of them expect to be alone on the network, but this is not possible. One for Unixes, one for Windows and one for phones. This would enable it for all - and I do not want to say provision a system I do not control.Īt the moment there are three systems allowing to boot from. But just exact this could happen with unknown computer support enabled.
You do not await your device boot something quite different than you expected. These systems would try to boot what sccm then provides on a base of "whoever is faster". Enable unknown computer support will boot some systems dhcp is enabled, but they are waiting for some boot image from an other server not under sccm control.
0 kommentar(er)
