![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Just trying to wrap my head around the imaging process of Kace......
We have K1000 pushing all software, 2000 pushes image. We use VM boxes for this, as we did not purchase the appliance.
Our network guy set it up so there is a reservation (7 ip addys) that we have to set for each asset we image.
I am used to IBM Bigfix where you pxe boot and somehow (not a specialist in either of these fields) Bigfix knew that once you boot from nic that means you want an image on it, so the GUI pops up for imaging.
Why would our network guy want us to load each individual asset's mac addy for a reservation when I am quite sure Kace can be set up to listen on boot from nic no matter the IP.
idk, just kinda trying to wrap my head around why this extra step (looking at each asset for its mac addy, giving it a reservation, then pxe boot).
Thoughts?
We have K1000 pushing all software, 2000 pushes image. We use VM boxes for this, as we did not purchase the appliance.
Our network guy set it up so there is a reservation (7 ip addys) that we have to set for each asset we image.
I am used to IBM Bigfix where you pxe boot and somehow (not a specialist in either of these fields) Bigfix knew that once you boot from nic that means you want an image on it, so the GUI pops up for imaging.
Why would our network guy want us to load each individual asset's mac addy for a reservation when I am quite sure Kace can be set up to listen on boot from nic no matter the IP.
idk, just kinda trying to wrap my head around why this extra step (looking at each asset for its mac addy, giving it a reservation, then pxe boot).
Thoughts?