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.

How to automate connected clients migration from old Afaria server to a new one

3 posts in General Last posting was on 2008-06-17 13:22:49.0Z
Michael Prokunin Posted on 2008-05-20 07:32:01.0Z
Sender: 271.48327af8.1804289383@sybase.com
From: Michael Prokunin
Newsgroups: ianywhere.public.afaria.general
Subject: How to automate connected clients migration from old Afaria server to a new one
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48327e71.2c2.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 20 May 2008 00:32:01 -0700
X-Trace: forums-1-dub 1211268721 10.22.241.41 (20 May 2008 00:32:01 -0700)
X-Original-Trace: 20 May 2008 00:32:01 -0700, 10.22.241.41
Lines: 14
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:17
Article PK: 4

Please advise how to automate connected clients migration
from old Afaria server to a new one by configuring
tasks-channels.

Old server can be found in Afaria Chanel Viewer as AFARIA
and has IP 10.1.1.1. New one is named AFARIA-NEW and has IP
10.1.2.2

Clients connects from WinXP hosts to AFARIA by a specified
schedule.

Regards,
Michael Prokunin
xmike@sybase.ru


Steve Moss Posted on 2008-06-16 16:48:02.0Z
Sender: 6b6c.48569881.1804289383@sybase.com
From: Steve Moss
Newsgroups: ianywhere.public.afaria.general
Subject: Re: How to automate connected clients migration from old Afaria server to a new one
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48569942.6b89.1681692777@sybase.com>
References: <48327e71.2c2.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 16 Jun 2008 09:48:02 -0700
X-Trace: forums-1-dub 1213634882 10.22.241.41 (16 Jun 2008 09:48:02 -0700)
X-Original-Trace: 16 Jun 2008 09:48:02 -0700, 10.22.241.41
Lines: 18
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:28
Article PK: 14


> Please advise how to automate connected clients migration
> from old Afaria server to a new one by configuring
> tasks-channels.
>
> Old server can be found in Afaria Chanel Viewer as AFARIA
> and has IP 10.1.1.1. New one is named AFARIA-NEW and has
> IP 10.1.2.2
>
> Clients connects from WinXP hosts to AFARIA by a specified
> schedule.
>
> Regards,
> Michael Prokunin
> xmike@sybase.ru

Do you have test environment? If you can have a test machine
make an XEC with the new address embedded and a schedule you
could send that to the clients for conversion.


Christopher Heeter Posted on 2008-06-17 13:22:49.0Z
Reply-To: "Christopher Heeter" <Chris.Heeter@Sybase.com>
From: "Christopher Heeter" <Chris.Heeter@Sybase.com>
Newsgroups: ianywhere.public.afaria.general
References: <48327e71.2c2.1681692777@sybase.com> <48569942.6b89.1681692777@sybase.com>
Subject: Re: How to automate connected clients migration from old Afaria server to a new one
Lines: 37
Organization: Sybase iAnywhere
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4857baa9$1@forums-1-dub>
Date: 17 Jun 2008 06:22:49 -0700
X-Trace: forums-1-dub 1213708969 10.22.241.152 (17 Jun 2008 06:22:49 -0700)
X-Original-Trace: 17 Jun 2008 06:22:49 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.afaria.general:33
Article PK: 215

Michael ,
Steve's solution will work very effectively for getting the Clients
connected to the new Sever. You may want to be aware that if you do not
clean up references to the old server (file system including schedule files
and registry entries) your users will still have the ability to attempt a
connection to the old server, also schedules from the older server will
still be firing. If you are NOT migrating all clients at the SAME time to
the new server this could be problematic depending upon your usage of
Afaria. I would recommend you build a Channel on the new Server that cleans
up the references to the old server. That way upon the first connection to
the new Server, Clients can will/can no longer connect to the old Server.

Thanks,
Chris

<Steve Moss> wrote in message news:48569942.6b89.1681692777@sybase.com...
>> Please advise how to automate connected clients migration
>> from old Afaria server to a new one by configuring
>> tasks-channels.
>>
>> Old server can be found in Afaria Chanel Viewer as AFARIA
>> and has IP 10.1.1.1. New one is named AFARIA-NEW and has
>> IP 10.1.2.2
>>
>> Clients connects from WinXP hosts to AFARIA by a specified
>> schedule.
>>
>> Regards,
>> Michael Prokunin
>> xmike@sybase.ru
>
> Do you have test environment? If you can have a test machine
> make an XEC with the new address embedded and a schedule you
> could send that to the clients for conversion.