IntelSBA OEM Guide
IntelSBA OEM Guide
Version 1.0
Document Release Date: January 23, 2012
UNLESS OTHERWISE AGREED IN WRITING BY INTEL, THE INTEL PRODUCTS ARE NOT DESIGNED NOR
INTENDED FOR ANY APPLICATION IN WHICH THE FAILURE OF THE INTEL PRODUCT COULD CREATE A
SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR.
Intel may make changes to specifications and product descriptions at any time, without notice. Designers
must not rely on the absence or characteristics of any features or instructions marked “reserved” or
“undefined”. Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts
or incompatibilities arising from future changes to them. The information here is subject to change without
notice. Do not finalize a design with this information.
The products described in this document may contain design defects or errors known as errata which may
cause the product to deviate from published specifications. Current characterized errata are available on
request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing
your product order.
Copies of documents which have an order number and are referenced in this document, or other Intel
literature, may be obtained by calling 1-800-548-4725, or go to: http://www.intel.com/design/literature.htm
Any software source code reprinted in this document is furnished under a software license and may only be
used or copied in accordance with the terms of that license.
Intel, Intel vPro, and the Intel logo are trademarks of Intel Corporation in the U.S. and other countries.
Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft
Corporation in the U.S. and/or other countries.
2 Prerequisites.................................................................................................................................... 8
Firmware
The advanced functionality provided by Intel SBA is defined in the Firmware of the Intel
chipset. The Firmware is the software that controls the Intel ME. For more information, see
Firmware Functionality.
Supported
Type of Firmware Description
by Intel SBA
If the power scheme is changed, the service cannot wake-up the computer from Sx power
states. In this release of Intel SBA, when the service starts it checks that the power scheme
is set to SCHEME 1. If the power scheme is incorrect, the service sends a warning message
but does NOT reconfigure the power scheme in the Firmware.
By default, the Intel ME is in an unconfigured state. Before the hardware capabilities of the
Intel ME can be used by Intel SBA software, the Intel ME must be configured. This is done in
the Settings > Password Settings tab in the main menu of the GUI. The first time that the
Save button in the Settings window is clicked, the Intel ME is configured with the hardware
functionality of Intel SBT. This will usually be done by the end user when they want to start
using Intel SBA (so that they will know the password).
Clicking Yes configures the Intel ME with the hardware functionality of Intel SBT.
Intel AMT is the Firmware component included with Intel® vProTM systems. Intel AMT includes
additional functionality used by enterprise organizations. The additional functionality of
Intel AMT is not used by Intel SBA.
When an Intel vPro system is configured by Intel SBA, the Intel ME is configured with the
hardware functionality of Intel SBT only (see Firmware Functionality). This means that all Out
of Band functionality is blocked.
If you want more information about Intel AMT, refer to the Intel AMT documentation located
on the Intel Manageability website (click here).
• Application Manager – The main Graphical User Interface (GUI) of Intel SBA that lets
users configure the settings and applications they want to use in their business.
• Service – A Windows service that runs in the background and provides communication
between the Main GUI, the Applications, and the Firmware.
• Applications – Intel provided applications that provide useful features for the small
business. For more information, see:
• Software Monitor
• PC Health Center
• USB Blocker
• Energy Saver
The Software Monitor application detects and monitors security-related applications that are
installed on the computer. If a monitored application is disabled or attacked, Software
Monitor sends an alert to tell the user that something has occurred. The user can define
which applications to monitor and how they want to be notified.
The monitoring and reporting mechanism are located with the hardware, and are
independent of the operating system. This gives more security because it is harder for a virus
to attack a monitored application without leaving a trace of the attack.
• Norton 360*
You can use the customization wizard to define additional applications that Software Monitor
can monitor.
The PC Health Center application lets the user quickly and easily schedule all maintenance
tasks to run outside business hours when the computer is not being used. The user can
define which tasks to run and when to run them. If the computer is turned off, the
PC Health Center application will wake up the computer and run the scheduled tasks. (The
computer must be plugged in to a power source. For automatic software updates, an internet
connection is necessary.)
PC Health Center uses the hardware-based functionality of the Intel SBA to wake up the
computer if it is turned off. After configuration, the tasks will automatically run at the
scheduled time with no user intervention necessary.
• Windows* updates
• Disk defragmentation
You can use the customization wizard to define additional tasks that PC Health Center can
schedule.
Computers in a small business need protection from possible security threats caused by the
increased use of USB ports and USB devices. Controlling access to these ports can increase
security. For example, controlled access can:
• Prevent valuable business data from being removed, copied, or even stolen
from the business
• Prevent viruses from being brought into the business on USB keys
The USB Blocker application lets the user quickly and easily define which USB devices can
connect to the computer. The user can define which categories of USB devices to block, and
also define a whitelist of specific devices that are always allowed.
Small businesses must make sure that business data is backed up frequently. But, users often
defer backing up during business hours. Then if they power off their computer overnight, no
backup can occur.
• Launch the Microsoft Backup and Restore application from the Intel SBA GUI
• Schedule the backup to run outside of the regular business hours. If the computer is
turned off, Intel SBA will wake up the computer so that the backup can run. (The
computer must be plugged in to a power source.)
Data Backup and Restore uses the hardware-based functionality of Intel SBA to wake up the
computer if it is turned off.
The Energy Saver application lets the user quickly and easily set a power schedule for the
computer. The computer can be powered down (put into the sleep state) at the end of
business hours, thus saving energy costs. In addition, the computer can be powered up just
before the beginning of business hours, thus improving productivity.
Energy Saver uses the hardware-based functionality of Intel SBA that can “wake-up” a
computer even if it has been shut down. After configuration, the computer will continue to
power up and power down at the scheduled times with no user intervention necessary. (But
the computer user can cancel the power down operation and adjust the schedule when
necessary.)
Note: The Intel® Management Engine software kit must be installed. (The Local Manageability
Service and the Intel® Management Engine Interface must be installed and running.)
Note:
• Although validation was done only on these operating systems and versions, Intel SBA
should also work correctly on other Windows 7 versions.
• Intel SBA also requires Microsoft .NET Framework version 3.5 or higher installed on the
computer. This is usually included in the supported operating systems.
To prevent this, make sure that you do NOT select the Never check for updates option
when installing the Windows operating system.
• Disk defragmentation
Instead, let the end user set the schedule for all these tasks via PC Health Center.
Note:
The time and date set for these tasks via PC Health Center will replace any setting that
was set outside of PC Health Center. There are exceptions to this behavior:
• Setting a schedule in the Windows Backup and Restore application, adds the “Windows
Backup and Restore” task to the list of tasks. This occurs even if the PC Health Center
application is not configured. If the Intel ME is configured, an alarm clock is also set.
• Setting a schedule for the Disk Defragmentation task in PC Health Center does not
change any setting that was set in the Windows Disk Defragmenter application. This
means that two independent schedules could exist for this task. The computer will only
wake up for the schedule set via PC Health Center.
1. Prepare a computer that includes all the hardware and software that will be included in the
computer when it is sent to the customer (or Reseller).
5. Make sure that all the XML files are signed (see Signing the XML Files).
• All the changes that you made with the customization wizard are shown
correctly in the GUI
Note:
When you open the GUI, you are asked to accept two license agreements. These
license agreements are for the end user. After testing is complete, you must reset
these licenses (see Resetting the End User Licenses).
7. Prepare the completed and customized Intel SBA installation for deployment on multiple
computers (see Copying an Intel SBA Installation).
3. Double-click Setup.exe.
Note:
The installer also supports “Silent” install. This is the syntax: Setup.exe –s
2. From the Control Panel, select Intel® Small Business Advantage (or the new name if
the product name was changed) and click Uninstall.
Note:
• When you uninstall from the Control Panel, a copy of the Setup.exe file containing
the installation settings is used. This file is located in the Uninstall folder in this
location: Program Files\Intel\Intel(R) Small Business Advantage\Uninstall. This file
can only be used from the Control panel, or from a command prompt. If you
double-click the file, an error message is shown.
• This is the syntax if you want to uninstall Intel SBA from a command prompt:
Setup.exe -uninstall.
3. (Optional) By default, uninstall deletes the data files used by Intel SBA. If you do not want
to delete these files, clear the Delete data files check box.
Note:
This window opens even if you did not configure Intel SBA, or configured with a blank
password.
5. Type the password and click Next. (Or just click Next.) The installer starts the
uninstallation and the Uninstallation Progress window opens showing the progress of the
uninstallation. When uninstallation is complete, the Next button is enabled.
6. Click Next. The Uninstallation Is Complete window opens. By default, the installer will
restart the computer when you click Finish. If you want to restart the computer at a later
time, select No, I will restart this computer later.
Note:
To complete uninstallation, the computer MUST be restarted. If you reinstall Intel SBA
without first restarting the computer, the new installation cannot be uninstalled from
the Control Panel. This is because Intel SBA will not be listed in “Programs and
Features” and the Uninstall folder is deleted during reboot after the new installation.
7. Click Finish. The installer closes and the computer restarts (if you did not select to restart
it later).
Note:
All content referenced by the customization wizard must be pre-installed on the target
system. Before starting the wizard, make sure that:
• All applications, files, and icons that you want to use in the customized
Intel SBA are installed in their final installation location.
• All the final installation locations are accessible to all users of the computer. If
a user does not have permissions in a location, the content will not be
displayed correctly in the GUI.
In the customization wizard, make sure that you load applications, files, and icons, from
their final installation location. The wizard creates paths for the loaded content based on
the location from where you loaded them. The GUI uses these paths to load and display
the content. If the path is incorrect the content will not be displayed correctly in the GUI.
2. Close the GUI by right-clicking the Intel SBA icon in the notification area of the taskbar and
selecting Exit.
3. Copy the OEMWizard folder (including all content and subfolders) to the computer.
6. Click Next and follow the instructions in the windows of the wizard. This table gives a brief
description of what you can define in each window.
7. The SETUP COMPLETE window is the last window of the wizard. When you get to this
window, do one of these:
9. If you changed the product name, press F5 to refresh the desktop. This action is necessary
to update the name and icon of the shortcut to Intel SBA.
10. Open the GUI and make sure that the settings you defined with the wizard are shown
correctly in the GUI.
Window What
Tasks added in a previous run of the wizard are shown in the list of
tasks. If you add tasks, a new XML file is created for those tasks.
You cannot use the wizard to remove tasks added in a previous run.
PC HEALTH CENTER If necessary, you must do this manually by deleting all the XML files
that begin with “HealthCenterData” and include numbers.
For example: HealthCenterData376604851.839805.xml
Note: DO NOT delete this file: HealthCenterDataIntel.xml.
Applications added in a previous run of the wizard are shown in the
list of applications. If you add applications, a new XML file is
created for those applications. You cannot use the wizard to remove
applications added in a previous run.
SOFTWARE MONITOR
If necessary, you must do this manually by deleting all the XML files
that begin with “SoftwareMonitorData” and include numbers.
For example: SoftwareMonitorData376604862.990606.xml.
Note: DO NOT delete this file: SoftwareMonitorData DataIntel.xml.
Custom applications added in a previous run of the wizard are NOT
shown in the list of applications. If you add applications, a new XML
file is created for each application.
CUSTOM APPS If necessary, you must do this manually by deleting all the XML files
that begin with “UiApplicationsData” and include numbers.
For example: UiApplicationsData376604914.190804.xml.
Note: DO NOT delete this file: UiApplicationsDataIntel.xml.
Note:
When deleting an XML file, you must also delete all the copies of the file in the language
subfolders.
Intel SBA automatically checks the locale ID in the operating system and loads the relevant
language files for each user. Some of these files are XML files located in this folder and its
language subfolders: C:\ProgramData\Intel\Intel(R) Small Business Advantage.
When you run the customization wizard, additional XML files are created. Some of these XML
files include text that you defined in the customization wizard. The wizard automatically
creates 16 copies of each of these files:
• One copy in each of the 15 language subfolders (for example: de-DE). For these files, the
name of the language folder is added to the end of the filename.
For example: UiSettingsData.de-DE.xml.
It is necessary to edit the text values of the files in the language folders with translated
values for each language. (Except for the language folder containing the language that was
used to define the values in the customization wizard.)
• Custom Applications
• Other Translations
Note:
• Make sure that you only edit the values of the tags described in the sections above. If
you edit other tags or files, Intel SBA might not operate correctly.
• After editing the XML files, you must re-sign them (see Signing the XML Files).
You can force Intel SBA to always start in a specific language of your choice by adding the
“-lang” argument to the desktop icon, the start menu icon, and the Registry. The “–lang”
argument has one parameter that defines the language. Valid values for this parameter are
the “Folder Name” of the language (see the table in Supported Languages and Locale IDs).
For example, adding this argument and parameter will cause Intel SBA to always start in
Spanish:
-lang es-ES
3. Right-click IntelSBA and select Modify. The Edit String window opens.
4. Add the lang argument and the desired language value, as shown in this example.
6. Restart the computer. After the computer has rebooted, wait a few minutes until the icon is
shown in the system tray. Open the application and check that the language in the GUI is
the language you defined in step 4.
2. In the Target location field, add the lang argument and the desired language value, as
shown in this example. To check that the GUI opens in the correct language, stop the
service and then double-click the icon.
Example
<HealthCenterTaskData>
<Name>Example Task</Name>
<GUID>c03dc9e7-06b8-4430-be61-ab9c9b7b20d2</GUID>
<RecommendedRunInterval>Daily</RecommendedRunInterval>
<ExecutionCommandPath>C:\ExampleTask.bat</ExecutionCommandPath>
<TaskType>WindowsTaskScheduler</TaskType>
</HealthCenterTaskData>
Example
<SoftwareData>
<ExecutableName>example.exe</ExecutableName>
<GUID>1f7265af-ed77-406c-b12e-6929389d2caf</GUID>
<ExecutableType>Process</ExecutableType>
<ApplicationName>Example Application</ApplicationName>
<Ignore>false</Ignore>
</SoftwareData>
Example
<Application>
<ApplicationName>Example Custom Application</ApplicationName>
<GUID>34d29d21-7608-41a3-b7e7-dad7a8e9fcfb</GUID>
<LaunchCommand>C:\CustomApplication.exe</LaunchCommand>
<LaunchCommandArguments>-someargument</LaunchCommandArguments>
<ApplicationIconFullPath>file:///C:/customicon.png</ApplicationIconFullPath>
<Description>Description for the custom application</Description>
<DescriptionImageFullPath>file:///C:/image</DescriptionImageFullPath>
<DescriptionLinkUri>http://customappwebpage.com</DescriptionLinkUri>
<DescriptionLinkText>Click here for more information</DescriptionLinkText>
</Application>
This table describes the tags that you might need to translate (in each file):
Tag Description
<ApplicationName> Contains the name of the application
Contains a description for the application that is shown
<Description>
in the status panel when the application is selected
Example
<BackgroundColor>Light</BackgroundColor>
<ProductName>ACME Corp</ProductName>
<DesktopIconFullPath>C:\CustomProgram.ico</DesktopIconFullPath>
<TrayIconSuccessFullPath>C:\TaskTray1.ico</TrayIconSuccessFullPath>
<TrayIconWarningFullPath>C:\TaskTray2.ico</TrayIconWarningFullPath>
<TrayIconErrorFullPath>C:\TaskTray3.ico</TrayIconErrorFullPath>
<OemLogoFullPath>file:///C:/OEMlogo.png</OemLogoFullPath>
<ResellerLogoFullPath>file:///C:/Resellerlogo.png</ResellerLogoFullPath>
<ContactDetails>
<CompanyName>ACME Corp</CompanyName>
<SupportPhoneNumber>001-xxx-xxxxxxxx</SupportPhoneNumber>
<SupportEmail>[email protected]</SupportEmail>
<CompanyWebsite>http://acmecorp.com</CompanyWebsite>
<CompanyMailingAddress>Company mailing address</CompanyMailingAddress>
</ContactDetails>
<AccentColor>
<R>165</R>
<G>42</G>
<B>42</B>
</AccentColor>
<LicenseAgreement>Custom EULA license This is a custom license that will
replace the Intel license</LicenseAgreement>
Tag Description
Contains the product name that will replace the default product
name of “Intel® Small Business Advantage”. This tag only exists if
<ProductName>
you changed the product name in the PRODUCT NAME window of
the wizard.
Contains the values that you defined in the CONTACT DETAILS
window of the wizard. These values are shown on the Contact
window when the user clicks Contact in the GUI menu.
<ContactDetails>
Note: Some of the fields in the CONTACT DETAILS window are
optional. If you did not define a value in a field, the tag for that
field is not created in the XML file.
Contains the End User License Agreement (EULA) that will replace
the default Intel EULA. This tag only exists if you changed the
<LicenseAgreement> product name in the PRODUCT NAME window of the wizard.
(When you change the product name, you must load a new EULA
in the LICENSE AGREEMENT window of the wizard.)
This table shows the command line switches available in this release.
Application Switch
The help is a set of compiled HTML help (*.chm) files. The chm files were created as modular
help files and are linked to each other. This means that you can open any chm file and
always see the content of all the chm files. Only the content of the chm files located in the
same folder is shown. If you remove a chm file from the folder, the content of that file is not
shown in the help. This means that if you remove an application that was provided by Intel,
you can easily remove all traces of the documentation for that application.
For example, if you removed USB Blocker it will not be shown in the GUI. But when the end
user opens the help, the USB Blocker topic will be shown in the Contents tab of the help. To
remove the topic and all references, simply remove the USBBlocker.chm file from the folder
where the chm files are located.
The Documentation folder contains a separate folder for each language supported by
Intel SBA. The default language is English (in the folder en-US).
Note:
• If you remove a chm file, you must remove it from each of the language folders.
• In this release, the chm files for all supported languages were added, but they are only
partially translated and are not fully updated.
To help the end user define these settings, Intel SBA can automatically populate these fields
with the correct settings. When the user enters a valid email address in the “Email Address”
text box, Intel SBA looks in an XML file named “MailProviders.xml”. If an entry exists for the
mail provider, the settings (marked in yellow in this screenshot) are populated.
By default, the MailProviders.xml file contains settings for Gmail* and Yahoo!* Mail. You can
add settings for additional email service providers to this file.
Tag Description
<SmtpSettings> Create a <SmtpSettings> tag for each email service
provider that you want to add to the MailProviders.xml file.
<Hostname> The name given by the email service provider to their server
that accepts emails via the web. The value of this tag is put
in the “Outgoing Mail Server (SMTP)” text box.
<Port> The number of the port that the server of the email service
provider uses to listen for incoming emails. The value of this
tag is put in the “Port” text box.
<Login> The suffix of the email address that can be used to identify
the email service provider (including the @ symbol).
When the end user types an email address in the “Email
Address” text box, Intel SBA looks at the <Login> tags. If a
match is found, the settings are automatically populated.
Note: The value of this tag must match the email address
exactly. This means that for email service providers that use
multiple domains with different suffixes, you must create
more than one set of <SmtpSettings> tags.
<EnableSsl> Defines if the email service provider uses the Secure Sockets
Layer (SSL) to encrypt the connection. The value of this tag
defines if the “Use SSL” check box is selected. Valid values:
• true – the check box is selected
• false – the check box is not selected
<ServerAuthentication> The type of authentication. Valid value: Password
3. In the APPLICATION DESCRIPTION field, type the text that you want to show in the status
panel when this “application” is selected.
4. In the UPLOAD APPLICATION field, click Browse and then select executable file of the
browser that you want to use to open the website. For example:
5. In the UPLOAD ICON field, click Browse to load an icon to replace the default icon of the
web browser that you selected in step 4.
Note:
It is not necessary to use the remaining fields. The LINK TO WEB PAGE and TEXT FOR LINK
fields are used to add links to a website for “real” applications. For this “application” the
APPLICATION ARGUMENTS field is used instead (step 6).
7. Click Add App. The application is added to the YOUR CUSTOM APPS list.
8. Continue to the end of the customization wizard and click Finish to create the customized
files.
Note:
Intel SBA requires the XML files to be signed using a Code Signing Certificate.
Secure Sockets Layer (SSL) Certificates and Self Signed Certificates are not supported.
Method #1: Automatically Generate the CSR Method #2: Manually Create the CSR
The latest versions of Microsoft* Internet If the CA that you select does not support
Explorer* and Mozilla Firefox* can generate automatic generation of the CSR, you will
the CSR automatically. If the CA supports this need to create it manually. This process is
option, a private key (and a CSR) will be not as easy as automatic generation, and
generated on the computer that you use to requires the use of third-party tools. For
apply for the certificate. After the CA approves more information, see Manually Creating
the request, you will receive a signed the CSR File.
certificate and installation instructions.
Note: Make sure that you always use the same computer, user, and browser to request
and install the certificate.
Method #1: Use the Customization Wizard Method #2: Use the Code Signing Tool
The customization wizard can use a PFX file Intel SBA also includes a command line tool
to automatically sign the XML files for you. that you can use to sign the XML files. This
To do this, in the CERTIFICATES window of can be useful if the XML files will be signed
the wizard click Browse and select the PFX at a later stage or by another department in
file. your organization. To use this tool, in the
If you used method #2 in step #1, you CERTIFICATES window of the wizard, select
already have a PFX file that you can use. If the Skip this step check box.
not, you will need to export the certificate This tool can use a PFX file (like the wizard)
into a file in PFX format (see Exporting to a or use the code signing certificate directly in
PFX File). the certificate store. For more information,
see Using the Code Signing Tool.
• Go Daddy*
http://www.godaddy.com/ssl/code-signing-certificate.aspx?isc=sslqgis01d&ci=13314
• Verisign*
http://www.verisign.com/code-signing/index.html?tid=a_box
• GlobalSign*
http://www.globalsign.com/code-signing/
• Thawte*
https://www.thawte.com/code-signing/index.html
• TrustCenter
http://www.trustcenter.de/en/products/desktop_code_signing.htm
• Comodo*
http://www.comodo.com/
http://www.chosensecurity.com/tc-publisher-id-for-ms-authenticode
Note:
Some of the Certification Authorities websites offer options for several different platforms.
In these websites, select the “Microsoft Authenticode” option.
The user is allowed to continue and open the GUI, but data from unsigned or compromised
files is NOT loaded in the GUI. If default data exists for the file, the default data is loaded.
Note:
These files have localized versions that must also be signed. For more information, see
Translating Customized Settings.
• UiSettingsData.xml
• HealthCenterOrderAndDefaultData.xml
• SoftwareMonitorOrderAndDefaultData.xml
• UiApplicationsOrderData.xml
• IntelEnergySaverData.xml
• MailProviders.xml
The GUI does not warn the end user if changes are made to these files.
• #1: “Certificates – Current User” – Use this snap-in on the computer that you are using to
sign the XML files. If you want to use the Code Signing Tool, the certificate with the
private key must be located in this Personal > Certificates store.
• #2: “Certificates (Local Computer)” – Use this snap-in on the target computer that will be
sent to the customer (or Reseller). It is recommended to install a “P7B” certificate in this
Personal > Certificates store (see Preparing the Target System).
This procedure describes how to create a console view for both of the certificates snap-ins.
2. Click Start, type mmc.exe, and then press <Enter>. The Microsoft Management Console
window opens.
3. Select File > Add/Remove Snap-in. The Add or Remove Snap-ins window opens.
5. Select My user account and click Finish. The Certificates snap-in window closes and the
“Certificates – Current User” snap-in is added to the list of selected snap-ins.
6. From the list of available snap-ins (in the left pane of the window), select Certificates
and click Add. The Certificates snap-in window opens again.
7. Select Computer account and click Next. The Select Computer window opens.
9. Click OK. The Add or Remove Snap-ins window closes and the snap-ins are added to the
Console Root tree (in the left pane of the window).
10. Close the console. When you close the console, you will be asked if you want to save the
settings for this console view. If you save the settings, they are saved in an *.msc file with
a name that you specify. You can then double-click this file to quickly open the console with
the certificates snap-ins already loaded. You can also use this file to open the console on
other computers.
1. Use a tool to create a file containing a private key (*.key) and another file containing the
CSR (*.csr). For example, using OpenSSL, this command :
• MyKey.key – A file containing your private key. Make sure that you keep this
file secure and do not give access to it to unauthorized persons. Do NOT
send this file to the CA.
2. Go to the website of the CA and start the certificate request process. Follow the instructions
in the website.
3. One of the fields/pages in the website will contain a field in which you will be asked to
supply the CSR. Open the MyCSR.csr file (for example using Notepad) and copy/paste the
contents into this field/page. Complete the request process in the CA website.
4. After the CA approves the request, you will receive a signed certificate from the CA. The
next step is to add the private key to this certificate file and create a PFX file. For example,
using OpenSSL, this command:
will add the private key (from the MyKey.key file) to the certificate received from the CA
(in this example “filefromCA”) into a pfx file named “certname.pfx”. When you run the
command, you will be asked to define a password for the pfx file. Make sure that you
define a strong password. You will be asked for this password for any operation that you
want to perform using the PFX file (for example, using the customization wizard).
Note:
• You can now use this PFX file with the customization wizard and the code signing
tool. If you want to install the certificate, double-click the PFX file to open the
Certificate Import Wizard. (Click Next in the wizard, accepting the default options,
and then Finish.)
• For more information about OpenSSL, see this webpage: http://www.openssl.org/
2. Locate the certificate in the Microsoft Management Console (see Using Microsoft
Management Console).
3. Right-click the certificate and select All Tasks > Export. The Certificates Export Wizard
opens.
5. Select Yes, export the private key and click Next. The Export File Format window
opens.
10. Click Browse to define the name of the PFX file and the location where you want to save
it (or type the full path and name in the File name field).
11. Click Next. The Completing the Certificate Export Wizard window opens.
12. Click Finish and then click OK to close the message stating that the export was
successful.
The code signing tool can get the necessary data to sign the files from these locations:
– OR –
• Directly from the certificate store (from “Certificates – Current User”). To use this option,
you must run the tool with the user that was used to install the code signing certificate.
Note:
For testing purposes, you can use the code signing tool to sign any XML file. After signing,
make a change to the value of a tag in the XML file and then try to verify the file again. You
will see that the code signing tool recognizes that the signature is invalid (and therefore so
will Intel SBA).
7.7.1 Syntax
Parameter Description
<command> Mandatory. The command that you want to perform. Valid values:
• Sign – Digitally sign the files
• Verify – Verify the digital signature of files
<target> Mandatory. The target for the command. Valid values:
• The full path to a single XML file
• The full path to a folder containing the XML files
Note: If you provide the full path to a folder, ALL the XML files in the
root of that folder are signed/verified with the digital signature of your
company.
/f <pfxFile> Optional. If supplied, the signing tool uses the supplied PFX file. If not
supplied, the signing tool uses the first code signing certificate that it
finds in the personal certificates store of the current user.
/p <password> Optional. Specifies the password to use when opening a PFX file.
Note:
• The signing tool expects to find only one valid code signing certificate in the personal
store.
• To use this option, you must run the code signing tool on the computer where the code
signing certificate is located. You must also be logged in as the correct user.
• A check that the content of the XML file has not been changed since the file was signed.
This check is always done locally on the computer running Intel SBA.
• A check that the certificate that was used to sign the file was issued by a “trusted” entity.
This check is done locally if possible, and over the Internet if not possible locally.
Each certificate contains data about the organization from which it was issued (the issuer).
This data forms a “certificate chain” that ends in a trusted root certificate of a known CA.
Intel SBA tries to validate this chain locally on the computer. If the chain cannot be validated
locally on the computer, Intel SBA goes out to the Internet to validate the CA.
In certain conditions, validating the certificate chain over the Internet can take a few
minutes. The end user will not know why Intel SBA does not open immediately. Thus, it is
recommended to install a certificate with this chain on the target computer before it is sent
out to the customer (or Reseller). This is done by installing a P7B file on the target system. A
P7B file contains the full certificate chain but does not contain the private key.
Note:
• You should never install the private key on the target system. If you installed the code
signing certificate on the target system, make sure that you delete it from the
“Certificates – Current User” store.
• After installing the P7B file on the target system, it is recommended to check that it was
installed in the correct location (“Certificates (Local Computer)”).
For information about how to view certificates, see Using Microsoft Management Console.
2. Locate the certificate in the Microsoft Management Console (see Using Microsoft
Management Console).
3. Right-click the certificate and select All Tasks > Export. The Certificates Export Wizard
opens.
5. Select No, do not export the private key and click Next. The Export File Format
window opens.
8. Click Browse to define the name of the P7B file and the location where you want to save
it (or type the full path and name in the File name field).
9. Click Next. The Completing the Certificate Export Wizard window opens.
10. Click Finish and then click OK to close the message stating that the export was
successful.
After creating the P7B file, install it on the target system using the CertUtil.exe utility
(included in Windows* 7). The file must be installed in the “Certificates (Local Computer)”
store of the target system. For example, this command installs a P7B file named
“MyP7Bfile.p7b” in the correct location:
The procedure below describes how to copy a customized Intel SBA installation to another
computer. If you want to create a deployment image of the customized installation, do the
tasks described in step 1 of the procedure.
To delete the files, you will need to reset the file permissions (see Resetting File and
Folder Permissions).
2. Install Intel SBA on the target computer (see Installing Intel SBA).
3. Reset the file and folder permissions on the target computer (see Resetting File and
Folder Permissions).
4. Copy the contents of this folder from the source computer to replace the contents of this
same folder on the target computer:
Note:
Copy all the subfolders and files, EXCEPT for the IUM folder. This folder contains data
used by the update mechanism of Intel SBA.
a. On the target computer, update the program name (see Updating the Program
Name in the Control Panel).
b. Copy the desktop shortcut created by the customization wizard from the source
computer to the desktop of the target computer.
c. Update the program name and the icon in the Start > All Programs menu.
For increased security, permissions on this folder and the files it contains are limited. Each
time the service starts, it removes all existing permissions for all users on this folder and files
and gives only the Read permission. This means that before you can copy files to this folder,
you must give yourself permissions on the folder. Also, if you want to make changes to a file
in the folder after the service has started, you must give yourself permissions on the file. The
easiest way to do this is to give full control to the Everyone group.
Note:
Opening the customization wizard automatically gives full permissions to all files in the
folder. (Advance to the Welcome window and then close the wizard.)
4. Select the Full control check box. (All the check boxes will be selected.)
5. Click Apply and then OK. When you restart the service, the service will automatically
remove the full control permissions from the Everyone user group. If the service does not
start, try running the customization wizard. This will correct any problems that exist in the
folder and file permissions.
• End User License Agreement – The end user must select the check box to accept the
agreement before they can use Intel SBA. If you changed the product name, the license
that you uploaded in the customization wizard will be shown instead of the Intel license.
• Update Consent Agreement – The end user can select if they want to activate the
optional mechanism to automatically check for updates. If they decline, they will be able
to activate it later from the main menu in the GUI.
Note:
• The AllUsersGuiData.xml is not installed during installation. It is created each time the
GUI is opened and the license agreements are shown.
• You must delete the AllUsersGuiData.xml file before sending the completed installation
to the customer (or Reseller). This is a mandatory requirement. If you do not delete the
file, the end user will not be asked to accept the licenses.
• The remediation questions and answers (for authentication to change the service
password if it is forgotten)
• A list of software applications that are being monitored by the Software Monitor
application
• A list of tasks that were configured to run using the PC Health Center application
Note:
• The ServiceData.bin is not installed during installation. It is created when the password
is set and the Intel ME is configured (see How the Intel ME is Configured).
• You must delete the ServiceData.bin file before sending the completed installation to
the customer (or Reseller).
When you copy the customized installation to another computer, the name in the Control
Panel is not changed. You will need to change it manually. When you change the product
name, the customization wizard creates these registry files that you can use to do this task:
The files are located in this folder: C:\ProgramData\Intel\Intel(R) Small Business Advantage
3. Open the Control Panel and check that the correct name is shown.
ID Description
In the Settings > Send Email Settings window, sending a test email using a
Hotmail account sometimes fails without giving the correct reason. This can occur if
DE1732 Hotmail uses picture verification during the email sending process (to prevent
spamming). When this happens, the test email will fail and the user will not know
the reason why.
Trying to uninstall Intel SBA while Intel SBA is still checking for updates causes an
DE1719 error message. After clicking OK, the uninstallation continues but the Service\IUM
folder is not deleted.
When uninstalling Intel SBA, you can select to keep the customized data files (by
clearing the Delete data files check box). When reinstalling Intel SBA, the
customized settings should still be available exactly as they were defined before
uninstalling Intel SBA. But, after reinstall:
DE1715 • The applications in Software Monitor and the tasks in PC Health Center are not
shown in the same order that they were defined.
• Applications added to Software Monitor and tasks added to PC Health Center
do not have their check boxes selected. (This means that they will not appear
as “selected” by default in the GUI).
In the Alert Center, users without administrator privileges are incorrectly allowed to
select/unselect the check boxes in the IGNORE column. This only occurs if
DE1701
Intel SBA is configured with an empty password. Non-admin users should not be
allowed to make any configuration/settings changes in Intel SBA.
The customization wizard incorrectly lets you select a *.bat file in the
DE1698 CUSTOM APPS window. Applications based on *.bat files are not supported and will
not be shown in the GUI.
In the Exceptions tag of USB Blocker, adding more than five connected USB
DE1695
devices to the whitelist creates an empty item in the DETECTED USB DEVICES list.
During normal operation of the Energy Saver and PC Health Center applications,
Intel SBA makes changes to the Windows power settings. When the task is
complete, Intel SBA changes the Windows power settings back to the original
DE1694 settings. During uninstall, this reset does not occur if uninstall is started after the
Windows power settings were changed by Intel SBA. This could cause the
computer to go to sleep after Intel SBA is uninstalled (but only if no activity is
detected for 15 minutes).