Again I haven't done an integration of SCS 9 with CM12 R2 so it's possible that has changed, but in previous versions you could set the "Enable WOL" in the site settings and in packages however it wouldn't actually power on the devices if you didn't provision with SCCM. Basically if you provision with SCS and integrate with SCCM then you are limited to the functions in the OOB console. I'll do some more research though to see if that has changed. unless someone on the list has tested this.
When you integrate SCS with SCCM it will automatically create some task sequences for you for provisioning, maintenance, and discovery. These are basically just using acuconfig.exe (which is part of the SCS installer) with some command line parameters. I think the maintenance is set to once a month by default, but it's really dependent on your environment and how frequent IPs change. IMSS should be a part of your imaging process. It can technically be installed at any time, but it's the mechanism that allows the OS to communicate and update the vPro chip so if it's not there then the maintenance and discovery tasks will fail. You also can't write to the 3rd party data store if you have any use cases that utilize that feature. From: [email protected] [mailto:[email protected]] On Behalf Of Mattias Benninge Sent: Wednesday, February 5, 2014 10:04 AM To: [email protected] Subject: Re: [mssms] RE: OT: VPro How do you mean that it is misleading around WOL, will it only work for 8.x and lower or for no AMT systems? This feature is one of the requirements for us.. Already got a SAN cert so hopefully that bit will work at least. What is the "acuconfig maintenance tasks" and how often is periodically? Should the IMSS be installed after the system is provisioned or only after? Tnx for the tips, hard to find good information around this topic.
