Identify a device with a connection

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #630
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    I’m trying to find out if there is a way to identify a certain connection on a device, and delete it if possible. I really just need to identify machines with the connection — I can take care of deleting I identify it.

    I can read a registry value with an RSP script, but there are no conditionals in the scripting language so I can’t do anything after I read it other than export it to a reg file. So reading a reg key isn’t going to help.

    I tried SNMP, but it doesn’t look like I can access the connections on the machine.

    What I want to do is just delete any connections named “MyConnection” and push out a new one to them. Thing is, I don’t want it to happen on all my thin clients, only the ones that have the existing web connection.

    Any ideas?

    They’re all S30 devices running CE.NET. I’m open to even obscure ways of doing it! 🙂 Eventually they’ll all be in groups in WDM, and then I can dump a config to all of them. But, since they weren’t in groups previously, I have no way to find out if the connection exists on the client or not.

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

    Hi,

    Three suggestions:

    – Use a G-Key package (on this site) to reset the unit and then push out a new device config

    – Create a package to delete all the connections and then create new ones. You can also create a addon to do this with some tools from Wyse

    – Create a batch file and send this down to execute. This gives you more control of the script flow

    Cheers,
    -TT

    #10427
    ConfGenConfGen
    Keymaster
    • Total Post: 10966
    • Jedi Master
    • ★★★★★★★

    Some infos on Thinkthins comment:
    – Use WDM to extract the config of a correct configured device (with the new ICA connection defined)
    – edit the settings.reg file you can find under ftproot/rapport/
    – add these lines at the beginning of settings.reg right after all listed addons:
    [HKEY_LOCAL_MACHINESoftwareMicrosoftWBTClientsRegistrationICAConnections_DeleteValue_]
    “_DeleteAll_”=””

    This will delete all existing ICA sessions except the one defined in your settings.reg.

    Push this config back to all other devices.

    ConfGen

    #10432
    AvatarJoe
    Member
    • Total Post: 106
    • Legend in Own LunchBox
    • ★★★★★

    Thanks for the tips, guys…

    The problem is we don’t want to push a package down to all 4000 devices if we don’t have to. So we’d like to be able to identify the devices before we push a package down.

    I’ve already got a way to delete the connection, I just need to identify the device that has the old connection so I can push the new package to it without disturbing the 3500 devices that don’t have the connection that I wanted to delete.

    I’m 99% sure it’s not possible, but I just wanted to throw it out there and see if anyone had any ideas! 🙂

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

    Yep, think it would be hard. You may be able to execute a .bat file to look for the connection and if it exists upload a file to a file server with the terminal name.

    Now you would still need to run this on every device but nothing actually gets modified on the terminal (low risk). You just end up with 500 odd files on a file server so you can collate a list to target for the actual change.

    Now I have never tried do do this so its all based on guess but its an interesting idea…

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