Forum Discussion
MicrosoftSleeping tabs FAQ
HotCakeXThank you. This surprising change to the originally communicated schedule is very troubling news. It means customers will now have to take immediate meassures to disable Sleeping Tabs in order to avoid application compatibility issues instead of being able to do this within the v89 timeframe.
Yw, I agree, 3 insider channels are available already for all kinds of testing, the 4th channel is supposed to be free of experiments.
but businesses and enterprises have nothing to worry about. they added this policy over a year ago
Control communication with the Experimentation and Configuration Service Supported versions:
- On Windows and macOS since 77 or later
In Microsoft Edge, the Experimentation and Configuration Service is used to deploy Experimentation and Configuration payload.
Experimentation payload consists of a list of early in development features that Microsoft is enabling for testing and feedback.
Configuration payload consists of a list of settings that Microsoft wants to deploy to Microsoft Edge to optimize user experience. For example, configuration payload may specify how often Microsoft Edge sends requests to the Experimentation and Configuration Service to retrieve the newest payload.
Additionaly, configuration payload may also contain a list of actions to take on certain domains for compatibility reasons. For example, the browser may override the User Agent string on a website if that website is broken due to the new User Agent string on Microsoft Edge. Each of these actions is intended to be temporary while Microsoft tries to resolve the issue with the site owner.
If you set this policy to 'FullMode', the full payload is downloaded from the Experimentation and Configuration Service. This includes both the experimentation and configuration payloads.
If you set this policy to 'ConfigurationsOnlyMode', only the configuration payload is delivered.
If you set this policy to 'RestrictedMode', the communication with the Experimentation and Configuration Service is stopped completely.
If you don't configure this policy, on a managed device on Stable and Beta channels the behavior is the same as the 'ConfigurationsOnlyMode'.
If you don't configure this policy, on an unmanaged device the behavior is the same as the 'FullMode'.
Policy options mapping:
FullMode (2) = Retrieve configurations and experiments
ConfigurationsOnlyMode (1) = Retrieve configurations only
RestrictedMode (0) = Disable communication with the Experimentation and Configuration Service
Use the preceding information when configuring this policy.
Supported features:- Can be mandatory: Yes
- Can be recommended: No
- Dynamic Policy Refresh: Yes
- Integer
that being said, if anyone has problem with this, please do voice your concerns through feedback button on Edge or the online form
https://www.microsoftedgeinsider.com/en-us/support
- Probably yes,
but good that you already had that policy in place - Okay, so looking closer at the release notes and your post on the "Experimentation and Configuration Service" GPO, may explain why we're not seeing Sleeping Tabs.
We have the "Experimentation and Configuration Service" set to 0 (RestrictedMode), and the release notes state that the "feature is limited to a randomly selected group of users who have enabled experimentation." I glazed over that earlier, and I honestly didn't recall there was an "experimentation" policy, but it makes sense I wouldn't want that enabled in the Enterprise.
I'm just surprised that all indications I'd found online prior to now had seemed to indicate this was out of beta for all. It sounds like perhaps like consumers all have the feature, but enterprise are being phased in???
