Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Afaria Client in Windows OS Image

5 posts in General Last posting was on 2008-09-04 18:33:01.0Z
Thomaz Koberle Posted on 2008-09-02 19:11:22.0Z
From: "Thomaz Koberle" <tkoberle@sybase.com>
Newsgroups: ianywhere.public.afaria.general
Subject: Afaria Client in Windows OS Image
Lines: 10
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48bd8fda@forums-1-dub>
Date: 2 Sep 2008 12:11:22 -0700
X-Trace: forums-1-dub 1220382682 10.22.241.152 (2 Sep 2008 12:11:22 -0700)
X-Original-Trace: 2 Sep 2008 12:11:22 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:131
Article PK: 261

One of our customers is considering the idea of building a custom OS image
which includes the Afariia Client in ROM to ease the process of provisioning
and to ensure the client does not get wiped out after a hard reset. Has this
idea ever been considered and perhaps tested ? My concern is that putting
the client in ROM might break the updates and perhaps break the client
altogether.

Thomaz


forums.sybase.com Posted on 2008-09-03 04:19:05.0Z
From: "forums.sybase.com" <SybaseiAnywhere@Live.com>
Newsgroups: ianywhere.public.afaria.general
References: <48bd8fda@forums-1-dub>
In-Reply-To: <48bd8fda@forums-1-dub>
Subject: Re: Afaria Client in Windows OS Image
Lines: 35
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48be1039$1@forums-1-dub>
Date: 2 Sep 2008 21:19:05 -0700
X-Trace: forums-1-dub 1220415545 10.22.241.152 (2 Sep 2008 21:19:05 -0700)
X-Original-Trace: 2 Sep 2008 21:19:05 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:132
Article PK: 595

Thomaz,
It has been done before. I would recommend that you have the customer
use an installation CAB for the Afaria Client that includes the
configuration data specific to their environment. Have the customer ask
their device manufacturer place the Afaria Cable in the setup script that
loads any other CABs to customize the device. That way the Afaria Client is
installed fresh with each hard reset. I recommend this only for Windows
Mobile 5 or higher and only on Afaria supported devices. On WM5 or higher,
the Afaria GUID will always be the same for the same device. That way if
the device is hard reset, then the Afaria CAB is installed again, the GUID
is preserved, thus preventing duplicate clients records for the same device
in the Afaria database .

One other item to consider, the configuration data embedded with the
installation CAB would be static on the ROM, therefore if the customer every
changes their IP Address (if using static IP) or DNS name, the Client would
still need to be manually configured after a hard reset... so their best bet
is to decide on a FQDN to place in the configuration and don't ever change
it ;)


Chris

"Thomaz Koberle" <tkoberle@sybase.com> wrote in message
news:48bd8fda@forums-1-dub...
> One of our customers is considering the idea of building a custom OS image
> which includes the Afariia Client in ROM to ease the process of
> provisioning and to ensure the client does not get wiped out after a hard
> reset. Has this idea ever been considered and perhaps tested ? My concern
> is that putting the client in ROM might break the updates and perhaps
> break the client altogether.
>
> Thomaz
>


Thomaz Koberle Posted on 2008-09-03 13:05:44.0Z
From: "Thomaz Koberle" <tkoberle@sybase.com>
Newsgroups: ianywhere.public.afaria.general
References: <48bd8fda@forums-1-dub> <48be1039$1@forums-1-dub>
Subject: Re: Afaria Client in Windows OS Image
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48be8ba8@forums-1-dub>
Date: 3 Sep 2008 06:05:44 -0700
X-Trace: forums-1-dub 1220447144 10.22.241.152 (3 Sep 2008 06:05:44 -0700)
X-Original-Trace: 3 Sep 2008 06:05:44 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:133
Article PK: 295

Thanks for the guidelines Chris

"forums.sybase.com" <SybaseiAnywhere@Live.com> wrote in message
news:48be1039$1@forums-1-dub...
> Thomaz,
> It has been done before. I would recommend that you have the customer
> use an installation CAB for the Afaria Client that includes the
> configuration data specific to their environment. Have the customer ask
> their device manufacturer place the Afaria Cable in the setup script that
> loads any other CABs to customize the device. That way the Afaria Client
> is installed fresh with each hard reset. I recommend this only for
> Windows Mobile 5 or higher and only on Afaria supported devices. On WM5
> or higher, the Afaria GUID will always be the same for the same device.
> That way if the device is hard reset, then the Afaria CAB is installed
> again, the GUID is preserved, thus preventing duplicate clients records
> for the same device in the Afaria database .
>
> One other item to consider, the configuration data embedded with the
> installation CAB would be static on the ROM, therefore if the customer
> every changes their IP Address (if using static IP) or DNS name, the
> Client would still need to be manually configured after a hard reset... so
> their best bet is to decide on a FQDN to place in the configuration and
> don't ever change it ;)
>
>
> Chris
>
> "Thomaz Koberle" <tkoberle@sybase.com> wrote in message
> news:48bd8fda@forums-1-dub...
>> One of our customers is considering the idea of building a custom OS
>> image which includes the Afariia Client in ROM to ease the process of
>> provisioning and to ensure the client does not get wiped out after a hard
>> reset. Has this idea ever been considered and perhaps tested ? My concern
>> is that putting the client in ROM might break the updates and perhaps
>> break the client altogether.
>>
>> Thomaz
>>
>


Thomaz Koberle Posted on 2008-09-04 17:17:28.0Z
From: "Thomaz Koberle" <tkoberle@sybase.com>
Newsgroups: ianywhere.public.afaria.general
References: <48bd8fda@forums-1-dub> <48be1039$1@forums-1-dub>
Subject: Re: Afaria Client in Windows OS Image
Lines: 50
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48c01828@forums-1-dub>
Date: 4 Sep 2008 10:17:28 -0700
X-Trace: forums-1-dub 1220548648 10.22.241.152 (4 Sep 2008 10:17:28 -0700)
X-Original-Trace: 4 Sep 2008 10:17:28 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:134
Article PK: 606

Chris

The manufacturer of the customer's devices is Symbol (Motorola), we
contacted them here in Brazil but they don't have the resources to build
ROMs locally. Do you know of anyone inside the iAnywhere organization that
could help me find the apropriate channel to get in touch with Symbol ?

Regards
Thomaz

"forums.sybase.com" <SybaseiAnywhere@Live.com> wrote in message
news:48be1039$1@forums-1-dub...
> Thomaz,
> It has been done before. I would recommend that you have the customer
> use an installation CAB for the Afaria Client that includes the
> configuration data specific to their environment. Have the customer ask
> their device manufacturer place the Afaria Cable in the setup script that
> loads any other CABs to customize the device. That way the Afaria Client
> is installed fresh with each hard reset. I recommend this only for
> Windows Mobile 5 or higher and only on Afaria supported devices. On WM5
> or higher, the Afaria GUID will always be the same for the same device.
> That way if the device is hard reset, then the Afaria CAB is installed
> again, the GUID is preserved, thus preventing duplicate clients records
> for the same device in the Afaria database .
>
> One other item to consider, the configuration data embedded with the
> installation CAB would be static on the ROM, therefore if the customer
> every changes their IP Address (if using static IP) or DNS name, the
> Client would still need to be manually configured after a hard reset... so
> their best bet is to decide on a FQDN to place in the configuration and
> don't ever change it ;)
>
>
> Chris
>
> "Thomaz Koberle" <tkoberle@sybase.com> wrote in message
> news:48bd8fda@forums-1-dub...
>> One of our customers is considering the idea of building a custom OS
>> image which includes the Afariia Client in ROM to ease the process of
>> provisioning and to ensure the client does not get wiped out after a hard
>> reset. Has this idea ever been considered and perhaps tested ? My concern
>> is that putting the client in ROM might break the updates and perhaps
>> break the client altogether.
>>
>> Thomaz
>>
>


Frontline Newsgroups Posted on 2008-09-04 18:33:01.0Z
From: "Frontline Newsgroups" <SybaseiAnywhere@Live.com>
Newsgroups: ianywhere.public.afaria.general
References: <48bd8fda@forums-1-dub> <48be1039$1@forums-1-dub> <48c01828@forums-1-dub>
In-Reply-To: <48c01828@forums-1-dub>
Subject: Re: Afaria Client in Windows OS Image
Lines: 65
Organization: Sybase iAnywhere
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48c029dd@forums-1-dub>
Date: 4 Sep 2008 11:33:01 -0700
X-Trace: forums-1-dub 1220553181 10.22.241.152 (4 Sep 2008 11:33:01 -0700)
X-Original-Trace: 4 Sep 2008 11:33:01 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:135
Article PK: 296

Thomaz,
Here are some links from Sybase.com that may steer you in the right
direction...

http://www.sybase.com/partner/find

http://ptnrweb.sybase.com/public/web.pbw/ePartner/partner/detail?ptnr_id=206129

http://www.sybase.com/partner/contactus

Chris

"Thomaz Koberle" <tkoberle@sybase.com> wrote in message
news:48c01828@forums-1-dub...
> Chris
>
> The manufacturer of the customer's devices is Symbol (Motorola), we
> contacted them here in Brazil but they don't have the resources to build
> ROMs locally. Do you know of anyone inside the iAnywhere organization that
> could help me find the apropriate channel to get in touch with Symbol ?
>
> Regards
> Thomaz
>
>
> "forums.sybase.com" <SybaseiAnywhere@Live.com> wrote in message
> news:48be1039$1@forums-1-dub...
>> Thomaz,
>> It has been done before. I would recommend that you have the customer
>> use an installation CAB for the Afaria Client that includes the
>> configuration data specific to their environment. Have the customer ask
>> their device manufacturer place the Afaria Cable in the setup script that
>> loads any other CABs to customize the device. That way the Afaria Client
>> is installed fresh with each hard reset. I recommend this only for
>> Windows Mobile 5 or higher and only on Afaria supported devices. On WM5
>> or higher, the Afaria GUID will always be the same for the same device.
>> That way if the device is hard reset, then the Afaria CAB is installed
>> again, the GUID is preserved, thus preventing duplicate clients records
>> for the same device in the Afaria database .
>>
>> One other item to consider, the configuration data embedded with the
>> installation CAB would be static on the ROM, therefore if the customer
>> every changes their IP Address (if using static IP) or DNS name, the
>> Client would still need to be manually configured after a hard reset...
>> so their best bet is to decide on a FQDN to place in the configuration
>> and don't ever change it ;)
>>
>>
>> Chris
>>
>> "Thomaz Koberle" <tkoberle@sybase.com> wrote in message
>> news:48bd8fda@forums-1-dub...
>>> One of our customers is considering the idea of building a custom OS
>>> image which includes the Afariia Client in ROM to ease the process of
>>> provisioning and to ensure the client does not get wiped out after a
>>> hard reset. Has this idea ever been considered and perhaps tested ? My
>>> concern is that putting the client in ROM might break the updates and
>>> perhaps break the client altogether.
>>>
>>> Thomaz
>>>
>>
>
>