AppCenter 2.0 WM Admin Guide Build 899 App Center

User Manual:

Open the PDF directly: View PDF .
Page Count: 43

Download
Open PDF In Browser	View PDF

AppCenter™ 2.0
for Windows Mobile
Administration Guide

AppCenter 2.0 – Administration Guide (Build 899)

Page 1

AppCenter 2.0 for Windows Mobile
Administration Guide

What is AppCenter?
a. What is it used for?
b. Who is this guide intended for?
c. Overview: Admin Mode and User Mode, debug mode, how it
works

How to use it – End User
a. Overview: Launch screen
b. Navigating the Launch screen

How to use it – Administrator
a. Overview
b. Program Files, Configuration Files and Log Files
c. Initial Setup
d. Adding New AppCenter™ User-Mode Menu Items

Usage Examples
a. PDA Phone

Appendix A – AppCenter Log file format
Appendix B – AppCenter Command line Options
Appendix C – AppCenter Configuration files
Appendix D – Pre-approved applications
Appendix E – Installation Instructions
Appendix F – New Taskbar options

AppCenter 2.0 – Administration Guide (Build 899)

Page 2

Section 1 - What is AppCenter™?
AppCenter™ is an “end-user” administration application that
provides two major services: (1) It will lock the user out of executing
“unauthorized” applications on a Windows Mobile device as specified by
an administrator and (2) it replaces the Desktop GUI of the mobile unit
with a secure “launch platform” displaying approved applications in icon
form. Any “unauthorized” application that attempts to start up (either
automatically or by user control) will immediately be terminated.
AppCenter can also be configured to disable the Start Menu
screen keyboard) and Smart-Minimize
from the user.

, SIP (on

[Fig. 1a – Launch screen]

hidden

With Smart Minimize

enabled]

[Fig. 1b – With Smart Minimize
and Menu Bar configured]

A. What is it used for?
AppCenter™ is intended for use on end-user mobile devices where
only certain applications should be allowed to be accessed by the enduser. It can be configured to lock end-users out of critical and sensitive
areas of the Windows Mobile device. For example it might be used for a
“kiosk” application where the end-user should run ONLY the specified
information application and nothing else and the application would
“auto-start” whenever the Kiosk hardware is rebooted –or- the application
terminates due to some unknown reason.

AppCenter 2.0 – Administration Guide (Build 899)

Page 3

B. Who is this guide intended for?
This AppCenter™ administrators’ guide is intended for developers
and designers who are creating full-device applications where access to
other parts of the Windows Mobile device should be restricted.

C. Overview: User Mode and Administration Mode
The AppCenter™ user interface has two main modes: User Mode
(also known as the Launch screen) and Administration Mode. While in
User Mode, users are presented with the AppCenter™ Launch Screen that
lists all the approved visible applications in icon form. From this they can
launch any of the approved applications by tapping or selecting the
requested icon. This Launch screen or the AppCenter™ process cannot
be closed or shut down from the user interface.
In Administration Mode, the administrator can access the
administrators’ menu by supplying the proper password. From there they
can add, change and/or remove items from the list of approved
applications, specify options to configure the Menu bar with showing or
and
} and showing or hiding AppCenter™
hiding Start Menu icons (
Menu Icons for Home, Signal Strength, Time, Date, Battery or other
informative device status information.

Section 2 - How to use it – End User
A. Overview: Launch screen
As stated before, the end-user is provided with a Launch screen from
which they can choose which approved application to launch. This
Launch Screen is always active so the end-user will be returned to this
screen after the approved application exits -OR- if the Menu bar contains
the AppCenter™ “Home” icon (discussed in section X) the user can leave
the approved application active and return to the AppCenter™ Launch
screen for further options. The previous application remains active and
operational and can be returned to by tapping / selecting that
application icon again from the Launch Screen. Quick Tip: On the Menu
bar of the AppCenter™ Launch screen, both the Smart Minimize
and
Start
icons are displayed (enabled) or hidden (disabled) by the
Administrator changing the setting “Hide Start Menu” in the Administrator
Menu : Tools -> Options -> Taskbar tab.

AppCenter 2.0 – Administration Guide (Build 899)

Page 4

The AppCenter™ Menu bar Icons can be configured to display a
variety of immediate information about the operating condition of the
mobile device. Below is a chart showing all the available icon graphics
and their meanings:
[Fig. 2 – Launch Menu bar Icons]
Battery
Charging

Battery
Fully
Charged

Battery
Good

Battery Low

Battery Very
Low

Battery
Status
Unknown

AirBeam®
Status
UNKNOWN

AirBeam®
Status
CONNECTED

AirBeam®
Status
NOT
CONNECTED

AirBeam®
Status
ROAMING

WLAN /
Signal
STRONG

WLAN /
Signal
GOOD

WLAN /
Signal
MEDIUM

WLAN /
Signal FAIR
or

or
WLAN /
Signal
POOR

Back to
AppCenter
(HOME)

Speaker
ON
(Volume
Up)

Speaker
OFF
(Volume
Muted)

WWAN /
Phone
GOOD

WWAN /
Phone
MEDIUM

WWAN /
Phone
FAIR

WWAN /
Phone
NO SIGNAL

WLAN /
Signal
NO SIGNAL

WWAN /
Phone
STRONG

WWAN /
Phone
POOR

Connectivity
Icon

AirBeam® is a registered trademark of Symbol Inc.

The display inclusion of these icons on the AppCenter™ Menu bar is
controlled by the settings in the Administrator Menu : Tools -> Options ->
Taskbar tab.
Quick Tip: If the setting “Hide Start Menu” on this same page is turned OFF
(not checked) then the AppCenter™ Launcher Menu bar will display the
devices’ default menu bar and NOT any of the configured icons above.

AppCenter 2.0 – Administration Guide (Build 899)

Page 5

B. Navigating the Launch screen
[Fig. 3 – Launch Screen -> Tools menu]

The “Tools” menu at the bottom of the
Launch Screen has “About…”, “Admin
Login…” and “Exit …” as choices.
Quick Tip: This menu may not have the
options “Admin Login …” or “Exit …” if the
administrator has disabled user login
during the configuration (see Fig. 11)

[Fig. 4 – About Screen]

The “About…” menu shows version
information about the AppCenter™
application installed on this device.

AppCenter 2.0 – Administration Guide (Build 899)

Page 6

[Fig. 5 – Admin/Exit Password Screen]

The “Admin Login…” is used to switch into
Administrator mode and access the
Administration menu. The “Exit …”
selection is used to exit out of
AppCenter™ and return to the Desktop.
Both the “Admin Login …” and the “Exit
…” selections require an administrator
password to continue. In both cases, if
the end-user does not have the correct
password, they will be denied access
and sent back to the AppCenter™
Launch Screen.

Section 3 - How to use it – Administrator
A. Overview
After the initial installation of AppCenter™ is complete (see Appendix E
for installation instructions), AppCenter™ will need to be configured to
meet your particular needs. These configuration details are initially
created by the use of the Administrators’ menu described in the following
section. The details of your particular configuration are contained in a
pair of configuration files written and saved on the mobile device. These
files can be exported and placed on additional devices to replicate these
configuration options on additional mobile devices. By default after initial
installation, these files do not exist and are created with certain default
information upon the first execution of AppCenter™ (User Mode). These
two files are named “AppCenter.cfg” and “AppCenter-User.cfg” and are
normally found in the directory as the AppCenter™ executables
(“AppCenter.exe” and “AppCenterAdmin.exe”). All access violations to
the “lock down configuration” attempted while AppCenter™ is in User
Mode are logged to a text file which by default is named
“AppCenter.log” and located in the same directory as the AppCenter™
executables.

AppCenter 2.0 – Administration Guide (Build 899)

Page 7

B. Program Files, Configuration Files and Log Files
To allow the configuration files and Log files to be placed in storage
areas other than the storage area housing the Program executables,
there are several commandline arguments that of AppCenter™ User
Mode (“AppCenter.exe”) can be started with. These commandline
arguments are detailed in Appendix B. Examples include using these
commandline arguments to allow you to place the Configuration files in a
Non-Volatile directory for Cold-Boot recovery –or- you might only want
the log files to be in a directory in “\My Documents” for easy access by
Pocket Word. Quick Tip: On Windows Mobile, launching an application
with commandline arguments requires you to create a shortcut and then
edit the shortcut (“.lnk” file) to include the commandline arguments you
wish to add. This procedure is also detailed in Appendix E. The format of
the configuration files is discussed further in Appendix C and the format of
the Log files are discussed in Appendix A. Quick Tip: You will rarely need
to edit the Configuration files manually since the Administrator’s Menu
application (“AppCenterAdmin.exe”) edits this file for you. The Appendix
C for Configuration File format is for informational purposes only and
manual editing of the Configuration files is not recommended.

C. Initial Setup
[Fig. 6 - Administrator screen (Home)]

1. Enter Admin Mode to configure
AppCenter™. Refer to Figures 3
and 5 on entering Administration
Mode from the AppCenter™
Launch screen. Quick Tip:
Administration Mode can also be
started by running the
Administration application
(“AppCenterAdmin.exe”) but this
application still requires the
administration password to be
supplied. Quick Tip: The initial
default administration password is
‘odyssey’. This password is not
case-sensitive.

AppCenter 2.0 – Administration Guide (Build 899)

Page 8

[Fig. 7 - Administrator screen -Tools]

2. From the Administration Main
screen, select “Options” to
configure AppCenter™ systemlevel settings.

[Fig. 8- Administrator screen –Tools – Options – Taskbar tab]

3. The system-level settings are
contained in a series of Tabbed
Panels labeled: Taskbar, Title, Time,
Signal, Log, Admin, Browse, Close
and Keys. The first tab Taskbar is
displayed upon opening the
Options. This dialog controls the
display of icons on the Taskbar at
the top of the AppCenter™
Launch screen. The AppCenter™
icons being controlled are
displayed in Figure 2.
a. If the checkbox “Hide Start
Menu” is UNCHECKED (OFF)
then no AppCenter™ icons will
display and instead the Smart
Minimize
and the Start
icons will be visible on the
AppCenter™ Launch Taskbar.

AppCenter 2.0 – Administration Guide (Build 899)

Page 9

[Fig. 9 - Administrator screen –Tools – Options – Title tab]

4. The “Title” tab allows customization
to the Title portion of the
AppCenter Launch screen Taskbar.
The “Alternate Title” data placed in
the textbox will replace the default
text “AppCenter“ displayed to the
far left of the Taskbar (here in
Figure 9 it is to the right of the Start
icon).

[Fig. 10 - Administrator screen –Tools – Options – Time tab]

5. The “Time” tab allows
customization to the Time portion
of the AppCenter Launch screen
Taskbar if “Show Time” has been
CHECKED in the “Taskbar” tab.

AppCenter 2.0 – Administration Guide (Build 899)

Page 10

[Fig. 10 - Administrator screen –Tools – Options – Signal tab]

6. The “Signal” tab allows a certain set of
actions to occur if the AppCenter
Launch screen Taskbar Icon for Signal
(WLAN) is tapped. These options are
for Symbol®/Motorola Mobile Devices
with 802.11x radios. The Adapter
Name which is tied to the resident
802.11x radio is displayed at the top of
the screen EVEN if it is not a
Symbol®/Motorola Mobile Device. To
use this action, the “Show Signal”
checkbox has to be CHECKED in the
“Taskbar” tab.

[Fig. 11 - Administrator screen –Tools – Options – Log tab]

7. The “Log” tab allows the review of
the current contents of the
AppCenter™ logfile. The logfile
format is discussed in greater detail
in Appendix A. All attempted
program accesses that are not
permitted (access violations) are
captured and made viewable in
this dialog. The logfile is also a flat
file that can be exported and
viewed on other platforms (see
Section 3A). The logfile allows the
administrator feedback on
whether the current AppCenter
configuration is blocking known
good application functionality
such that he or she can add
additional program items to complete a desired AppCenter
configuration.

AppCenter 2.0 – Administration Guide (Build 899)

Page 11

[Fig. 12 - Administrator screen –Tools – Options – Admin tab]

8. The “Admin” tab allows the
change of the current license key
for AppCenter™ as well as change
of the Administrator password.
Additionally, changing the
checkbox labeled “Login disabled
in user mode” will disable the
ability to Exit the AppCenter™
Launch screen by supplying the
Administrator password –OR- Enter
the Administrator Menu from the e
AppCenter™ Launch screen by
supplying the Administrator
password. Quick Tip: If you disable
the “Login in user mode” –AND- do
not have the AppCenterAdmin
application approved and visible as an icon in the AppCenter™
Launch screen –AND- you have the AppCenter™ Launch
application auto-started upon boot of the mobile device, you will
be unable to change the AppCenter configuration of this device
directly. You can still either use Odyssey Software’s Athena™
remote management application –OR- Microsoft’s ActiveSync to
copy an “unrestrained” version of the configuration file
“AppCenter_User.cfg” to replace the existing configuration on the
unit. You must then reboot the unit –OR- restart the AppCenter User
mode application (“AppCenter.exe”) for the changes to take
effect.
[Fig. 12a - User Mode Launch screen with Login disabled]

AppCenter 2.0 – Administration Guide (Build 899)

Page 12

[Fig. 13 - Administrator screen –Tools – Options – Browse tab]

9. The “Browse” tab defines the scope of
the search for possible applications to
add when you want to browse for
existing applications to approve in the
Administrator Menu -> New - >
button (discussed further
“Browse”
in this document). This extensible list of
device directories and allowable file
extensions for executables enables
additional installed runtimes and
interpreters to be supported and
controlled within the AppCenter™
architecture. The checkbox “Include
all shortcuts” will allow the shortcuts to
be visible in the Browse list as long as
the shortcut exists in the directories
specified under the “Folders” list. Only those executables whose file
extension is registered in the “Ext” list will be displayed in the “Browse”
list as well.
[Fig. 14 - Administrator screen –Tools – Options – Close tab]

10. The “Close” tab allows the
administrator to define either
Executable Names that will always be
closed immediately if they are started
–AND/OR- Executable Names that will
always be permitted if they are
started. These entries override any
Approved Application definition in the
Main Administrator screen. For
example, if an Executable Name is
defined as an approved applications
by being an item in the main
Administration screen BUT the same
Executable name is in the list “Always
Close:”, the Executable name will be
shutdown immediately if it is started.

AppCenter 2.0 – Administration Guide (Build 899)

Page 13

[Fig. 15 - Administrator screen –Tools – Options – Keys tab]

11. The “Keys” tab allows the
administrator to allow or disallow the
application launch capability of the
special Mobile Device Keys for
Speaker / Headset Volume and
Phone Call/End/Mute (if available).
This tab also allows or disallows the
display of the SIP when the main
AppCenter window is displayed.

[Fig. 16 - Administrator screen –Tools – Options – Security tab]

12. The “Security” tab allows the
administrator to allow or disallow
access to files on memory cards
(including AutoRun) and IR, Bluetooth
and ActiveSync connections.

AppCenter 2.0 – Administration Guide (Build 899)

Page 14

[Fig. 17 - Administrator screen –Tools – Options – Phone tab]

13. The “Security” tab allows the
administrator to control access to the
Phone features of a Phone Edition
device. Access to the Flight Mode
menu can be controlled by the “Add
phone menu to WWAN icon” setting
and access to the Phone related
notification icons can be controlled
by the “Show phone icons on taskbar”
setting.

14. At the end of this configuration session, close out of the tabbed dialogs
for “Options …” by selecting / pressing the
of the screen.

button at the top right

[Fig. 18 - Administrator screen –Tools – Restore Default Programs]

15. Selecting the “Restore Default
Programs” menu item will allow the
administrator to “undo” all changes
and have the configuration revert
back to the initial default (“factory”)
approval settings.

AppCenter 2.0 – Administration Guide (Build 899)

Page 15

[Fig. 18a - Administrator screen –Tools – Restore Default Programs - Confirmation]

16. The “Restore Default Programs”
confirmation will display before the
configuration settings are reset.

[Fig. 19 - Administrator screen –Tools – Admin Logout]

17. The “Admin Logout” selection simply
exits the Administration application
and if the Administration application
was called from AppCenter™ User
mode, then you are returned to the
AppCenter™ Launch menu. If you
started the AppCenterAdmin.exe
application directly, you are returned
to the window which inherits focus.

AppCenter 2.0 – Administration Guide (Build 899)

Page 16

18. Selecting the
button at the top right of the Main Administration
screen will present the following Exit dialog :
[Fig. 20 - Administrator screen – Tools – Admin Logout]

19. Selecting “Logout” will have the
same effect as selecting “Tools” ->
“Admin Logout”. Selecting “Exit” will
terminate BOTH the AppCenter Admin
mode process AND the AppCenter
User mode process and you are
returned to the window which inherits
focus.

AppCenter 2.0 – Administration Guide (Build 899)

Page 17

D. Adding New AppCenter™ User-Mode Menu Items
To add individually defined approved applications which either
display as selectable icons on the AppCenter™ Launch menu or allow
other processes to run in the background or as child processes from other
approved applications, you will need to add these processes using the
“Tools” ”New Program …” menu selection at the bottom of the
AppCenter Administrator screen. Generally, there are two sources for the
request to add approved applications: (1) The requirement from the user
community to have the application on the menu to run on demand and
(2) Logfile contents that point to processes that AppCenter™ stopped
because they were not approved that need to be approved so that the
existing approved applications can run successfully. The format of the
contents of the logfile is described in Appendix A.
[Fig. 21 - Administrator screen – (Pre-approved and Admin Approved Applications)]

1. These applications are created
upon initial installation of
AppCenter™ and are added
automatically to the Configuration
file as well. In addition to these
Administrator Visible definitions,
there is also a pre-approved list of
Executable names that are not
stopped by AppCenter™ that the
operating system needs to have
running in order to function. This list
is detailed in Appendix D. The
items on this screen other than
“Calculator” are system level
functions that most people utilizing
AppCenter™ would probably like to
have approved on their system but may elect to remove
depending upon their needs. These are listed here so that they can
be removed if desired. You may delete them AT YOUR OWN RISK if
you so choose.

Fig. 21a - Pre-approved Applications and what they do]

AppCenter 2.0 – Administration Guide (Build 899)
ActiveSync Defines approval for
ActiveSync
autoconnect when
PC makes an
ActiveSync
connection
Calculator Used as an example
of a Visible Menu Item
– EXAMPLE ONLY

Device

Defines approval for
dynamic plug and
play operation – DO
NOT DELETE

GWES

Defines approval for
System Level
Windowing functions –
DO NOT DELETE
Defines approval for
Windows Classes
“static”, “worker”,
“Dialog” used in
Message Boxes and
other built-in alerts DO NOT DELETE

Shell32

CAB Files

Page 18
Defines approval that
allows for CAB files to
install when opened

Connection
Manager

Defines approval for
dynamic network
connections to
automatically
connect when media
is attached.
Dialup
Defines approval for
Networking dynamic WWAN
network connections
to automatically
connect when
network access is
requested by
applications
Mobile
Defines approval for
Companion Symbol/Motorola S24
WLAN Management
Application
Welcome
Defines approval for
the Welcome
Application launched
when Windows
Mobile starts from a
cold boot, allowing
Time Zone and
Calibration changes.

AppCenter 2.0 – Administration Guide (Build 899)

Page 19

[Fig. 22 - Administrator screen – New – General tab]

2. After you select “New” from the
lower right corner, AppCenter™
presents you with a multi-tabbed
form with which you can
configuration your new approved
application. The tabs here
separate the entries into related
function. Each tab will be
described in detail below.
Quick Tip: If your application already is
installed on the device –AND- you have
included the directory where it resides in
the paths specified in “Tools – Options –
Browse” tab as shown in Figure 12, you
can shortcut your efforts by using the
button from this initial
“Browse”
“General” tab. If the application is not
on the device yet OR you wish to configure it manually, all the New
Approved Application entries are described following the details of the
“Browse” wizard
[Fig. 22a - Administrator screen – New – General tab – Browse Wizard]

3. Selecting the “Browse” button will
display all Executables whose file
extension is listed (registered) in the
“Ext” list in the “Tools – Options –
Browse” tab as shown in Figure 12.
Also, only those Executables
residing in the directories specified
in the “Folders” list in the “Tools –
Options – Browse” tab as shown in
Figure 12 will be displayed. If a
program executable is selected,
the Wizard will automatically
create entries in all the Tabs based
upon the programs’ attributes
defined in the registry and in other
system resources.

AppCenter 2.0 – Administration Guide (Build 899)

Page 20

[Fig. 23 - Administrator screen – New – General tab – Manual Entry]

4. If the “Browse” wizard is not used,
the approved application
attributes can be defined
manually. The “Description” entry
will be the Title of the Icon in the
AppCenter™ Launch screen. The
“Execute” entry specifies the Full
Path and Filename of the
executable file to be approved.
The “Arguments” entry allows the
specification of any command line
arguments required for running the
selected application. The “Icon
File“ entry specifies the Full Path
and Filename of the Executable
whose Icon will be used as the Icon
™
on the AppCenter Launch screen (typically this would be the
same data as the “Execute” entry). The “EXE Name” is used to
specify an Executable file IF the entry “Execute” contains the Full
Path and Filename to a Non-Executable such as a Pocket Word
document, a Pocket Excel spreadsheet, a Windows Movie file, etc.
The buttons “Save” and “Cancel” are displayed on each tab and
“Save” will save ALL the data on ALL tabs and “Cancel” will negate
ALL entries modified since the last “Save”.
[Fig. 24 - Administrator screen – New – Windows tab – Manual Entry]

5. The “Windows” tab allows you to
restrict the approved application
to only displaying windows whose
Title and Class attributes match the
specification in the list. A “catch
all” entry “*|*” is supplied by
default. The format for an entry
into this list is
[WindowTitle]|[WindowClass].
The following characters have
special meaning when used in an
approved window string : “|” divides Title from Class; “*” –
Wildcard - Match up to the first

AppCenter 2.0 – Administration Guide (Build 899)

Page 21

occurrence of *, Characters after * are ignored; “?” – Universal
match for one character position; “\” - Indicates next character
should be taken literally. Applications approved in this manner will
be IN ADDITION to applications approved by Executable Name as
defined by Name at the main Administration screen. The following
formats are supported for approved windows:
Title or Title| or
Match title. Any class allowed.
Title|*
Title|Class
Match title and match class.
|Class
Match blank title and match class.
|
Match blank title and any class.
*|Class
Any title allowed. Match class.
abc*|xyz*
Match any title starting with "abc" and
match any class starting with "xyz"
Quick Tip: If you are unsure what your applications’ windows are using
for Title and/or Class, remove the default entry “*|*” “Save” your
configuration and run the application from the AppCenter™ Launch
screen. The application should not display many if any windows. Reenter the AppCenter Admin application and examine the logfile using
Tools – Options – Log tab as in Figure 11. The unapproved windows’
Title and Class will be listed and then added to this list.
[Fig. 25 - Administrator screen – New – Options tab – Manual Entry]

6. The “Options” tab allows you to
specify how the AppCenter™
Launch screen Icon for this
application will behave as well as
how the application will interact
with the display. The checkbox
“Hide from user” will prevent this
approved application from
appearing on the AppCenter™
Launch screen. The checkbox
“Hide menu bar” will prevent the
Applications’ Menu bar from
appearing while the application
has the foreground. The checkbox
“Hide start menu” will hide the start
menu if the same system-wide
setting is not ON (see Figure 8). The same is true for the “Hide done
button (X)” checkbox. The checkbox “Hide SIP” will disable the use
of the “On Screen Keyboard” if checked. The checkbox “Always
© 2006, Odyssey Software, Inc • ® All rights reserved

AppCenter 2.0 – Administration Guide (Build 899)

Page 22

launch program” will cause AppCenter™ to automatically re-launch
this program if it terminates for any reason. The entry “Disable
relaunch for X seconds” will insert a delay of X seconds between
the time AppCenter™ acknowledges the application has
terminated and the time AppCenter™ re-launches this application.
Note: Hiding the Start Menu will also disable the Volume and
Time/Next Appointment icons while this application is active.
Note: The Smart Minimize (X) button is hidden for all applications in
AppCenter if the Hide Start Menu option is checked from the Admin
Options global options screen.
Examples of several “Hide” options
[Fig. 26a – Start Menu Visible]

[Fig. 26b – Start Menu Hidden]

[Fig. 24c –
Smart [Fig.
[Fig. 26c – Smart Minimize (X) Hidden]

[Fig. 26d – Menu Bar Hidden]

AppCenter 2.0 – Administration Guide (Build 899)

Page 23

[Fig. 27 - Administrator screen – New – Startup tab – Manual Entry]

7. The “Startup” tab allows your to
specify how this approved
application will start. If neither
checkbox is checked, the program
will be able to be started ondemand if it not hidden from the
user (see Fig. 21). The launch and
termination of this application can
be made dependent to the launch
and/or termination of AppCenter™
and optionally a delay can be
inserted before the application is
launched for proper sequencing of
multiple applications being
launched by AppCenter™.
[Fig. 28 - Administrator screen – New (New Program)]

8. An approved application can
edited or deleted by “holding
down” the stylus on the desired
item and waiting for the options
menu to appear …

AppCenter 2.0 – Administration Guide (Build 899)

Page 24

[Fig. 28a - Administrator screen – New (New Program Delete Confirm)]

9. Deleting an existing approved
application prompts you to confirm
the deletion ….

Section 4 - Usage Examples
A. PDA Phone
After the initial installation of AppCenter™ is complete AppCenter™ will
need to be configured to meet your particular needs. This example takes
you thru the basic steps needed to configure AppCenter™ for use on a
PDA Phone (AppCenter™ is not intended for use on
SmartPhone® devices, only Windows Mobile Phone
Edition or Windows Mobile devices).
The first step to take is to start the default
AppCenter™ configuration and have the device sit
at the AppCenter™ Launch screen.
Quick Tip: The Phone application may already be
installed in the default Browse paths defined in
“Administrator -> Tools -> Options -> Browse” (see
Fig. 13). You should always try to use the “Browse
Wizard” to add new approved applications if
possible.
We now need to find out what applications are behind the hardware
buttons for the phone operation (normally “Send” and “End”). To do this,
press the “Send” (Green) phone key on your PDA. AppCenter™ will sense
© 2006, Odyssey Software, Inc • ® All rights reserved

AppCenter 2.0 – Administration Guide (Build 899)

Page 25

the phone application starting but because it is not yet approved, it will
shut this application down and place the results of the violation in the
AppCenter™ logfile. This logfile contains the information necessary to
approve the phone application with minimal setup options.
To view this information, login to the Administration screen and navigate
to “Administrator -> Tools -> Options -> Log” (Fig 11). We will now use this
information to make an approved
application entry. NOTE: The logfile lists
the Window Title and Class of the first
window that tried to open with the
starting of the specified executable.
Unless you are trying to restrict your
phone application to only show a certain
series of windows, it NOT advisable to
restrict the allowed windows by Windows
Title Name and/or Windows Class Name.
The universal wildcard “*|*” is
recommended for most applications.

To create our approval for the Phone application using this manual
method, navigate to “Administrator -> New” (Figs 19 and 20) The logfile
line titled “ExeName” should be used for
all three “General” tab entries requiring a
full path and/or filename for “Execute”,
“Icon File’ and “EXE Name”. The entry
“Execute” does not require a Path
component if the data being entered is
an executable and not a file to open
(see Fig 21 and the description). For the
entries “Icon File’ and “EXE Name”, the
Path component of the Full path and
Filename can be omitted IF THE DESIRED
APPLICATION IS IN THE “\WINDOWS”
directory or any of the subdirectories the
device manufacturer setup to be
searchable for executables.

AppCenter 2.0 – Administration Guide (Build 899)

Page 26
The rest of the
tabs can be
filled in roughly
the same as
these examples.
Make sure to
“Save” the
changes or
select the
button.

Selecting “Cancel” will lose your changes.
Because this device is a
specialized device and supports
some additional hardware
buttons, you will need to make
sure that the dialog in
“Administration -> Tools ->
Options -> Keys tab” does not
disable the phone key and allows
the Volume key if desired. Once
complete, select the “Log” tab
and select “Clear Log” button. This will clear the violations from the log
and allow you to re-test your application to see if any additional violations
resulting from application functions are generating unapproved
application calls that need to be handled.
Once the logfile is cleared, select the
button to
post your changes. Exit the administration application
and examine the AppCenter™ Launch screen. Make
sure the icon image is proper and then select your
icon to test. Test one application function at a time.
After each test, exit the Phone application and reenter AppCenter™ Administration and re-examine
the logfile for additional violations. Repeat the
application approval and application testing process
until the application has been completely operated
and the logfile remains clear. This process is the same
for all applications you wish to add to the AppCenter™ Launch menu.
NOTE: Some logfile violations may be from executables that you may not
want selectable as icons from the AppCenter™ Launch menu but you
want approved so that the Main application functions properly. The
checkbox “Hide from user” in the “Options” tab controls this property.

AppCenter 2.0 – Administration Guide (Build 899)

Page 27

Appendix A – AppCenter™ Log file format
The AppCenter™ Logfile is a text file normally resident in the same
directory as the AppCenter™ executables. This location can be changed
through the use of a commandline option (see Appendix b). The logfile
has the following format:
Each violation consists of a group of 6 lines;
• Line 1 is a general description of the violation
• Line 2 is the date and time (PDT’s time) when the violation occurred
• Line 3 is the ExeName (process name) of the offending process
• Line 4 is the Window Title of the unapproved window (if present)
• Line 5 is the Window Class of the unapproved window (if present)
• Line 6 is the Window Action of the Last action the window
attempted before it was stopped
Below is an example of a typical violation.
Unapproved window detected.
12/02/05 1:08:49 PM
ExeName = cprog.exe
Title = Phone
Class = Dialog
Action = Close window

J
Class = Dialog
Action = Close window

AppCenter 2.0 – Administration Guide (Build 899)

Page 28

Appendix B – AppCenter™ Commandline Options
-terminate – Causes AppCenter™ to shut down, closing any
applications that have the “AutoStop” option set (See Fig 24). This option
is ignored when AppCenter is in admin mode.

-restart – Causes AppCenter™ to shut down, closing any applications
that have the “AutoStop” option set. AppCenter is then restarted and any
applications that have the “AutoStart” option set with be started (See Fig
24). This option is ignored when AppCenter is in admin mode.
-silent

- Specifies whether AppCenter™ should display error messages
on startup if the license key is missing, invalid or expired. When -Silent is
used, AppCenter shuts down without displaying an error message.

-config - Specifies the directory location of the administration
configuration file (AppCenter.cfg), the user defined configuration file
(AppCenter-User.cfg) and the location of the log file (AppCenter.log).
This option obsoletes the commandline options “-adminpath”,
“-userpath”, “-logpath” and “-path” options
Note: The file name(s) cannot be specified, just the path. If there are no
command line arguments, all file locations are in the same folder as the
AppCenter™ Executables (AppCenter.exe and optionally
AppCenterAdmin.exe).
Example : -config "\Storage Card\AppCenter\Config"

AppCenter 2.0 – Administration Guide (Build 899)

Page 29

Appendix C – AppCenter™ Configuration files
AppCenter Configuration (AppCenter.CFG)
The AppCenter CFG file contains the license and administrative password
settings. The license setting is required for AppCenter to run. If a password
setting is not supplied AppCenter will create the password setting with the default
value of "odyssey". To change the password, enter a new password in plain text.
When AppCenter is launched it will automatically encrypt the password and save
it back to the CFG file. The Symbol/Motorola build of AppCenter will only contain
the Password entry in the AppCenter.cfg file.
License YTYTW3DE7AAEPCDA85HWRPWQK2 "Evaluation"
Password {ENC}n2Vc20G1Ig==

AppCenter User Configuration (AppCenter-User.CFG)
The AppCenter-User CFG file contains configuration options for approved
applications and the general appearance of AppCenter. This file is auto-created
when AppCenter is first run. If a previous version of AppCenter was on the device
any existing registry settings will be read and saved to this file. If no existing
settings exist this file will be created with the default settings listed below. All
Administration actions done with the UI on the device are captured and saved
here.

System Options
The following settings are used on a global basis for the current AppCenter
session.
HideStartMenu – This setting is used to disable the Start Menu and enable the
other AppCenter task bar options. The default value is true/enabled.
ShowStandardIcons – This setting is used in conjunction with the
HideStartMenu setting to control taskbar functionality. The default value is
false/disabled. See Appendix F for more information.
ShowHome – This setting will display a home icon on the AppCenter task bar
that can be used at any time to return to the main AppCenter screen. The
default value is true/enabled.
AdminLoginDisabled – This setting controls whether or not the login menu item
is available from user mode. The default is 0 which means the login menu item
is available. Set to 1 to disable the login option.
TitleBold – This setting allows you to change the weight of the font used to
display the AppCenter task bar. TitleBold defaults to true (1) which is
consistent with the font used in the previous version. Set false (0) to reduce the
weight of the font used in the AppCenter task bar.

AppCenter 2.0 – Administration Guide (Build 899)

Page 30

TitleFontSize – This setting allows you to change the size of the font used in the
AppCenter task bar. TitleFontSize defaults to 11 which is consistent with the
font size used in the previous version. Depending on which AppCenter options
are enabled, a long title may not have room to display on the AppCenter
task bar. Reducing the font size allows more of the title to display. Values in
the range of 9-14 are recommended. Values of 6-36 are allowed but may
produce undesirable results. If a value outside the allowed range is used the
font size is set to the default of 11.
AlternateTitle – This setting allows you to change the default AppCenter task
bar title. The default is an empty string which means the title will be
"AppCenter".
AdapterName – AdapterName is used in conjunction with DisplayIpAddress
and DisplayMacAddress. AdapterName controls which adapter is used to
retrieve the IP or MAC address. Partial matches are supported. For example,
an AdapterName of "NETWLAN1" would match an adapter named
"NETWLAN1" or "CTIP\NETWLAN1". If no match is found for AdapterName, the
normal AppCenter title is displayed regardless of how DisplayIpAddress and
DisplayMacAddress are set. AppCenter will attempt to set this value to a
device's 802.11b radio if this setting is not provided.
DisplayIpAddress – This setting instructs AppCenter to use the current IP
address of the device as the AppCenter task bar title. DisplayIpAddress
defaults to false (0). Set true (1) to display a device's IP address as the
AppCenter task bar title. If a device has no IP address, the normal AppCenter
title is displayed.
DisplayMacAddress – This setting instructs AppCenter to use the current MAC
address of the device as the AppCenter task bar title. DisplayMacAddress
defaults to false (0). Set true (1) to display a device's MAC address as the
AppCenter task bar title. If a device has no MAC address, the normal
AppCenter title is displayed. If both DisplayMacAddress and DisplayIpAddress
are set true, the MAC address is displayed.
ShowBatteryLevel – This setting will display an icon on the AppCenter task bar
that will indicate the current battery strength. The default value is
true/enabled.
BatteryPercentFormat - BatteryPercentFormat defaults to false (0) which is
consistent with previous versions. Set true (1) to change the battery display
from an icon to a percentage that indicates the remaining battery charge.
ShowAirBeam (Symbol/Motorola-only) – This setting is used to display an icon
on the AppCenter task bar that will indicate whether AirBeam Safe is
connected or not, roaming, or disabled. The default value is true/enabled.
ShowSignalStrength – This setting is used to display an icon on the AppCenter
task bar which indicates the wireless network signal strength. The default
value is true/enabled.

AppCenter 2.0 – Administration Guide (Build 899)

Page 31

FusionMode (Symbol/Motorola-only) – This setting provides access to the new
Symbol/Motorola Fusion radio utilities and allows more control over the action
taken when a user taps the signal strength icon. The first time AppCenter is run
this registry setting is created with the default value of 0. If this setting is
greater than zero, it will override the MobileCompanionMode setting. The
following values are supported:
0 - No action is taken.
1 - Run the Fusion status program.
2 - Run the Fusion diagnostics program.
3 - Show a menu for status or diagnostics.
4 - Show the full Fusion menu.
ShowConnectivity – This setting allows you to control whether a network
connectivity icon is displayed on the task bar. The icon indicates whether or
not there is any connection available. All connection types are supported,
including ActiveSync, Ethernet cradle, WLAN, WWAN and Bluetooth. The
default for this setting is false (0). This setting is only supported under WM5.
MobileCompanionMode (Symbol/Motorola-only) - This setting allows more
control over the action taken when a user taps the signal strength icon. There
is no user interface for this setting. The first time AppCenter is run this setting is
created with the default value of 2 which is consistent with previous versions.
The following values are supported:
0 - No action is taken.
1 - The Mobile Companion Status dialog is launched.
2 - The Mobile Companion popup menu is displayed.
On devices where Mobile Companion is not running, this setting has no
effect and tapping the signal strength icon always results in no action.
ShowWwanSignalStrength – Controls whether to display the WWAN signal
strength on a task bar on devices that support the Radio Interface Layer
(RIL.DLL). Displaying both WLAN and WWAN signal strength at the same time
uses the same amount of task bar area as displaying just WLAN or WWAN
signal strength alone.
ShowTime – This setting will display the current time on the AppCenter task
bar. The default value for this setting is true/enabled.
24HourTimeFormat - 24HourTimeFormat defaults to false (0) which is consistent
with previous versions. Set true (1) to change the time display from a 12 hour
format (11:59p) to a 24 hour format (23:59).
AddWwanPhoneMenu – This setting allows more control over the action taken
when a user taps the WWAN signal strength icon. The default for this setting is
false (0). When set true a menu displays when the WWAN signal strength icon
is tapped. The menu contains choices for turning the phone on and off. The
ShowWwanSignalStrength settings must be true for this setting to have any
effect. This setting is only supported on devices that have RIL installed.

AppCenter 2.0 – Administration Guide (Build 899)

Page 32

BlockIncomingCalls – This setting allows more control over the action taken
when a phone call is received by the device. The default for this setting is
false (0). When set true, AppCenter will hangup the phone whenever an
incoming call is detected. This setting is only supported under WM5.
ShowPhoneIcons – The setting hen set true, AppCenter will display icons for
missed calls, unread text messages and voice mail. Tapping the missed calls
icon takes you to the call log filtered to show just missed calls. Tapping the
text messages icon takes you to the text message inbox. Tapping the voice
mail icon brings up the phone and attempts to connect to the voice mail
box. The default for this setting is false (0). This setting is only supported under
WM5.
When ShowPhoneIcons is set true, the phone and messaging applications
need to be approved to support tapping on the icons. The simplest way to do
this is to add cprog.exe and tmail.exe to the approved EXEs under System. For
the Palm Treo, also add *|DesktopExplorerWindow to the approved windows
under Shell32.
VoiceMailPhoneNumber – This setting is used to tell AppCenter what number
to dial when the voice mail notification icon is tapped. It defaults to an
empty string. If a number is specified, AppCenter will dial this number. The
number can be a full phone number or can be a shortcut number such as *86
on Verizon. If this setting is left empty, AppCenter will attempt to retrieve the
device phone number and call that number. If AppCenter can't retrieve the
device phone number it brings up the phone application. This setting is only
supported under WM5.
SuppressSmsNotifications – This setting tell AppCenter to automatically close
the "New Text Message" notification bubble when an SMS message is
received. The default value is false (0) which is backward compatible with
the previous version.
RegionalTimeFormat – RegionalTimeFormat defaults to false (0) which is
consistent with previous versions. Set true (1) to display the time based on the
current regional settings. When RegionalTimeFormat is set true the
24HourTimeFormat setting is ignored.
RegionalTimeOptions – RegionalTimeOptions give you further control over the
time display. RegionalTimeOptions is ignored unless RegionalTimeFormat is set
to true. The default setting is 2 which removes seconds from the time display.
The default setting is always enforced regardless of what other options are
used. That is, you are not allowed to display seconds. Additional options are
specified by adding the desired option numbers together. If an invalid option
number is specified, all options are ignored. The following options are
available:
1 = Only display the hour. Do not display minutes or seconds.
2 = Only display the hour and minutes. Do not display seconds.
4 = Do not display AM or PM or international equivalents.
8 = Always use 24 hour format.

AppCenter 2.0 – Administration Guide (Build 899)

Page 33

2147483648 = Always use the default format for the current locale. Ignore
any user overrides.
ShowVolume – This setting will display the volume icon on the AppCenter task
bar and enable the volume slider control. The default value for this setting is
false/disabled.
VolumeKeysAllowed – This setting allows you to control whether the volume
hardware keys are disabled. The setting idefaults to true (1) which means
volume hardware keys are enabled. Set false (0) to disable volume hardware
keys. There is no user interface for this setting. The first time AppCenter is run
this setting is created with the default value.
DisablePhoneKey – This setting allows you to disable the phone key on
Symbol/Motorola 9000 devices. The phone key is the key with the green dot
that launches the phone application. The DisablePhoneKey defaults to false
(0) which is consistent with previous versions. Set true (1) to disable the phone
key. The first time AppCenter is run this setting is created with the default
value.
HideSip – This setting allows the SIP to be displayed in the main AppCenter
user program. The HideSip setting defaults to true (1) which is compatible with
previous versions. Set to false (0) to display the SIP. The first time AppCenter is
run this setting is created with the default value.
BrowseAllShortcuts – This setting tells AppCenter to list all shortcuts in the list of
applications that can be approved from admin mode. The setting defaults to
true (1). If set to false (0), only shortcuts whose target file extension is in the
BrowseExtensions setting will be added to the admin mode browse window.
By default, all shortcuts in the BrowseFolders setting are listed.
BrowseFolder – This setting allows you to override the default folders searched
when browsing for an approved application. The setting is a folder name
delimited and all subfolders of the listed folder are also searched. Each folder
is listed on a separate BrowseFolder settings line.
The default folders are:
BrowseFolder
BrowseFolder
BrowseFolder
BrowseFolder

"\Windows\Start Menu"
"\Windows\Startup"
"\Windows\Programs"
"\Program Files"

BrowseExtension – This setting provides the default file extensions searched
when browsing for an approved application. The extensions used are not
limited to executable programs and are not case-sensative. Document file
extensions can also be used. Do not add a "." as part of the extensions you
provide. Normally shortcuts are always browsed regardless of the target file
extension. You can change this behavior with the BrowseAllShortcuts setting.
Each extension is listed on a separate BrowseExtension settings line.
The default extensions are:

AppCenter 2.0 – Administration Guide (Build 899)

BrowseExtension
BrowseExtension

Page 34

exe
vb

BrowseControlPanel – This setting tells AppCenter whether or not control panel
applets are included in the "Select a program..." dialog when creating a new
approved program. The default is true which is compatible with previous
versions.
NeverCloseExe/AlwaysCloseExe – These settings tell AppCenter how to
handle unapproved windows. AppCenter attempts to send all unapproved
windows to the bottom of the Windows z-order. AppCenter then determines
the EXE name that owns the window. If the EXE name is not on AppCenter's
internal list of Windows system processes, AppCenter attempts to close the
window. In most cases this results in the application being shut down.
The default behavior for unapproved windows can be overridden with
NeverCloseExe and AlwaysCloseExe settings. AppCenter will never attempt
to close a window that belongs to an EXE listed under the NeverCloseExe
setting. These windows will just be sent to the bottom of the z-order.
AppCenter will always attempt to close windows that belong to an EXE listed
under the AlwaysCloseExe setting.
Multiple files may be listed one per setting line i.e.
AlwaysCloseExe
AlwaysCloseExe
NeverCloseExe
NeverCloseExe

always1.exe
always2.exe
never1.exe
never2.exe

These settings should not be changed unless instructed to by Odyssey
Software Technical Support.
DisableMemoryCardInsert – This setting tells AppCenter to prevent memory
cards from being mounted in the file system. This also stops any auto-run
programs on the memory cards from running. This feature is supported on
PocketPC 2003 and later. The setting defaults to false (0).
DisableIR – This setting tells AppCenter to disable the "Receive all incoming
beams" setting in the control panel. This makes a device incapable of
automatically receiving IR data from another device. This feature is
supported on PocketPC 2003 and later. The setting defaults to false (0).
DisableBluetooth – This setting tells AppCenter to turn off the Bluetooth radio
on devices where the Windows CE BthSetMode function is operative.
Because of the large number of different Bluetooth implementations,
BthSetMode is not always effective in turning the Bluetooth radio off. This
feature is supported on PocketPC 2003 and later. The setting defaults to false
(0).

AppCenter 2.0 – Administration Guide (Build 899)

Page 35

DisableActiveSync – This setting tells AppCenter to disable a device from
connecting via ActiveSync. Additionally, if an ActiveSync connection is
established when AppCenter starts, AppCenter will close the connection.
Closing an active connection on Windows Mobile 5.0 devices only works on
devices using the RNDISFN1 adapter. The setting defaults to false (0).
BlockTaskbarKey – This setting allows AppCenter to be configured to block
keys that bring up the start menu. This behavior was previously hardcoded in
AppCenter and the default settings are consistent with past versions. Different
keys bring up the start menu on different devices, so the default settings are
not all needed on every device, and can in fact interfere with desired
behavior.
IconsDisabledCount – This setting tells AppCenter to initially disable all icons
for X seconds when AppCenter starts. The default is 0 which is backwards
compatible with previous versions.
AlwaysUseAppCenterTitle – This setting tells AppCenter to always use the
currently configured AppCenter title as the taskbar title rather than the title
of the foreground program. The default is false (0) which is backwards
compatible with previous versions.
AirBeamLock (Symbol/Motorola-only) – This setting tells AppCenter to disable
all approved application icons when an AirBeam update is in process. The
default is false (0) which is backwards compatible with previous versions.
ViewMode – This setting tells AppCenter how to display the list of approved
applications. ViewMode has three settings. LargeIcons mode is the default
and is the same as previous versions of AppCenter. SmallIcons mode uses
smaller icons that display to the left of the program descriptions. Programs will
be in 1 or more columns depending on the length of the descriptions, the font
size used and whether the device is in portrait or landscape orientation. List
mode uses no icons and displays a single list of program descriptions centered
on the screen.
ViewTextColor, ViewBackgroundColor – This setting tells AppCenter which
colors to use for the display of the AppCenter main form. ViewTextColor
defaults to 0x000000 (Black) and controls the color of the text used to display
the program descriptions. ViewBackgroundColor defaults to 0xFFFFFF (White)
and has two purposes. First, if no custom background bitmap is being used,
the background color is used for the entire AppCenter background. Second,
the background color is always used as the text background color so when
using custom bitmaps as a background you may want to set
ViewBackgroundColor to match the predominant color of the bitmap. Colors
can be specified in decimal or hexadecimal. Precede the number with "0x" to
specify hexadecimal. For example, 255 and 0x0000FF both specify bright red.
In hexadecimal format the first two digits specify blue, the next two digits
specify green and the last two specify red. Each two digits specify 256 shades
of the color with 0/0x00 being darkest and 255/0xFF being brightest. When all
three color settings are equal you get varying shades of gray from white to
black. 16,777,216 different colors can be specified but there is no guarantee

AppCenter 2.0 – Administration Guide (Build 899)

Page 36

a device can render all the colors. If a color isn't supported, the closest
match is used.
ViewFontSize, ViewFontBold – This setting tells AppCenter which font to use for
the display of the AppCenter main form. ViewFontSize defaults to 12 and
ViewFontBold defaults to false. Together they control the appearance of the
font used for program descriptions.

Application Options
The following settings are used on an application by application basis. Each
setting must be preceded by a Program statement and the application
name.
i.e. Program Calculator Execute \windows\calc.exe
Execute – This setting is the name of the program, document or shortcut to
launch.
Arguments – This setting allows you to pass any command line arguments
required for running the application.
ExeName – This is the name of the process that is launched. For example, the
"Execute" setting might be "\My Documents\Letter1.psw" and the "EXE Name"
would be "pword.exe". In most cases the "Execute" setting will contain the full
path name of the EXE while "EXE Name" will contain just the EXE name with no
path.
IconFile – This is the name of the executable file that contains the icon
resource that is to be displayed on the AppCenter screen for this application.
ApprovedWindow – This setting tells AppCenter what window titles are to be
approved for this application. Since AppCenter now uses the EXE name as
the primary match, most approved programs should simply specify *|* as the
only approved window. Previously, approved windows were global in scope.
Now, approved windows apply only to the approved program under which
they are entered. For example, under previous versions an approved window
of *|* would approve all windows system wide. Now *|* will approve all
windows for the process specified by the "EXE Name" setting. Additionally, the
wildcard characters * and ? are now fully supported anywhere in the window
title or class name. * matches any sequence of characters. ? matches any
one character.

IMPORTANT!!!! The sequence is {Window Title}|{Window Class}
ReadOnly – This setting can be used to disable modification of the approved
application when AppCenter is in Admin Mode. Default value is False.
HideFromUser – This setting indicates to AppCenter whether this approved
application should be available to users through AppCenter. The default
value for this setting is True.

AppCenter 2.0 – Administration Guide (Build 899)

Page 37

HideMenuBar – This setting allows you to hide the command bar for an
approved program. The program's window is also resized to use the extra
screen space. Applications must be written to make use of all available
screen space for the Hide Menu Bar to be effective. The default value for this
setting is False.
HideDoneButton – This setting allows you to hide the Smart Minimize (X) button
of the approved application. The Smart Minimize (X) button is hidden for all
applications in AppCenter if the Hide Start Menu option is checked from the
Admin Options global options screen. The default value for this setting is False.
HideStartMenu – This setting allows you to hide the Start Menu when the
approved application is running. The default value for this setting is True.
ShowStandardIcons – This setting is used in conjunction with the
HideStartMenu setting to control taskbar functionality while this application is
running. The default value is false/disabled. See Appendix F for more
information.
HideSip – This setting allows you to hide the SIP (pop-up on screen keyboard)
of the approved application. The default value for this setting is False.
AutoStart – This setting tells AppCenter to automatically launch an approved
application when AppCenter starts. The default value for this setting is False.
StartupDelay – This setting is used in conjunction with the AutoStart setting.
The StartupDelay specifies, in seconds, how long of a delay to wait before
starting up the application. The default value is zero (0).
AutoStop – This setting tells AppCenter whether this application should be
closed when AppCenter is shutdown or restarted. It defaults to false (0). If this
setting is true (1), AppCenter will shut down the program when AppCenter
ends. AppCenter attempts to gracefully close the program by sending the
WM_CLOSE message to all top level windows owned by the program. If this
approach is not successful, AppCenter terminates the program. The ExeName
setting for a program must be correct for this functionality to work.
RelaunchInterval – This setting can be used to disable an approved
application icon for a period of time after it has been initially tapped. This
prevents an application from being launched multiple times. This may be
necessary when launching .NET Compact Framework applications that take a
long time to initialize and load. The interval is entered in hex.
VolumeKeysAllowed – This has been a global setting within past AppCenter
releases. The default value is the current value of the global
VolumeKeysAllowed setting. That setting now is meaningful only when
AppCenter is in the foreground. VolumeKeysAllowed controls whether or not
the volume hardware keys are disabled for a specific approved application.
RequiredIpAddress – This setting tell AppCenter to only enable the approved
application if the device has a specific IP address. The settings can be used
multiple times to specify multiple IP addresses. The wildcard characters * and

AppCenter 2.0 – Administration Guide (Build 899)

Page 38

? can be used. Ex: 192.168.1.*. When both RequiredIpAddress and
RequiredSSID are used, both requirements must be met for the program to be
enabled. The default setting is blank which is compatible with previous
versions.
RequiredSSID – This setting tell AppCenter to only enable the approved
application if the device is associated to a specific access point. The settings
can be used multiple times to specify multiple SSIDs. The wildcard characters
* and ? can be used. Ex: ABC*. When both RequiredIpAddress and
RequiredSSID are used, both requirements must be met for the program to be
enabled. The default setting is blank which is compatible with previous
versions.
AddToToolsMenu – This setting tells AppCenter to place the approved
application descriotion on the AppCenter Tools menu. Tapping the menu
item launches the program. If HideFromUser is set true, the program appears
only on the Tools menu, otherwise the program also appears as an icon on
the AppCenter screen. The menu items appear in the same order that
programs are defined in the configuration file. The default value is false (0)
which is compatible with previous versions.

AppCenter 2.0 – Administration Guide (Build 899)

Page 39

Appendix D – Pre-approved applications
The following is the list of Defined Approved Applications with modifiable
attributes that are pre-approved when AppCenter™ is first run. These are
discussed in detail in Fig 19a:
Calculator (calc.exe) – used as a User Mode application example
Dialup Networking (rnaapp.exe)
Connection Manager ()
ActiveSync (repllog.exe)
CAB Files (wceload.exe)
Mobile Companion (nictt.exe) – For Symbol/Motorola S24 radio devices
only
Welcome (welcome.exe)
Device (device.exe)
Shell32 (shell32.exe)
GWES (gwes.exe)
The following is the default list of Executables whose windows or processes
will never be closed by AppCenter™. NOTE: You can override this
behavior by adding an EXE name to the “AlwaysCloseExe” configuration
setting. Be aware that closing some system executables can cause the
device to crash or behave strangely. Add these “AlwaysCloseExe“
entries AT YOUR OWN RISK.
cemgrc.exe
evmon.exe
nictt.exe
remnet.exe
shell32.exe
udp2tcp.exe

conmanclient.exe
filesys.exe
nk.exe
repllog.exe
srvtrust.exe
welcome.exe

ctlpnl.exe
gwes.exe
poutlook.exe
rnaapp.exe
tmail.exe
connmgr.exe

device.exe
keymode.exe
rapisrv.exe
services.exe
toolbox.exe

AppCenter 2.0 – Administration Guide (Build 899)

Page 40

Appendix E – Installation Instructions
The installation of AppCenter™ consists of THREE steps (Step 2 OR 3):
1.
Copy the files to the device
a. Depending on how you wish to allow Cold-Boot recovery or
not will determine where you place the following files
i. AppCenter.exe
ii. AppCenterAdmin.exe (only required for the
Administrator UI)
iii. AppCenter.cfg
b. If the “AppCenter.cfg” file is not located in the same directory
as the Executable(s), then the “-config" command line option
WILL BE REQUIRED
2.
Configure AppCenter™ via the AppCenter Administration
application

-OR3.

Copy an existing AppCenter User Configuration
a. Copy the “AppCenter-User.cfg” file to clone an existing
configuration
b. If the AppCenter-User.cfg file is not located in the same
directory as the Executable(s), then the “-config" command
line option WILL BE REQUIRED
4.
Create a Shortcut to the now resident AppCenter™ executable
and place it in the “\windows\startup” directory. NOTE: Cold Boot
recovery may change this startup method.
a. If command line options are required, you will need to edit
the shortcut to add them.
i. Use either ActiveSync or Athena™ to copy the shortcut
(“AppCenter.lnk”) to your PC for editing.
ii. The format of a shortcut is as follows :
99#XXXXXXXXXXXXXXXXXXXX
Where “99” is the number of “X”s, “# ” is a literal
constant and the “X”s represent the entire
commandline
iii. An example of a shortcut for AppCenter™ :
67# "\Windows\Start Menu\Programs\AppCenter.exe" -config "\Application”
iv.

Any arguments in the commandline that contain
spaces must be enclosed in double quotes : Note that
you cannot enclose multiple arguments within quotes
as they will not be treated as separate arguments

AppCenter 2.0 – Administration Guide (Build 899)

Page 41

Appendix F – New Taskbar Options
AppCenter can be configured to control the Start Menu and Taskbar in
three different ways. Traditionally AppCenter was configured to either
Hide the Start Menu or not.
HideStartMenu Option
True
False
A new configuration file setting named ShowStandardIcons has been
added. This setting is located under taskbar options and under program
options. The default is false. This setting works in conjunction with the
HideStartMenu setting to control taskbar functionality and similar to
HideStartMenu it can be configured on a program by program basis.
When HideStartMenu is false, the normal windows taskbar is displayed and
functions normally. When HideStartMenu is true and ShowStandardIcons is
false the AppCenter taskbar is displayed. When HideStartMenu is true
and ShowStandardIcons is true the normal windows taskbar is displayed
but the start menu is disabled. The standard taskbar icons can be used.

When ShowStandardIcons and ShowHome are set true, tapping the start
menu icon brings AppCenter to the foreground. That is, tapping the start
menu icon behaves the same as tapping the AppCenter taskbar home
icon.
When ShowStandardIcons is set true, AppCenter uses fewer CPU cycles
because it doesn't have to track such things as signal strength and battery
usage.
NOTE: When ShowStandardIcons is set true for any or all programs, it is
recommended that it also be set true for Shell32.exe. Otherwise when a
taskbar icon is tapped and a notification bubble displays the taskbar is
switched back to the AppCenter taskbar.
When ShowStandardIcons is set true for any or all programs, the taskbar
icons contain links to other programs. To allow user navigation to these
programs, they will need to be approved. Simply tap these links and then
© 2006, Odyssey Software, Inc • ® All rights reserved

AppCenter 2.0 – Administration Guide (Build 899)

Page 42

check the AppCenter log to determine which programs/windows need to
be approved. Please note that adding *|* as an approved window for
Shell32.exe will allow all Settings applets to be used, so in general only
approve windows for Settings the user is allowed to change.

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Page Count                      : 43
Producer                        : GPL Ghostscript 8.15
Create Date                     : 2008:09:03 12:24:29
Modify Date                     : 2008:09:03 12:24:29
Title                           : Microsoft Word - AppCenter 2.0 WM Admin Guide Build 899.doc
Creator                         : PScript5.dll Version 5.2.2
Author                          : jsullivan

EXIF Metadata provided by EXIF.tools

AppCenter 2.0 WM Admin Guide Build 899 App Center

Navigation menu

Versions of this User Manual:

Views

Navigation