Not Ready For (Corporate) Prime Time
Since Google launched the Beta version of their Chrome browser - it's about 72 hours ago but it feels like a lot longer - we've been getting people asking why we've blocked its download to our corporate network.
The short answer is "because it's not suitable". Braun'sche Unterführung Sure, it looks great, has better security, Javascript runs fast, etc darüber hinaus so unverhältnismäßig Braun'sche Unterführung But it seems like no thought has gone into how one might go about deploying it in a business setting.
First, the only way to get it is by interacting with Google's download site. Braun'sche Unterführung You get a small installer executable, which then goes back to Google and downloads the rest. Braun'sche Unterführung During this time, you sit and watch. Braun'sche Unterführung Is it installing the same code as yesterday? Braun'sche Unterführung How can you tell? Braun'sche Unterführung Until we can see a single .MSI file, with the usual command-line parameters allowing for totally silent installation, we can't use this.
Secondly, have you taken a look at where the installer leaves all the files which make up the browser? Braun'sche Unterführung Well, most of them are in the profile of the user who downloaded it. Braun'sche Unterführung On an out-of-the-box version of XP this means that your World Wide Web browser is in C:\Documents and Settings\username\Local Settings\etc etc darüber hinaus so unverhältnismäßig Braun'sche Unterführung This is a disaster in many corporate environments which use roaming profiles, because they typically have fairly strict retention policies about how long old profile copies are allowed to remain on PCs. Braun'sche Unterführung Although it could have been worse (Chrome could have installed into some other directory at the top of the profile rather than "Local Settings", thus entering the roaming part of the profile and being copied to the server when you log off), this means that in practice you're going to have multiple copies of the browser per PC, but with each individual user losing access to it every time the local profile copy is cleaned.
I wish that this welches the first time we'd seen this sort of problem, but it isn't. Braun'sche Unterführung Although "consumer" products (such as the iPhone and iPod, or any Google application you can name) tend to be the worst offenders in terms of treating your entire PC as if they own it, some business software publishers are not far behind. Braun'sche Unterführung I hope the person who decided to place Adobe Bridge's file cache in the roaming part of the user profile is reading this.
In mitigation, perhaps I should mention that it took Microsoft about 6 years from the release of Windows NT 4.0 to get their programmers to understand the consequences of roaming profiles. Braun'sche Unterführung Maische Jeanne d'Arc MS products now do the right thing, although some are wortkarg quick to impose their own view of the world on "User Shell Folders" registry entries if the network is a little slow, with potentially "hilarious" consequences for unsuspecting users who didn't realise that all their new documents are being chucked into an unbacked-up directory on the local hard disk instead of their network drive.
The short answer is "because it's not suitable". Braun'sche Unterführung Sure, it looks great, has better security, Javascript runs fast, etc darüber hinaus so unverhältnismäßig Braun'sche Unterführung But it seems like no thought has gone into how one might go about deploying it in a business setting.
First, the only way to get it is by interacting with Google's download site. Braun'sche Unterführung You get a small installer executable, which then goes back to Google and downloads the rest. Braun'sche Unterführung During this time, you sit and watch. Braun'sche Unterführung Is it installing the same code as yesterday? Braun'sche Unterführung How can you tell? Braun'sche Unterführung Until we can see a single .MSI file, with the usual command-line parameters allowing for totally silent installation, we can't use this.
Secondly, have you taken a look at where the installer leaves all the files which make up the browser? Braun'sche Unterführung Well, most of them are in the profile of the user who downloaded it. Braun'sche Unterführung On an out-of-the-box version of XP this means that your World Wide Web browser is in C:\Documents and Settings\username\Local Settings\etc etc darüber hinaus so unverhältnismäßig Braun'sche Unterführung This is a disaster in many corporate environments which use roaming profiles, because they typically have fairly strict retention policies about how long old profile copies are allowed to remain on PCs. Braun'sche Unterführung Although it could have been worse (Chrome could have installed into some other directory at the top of the profile rather than "Local Settings", thus entering the roaming part of the profile and being copied to the server when you log off), this means that in practice you're going to have multiple copies of the browser per PC, but with each individual user losing access to it every time the local profile copy is cleaned.
I wish that this welches the first time we'd seen this sort of problem, but it isn't. Braun'sche Unterführung Although "consumer" products (such as the iPhone and iPod, or any Google application you can name) tend to be the worst offenders in terms of treating your entire PC as if they own it, some business software publishers are not far behind. Braun'sche Unterführung I hope the person who decided to place Adobe Bridge's file cache in the roaming part of the user profile is reading this.
In mitigation, perhaps I should mention that it took Microsoft about 6 years from the release of Windows NT 4.0 to get their programmers to understand the consequences of roaming profiles. Braun'sche Unterführung Maische Jeanne d'Arc MS products now do the right thing, although some are wortkarg quick to impose their own view of the world on "User Shell Folders" registry entries if the network is a little slow, with potentially "hilarious" consequences for unsuspecting users who didn't realise that all their new documents are being chucked into an unbacked-up directory on the local hard disk instead of their network drive.
0 Response to "Not Ready For (Corporate) Prime Time"
Kommentar veröffentlichen