Any organization progressive enough to be using Google Apps for anything is unlikely a locked-down IE8/XP environment.
i.e. a venn diagram between Google App using orgs and IE8/XP lockdown orgs will have very little overlap.
Any organization progressive enough to be using Google Apps for anything is unlikely a locked-down IE8/XP environment.
i.e. a venn diagram between Google App using orgs and IE8/XP lockdown orgs will have very little overlap.
Chrome has design eccentricities that make it interact w/ some Windows management functionality (redirected "Application Data" folders, specifically) in a very suboptimal manner (maintaining 10MB+ of files in each user's redirected AppData folder is a problem on a server hosting 3,000 users' folders). Installing Chrome on the Windows XP machines isn't a slam-dunk.
I suspect we'll just have to bite the bullet and use Chrome while, simultaneously, giving up functionality in Windows to do it.
I'm having the hardest time believing you said that with a straight face.
If Google got SSO to our SAML server working for Chrome Sync this would be a non-issue but, apparently, we're also the only people in the world that want that functionality, too.
I'd love to use something like ZFS to handle this storage, at which point this wouldn't be an issue, but I have to work under the constraint that various teachers acting as Windows admins need to be able to manage the servers. More money would solve this problem for me.
Money aside, it's galling that the developers aren't building for the enterprise deployment case. I WANT to run Chrome _badly_ in corporate environments but it's not engineered for my use-case.
You can find it by going to "Install Chrome for all user accounts" http://support.google.com/chrome/bin/answer.py?hl=en&ans..., which points to "Alternate (offline) Google Chrome installer (Windows)" http://support.google.com/chrome/bin/answer.py?hl=en&ans...
You want the "Alternate installer for all user accounts" (https://www.google.com/intl/en/chrome/browser/eula.html?syst...). That will install Chrome in the Program Files directory.
We're using the "Enterprise" MSI-based installer. We are seeing difficulties with it. It's storing large DLL files in each user's user data folder, which we're putting on a server so that user settings will "follow" them from computer-to-computer.
Last I heard, it was in Google Pack.
You might want to re-evaluate where you are focussing your energy on optimization.
We also have full support for global policies and pretty much any administration features you could need. I'd be happy to point you in the right direction if you have specific questions or difficulties.
Chrome installs a gcswf32.dll file into "Program Files" but it appears to be downloading a new one for each user, stashing it in their user data folder, then failing to load it properly on subsequent sessions because it's stored on a network path.
The thread you referenced should actually be resolved in Chrome 21. That said, it refers to a scenario where parts of the profile are remapped to a network share. It's important to understand that this is not a supported configuration for Windows profiles in general, and is known to break applications other than Chrome. Whereas standard roaming profiles should work fine in all applications, and are the configuration supported by Windows.
I don't know where you're getting the phrase "... this is not a supported configuration for Windows profiles in general". Unsupported by whom? Microsoft has been shipping Application Data Folder Redirection as feature of Windows Group Policy since Windows 2000. ) and not some kind of "registry hack" or unsupported (by Microsoft) tweak. I've yet to find any Microsoft developer documentation advising that this feature is "unsupported". I _have_ seen multiple applications broken by using this feature (including Microsoft applications) but I don't think that makes the feature "unsupported" by Microsoft. It seems like this feature is "unsupported" by applications because they make assumptions about how Windows behaves and don't engage systems administrators in their development process.
In the case of Chrome I _really_ want to use it in enterprise situations-- it's my favorite browser, personally. The attitude of installing into folders writable by individual users seems to pervade even the enterprise distribution of Chrome, however. I would argue that, in an enterprise environment, updates should only be applied to the computer's copy of Chrome and not into individual user folders. This creates pain and frustration for sysadmins. It sounds, to me, like the "component updater" doesn't take into account installs where there is a computer-wide copy of Chrome and needs some re-architecting.
Alternatively, we would be able to completely circumvent this problem and just leave the user's Chrome "User Data" folder in their local profile if we could use "Chrome Sync" with our SAML SSO that we use for Google Apps for Education. I haven't looked at it for 6 months, but the last time we looked Chrome Sync did not support authenticating via our SSO, so we had to scrap that idea and go with using a redirected user data folder to allow users to have their Chrome data "follow" them between computers.