• No results found

Solutions for managing a fleet of Trimble Windows Mobile devices

N/A
N/A
Protected

Academic year: 2021

Share "Solutions for managing a fleet of Trimble Windows Mobile devices"

Copied!
34
0
0

Loading.... (view fulltext now)

Full text

(1)

Solutions for managing a fleet of

Trimble Windows Mobile devices

(2)

Agenda

Learn AEP’s device management history and the

common problems large organizations face in

managing devices.

Best practices for admin managing Trimble

Windows Mobile devices.

Tips on creating an in-house device

management solution.

(3)

AEP MDM Challenges

500+ Trimble Windows Mobile devices

(4)

AEP MDM Challenges

(5)

AEP MDM Challenges

2 Admins/Support personnel (Selfies)

Hello,

I’m Matt

Hola,

I’m Josh

(6)

AEP MDM Challenges

Heavily-used devices. Used for over 6,000

designs from January 2014 through October

10th of 2014.

(7)

Where We Started

iPaq’s, 2003 GeoExplorers, 2005 Series

GeoExplorers, 2008 Series GeoExplorers, and

Nomad’s

Manual installations requiring user interaction

throughout the entire process.

Long “how to” installation guides.

Install everything for the user from an SD card before

sending the device to the user.

(8)

Provisioning via Commontime

Why provisioning via Commontimes mSuite

platform.

Already being used internally by AEP

Push all cabs, files and registry settings

automatically requiring the user to sign in with

email credentials.

Commontime wrote a C# application to handle the Cab

installs.

Provides a secure tunnel back into AEP’s network

for remote syncing of data.

(9)

Provisioning via Commontime

Pain Points

No ability to factory reset the device resulting in a fair

number of user mistakes on loading new software

(10)

Provisioning via Commontime

Pain Points

Not intended for Windows mobile device management.

Again Commontime needed to write a C# application to

(11)

Provisioning via Commontime

Pain Points

Initially required users to call support to clear the

previous instance of the device from the server before

factory resetting and provisioning.

(12)

Provisioning via Commontime

Pain Points

(13)

Email with Instructions

All GeoXH 6000 users,

The following procedure should be used to update your GeoXH 6000 with the latest version of Asset Designer and Scout. If you still have an older Dell Windows XP PC, you will need to connect to a newer Windows 7 PC in order to complete step 5. Steps 6-8 can be completed while the device is connected to any PC that is connected to the AEP network.

Your device should be disconnected from the PC for steps 1 through the first part of step 4.

1. Click this link for instructions –see page 34—to factory reset your GeoXH 6000. This will remove all existing data from your device.

2. Click this link for instructions to configure your GeoXH 6000 after the factory reset is complete. 3. Click this link for instructions to get your device connected to your Windows 7 PC.

4. Click this link for instructions to provision your device with CommonTime.

With your device connected to your PC, Tap Start > Programs > Asset Manager > DB Sync Tool.

In the user name field fill in your user id (ex. S123457) in place of the word userid (see example). In the Password field fill in your AEP LAN password (this is the password that you logon to your PC with).

Tap Initialize, this will create the database on your device. Once complete the Initialize button will change and be labeled Synchronize.

NOTE: You will want to change the default point and span type in Asset Designer before you collect any new data. The default point type and span type can be changed in Asset Designer under Settings > Options.

NOTE: Those using Real-Time correction from an internet source will need to copy their specific XML file into their

device. If you need assistance check with your local support person or call the EBP Hotline 8-200-3324. AEP-Texas users call 8-430-5500.

(14)

Provisioning via Commontime

Pain Points continued

Still lots of user interaction.

(15)

Where we are now

We primarily have 6000 Series GeoExplorers,

about 400, with a few 2008’s and Nomad’s.

Now getting a few GeoExplorer 7x devices.

New process for 6000 Series and 7x devices only.

Created a Cab to handle almost everything with a

batch file to get things kicked off.

(16)

Batch File

SetLocal EnableDelayedExpansion @echo off @set REBOOT=false \\dea\ldpro\Asset_Manager_Suite\Support\rapiutils\RAPIEX~1.EXE "\Windows\Startup" @set ERR=%ERRORLEVEL%

@if %ERR% NEQ 0 (

@echo **************************************************************************** @echo *

@echo * Sponge Bob Not Found! @echo *

@echo * Please make sure your device is

@echo * plugged in and has a Windows Mobile Device Center connection @echo * and then try again.

@echo *

@echo **************************************************************************** @pause

)

::Creates folder if it does not exists

\\dea\ldpro\Asset_Manager_Suite\Support\rapiutils\RapiDir.exe -m "\My Documents\TrimbleGeoxInstall" PUSHD \\dea\ldpro\Asset_Manager_Suite\Geo_Provisioning\TrimbleGeoxInstall

@CALL :copyInstallFile

\\dea\ldpro\Asset_Manager_Suite\Support\rapiutils\RapiStart.exe "\Windows\wceload.exe" "\"\My Documents\TrimbleGeoxInstall\AEP_WM_Setup.CAB\" /nodelete"

@echo * @echo *

@echo * PLEASE FINISH THE AEP DEVICE CONFIGURATION ON THE DEVICE!!!!!! @echo *

@echo * pause

:copyInstallFile

\\dea\ldpro\Asset_Manager_Suite\Support\rapiutils\RapiCopy.exe "AEP_WM_Setup.CAB" "\My Documents\TrimbleGeoxInstall\AEP_WM_Setup.CAB"

(17)

Visual Studio Solution CAB contents

C# project that installs the applications, copy’s and renames

files, and provides a GUI (AEP_WM6.exe).

SetupDLL that kicks off AEP_WM6.exe once the CAB finishes

Contains everything to install on both 6000’s and 7x’s including

OS firmware, GPS firmware updates and all registry settings.

(18)
(19)

Current Provisioning Process

User

factory

resets the

device.

(20)
(21)
(22)

Current Provisioning Process

Commontimes mSuite is installed to provide the secure tunnel

back into AEP’s network for syncing of data from the field. This

will go away once we move to the Cloud implementation of our

damage assessment tool (GeoSpatial Innovations Scout).

(23)
(24)
(25)

Old Email with Instructions

All GeoXH 6000 users,

The following procedure should be used to update your GeoXH 6000 with the latest version of Asset Designer and Scout. If you still have an older Dell Windows XP PC, you will need to connect to a newer Windows 7 PC in order to complete step 5. Steps 6-8 can be completed while the device is connected to any PC that is connected to the AEP network.

Your device should be disconnected from the PC for steps 1 through the first part of step 4.

1. Click this link for instructions –see page 34—to factory reset your GeoXH 6000. This will remove all existing data from your device.

2. Click this link for instructions to configure your GeoXH 6000 after the factory reset is complete. 3. Click this link for instructions to get your device connected to your Windows 7 PC.

4. Click this link for instructions to provision your device with CommonTime.

With your device connected to your PC, Tap Start > Programs > Asset Manager > DB Sync Tool.

In the user name field fill in your user id (ex. S123457) in place of the word userid (see example). In the Password field fill in your AEP LAN password (this is the password that you logon to your PC with).

Tap Initialize, this will create the database on your device. Once complete the Initialize button will change and be labeled Synchronize.

NOTE: You will want to change the default point and span type in Asset Designer before you collect any new data. The default point type and span type can be changed in Asset Designer under Settings > Options.

NOTE: Those using Real-Time correction from an internet source will need to copy their specific XML file into their

device. If you need assistance check with your local support person or call the EBP Hotline 8-200-3324. AEP-Texas users call 8-430-5500.

(26)

Current Email

All GeoXH 6000 & 7x users,

The following procedure should be used to update your GeoXH 6000 & 7x with the latest version

of GSI Designer and Scout. If you still have an older Dell Windows XP PC, you will need to

connect to a newer Windows 7 PC in order to complete step 5. Steps 6-8 can be completed while

the device is connected to any PC that is connected to the AEP network.

1.

Click this link for instructions

–see page 34—to factory reset your GeoXH 6000. This will

remove all existing data from your device.

2.

Click this link for instructions

to get your device connected to your Windows 7 PC.

3.

Click this link for instructions

to provision your.

NOTE: Those using Real-Time correction from an internet source will need to copy their specific

XML file into their device. If you need assistance check with your local support person or call

the EBP Hotline 8-200-3324. AEP-Texas users call 8-430-5500.

(27)

Installation guide comparison

Commontime Guide:

(28)

What is next?

We are currently looking at 3

rd

party software

vendors of Mobile Device Management (MDM)

solutions.

Move to cloud implementation of current

software.

Possibly enroll device in domain to access

network drives and resources.

Connect devices to our Wi-Fi network.

(29)

3

rd

party MDM solutions advantages

No custom applications need to be written and kept up to date.

Who will update it as needs change if I leave the group?

Adding features is time consuming.

Creating groups and their policy's can be done dynamically.

The ability to pushing out software updates and enforcing user

to update.

Installation for users is further simplified.

Kiosk like mode allowing users to only be able to use

applications and functions we allow.

Security options.

(30)

3

rd

party MDM solutions options

Most vendors offer 2 options:

Purchase

(31)

3

rd

party MDM solutions options

If purchased the server side software is installed and hosted on

your servers and maintained by your IT (with support from the

vendor).

Potential scalability issues and slower updates

Purchasing has a higher upfront capital cost but a low yearly

(32)

3

rd

party MDM solutions options

The subscription model is cloud or SaaS implementation with an

annual fee, typically a per device fee.

Purchasing has a higher upfront capital cost and a yearly

maintenance fee.

SaaS has a higher yearly fee but is lower then the upfront

purchasing fee. If you purchase a 5 year or longer subscription

you may be able to capitalize this fee.

(33)

Domain enrollment, Wi-Fi and Security

IT told us with no uncertainty that we cannot enroll the devices

on the domain due to security risks.

Wi-Fi is problematic due to the lack of support for newer

security protocols on the Windows Mobile devices but we are

exploring options.

Security is currently not a priority for these devices but they will

be in the near future.

(34)

Conclusion

Supporting hundreds of devices across multiple states with

minimal support can be achieved with a little forethought and

work.

Try to keep your solution as simple and “stupid proof” as

possible.

References

Related documents