[German]I got reports where a Terminal Server environment is causing isues. Users have to log in to OneDrive for Business every time they log in to the Terminal Server. Quick question: Is someone from you is affected by the same problem?
Advertising
Windows Server 2019 – Terminal Server
The environment in which the Windows Terminal Server is running is a Windows Server 2019. Previously, it was the case that users entered their credentials for OneDrive for Business once and these were retained over the sessions on the Terminal Server. However, as of "recent" this has changed, writes the administrator in question here (I've translated the German text).
On a terminal server (Windows Server 2019) that I support, it has recently become impossible to use OneDrive permanently.
All users who use OneDrive must also log back into the OneDrive client after logging into the terminal server. After that, everything runs without problems until the next logout/login from/to the terminal server.
The administrator writes that the was not necessary until now, because the OneDrive client remembered the login data and stored them permanently. This meant that OneDrive for Business was ready for use immediately after logging into the terminal server and could be used by users.
The administrator writes that this was not necessary until now because the OneDrive client remembered the login data and stored it permanently. This meant that OneDrive for Business was ready for use immediately after logging into the terminal server and could be used by users.
No solution so far
The affected person writes that so far no solution has been found. He has tested the following things, without a result:
1) Uninstalled OneDrive
2) Then deleted all credentials from credentials management.
3) Deleted all OneDrive subfolders from %appdata%.
4) Then reinstalled OneDrive
5) Login at OneDrive client->Use without problems possible
6) Logout/Login at terminal server -> new login at OneDrive client necessary
7) Exit/Restart OneDrive client (without logout/login at terminal server) -> No new login at OneDrive client necessary.
OneDrive client can be used again immediately without frequent login – but not on terminal server.
Advertising
The affected person writes that so far no solution has been found. Whether a reset of OneDrive for Business (as described here and here) helps is not clear. A ticket to Microsoft is open, their support is "anything but satisfactory". So far, the supporters have not been able to provide a solution and are only trying out the terminal server.
The affected administrator's assumption is that it could be related to one of the last updates installed in May 2023. The funny thing is that all other applications in the Microsoft Office 365 package are not affected by this issue.
I am reminded of my post Connection issues with Microsoft 365 applications? (Feb. 2023) from February 2023, where such problems were also reported. However, this affected all Office 365 apps. In that context, the affected person outlined some workarounds (Fix for connection issues with Microsoft 365 apps (March 2023)). Also FXLogic may have played a role. I'm now interested to know if this is an isolated case, or if other users have observed this behavior (some German readers has confirmed similiar observations). Or is there a known solution.
i found a way!
after this the user only needs to log on once :)
Just incase id deactivate the scheduled task too when youre finished with the script/install "OneDrive Per-Machine Standalone Update Task"
If you have an older version of the onedrive installer, you can create a powershell script that loops with a sleep of 100 milliseconds, that disables the onedrive update service if found and also tries to stop it just incase. Script must have $erroractionpreference = "SilentlyContinue" to not get stuck
just tried it, seems the onedrive installer updates to the latest version as the last step of the install :) works fine and dandy for me, also disables the scheduled task.
Dont forget to do "get-process onedrive | stop-process" before doing this
For those who need help:
while($true)
{
$service = Get-Service -Name "OneDrive Updater Service" -ErrorAction SilentlyContinue
if($service)
{
Write-Host "Found OneDrive Updater Service. Disabling and stopping…"
Set-Service -Name "OneDrive Updater Service" -StartupType Disabled -Status Stopped -ErrorAction SilentlyContinue
Write-Host "OneDrive Updater Service has been disabled and stopped."
}
else
{
Write-Host "OneDrive Updater Service not found."
}
Start-Sleep -Milliseconds 100
}