Can someone share their insight on the following problem?
We have 6000 PCs spread across 7 local campuses via high speed WAN links. We currently use Altiris and will be migrating to SCCM over time. Our biggest management obstacle nightmare has been waking up machines. Our networking guys say that everything is wide open and there should be nothing blocking/hindering WOL. To their credit, it doesn't work, but it's very inconsistent. It doesn't matter what WOL utility we use (Altiris, mc-wol, Emco, etc) none of them are rock-solid-reliable. One day they work, they next they may not, it's random. Networking has insisted for years that it's not on them, the problem is on our end.
This has got to change. We simply must be able to wake up machines reliably to manage them effectively. Both on-demand and scheduled wake-ups are essential. This is all we need from AMT, nothing more.
1) With the following in mind, what is the least complex (not quickest) method to configure AMT?
- We are willing to touch every machine
- We'd like to avoid certificates unless someone can provide a great tutorial (lack of experience + Network team manages certificates)
- We need to be able to wake up machines for both SCCM and Altiris, using integrated commands, or some external mechanism
2) Can vPro work independently while integrated with SCCM?
3) Will AMT simply not work at all in SCCM if certificates aren't used?