Plantronics + Polycom. Now together as Poly Logo

BToE not signing in after user moved from s4b 2015 to 2019 pool

SOLVED
SteffenBaierUK
Polycom Employee & Community Manager

Re: BToE not signing in after user moved from s4b 2015 to 2019 pool

Hello @guideclothing ,

 

Welcome back to the Poly Community.

I have updated the FAQ post here:

 

Feb 02, 2016 Question: How can I prevent a Poly Phone to be downgraded/upgraded automatically via Skype for Business and/or Office365?

Resolution: For Skype for Busines please download, unpack and import the attached LyncProvisionDeviceParams


The ZIP file now contains all these:

<web device.set="1"
	device.prov.lyncDeviceUpdateEnabled.set="1"
	device.prov.lyncDeviceUpdateEnabled="0"
	lync.provisionDeviceParams.enabled="0"
	feature.lync.overrideIpPhonePolicy="1"
	server.log.setting.enabled="0"
	feature.deviceLock.enable="0"
	httpd.cfg.session.maxSessionAge="86400"
/>

 

We added a new Parameter in UC Software 5.8.3 and later and from 6.0.0 onwards:

feature.lync.overrideIpPhonePolicy="1"

The above stops Skype for Business pushing the BToE settings and the Power Saving related parameters.


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

----------------
The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 11 of 12
guideclothing
Frequent Advisor

Re: BToE not signing in after user moved from s4b 2015 to 2019 pool

this cost be a year of troubleshooting

Message 12 of 12