![]() If you have problems installing Drive for desktop, restart the computer where you're having trouble and try again. ![]() To turn off auto-updates, depending on your user's device and system, follow the steps at Configure auto-updates (Windows) or Manage Chrome updates (CBCM) This is expected behavior, and you can ignore this folder.ĭrive for desktop comes packaged with Google Update (Windows) or Google Software Update (Mac) to auto-update Drive for desktop on your users’ computers. Note: You might see a folder called "localhost" when starting Drive for desktop (v.48 and later) on a Mac for the first time. Use caution deleting this folder, as it might contain content that has not yet been saved or synced. (Optional) Delete the Google Drive folder at ~/Google Drive.Hdiutil mount GoogleDrive.dmg sudo installer -pkg /Volumes/Install\ Google\ Drive/GoogleDrive.pkg -target "/Volumes/Macintosh HD" hdiutil unmount /Volumes/Install\ Google\ Drive/ exe file and deploy it in silent mode: Windows For this option, users need administrator rights to their computer. Let each user install Drive for desktop on their own machine.Install Drive for desktop on each user's computer using one of these options: This lets users see when someone is editing shared Microsoft Office files, and can help prevent editing conflicts. (Optional) At the same Admin console page, check Allow users to enable real-time presence in Microsoft Office from Google Drive for desktop.This restricts access to Drive for desktop to only devices owned and managed by your organization. (Optional) At the same Admin console page where you turned on sync, check Only allow Google Drive for desktop on authorized devices.Make sure to allow Drive for desktop and specify whether users can see Drive for desktop download links. If you haven’t already done so, turn on sync for your organization.Also make sure to use a supported browser. ![]() For the best user experience, we recommend that you upgrade to the latest OS version available for your machine. EXAMPLE PS C:> Explanation of what the example does. ![]() It seems to work sometimes and sometimes it does not.Example of the code is listed below: The way that we are trying to mitigate this issue is via a custom PowerShell detection script that checks for the presence of the Google Drive File Stream app display name via a WMI query. We used to just deploy the current version at the time and simply check for the presence of the Google Drive executable because it always stayed in the same file path but File Steam installs itself in a different file path each and every time (very frustrating).įor example: C:\Program Files\Google\Drive File Stream\25.196.222.1747 C:\Program Files\Google\Drive File Stream\25.196.245.2031 I am curious to hear from other SCCM people who are deploying File Stream as to how they are managing this as we want to keep it up to date in the wild without having to create a new deployment each and every time a new release comes out. ![]() After we deploy the current version at the time and a new version comes along (they self update) SCCM thinks that that its no longer installed as the installation directory is in a different path and thus it tries to install the previous version again. We are having issues with deploying Google Drive File Stream with SCCM detection rules. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |