Can I send a config to a terminal Via FTP not via Rapport

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #124
    Avatarxylene
    Member
    • Total Post: 4
    • Newbie

    I am about to start standardizing the firmware/image and updating config’s in our 3125, 3150 and 3360 terminals.

    After the image has been downloaded via FTP pull method, we have to then send each terminal its own config(edit a device name, then send to the terminal).

    As we only have 1 Rapport server and 3 people simultaneously involved in the upgrade, is there any way to pull the config using the FTP upgrade option on the terminal(config resides on an FTP server)?

    I have tried, but the terminal is looking for a ‘params.ini’ file. Is there any way I can create this file to get the terminal to accept the config(‘settings.reg’) file pulled by Rapport?

    Thanks
    Ian

    #8647
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Hi,

    Have a look at the configuration of CE doc in the downloads – CE section of this site. Basically when you pull a CE config you just pull the registry. You then use the Rapport bundle wizard to bundle this up with the factory firmware and finally send this out as a single package to all the terminals.

    You can manually send this out, use the automated ftp or DDC method. I have put quite a bit up so far on both these methods on the site.

    Post back if this does not make sence or if it was not what you were after,

    Cheers,

    -TT

    #8648
    Avatarxylene
    Member
    • Total Post: 4
    • Newbie

    Yes I was looking at that document today and tried a couple of images with success although much more testing woul need to be done. Yes this seems be a great idea and I agree this would be the simplest process for this project. I will certainly try to push this method at today’s meeting.

    Unfortunately as I have just been thrown into this project recently and if you take into account the lack of knowledge and training with thin clients, combine this with bad past experiences with config’s bundled with firmware’s and very little time to run enough testing to try new things, this has left the management, less than enthusiastic about this the above method. You get the drift….

    So from your reply I am gathering that an FTP pull of a config is not possible? How about using SNMP to pull a config?

    Thanks very much for your reply ThinkThin!!! It is appreciated

    Ian

    #8650
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    Ahh, sounds like a fair bit of past history there…

    This is what I can suggest, you will need Rapport to pull the conifg file, this can be done in the lab not on the prod network. You will end up with a settings.reg file (the registry of the unit). You do not have to bundle this into an image of course, it can be just pushed back out so long as the target terminal has the exact same version/build of firmware.

    If you really are not able to use Rapport for the push you can use the ftp upgrade method to do this so long as the terminals have the automatic ftp upgrade option set to on. There is an artical on this here:

    http://www.freewysemonkeys.com/site/modules.php?name=News&file=article&sid=24&mode=&order=0&thold=0

    It is possiable to use this method to push the config file only but if the terminal is on a different firmware level this could be bad.

    Really however put Rapport back in the network and drag and drop the firmware and then the settings.reg if you do not want to bundle.

    Good Luck!

    -TT

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.