Deploying Configuration

  • This topic is empty.
Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #4331
    ltd2007
    Member
    • Total Post: 43
    • Frequent Flyer
    • ★★★

    Hi everyone,

    Question regarding deploying connections/configurations.

    I am currently looking at deploying an RDP Session/connection to a large group of 3125SE’s (will all be at firmware 576).

    I’ve created the RDP connection on one device and pulled the configuration but then when deploying this package to another device the connection is not there.

    I’ve tried many different options..
    – appending registry
    – replacing registry (would not really want to do this as I want to keep existing connections)
    – excluding terminal information
    – excluding everything but connections..

    Any ideas? thoughts?

    thanks!

    #16528
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Can you try to pull the config without checking any checkboxes to exclude something? Replace or append should not make diff.

    CG

    #16541
    ltd2007
    Member
    • Total Post: 43
    • Frequent Flyer
    • ★★★

    thanks i will try that…

    problem is I don’t want to lose the current configuration of the devices as they are location specific…

    #16542
    ltd2007
    Member
    • Total Post: 43
    • Frequent Flyer
    • ★★★

    Well I’ve tested not “checking” any of the exclusions and both the APPEND and REPLACE but neither have worked…

    just doesn’t take the config it seems…

    FTP log is showing the file is transferring successfully.

    device restarts without any errors.

    #16543
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    OK, let’s do it step by step.
    You have
    -configure a master device
    -pulled a config from that device without marking any checkboxes
    -pushed that config to another device which has
    -same hardware
    -same firmware as the master

    Correct?

    CG

    #16544
    ltd2007
    Member
    • Total Post: 43
    • Frequent Flyer
    • ★★★

    yup!

    they actually have the same custom image (build 576) installed… so theres no difference there, and are the exact same model.

    Weird thing is, if I add a Terminal Emulation config to the “master” device and push that configuration along with an RDP session it works! but it wont work with just a RDP session configured…

    strange.

    #16553
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Have you newly created the RDP session or have you used the default RDP session? Latter will not work.

    CG

    #16554
    ltd2007
    Member
    • Total Post: 43
    • Frequent Flyer
    • ★★★

    its a newly created RDP session….

    #16555
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Just in case: can you do a factory reset and create a new RDP session. Then test pull/push again?

    CG

    #16556
    ltd2007
    Member
    • Total Post: 43
    • Frequent Flyer
    • ★★★

    thanks I will try that!!!

    #16557
    ltd2007
    Member
    • Total Post: 43
    • Frequent Flyer
    • ★★★

    strange… same results.

    – reset “master” unit to factory defaults
    – deleted all “default connections”
    – created RDP
    – captured (without any checkboxes)
    – deployed to another device (same build/image) – NO change

    – went back to master and created Terminal Emul connection
    – captured Master (without any checkboxes) set to APPEND registry
    – deployed to another device and both the terminal emulation and RDP connection were there leaving original connections intact…

    #16559
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    😯

    Can you check if in the settings.reg (ftprootrapportyourPackageName) of the first try the RDP connection is included?
    Compare both settings.reg files (only RDP one against Ericom+RDP one)

    CG

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