Jump to content

Recommended Posts

Posted

installed windows 1709 - fresh install build 16299.19 but where is one drive and files-on-demand?

onedrive folder from start menu is empty - go to users folder on c drive and onedrive folder is empty.

So downloaded latest onedrive https://go.microsoft.com/fwlink/p/?linkid=851311 run installation and says preparing onedrive for first use and finishes but nothing appears still?

Any ideas - tried removing one drive and reinstalling including onedrive for business from office 2016 but cannot get any one drive to appear at all?

Posted
installed windows 1709 - fresh install build 16299.19 but where is one drive and files-on-demand?

onedrive folder from start menu is empty - go to users folder on c drive and onedrive folder is empty.

So downloaded latest onedrive https://go.microsoft.com/fwlink/p/?linkid=851311 run installation and says preparing onedrive for first use and finishes but nothing appears still?

Any ideas - tried removing one drive and reinstalling including onedrive for business from office 2016 but cannot get any one drive to appear at all?

It's a weird / slow install process for the client, initially it's not there, then it appears... disappears, upgrades then appears again and sometimes doesn't work until after a reboot.

 

What exact version is installed if you right click Settings on the system tray?

 

Also have you got any GPOs that may be disabling it?

  • Thanks 1
Posted
This doesn't deserve it's own thread, so i'll try asking in here. I upgraded client image to 1709 and i'm using local profiles (still testing, curric is still on Win7) and i'm just wondering about HDD usage with local profiles. Do you guys that are using local profiles clear them at log off or do it periodically?
Posted
This doesn't deserve it's own thread, so i'll try asking in here. I upgraded client image to 1709 and i'm using local profiles (still testing, curric is still on Win7) and i'm just wondering about HDD usage with local profiles. Do you guys that are using local profiles clear them at log off or do it periodically?

 

As we don't use SSD's yet all the HDDs are big enough and our image is pretty small so we just leave them.

 

You can set GPs to delete them after so many days of non use but due to Win 10 being pretty slow logging in we've took this off so anyone who manages to get a device they've logged into before will get logged in a lot quicker.

 

We re-image every few years so this then clears the devices.

  • Thanks 1
Posted
Today's experiment: WSUS update to 1709, took 80 mins during the rebooting phase from 1607 on a core i5 with ssd. While I was waiting I imaged a core i3 laptop via 100Mb ethernet, and installed all the apps, that was quicker.
Posted
Reading up about the one drive client. OnedriveSetup needs to run in the user context on login. This slows down the initial setup which could be a pain on shared PCs. If done a line of powershell to download the latest setup. Wondering weather to run the setup on user login if the version of Onedrive. Exe is not the same. May also check uev settings to see if they can roam. What are others doing? It feels like it's almost there. Just needs to be almost as fast as a mapped drive. I got team sites working.
Posted

I'm completely ignoring the ridiculous One Drive, call me when there's an msi that installs to program files like a reasonable application.

 

"This command must be run at user logon and using Administrator permissions. It must be run for each user on a machine."

 

It's not a thing for shared machines at all.

Posted

Expect if you run it as admin and the account has a o4b licence it says Onedrive cant run elevated. I think they mean Onedrivesetup. exe must run in the user context.

 

You could replace the Onedrive setup. exe in c:\windows\syswow64 with the latest.

Posted
Expect if you run it as admin and the account has a o4b licence it says Onedrive cant run elevated. I think they mean Onedrivesetup. exe must run in the user context.

 

You could replace the Onedrive setup. exe in c:\windows\syswow64 with the latest.

That's the method I've been trying via a script I found elsewhere. Errored out in MDT so need to look at it more closely.

 

Guess I could replace it using DISM but that ruins my plans to have a completely clean MS WIM as the base file.

Posted (edited)

I've been looking at this:

https://social.technet.microsoft.com/wiki/contents/articles/33549.onedrive-next-generation-sync-client-deployment-guide.aspx

 

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run Onedrive could be deleted.

 

Have a scheduled task on a server

Invoke-WebRequest -Uri "https://go.microsoft.com/fwlink/p/?linkid=844652" -OutFile "\\server\software\OneDrive Client\OneDriveSetup.exe" -Verbose

 

Then on client:

GPP (Replace)

From:\\server\software\OneDrive Client\OneDriveSetup.exe

To:c:\temp\onedrivesetup.exe

 

Then login script(need to add some version checking Onedrivesetup.exe file version against Onedrive. Exe)

 

start-process -wait "c:\temp\onedrivesetup.exe" -ArguementList "/silent"

start-process -wait "$env:USERPROFILE\AppData\Local\Microsoft\OneDrive\OneDrive.exe" -ArguementList "/background"

 

I'll test this and see if it speeds up things.

Edited by free780
Posted

Thing is if the old client deploys and someone launches it you could end up with a cache you don't want before Files on Demand kicks in.

 

Also reading that updater process seems odd when WSUS exists.

Posted

I'm kind of in a reverse situation from some of you folk.

 

I've been looking at LTSB as going to be our primary Windows 10 OS....

Then I see about 1709's improved "On demand" OneDrive.

Schools in Scotland all have access to a Scotland-wide educational resource called Glow. Which includes 1Tb of OneDrive space for each user (apparently?).

We've resisted OneDrive on clients because of the nightmare synch scenario.

Having dabbled with OnDemand, it looks the business.

It's just a pain in the whatnots that it NEEDS 1709 (and the latest client).

 

So because of OneDrive, my Windows 10 plans have gone from "Nearly ready" to "You'll need to wait while I find out how to switch off all of the other cobblers. And wait on our Infra team installing the 1709 ADMX".

 

 

Oh.. And my SCCM boot disk acts weird on 1709.

Previously, I could put in PAUSE commands in my Task Sequence so I could troubleshoot things.

With 1709, the Windows setup page takes priority and there's no way of seeing the TS window.

I can ALT TAB, but I can't get the window to appear.

 

Now downloading the updated 1709 ADK so I can update my SCCM boot disks - mutter, grumble, moan.

Posted
I'm kind of in a reverse situation from some of you folk.

 

I've been looking at LTSB as going to be our primary Windows 10 OS....

Then I see about 1709's improved "On demand" OneDrive.

Schools in Scotland all have access to a Scotland-wide educational resource called Glow. Which includes 1Tb of OneDrive space for each user (apparently?).

We've resisted OneDrive on clients because of the nightmare synch scenario.

Having dabbled with OnDemand, it looks the business.

It's just a pain in the whatnots that it NEEDS 1709 (and the latest client).

 

So because of OneDrive, my Windows 10 plans have gone from "Nearly ready" to "You'll need to wait while I find out how to switch off all of the other cobblers. And wait on our Infra team installing the 1709 ADMX".

 

 

Oh.. And my SCCM boot disk acts weird on 1709.

Previously, I could put in PAUSE commands in my Task Sequence so I could troubleshoot things.

With 1709, the Windows setup page takes priority and there's no way of seeing the TS window.

I can ALT TAB, but I can't get the window to appear.

 

Now downloading the updated 1709 ADK so I can update my SCCM boot disks - mutter, grumble, moan.

 

You get 1tb of onedrive with Office 365 anyway if you have that.

 

And there are products that already map the drive to a drive letter on logon without any synchronization so its not really new. Check out onedrive cloud mapper.

 

Basically you don't need this update.

Posted
You get 1tb of onedrive with Office 365 anyway if you have that.

 

And there are products that already map the drive to a drive letter on logon without any synchronization so its not really new. Check out onedrive cloud mapper.

 

Basically you don't need this update.

 

You would save £1000/year though. LTSB is supposed to be for specialised devices, not normal users, you're already paying for Enterprise if you're using it, which allows control of the app store etc. Updating Windows every 8 months instead of every 8 years means if anything breaks it'll be minor, it's just another patch tuesday.

 

Also you'll miss the new video editor in Photos, Paint 3D, Minecraft Education, Visual Studio, Sticky Notes, new hardware support, support from Microsoft

  • Thanks 2
Posted
You get 1tb of onedrive with Office 365 anyway if you have that.

 

And there are products that already map the drive to a drive letter on logon without any synchronization so its not really new. Check out onedrive cloud mapper.

 

Basically you don't need this update.

 

Exploit Guard, Credential Guard, Mixed Reality, supported OneDrive client that doesn't use the horribly dated WebDAV protocol... worth the update for me

  • Thanks 1
  • 4 weeks later...
Posted
1703 to 1709 WSUS delivered update takes 20 mins to reboot on an SSD core i3-2330M laptop, that's not too unreasonable to just send out to everyone I guess.
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...