Windows Softphone Update - Out of Band?

[pact]

With the release of SP3 has come the new version of the Windows Softphone.

Our userbase has been contacting us today because they have been receiving the update without us pushing it out via the Management Console...

Is this to be expected?

It has caused trouble as users do not have Administrative Rights, and some require additional plugins to be re-installed if the Softphone is updated.

This is ok if we have scheduled the upgrade, like normal, but not when it happens unexpectedly.

The Mac Client Update came through the correct channel and we were able to approve it after SP3 had been installed.

Has anyone else noticed this?

 

[techdummy]

With the release of SP3 has come the new version of the Windows Softphone.

Our userbase has been contacting us today because they have been receiving the update without us pushing it out via the Management Console...

Is this to be expected?

It has caused trouble as users do not have Administrative Rights, and some require additional plugins to be re-installed if the Softphone is updated.

This is ok if we have scheduled the upgrade, like normal, but not when it happens unexpectedly.

The Mac Client Update came through the correct channel and we were able to approve it after SP3 had been installed.

Has anyone else noticed this?

Hi,

Yes..I had a similar issue.
All our users are in remote location and there is a time difference of almost 6 hours, so I only got to know about the issue next day.
We had automatic updates disabled and I never downloaded the update for windows client.
But somehow every user received update notification.

But there was something I did before all this happened.
We have a test server on which I test out all the latest updates, and I did upgrade to SP3 and to the latest version of windows client on test server. I tried to register my test extension(1XXX) on my laptop and windows client asked for update, which I did.
Now, I had the latest version of the windows client in my laptop.

After testing was done, I removed the provisioning file for the test extension(1XXX) from the windows client and registered back my original extension (5XXX) from production server. It registered without any issues.
I'm not sure if registering my extension from production server on the latest version of windows client could have caused this.

The thing is, the update was never downloaded on the production server but one of the extensions did get registered on an updated windows client.
So I'm not sure if this might have somehow updated the database of the server, and hence others getting notification to update the client.
Just a guess.

If not this, then I can only think that the update was downloaded automatically by server and pushed to all clients.

Thanks