Can the Server List in One-X Communicator be auto-populated via .xml file or some other means?

[learningSkype]

have any of you tried updating the .xml file in One-X Communicator so that the Server List is populated when users open the app and they do not have to enter a server manually?

 

[kyle555]

Yeah. There's an executable with the isntaller that can grab it, configure it, and you can save it somewhere.

Ultimately when you deploy on the domain you a couple of XML files into the right places for different settings and stuff.

 

[learningSkype]

thanks Kyle. I downloaded the latest One-X Communicator and it includes the Centralized Administration Tool. gonna try it in Dev before rolling out to Production.

 

[biglebowski]

I did it the hard way and had the config files pre-configured and used SCCM.

SCCM installed the One-X app and then a script copied the config files to the users appdata folder.

Biglebowskis Razor - with all things being equal if you still can't find the answer have a shave and go down the pub.

 

[learningSkype]

what is SCCM?

 

[kyle555]

Its a MS thing that can manage apps intalled on domains and other stuff I think.

I've never done anything more than build a script to run as admin on a local machine to POC it for a customer. I presume they have some magic tool that can run that script on any number of domain joined PCs and let them figure that out on their own.

SCCM is a tool I've heard of that does that kinda thing.

 

[learningSkype]

so I did some digging and after using the CAT tool, there is a file called discover.xml that is supposed to be updated in order to get One-X to auto-populate the fields for Server List. but you also have to alter your 46xxsettings.txt file to include the CM servers that you're trying to use for registration.

I altered the 46xxsettings.txt file w/the following:

SET MCIPADD hostname1,hostname2
STATIC 0

then I updated the discover.xml file to pull this updated 46xxsettings file from a specific location but it still doesn't work. pretty much batting a thousand on this one

 

[Sean655]

I have a similar setup and used SCCM to drop the discover.xml file on a bunch of machines. I have discover.xml pulling a separate 46xx file that just has MCIPADD in it with the list of servers I want One-x to use. The user has to open settings in One-X and click on the Auto-configure button to get the updated settings. Have you used the auto-configure button to pull the settings? Are you trying to avoid any user interaction to get the updated settings?

 

[learningSkype]

I'm testing everything on just a desktop PC, so the discover.xml file is on just 1 PC and the 46xxsettings file is also in a Temp folder, not on an actual Utility server. not sure if that is screwing me up but I just want to test everything before putting it on production servers.

and to answer your question, I'm trying to set it up so that the user doesn't have to do anything other than open the One-X app and all the server settings are loaded when they launch the app. this way they just click on Log-in and the app registers to the correct CM.

does anyone know if the 46xxsettings file must reside on a Utility server? if so, my test is never going to work.

 

[Sean655]

It doesn't have to be on a utility server but it needs to be on a server that can do web hosting. There's some threads on here about what others run to host the 46xx file.
I'm not sure that you can just launch One-X and have everything set automatically. I messed around with One-X for a while trying to get the same thing done and having users open the settings window and click a button was the best I could do in my environment.

You could try playing with pushing the config.xml file to the One-X communicator folder under AppData for a user but there's some hurdles with that method that might be handled by using a batch file as part of a login script but no guarantees.