I hope this helps any Windows administrators or AWS instance managers. You can now use Google Chrome and not have to deal with any more confusing prompts and security settings. $LocalTempDir = $env:TEMP $ChromeInstaller = "ChromeInstaller.exe" (new-object ).DownloadFile('', "$LocalTempDir\$ChromeInstaller") & "$LocalTempDir\$ChromeInstaller" /silent /install $Process2Monitor = "ChromeInstaller" Do Until (!$ProcessesFound)Ĭhrome will download within a few minutes. Open the main menu and select "Windows Powershell". In the past, Google used to allow you to use. Fortunately, there is a way to install Google Chrome on a server, both 20 for all users. LOL.įor most people, this may not be much of a nuisance but as product manager, this is terrible user experience (UIX).Īvoid IE altogether and download Google Chrome using Windows Powershell. In older versions of Google Chrome and in Windows Server 2003, you could copy and app data folder from the user and dump it in the all users folder and create a shortcut to the executable file. IE will then mention that based on your security settings, Google is blocked. IE then warns you that you're about to do something that your security settings might consider insecure. IE asks you to configure your security settings. For example, here is what you see the first time you start IE. I generally dread any time I have to create a new instance of Windows and Internet Explorer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |