Home > Intel Communities > Open Port IT Community > Intel® vPro™ Expert Center > Activation > Documents
Currently Being Moderated

Discovery Checklist for Microsoft SCCM

VERSION 7

Created on: Jan 27, 2009 12:41 PM by Gary Szolnoki - Last Modified:  Aug 7, 2009 1:00 PM by Kelsey Witherow

 

Use this checklist to start gathering the information required for deploying Intel® vPro™ technology in your enterprise.

 

 

Customer Contact Information

Name

Date

Company

Phone

Address

Email

City, St Zip

Country

 

Intel Contact Information

BDM / EAM

Email

Region/District

Cell Phone

ETS

Email

Region/District

Cell Phone

 

Intel Technical Resources Assigned (after approval)

Project Lead

Email

Technical Lead

Email

Use Case Scenarios

It  is important to identify early in the activation of vPro technology the most  relevant use case scenarios. Please  prioritize the list below if more than one.

Prioritize using  the numbers 1-7

Software used for  this function

Remote  Asset Inventory

Hardware & Software Inventory

Remote Diagnostics and Repair

Remote power on and update (Encrypted)
Off-hours Software Update and Patch Management

Other (please explain)

 

Current Inventory of  vPro™ Systems

How many vPro desktops do you plan to have deployed in the next 12 months?

At what rate are you deploying? (e.g. 100/week)

How many vPro desktops are on hand, ready to be “activated”?

How many are already on customer desks?

How many are in a staging area? Specify where (reseller, customer, etc)

Are those vPro desktops that have been placed into service in one location or multiple locations?  (number of primary sites)

Which hardware manufacturer produced the vPro desktops?

Make, model, etc. of systems

AMT version:

FW (BIOS) version:

How many vPro notebooks do you plan to have deployed in the next 12 months?

At what rate are you deploying? (e.g. 100/week)

How many vPro notebooks are on hand, ready to be  “activated”?

How many are already on customer desks?

How many are in a staging area? Specify where (reseller,  customer, etc)

Are those vPro notebooks that have been placed into  service in one location or multiple locations? (number of primary sites)

Which hardware manufacturer produced the vPro notebooks?

Make, model, etc. of systems

AMT version:

FW (BIOS) version:

Are your vPro systems procured directly from the OEM, or through a VAR?

Are your vPro systems shipped directly to a user at a deployment site, or sent to a central location first?

 

Microsoft Account Status

Do you have a Microsoft Premium Support Account?

How much of your account has already been expended?

If you have Premium support, who is your Technical Account Manager (TAM)?

Name:

Email:

 

Microsoft SMS  / SCCM
Are you upgrading from Microsoft SMS to SCCM (only answer yes if you are actively using SMS today – many customer own SMS but have never deployed into production)?
Microsoft SMS

What version is installed at the client\customer?
SMS v3.0 is the current supported version with the Intel SMS plug-in.

What service pack level is currently installed?

Was the Intel SMS Add-on implemented?

If yes, what version?

Was the Intel Setup & Configuration Service installed?

If yes, what version?

If yes, was this service installed on a virtual machine (i.e. VMWare)?

If yes, how many vPro systems have been provisioned with SCS?

Microsoft SCCM

Will/Is SCCM deployed on Windows 2008 64-bit or 32-bit or Windows 2003 32-bit or 64-bit?

How soon will client\customer look to implement Microsoft SCCM

Will SCCM agents be deployed at the same time to all your client systems?

Would all the Desktops/laptops be managed by one SCCM Primary Site? If not, please  provide planned deployment model.

Would SCCM be managing AMT machines in cross domains?

 

Client OS Deployment

Which Operating System (OS) do you plan to deploy with your new vPro™ desktop and/or notebook systems?

Service Pack Level?

What is the complete server OS that will be used for ISV console/provisioning?

Are your clients configured with DHCP or Static IP addresses?

Will all vPro clients be a member of your Domain (no workgroup only systems)?

Are there any provisioning/image management tasks performed on the systems before they arrive on site?

Does your client imaging process allow for additional steps past the initial  imaging?

Do you use an IT outsourcer (ITO)?

If yes, which ITO?

 

Application Security  and Authentication Methodology

Do you currently use encrypted communication in your network?

Do you have any issues with the firewall settings or opening certain ports on  your routers and clients for communications? (Ports 16992 – 16995, 9971,  56666)

Do you use an Enterprise Certificate Authority in your Enterprise?  If Enterprise - please provide hierarchical deployment  with SCCM integration? (consult with your PKI team)

If yes, which one? (e.g. Microsoft Enterprise CA)

If not, are there plans to implement a PKI solution in the future?  If so, when?

What  size is your certificate key (1024, 2048, 4096-bit)? For you Root and any subordinate CAs?
Are their security policies that permit you from using a digital certificates from commercial CA's (VeriSign, GoDaddy, Comodo, etc)?,
If not, what commercial CA do you use and can you use others not used today?e

Would you have any problems creating a separate OU in each domain for AMT objects  to be stored?

Do you have a multi-tiered AD Forest or multiple Domains?

Do you use hard disk drive encryption software? Vendor/version?

Do you implement either a BIOS or Hard Disk password (power on)?

 

Network Topology

Do you currently support any of the following in your managed network today:

NAT (network address translation)

NAC (network access control)

NAP (network access point)

802.1x authentication / encryption

If yes (for 802.1x), is it a requirement for the LAN or WLAN

Do you want vPro to work across VPN?

For vPro notebooks – which wireless access points are used in your network infrastructure?  (please list brand and model)

When do you plan to support 802.11n?

What is your wireless protocol?

 

 

Domain Name Services  (DNS) & DHCP

Does your domain end with .com/.net or others - please provide details for domain?

Do you have multiple network domains (i.e. US.Intel.com and UK.Intel.com)?  Please list.

If multiple domains exist, how many will have vPro systems?

Is your Domain name registered and owned by your company (e.g. as listed in WHOIS)

Do you have a mixed client environment (Windows & Unix/Linux) that requires  Secure DNS registration?

Can you configure your DNS to include a static entry for the Provisioning Server?

Is your DHCP server allowed to insert “A” or “PTR” records in DNS on the  clients’ behalf?

Does your DHCP server support Option 15 (Insert DNS suffix) when providing a  client IP address?

What is the current Option 15 setting in your DHCP server?

What type of DNS/DHCP technology do you have (Microsoft, Bind or some other  flavor)?

Are clients managed by one DHCP or multiple DHCP servers with different scopes?

 

Return on Investment

Would you be willing to collaborate with Intel to determine the cost savings and/or  productivity gains realized by the following vPro features?
Sample ROI questions are included at the end of this document.

Yes

No

Reduced Power  costs by turning off systems after hours and performing reliable power on and  software updates, patches, or inventory scans

Improved  productivity by performing remote diagnostics and repair (reduced desk side  visits).

Cost savings realized by having an accurate hardware and/or software inventory

Other (please specify)

 

Key Customer Contacts

It is imperative that all key contacts, listed below, attend both the Workshop and Activation events. It is recommended that the Activations team postpone these meetings if it is apparent that full attendance will not be achieved.

 

Customer Contacts

Name

Phone  #

Email

Client Operations Support

Enterprise Infrastructure

Network Infrastructure (DNS, DHCP, Wireless, etc)

Security Infrastructure

Executive  Sponsor
Senior IT Manager (Title)

Systems Management Infrastructure

Directory Infrastructure

 

Ecosystem Technical Contacts

Name

Phone  #

Email

Management Console Software Vendor (ISV)

OEM/Computer Mfg.

IT Service Provider
(if applicable)

Computer Reseller
(if applicable)

Glossary

Inventory of vPro™ systems

Used to determine whether the customer has enough vPro systems in a location that allows adequate provisioning and then testing.  If the customer has already sent the equipment to multiple sites without the correct provisioning, a deskside visit will be required to fully enable. (Activation Program minimum is 100 or more PCs into customer production environment.)

 

Management Console

Determine if the customer has the correct software version and sufficient licenses in place to cover the Activation Program deployment.

 

OS Deployment

Ensure customer is deploying an operating systems that is supported

 

Authentication Methodology

Since vPro™ systems take advantage of encrypted management traffic, we want to determine the customer’s security requirements and which Certificate of Authority (CA) they use.

 

Use Case Scenarios

We’d like to know which use cases they plan on deploying so we can gauge the amount of time required for the support plan.  This is not a wish list, but a reality check.  If possible, please prioritize the use cases, 1 being most important.

 

Network Topologies

There are certain topologies that vPro™ technology does not currently support.  These questions determine if the customer already supports these fairly new topologies

 

Miscellaneous

If the customer uses an IT Outsourcer, we like to know who they are.  They’ll likely list some of their names in the contacts section if they use an ITO.  They may need to be involved in activation if they provide PC support services.

 

Contacts

For a successful activation, we will need to talk to various people in their organization.  It’s important to understand that various parts of the IT infrastructure will be touched depending on what type of integration is requested. We also want to capture the ISV and OEM Technical contacts too. Computer Reseller technical contact only needed if they provide software image/preload or installation services.

Attachments:
Average User Rating
(6 ratings)




There are no comments on this document

More Like This

  • Retrieving data ...