OneDrive StandAlone Update on Conference Room computers

%3CLINGO-SUB%20id%3D%22lingo-sub-2750956%22%20slang%3D%22en-US%22%3EOneDrive%20StandAlone%20Update%20on%20Conference%20Room%20computers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2750956%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20shared%20computers%2C%20such%20as%20conference%20rooms%2C%20I%20would%20like%20to%20know%20what%20other%20folks%20are%20doing%20to%20keep%20the%20OneDrive%20client%20up%20to%20date%2C%20without%20causing%20a%20disruption%20to%20the%20user.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20don't%20really%20have%20control%20over%20the%20update%20process.%26nbsp%3B%20The%20resulting%20issue%20for%20a%20shared%20resource%20such%20as%20a%20conference%20room%20pc%20is%20that%20the%20OneDrive%20StandAlone%20Updater%20Task%20launches%20off%2C%20often%20times%20during%20a%20presentation%2C%20resulting%20in%20DOS%20command%20windows%20popping%20up%20in%20front%20of%20the%20presentation.%26nbsp%3B%20I%20believe%20that%20the%20last%20step%20in%20the%20update%20process%20is%20to%20run%20the%20following%20which%20is%20the%20DOS%20command%20windows%20popping%20up.%26nbsp%3B%20How%20does%20your%20company%20handle%20this%20situation%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E%22C%3A%5CWindows%5CSystem32%5Ccmd.exe%22%20%2Fq%20%2Fc%20rmdir%20%2Fs%20%2Fq%20%22C%3A%5CUsers%5Cscotth%5CAppData%5CLocal%5CMicrosoft%5COneDrive%5C21.030.0211.0002%22%0A%22C%3A%5CWindows%5CSystem32%5Ccmd.exe%22%20%2Fq%20%2Fc%20rmdir%20%2Fs%20%2Fq%20%22C%3A%5CUsers%5Cscotth%5CAppData%5CLocal%5CMicrosoft%5COneDrive%5C21.030.0211.0002%5Camd64%22%0A%22C%3A%5CWindows%5CSystem32%5Ccmd.exe%22%20%2Fq%20%2Fc%20del%20%2Fq%20%22C%3A%5CUsers%5Cscotth%5CAppData%5CLocal%5CMicrosoft%5COneDrive%5CStandaloneUpdater%5COneDriveSetup.exe%22%0A%22C%3A%5CWindows%5CSystem32%5Ccmd.exe%22%20%2Fq%20%2Fc%20del%20%2Fq%20%22C%3A%5CUsers%5Cscotth%5CAppData%5CLocal%5CMicrosoft%5COneDrive%5CUpdate%5COneDriveSetup.exe%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2750956%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOneDrive%20for%20Business%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStandalone%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2750992%22%20slang%3D%22en-US%22%3ERe%3A%20OneDrive%20StandAlone%20Update%20on%20Conference%20Room%20computers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2750992%22%20slang%3D%22en-US%22%3EMaybe%20the%20answer%20is%20the%20sync%20app%20per%20machine%20installation%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fonedrive%2Fper-machine-installation%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fonedrive%2Fper-machine-installation%3C%2FA%3E%3C%2FLINGO-BODY%3E
New Contributor

For shared computers, such as conference rooms, I would like to know what other folks are doing to keep the OneDrive client up to date, without causing a disruption to the user.

 

We don't really have control over the update process.  The resulting issue for a shared resource such as a conference room pc is that the OneDrive StandAlone Updater Task launches off, often times during a presentation, resulting in DOS command windows popping up in front of the presentation.  I believe that the last step in the update process is to run the following commands that result in the DOS command windows popping up.  How does your company handle this situation?

 

 

 

 

"C:\Windows\System32\cmd.exe" /q /c rmdir /s /q "C:\Users\userName\AppData\Local\Microsoft\OneDrive\21.030.0211.0002"
"C:\Windows\System32\cmd.exe" /q /c rmdir /s /q "C:\Users\userName\AppData\Local\Microsoft\OneDrive\21.030.0211.0002\amd64"
"C:\Windows\System32\cmd.exe" /q /c del /q "C:\Users\userName\AppData\Local\Microsoft\OneDrive\StandaloneUpdater\OneDriveSetup.exe"
"C:\Windows\System32\cmd.exe" /q /c del /q "C:\Users\userName\AppData\Local\Microsoft\OneDrive\Update\OneDriveSetup.exe"

 

 

 

 

4 Replies

@MrPullman 
Besides your very valid technical question, I would like to ask if you really think, that such a shared PC in a conference room is a great idea in the first place.

There are so many littel or big details to make this both great to use for the users and secure on the other hand, that you might be better with insisting on BOYD or roll out of MTR Teams Rooms Systems.

 

Shared device in conference rooms tend to become more or less useless over time, not only but also because of unexpected updates, overrunning disks after zillion different users logged on and got their profile downloaded, looooong waiting times for new users logging on this very machine for the first time because of all sorts of GPO, software installation, etc..

Long story short: YES, it certainly can be made to work, but do not expect it to be as easy as a user's desktop PC.

@Harald_Steindl,

 

Thank you for the response.  Those are very valid questions.  I will take those questions in order.  If I understand your answer correctly, you avoid the issue by not having shared computers in your conference rooms and have taken the path of either a Teams Room or BYOD and share content from the device you bring with you.

 

Besides your very valid technical question, I would like to ask if you really think, that such a shared PC in a conference room is a great idea in the first place.

For our organization we do.  We provide a locked down computer with office, a wall mount display, an audio/video solution, and wireless display capabilities.  This allows a person to present with either their device or the provided computer.  Most times the person will use both, their personal device to take notes, and the shared on to present with.

 

There are so many littel or big details to make this both great to use for the users and secure on the other hand, that you might be better with insisting on BOYD or roll out of MTR Teams Rooms Systems.

With 300+ conference rooms, the cost of the MTR's is a big drawback for us.  Out of consistency we build each conference room the same.  The build is minimal.  Office, locked down OS, shortcuts to teams online.  Group policy to erase profiles not used in 15 days.  Group Policy to reboot each computer each evening at 1:20AM if there are no active or inactive sessions.

 

Shared device in conference rooms tend to become more or less useless over time, not only but also because of unexpected updates, overrunning disks after zillion different users logged on and got their profile downloaded, looooong waiting times for new users logging on this very machine for the first time because of all sorts of GPO, software installation, etc..

Our logon time is generally about 50 seconds in this configuration as measure by from the time the person enters a password to when they can click 'join meeting' in teams.  We us Windows Update for Business, WUfB, and coupled with the nightly reboots, patching only happens outside the set 'Active Hours' of Windows 10.  Updating during the day is not an issue EXCEPT for OneDrive.

Long story short: YES, it certainly can be made to work, but do not expect it to be as easy as a user's desktop PC.

Again, thank you for your input.  I will take into consideration what you have said.  It is helpful.

thank you for your detailed report. As you already digged into GPOs and such, your setup looks quite valid. This is where many try to take short cuts.