Video Screencast Help

How to install odyssey client offline

Created: 04 Dec 2012 | 5 comments

Our platform has a managed software deployment process which will install software during a cold boot.  We would like to know how to install the agent to the client devices without the required user input of the site server name.  Is there any way to customize the agent and create a .cab file that can be installed offline?

Comments 5 CommentsJump to latest comment

MacBrinky's picture

Is the fact that your users should not know the name of the Site Server the only reason why you need to carry out the agent like this?
In Mobile Management you can deploy\enroll the agent using a mail address instead of the URL. Would this make things easier?

Unfortunately so far we do not have such a thing as a cab file as supported method to deploy the agent.

rhull's picture

No there is no mail client utilized as these are locked down industrial devices. I have seen that the process downloads and extracts then prompts the user to input the siteservername. Then it proceeds to download the appupdate cab and the Athena cab to install them. The issue is we don't allow the user to access IE and if we autoinstall the it will prompt the user but if they aren't looking it will reboot in a few minutes because the other auto install process are finished and it is instructed to do so. If they put nothing in the client never gets registered. I am trying to ensure on a cold boot we get the agent installed. I have the capability to execute cabs or .exe files with arguments with custom scripts on the device. I was hoping I could copy the necessary cabs or exes with configs to the device and use my automation tools to get it installed or configured as necessary. I can even push registry changes if need be. I just need to understand the step by step process the standard install method uses and what config files are needed to be present with the correct values to make this work. My plan is to auto install the correct cab files then follow behind it with a script to copy config files to the appropriate application directories that would allow it to work. I will do most of the process development I just need someone with the intimate knowledge of the process as designed to tell me what happens when.

rscovel's picture

Hello RHULL,

I'll try to see what I can find out then get back with you, if MacBrinky doesn't get to it first.

I did some work configuring Windows Mobile Barcode Scanners in a previous life, and will see what I can find out.

When I did the above I would configure one device the way I needed it to be, then would do a backup of the device to use it as a template for my other devices. Have you attempted anything like this yet?

Russ Scovel
Inside Systems Engineer

Altiris SOS – Endpoint Management and Mobility
Symantec Corporation

rhull's picture

I am trying to create a process so if the device is reloaded in the field that the user is not involved in the installation or configuration of the client to ensure it is done properly.  I can backup the registry and restore it on a re-load if I was confident the installation of the appropriate cabs was done and the keys already existed.  That is why I want to understand the way the web install works to see if I can create my own process for configuration.  I was looking for the correct cabs to load locatesiteserver, appupdate, Athena, etc and the config files or registry keys that are relevant in the process.  I could probably figure it out from there.

rhull's picture

I found this article

which explains exactly what I want to do but is a little out of date.  the .run file will not execute on WM6.5

I have determined a way to do it with manufacturer power tools but can you tell me how to suppress the status screen on locatesiteserver.exe if the config file has the info already?  The user doesn't need to be bothered with it.