Windows 10: Drives dissapeared after Onedrive deployment

We have recently deployed both Microsoft InTune and with InTune policies have enforced synching with Sharepoint libraries. We are not sure if that is why, but many of the PC's are now not showing c drive, or other sharer drives under "This PC". They can still be accessed by typing "c:" for example, but do not display. We have not set any policy in InTune related to drive display, nor in Active Directory by GPO. Would anyone else have seen this behaviour?

:)

 

Windows 10 - OneDrive

Right click on the app and one of the properties has an option to not automatically start it. Uncheck, restart the computer, and it should stop. If you want to go another step further, find the OneDrive app in the start menu, right click on it and uninstall.

If that is still insufficient, there is a batch uninstaller for OneDrive available online. I can copy the code here if you need it.

 

Customised Windows 10 deployment on multiple desktops and laptops.

OK, after giving this a thought and thinking how I would do it, here's my suggestion. Please notice that, as I said, this is how I would do it. Other geeks might disagree with parts or all of it.

I tested this scenario using one Hyper-V VM as technician machine (the one to build image) and three virtual machines to test simultaneous deployment in two scenarios:

• Capturing install.wim from technician machine and using DISM to apply / deploy image from a network share
• Capturing install.wim from technician machine, making ISO from it, deploying by clean installing from ISO burned to Flash drive

Based on the fact that ISO method is clearly faster and simpler, it is what I suggest to you. I estimate you would need an hour and half to two hours to customize install image, capture it and make an ISO, then assuming you would make 5 Flash drives for install / deployment you would need about half an hour per five machines, in other words you would deploy to those 25 new machines in less than three hours, almost a full working day to deploy those 50 existing ones.

Two working days, day 1 to make the image and deploy to new machines, day 2 to deploy to old ones.

Chronological workflow based on my suggestion:

Phase 1, Image customization tutorial, parts One through Six:

• Install Windows 10 on a technician machine (I recommend Hyper-V VM but any capable PC is OK)
• Boot to Audit Mode
• Update Windows, install software, customize & personalize Windows
• Sysprep

Phase 2:

• Capture the install.wim from technician machine as told in this tutorial, Part Four steps 4.1 through 4.5 (physical PC as technician machine) or Part Four steps 4.6 through 4.13 (Hyper-V VM as technician machine)
• Create ISO as told in same tutorial, Part Five
• Burn / write ISO to as many Flash drives as you want to / need to for simultaneous installs
• Boot production machines from Flash drive, install Windows 10

The above is how I would do this. If you choose the DISM method instead, applying install.wim from a network share, see this Microsoft support article: https://technet.microsoft.com/en-us/.../hh824910.aspx

For more advanced deployment using MDT see this article: https://technet.microsoft.com/en-us/.../dn475741.aspx

 

Recent shortcuts for apps show files on OneDrive instead of local hard drive

I was able to follow the steps and uncheck the "Use Office apps to sync" box but it didn't change Office's behavior. I opened and closed an Excel spreadsheet on my local hard drive. After that, when I right-clicked on the Excel icon pinned to the taskbar, a link to the OneDrive cloud file was in the list of recent files instead of a link to the file on my hard drive.

Do you have any other suggestions?

Thanks!