On Tue, Feb 4, 2014 at 4:33 PM, Wood, Sandy <[email protected]> wrote:
Wouldn't you lose the SCCM Console functionality and WOL part if you provisioned vPro clients outside of SCCM? not any more, but they do have to use tcl or sccm will not "see" them. On Wed, Feb 5, 2014 at 8:08 AM, Outlook <[email protected]> wrote: > I think that post is a little misleading around the WOL part, but > hopefully I'm wrong since I haven't implemented with SCS9 and CM12 R2. When > you use SCS to provision and SCCM to manage you only get the Kerberos > enabled pieces which are found in the OOB console so you should be able to > set the alarm clock feature in AMT5.1 and above, but I don't think you get > the true WOL feature in your advertisements that is expected. Otherwise yes > you get KVM, IDER, and Power control in a one to one scenario which is > enough for most. > > > > Some gotchas I've found: > > Certs: If you have more than one root domain you'll need multiple certs > for each domain or a SAN cert from one of the supported vendors. > > > > Network: Make sure your network folks configure option 15 and option 81 > > > > Post Provisioning: Make sure you have Intel Management and Security Status > (IMSS) installed on your systems. By default you will most likely have the > AMT driver which will allow you to provision, but not the software driver > for the OS to communicate with the chip. You need to run acuconfig > maintenance tasks on the systems periodically so they update the chip with > the correct IP address. Then when you run a discovery that information will > get updated and you can keep a happy healthy environment. Otherwise in time > your SCS console will fill up with un-configured systems which you'll have > to re-provision to force the update. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Mattias Benninge > *Sent:* Wednesday, February 5, 2014 7:44 AM > *To:* [email protected] > *Subject:* Re: [mssms] RE: OT: VPro > > > > Seems like you shouldn't loose any functionality if integrated with SCS > according to this: > > > http://sccmguru.wordpress.com/2013/12/20/integrating-configuration-manager-2012-r2-with-intel-scs-9-0-part-1/ > > > > We are about to implement vPro as well and are planning on using a > certificate to provision. Any do and donts are appreciated :D > > > > > Regards > > Mattias Benninge > > http://myitforum.com/myitforumwp/author/matbe/ > > > > > > On Tue, Feb 4, 2014 at 4:33 PM, Wood, Sandy <[email protected]> > wrote: > > Wouldn't you lose the SCCM Console functionality and WOL part if you > provisioned vPro clients outside of SCCM? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Kent, Mark > > *Sent:* Tuesday, February 4, 2014 6:31 AM > > > *To:* [email protected] > *Subject:* [mssms] RE: OT: VPro > > > > Well, correct me if I am wrong but couldn't you technically provision them > without have a cert? It would seem, according to Intel's information, that > you could do the "Host" based provisioning and use SCCM to deploy the > provisioning EXE along with the XML file. Or am I missing something here? > > > > Mark Kent (MCP) > > Sr. Desktop Systems Engineer > > Computing & Technology Services - SUNY Buffalo State > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *[email protected] > *Sent:* Monday, February 3, 2014 4:45 PM > *To:* [email protected] > *Subject:* [mssms] RE: OT: VPro > > > > Way to much work to implement... > > > > Unless you already have a full PKI in-place. > > > > *Christopher Catlett* > > Consultant | Detroit > > *[image: MCTS_2013_small]* > > > > *Sogeti USA* > > Office 248-876-9738 |Fax 877.406.9647 > > 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 > > www.us.sogeti.com > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Kent, Mark > *Sent:* Monday, February 03, 2014 4:41 PM > *To:* [email protected] > *Subject:* [mssms] OT: VPro > > > > Just curious as to who is using this and whether they love it or hate it. > Doesn't seem to be discussed much. Thanks! > > > > Mark Kent (MCP) > > Sr. Desktop Systems Engineer > > Computing & Technology Services - SUNY Buffalo State > > > > > > > > > > > ------------------------------ > > > CONFIDENTIALITY NOTICE: This communication with its contents may contain > confidential and/or legally privileged information. It is solely for the > use of the intended recipient(s). Unauthorized interception, review, use or > disclosure is prohibited and may violate applicable laws including the > Electronic Communications Privacy Act. If you are not the intended > recipient, please contact the sender and destroy all copies of the > communication. > > > > > > > >
<<image001.jpg>>
