Dear Windows Server Insider Team,

much appreciate your change, that you now offer the same information about telemetry in sconfig as we were used to in OOBE (GUI).

The change comes with a potential unwanted behaviour:
The disclaimer and question for telemetry settings comes up with every use that is logging on for the first time (or starting sconfig). No matter GUI or Core Installation option.

repro:

install a new WS 2025 b26085 (GUI or Core)

logon as local admin

open sconfig (invoked automatically on Core)
on GUI the OOBE prompts you to choose a setting, independently of the sconfig

disclaimer prompts you choose a setting

domain join the server

reboot

logon as domain admin

open sconfig (invoked automatically on Core)

on GUI the OOBE prompts you to choose a setting, independently of the sconfig

disclaimer prompts you choose a setting again

This will continue with every other local or domain user that is logging on, not tested yet.
But it is also happening on GUI with the telemetry question at first logon

This might also break some automation processes.

​Dear Windows Server Insider Team,
much appreciate your change, that you now offer the same information about telemetry in sconfig as we were used to in OOBE (GUI).The change comes with a potential unwanted behaviour:The disclaimer and question for telemetry settings comes up with every use that is logging on for the first time (or starting sconfig). No matter GUI or Core Installation option.
 
repro:
install a new WS 2025 b26085 (GUI or Core)
logon as local admin
open sconfig (invoked automatically on Core)on GUI the OOBE prompts you to choose a setting, independently of the sconfig
disclaimer prompts you choose a setting
 

 
domain join the server
reboot
logon as domain admin
open sconfig (invoked automatically on Core)
on GUI the OOBE prompts you to choose a setting, independently of the sconfig
disclaimer prompts you choose a setting again
This will continue with every other local or domain user that is logging on, not tested yet.But it is also happening on GUI with the telemetry question at first logon

 
This might also break some automation processes.  Read More

​