Start OneDrive when using a RemoteApp in WVD

adam222 Yes, i moved the "OneDriveSetup=C:\\Windows\\SysWOW64\\OneDriveSetup.exe /thfirstsetup" from the Run key of the default user profile to the RailRunonce key in GPO instead. But i suspect its enough to just remove it, and not set it in RailRunonce. I had no time yesterday to check this, but will now. 🙂 Thanx for your reply!

Mtollex70 Hi, I tried the deletion of run keys in the default user hive and works for me. I deleted entries for Run and RunOnce though as there was another OneDrive entry in there. I will test and see if I need to delete both.

One thing to note, if you delete the reg keys above, and you also use the host pool for a desktop, you may need to use a GPO to launch OneDrive for normal logons..

Mtollex70 I am having the same problem. First login hangs on preparing Windows for 5 or so minutes. When RemoteApp opens, OneDrive is not configured. But on subsequent logons, it's there.

I can see in task manager that the renounce.exe is running for the user. I'd I kill renounce.exe in those 5 minutes while it's "preparing windows" it logs on successfully straight away.

I cannot work out why the runonce task is holding the login...

Any thoughts?

bnicholson80 Are you sure you didnt do anything else in this process? I've been struggling with this problem for a while, feel i have tried everything, including now your solution. Still 5 min on first login, 20-sek on logins after that. 😞 And OneDrive does not work on first login. 

Baljit Aujla 

Baljit, I believe I found a solution to this hang on RemoteApp application launch for new users with OneDrive integrated using the RailRunonce method.

• Load the default user profile hive into your registry editor. 
• From within the default user profile hive, browse to Software\Microsoft\Windows\CurrentVersion\RunOnce
• There you will find the issue. In the RunOnce key of the Default profile hive is the below string value.

• New accounts logging in for the first time are having the above run automatically when it builds the new user profile. This combined with RailRunonce causes the Runonce wrapper to hang up.
• Delete this string value from the default profile hive.
• Unload the default user profile hive in your registry editor.
• Attempt to launch a RemoteApp with a new user account.
• My initial logins went down from 5+ minutes to just 25 seconds by removing this string value from the default registry hive.
• Also to note, OneDrive works on first login which is a bonus!

ronald2424 

Hi,

In my case, I´m relying on sharepoint and synced document libraries for that. So remote users save their documents to the server´s onedrive (I have a per user installation, but will be trying the per machine installation soon on another implementation), onedrive syncs to sharepoint and SP syncs to the user´s workstation.

Robin Hobo 

Hi,

I applied the 3 registry settings for One Drive. However when the app is selected it does not open as a window for the users as they need to do map to network drives. Is that possible to achieve?

RD 

Rhys Williams

I tried that. It seems like OneDrive still opens and hangs once for every user at first login. Is this script all you had to change to make it work?

Johan Voerman DjTjon01 

We have been experiencing the same issues. We've tried using the reg keys however it doesnt work on the first login, it does then work if a user logs out and back in again.

The solution we have found is to publish a bat script as the remote app that launches the target app and also restarts the OneDrive sync client. This works on the first login from a clean profile:

@echo off
cd "%ProgramFiles%\Windows NT\Accessories\"
start wordpad.exe
taskkill /F /FI "USERNAME eq %username%" /IM OneDrive.exe 
cd "C:\Program Files (x86)\Microsoft OneDrive\"
start OneDrive.exe /background
exit

While this is quite dirty but it certainly does the job, better than making all users login once and then log out and back in again for KFM and FoD to work. 

Marcel Biebricher That did the trick, thanks! More people on other forums are talking about this setting as well, however, as you mentioned no documentation about what the value 2 means.

Robin Hobo we have same problem. But this isn't a onedrive problem. For example we use printix in a environment with the same Railrunonce. Also in this case the first logon attempt is stuck. After that it's ok. 

Anyone idea's?

Baljit Aujla  @racook 

I have exactly the same problem. WVD environment with Windows 10 multi-user session custom image (without O365 applications) with latest updates (including 1909 version). No FSLogix in place (we don't use O365 apps within th WVD environment).

Customer has an application (non Microsoft) and wants to access files to open from OneDrive. Installed the OneDrive per machine (latest version) and applied te following reg keys for silent account config;

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive]
"SilentAccountConfig"=dword:00000001
"FilesOnDemandEnabled"=dword:00000001

And the following for remote apps;

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RailRunonce]
"OneDrive"="\"C:\\Program Files (x86)\\Microsoft OneDrive\\OneDrive.exe\" /background"

On question, does the last registry key be a "REG_ZG" or a "REG_EXPAND_SZ" type?

Anyway, in both cases it is not working. If I go within the app to File > Open I see OneDrive, but it is not configured / user is not signed in. I also see the OneDrive system icon from the WVD environment in my local system tray (not logged in). If I publish OneDrive.exe as a RemoteApp and start this app, OneDrive is configired correctly and OneDrive files became also available in the first RemoteApp.

When publising the full desktop everyting is working fine!

One other problem that a have and wat Baljit montioned is the hang on "Preparing Windows". This will take up to 5 minutes! This problem is only with a RemoteApp and not with a Published Desktop. This problem started when installing the OneDrive per Machine installation. If I remove OneDrive from the Hostpool, the problem is gone. No strange errors in the EventLog.