Where can I download provisioning templates for Movi versions prior to 4.2.0.10318?

[Chris Swinney]

Hi all,

The question is in the title. I can only see versions from 4.2.0.10318 and above, but because you have to apply provisioning on a per version basis, and we have old version of Movi still in use, I need to apply provisioning template in order to upgrade users from older versions.

Many thanks

Chris

[Justin Ferello]

Chris,

What version are you looking for?  TMS PE only goes back to Jabber v4.3 for supported software.  If you are still running the legacy agent in TMS, then you should have most of the old templates, if not here they are.

Thank you,

Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: justin.ferello@kbz.com

[Chris Swinney]

Hi Justin,

Many thanks for this. We have moved to TMSPE but I can still see old Jabber Clients connecting (Systems --> Provisioning --> Devices).

I can see the the following device versions connecting for which we don't have a schema installed in TMS.

• 4.0.1.8289
• 4.1.1.9724

We do have a legacy schema installed of 3.1.1.6348 and we still have Movi 3.1 clients connect, but until yesterday I had not added the "Software URL" or "Software Version" parameters to point to an upgrade (4.6). I have also installed the 4.2.0.10318 schema which is avliable for download via the Cisco download pages.

However, based on what you said, will TMSPE actually push the provisioning information to clients prior to 4.3?

Many thanks

Chris

[Jens Didriksen]

Probably not as you can only go 4.2-->4.3 without uninstalling 4.2 first.

If you install 4.4 or later without uninstalling 4.2 you'll end up with two different products installed; one Movi and one JabberVideo,

You can find old Movi stuff here:

http://ftp.tandberg.com/pub/software/endpoints/movi/

/jens

[Chris Swinney]

Hey Jens,

I did try to apply the older schemas to TMS and provision the older versions with TMSPE. Whilst the schemas install correctly and I can add templates, and even the correct template get pushed to the VCSs where the old Movi client will register, I do not see the software download pop up in the same way that I do with the later Jabber clients.

I guess the only way to achieve this to get send and e-mail to each of the users with a link to the software and get them to update that way (again we have no way of automatically distributing software).

Its a shame I can't "burn in" the pre-configuration command line options to the installer so we can ensure that the right users have the right settings (such as Internal/External server).

Chris

[Chris Swinney]

Ok, after a bit of fiddling and setting full software build number in the provisioning template (), I can get the previous version of Movi to understand that there is an upgrade. Actually upgrading from ANY previous (read 3, or 4.0, 4.1) version to 4.6 in one step can be done - the pevious versiong is uninstalled in one step.

Problem is that if the client has been installed using the Pre-configured command line options setting the Internal and External VCS and SIP Domain, then theses are overwritten (as is also outline in the admin guide).

So the new question is how on earth can I get user to upgrade whilst keeping their pre-configured configuration? AS this has drifted from the original question, maybe I should post a new question.

[Chris Swinney]

OK- to answer my own question (and that for anyone else finding this). It appears that you can't update any old version of Movi (pre 4.3) that has been configured used the pre-configuration command line options AND keep these options (Note - IF anyone knows any differnt, I would love to know).

Essentially, although the client understands that a new version is available, on installation all those settings are wiped. The only thing I can now think of is to bastardise the TMSPE e-mail template to send to a group to say that an update is available but to also include the VCS settings and SIP domain.

This aassume that you are unable to use deployment tools.

Once you are on Jabber 4.3 and on, the update process seems to update without overwriting settings.

[Jens Didriksen]

swinster70 wrote:
Once you are on Jabber 4.3 and on, the update process seems to update without overwriting settings. 

That's what I thought too so I confidently enabled auto updates a couple of days ago, however, yesterday I found one workstation which had a pre-configured 4.5 installed and when he applied the upgrade to 4.6 - the settings were blanked. Whether this was just a one off remains to be seen, but I need to do a bit more experimenting before I re-enable the auto update feature. We have a mixed environment where some users have a custom package and others the "normal" package (long story ). Users running the "normal" package kept their settings after upgrading - so that's at least something.

/jens

[Chris Swinney]

I have to say, I have only tested on upgradeing from 4.3 and 4.4 pre configed installs. Indeed this is on the same machine so whether that has something to do with it or not I don't know.

What I would love to know is who's increadiably clever idea was it to offer the ability to pre-configure a client, then with a simple upgrade wipe the settings! I realise this was Tandberg technology, but still - what a ball drop!

[Chris Swinney]

Hey all

IMPORTANT NOTE!!!!

It appears as though if you use the Cisco documented pre-configuration techniques for installing Jabber client post 4.3, the the upgrade process WILL STILL BLANK OUT ALL CONFIGURATION! I have accidentally found a work around, which is outlined below.

There was a subtle change in the naming of the pre-configuration option between Movi and Jabber to 4.2, then Jabber from 4.3 and on:

In the original Movi administrator guides and up to Jabber 4.2, the pre-configureation options are listed as:

• DOMAIN - Corresponds to SIP Domain in the Advanced settings.
• EXTERNALVCS - Corresponds to External VCS in the Advanced settings.
• INTERNALVCS - Corresponds to Internal VCS in the Advanced settings.
• HIDEADVANCEDLOGIN - A value of 1 hides the Advanced settings link in the Movi client sign-in screen.

However, in the admin guide from 4.3 and on the preconfigureation options have the ford FORCED placed in front of them, such that:

• FORCEDDOMAIN - Identical to the SIP domain configured on the Cisco VCS, in VCS configuration > Protocols > SIP > Domains.
• FORCEDINTERNALVCS - The DNS address of the primary Cisco VCS Control cluster you want to connect to. Jabber Video will always look for this address first when connecting. It is also possible to specify which port to connect to. For example InternalVCS.example.com:5063.
• FORCEDEXTERNALVCS - The DNS address of the Cisco VCS Expressway cluster you want Jabber Video to connect to. If Jabber Video fails to connect to the Internal Server, it will try this address. It is also possible to specify which port to connect to. For example ExternalVCS.example.com:5063.
• FORCEDHIDEADVANCEDLOGIN - Setting to 1 makes the above network communication settings grayed out and inaccessible for editing by the user.

If you use these later setting to pre-configure Jabber 4.3 and on, when you then update the client, the settings contained in those fields will be WIPED!

However, I happened upon a workaround for the bug. I was lazily copying a pre-existing BAT file from an old Movi pre-configuration and simply pointed the BAT file to launch the newer client installer, thus using the OLD options (with out the word FORCED preceding the option). I found that the install complete and had pre-configured the client with the correct information, however, when I then downloaded and updated the client to 4.6, the setting were RETAINED!. Woo bloody Hoo!

I have tried the install using the old settings with Jabber 4.6 and they still work such that the command line should be:

JabberVideoSetup4.6.exe /s /v"/qn DOMAIN=domain.com EXTERNALVCS=expressway.domain.com INTERNALVCS=control.domain.com HIDEADVANCEDLOGIN=1"

Cisco - IF YOU ARE LISTENING - please do not remove these option, bit include them in your documentation. By all means, leave the options in that cause the settings to be wiped when you upgrade, but for the rest of us, we need the setting to be retain between upgrades.

Many thanks

Chris

[Martin Koch]

I am still not 100% sure if this is more a bug or a feature :-)

Did you try to contact TAC about it, ifso, what did they say?

[Chris Swinney]

I'll enquire tomorrow - our partner has gone home for the night!

However - I'm not entirely sure where and who would want this feature!

[Martin Koch]

Did you try if smaller steps of software versions keep the settings?

You can define a specific download version for a specific jabber/movi version.

So you could force all old programms to upgrade with intermediate steps (even if it might annoy your users :-)

The older versions kept the settings in some path in the registry with TANDBERG, the new ones with CISCO,

guess there might be a mid version which properly takes the settings and an other one which does not.

Other ways could be to roll out the parameters via AD or build a specific installer which includes

or fixes the parameters.

A lot of things might also be fixable by using an intranet site or sending out a mail to the users how

they can reconfigure their client  :-)

You can also just make a reg/bat file adding the new settings.

Guess it all depends on how many users you have and how much effort you put into it.

[Chris Swinney]

Yeah - tried that this evening. Went from 4.0 pre config to 4.1 - settings wiped. 4.0 pre config to 4.2 - setting wiped, 4.0 pre config to 4.3 - setting wiped.

We support multiple sites in multiple domain - our TMS is not attached to any of those domain and we do not have access to roil out software via deployment tools. We could ask the network admins at those site to ad AD regfixes, but still....

Martin Koch wrote:
A lot of things might also be fixable by using an intranet site or sending out a mail to the users how
they can reconfigure their client  :-)
You can also just make a reg/bat file adding the new settings.
Guess it all depends on how many users you have and how much effort you put into it.

I have created an email to be sent via TMSPE to walk the user through updating the settings. I need to update it for each group to contain new VCS and SIP domain setting, but still I think it the simplest approach. Did think about the BAT/REG file idea - maybe I'll mull it over a while longer.

[ahmashar]

Hi,

I have the template 4.2 but I cannot upload it here.

if you give me your email, I will email it to you.

regards, Ahmad