Windows Phone 8 Enterprise Application Deployment Guide (III)

Previous Windows Phone8 Enterprise Application Deployment Guide 2) describes how to import an Enterprise Mobile Code signature certificate from Symantec application to a computer and then export the PFX file. This section describes how to use the PFX file to generate the Application Registration tag AET: Application Enrollment Token and use the PFX file to sign the WindowsPhone8 enterprise Application developed by the company.

1. Generate AET: Application Enrollment Token

AET files are used by enterprises to help users complete secure registration mark files on their mobile phones. If enterprises have MDM capabilities such as Windows Intune, they can directly manage AET through MDM to complete the Mobile Phone registration process. If you do not have an enterprise that has MDM, you can use an email to distribute the AET to your mobile phone. After registering an enterprise user's mobile phone, you can install an enterprise-published application.

To create an AET, use the AETGenerator tool provided by Windows Phone SDK 8.0.

A) Enter CMD in the search bar of the Super button. OpenVS2012 X86 Native Tools Command Prompt is displayed in the result;

650) this. width = 650; "title =" 1.png" src = "http://www.bkjia.com/uploads/allimg/131228/06495A951-0.png"/>

B) Start VS2012 x86 Native Tools Command Prompt VS2012 X86 local tool Command Prompt as an administrator) and change the current directory to the directory where the PFX file is located;

C) run the following command to run the AETGenerator tool:Replace placeholders in the command with appropriate valuesText;

% ProgramFiles (x86) % \ Microsoft SDKs \ Windows Phone \ v8.0 \ Tools \ AETGenerator \ AETGenerator.exe PFXFile Password

Two parameters are described as follows:

Parameters	Description
PFXFile	Name of the PFX file generated from the Enterprise Mobile Code signature certificate provided by Symantec. If the current directory is not set to the location of the PFX file, this parameter must specify the complete path of PFX.
Password	The private key used to read the PFX file.

D) after the command is executed, the AET. aetx file and multiple other files are created in the current directory. Companies that use Windows intune and System Center 2012 Configuration Manager to manage mobile phones should send the AET. aetx file to users by email or other means, so that they can register mobile phones to obtain company app distribution. The following describes the files generated by the AETGenerator command.

File	Description
AET. xml	This file contains the original AET in XML format.
AET. aet	This file is base64-encoded in AET. xml. You can use this file to configure AET for distribution to mobile phones from the MDM system.
AET. aetx	This file contains the content of the XML-format AET. aet file, which can be processed by email and Internet Explorer on your mobile phone. For companies that do not use Windows Intune and System Center 2012 Configuration Manager, you can use this file to manually install AET on your mobile phone. After distributing this file to your mobile phone, you can click this file to install AET, and then register to get the company app distribution. For more information, see company app distribution for Windows Phone.

2. Pre-compile the Assembly and sign the company's applications

After creating the AET file, you can prepare for enterprise application distribution. Before distributing enterprise applications to enterprise users, perform the following operations:

--- Use the MDILXAPCompile tool provided by Windows Phone SDK 8.0 to pre-compile any hosted Assembly contained in XAP into local code.

--- Use the XapSignTool provided by Windows Phone SDK 8.0 to obtain an enterprise certificate from Symantec and sign the XAP.

Windows Phone SDK8.0 provides the Windows Power Shell script BuildMDILXap. ps1), which can be used to automatically execute these two tasks.

650) this. width = 650; "width =" 777 "height =" 498 "title =" 2.png" style = "width: 637px; height: 375px;" src = "http://www.bkjia.com/uploads/allimg/131228/0649562C1-1.png"/>

A) Enter Power Shell in the search bar of the Super button and select to run Power Shell with the Administrator permission.

B) enter the following command at the Power Shell prompt to ensure that the placeholder text in this command is replaced with the appropriate value:

BuildMDILXap. ps1-xapfilename XAP-pfxfilename PFXFile-password Password

Parameters	Description
-XapfilenameXAP	The complete path of the XAP file to be precompiled and signed, if the-pfxfilename option is specified.
-PfxfilenamePFXFile	Use the PFX file generated by the Enterprise Mobile Code signature certificate provided by Symantec to sign the XAP. If the PFX file is not in the current path, specify the complete path for the file.
-PasswordPassword	Password used to read the PFX file.

After the preceding steps are completed, enterprise applications are ready for distribution. Enterprise applications can be distributed in two ways: 1) by developing a Company Hub application, it is suitable for applications issued by multiple enterprises and requires unified mobile application management, download, update, and other services can be provided; 2) emial distribution and download are suitable for enterprises with only one application. It is a simple distribution method to save management costs. The following sections describe how to develop a Company Hub application.