Software Deployment Question

Google Chrome 29.0

09/16/2013 8525 views

Hello IT Ninja,

I have sequenced Google Chrome, and i have manually written a VB script to copy the UserData folder to %localappdata%\google\chrome folder (in order to apply my standards like home page, proxy settings etc). This folder is copied before the Virtual application is launched (Pre-launch Script added in OSD). When the application is launched the Virtual app, created its own UserData folder overriding my customized UserData folder resulting in removing my standards. Any help is appreaciated.




Answer Summary:
@dunnpy has helped me out to find out key things which are important while sequencing Google Chrome. We should not launch the app while sequencing it, and the local app data folders (Google and Crash Reports) which be deleted. Thanks Dunnpy
1 Comment   [ + ] Show comment


  • Hi Dunnpy, when i push the Virtual Google Chrome on my Windows 2003 Terminal Server, the application loads 100% however shuts downs without launching, when i looked at the system requirement for Google Chrome, i found the OS XP and above are supported. Do this mean, that even when we virtualize google chrome, this will not launch in 2003 Terminal Server. Please help. Thanks

All Answers


I followed this recipe for Chrome 29 (I know it's for an old version, but it worked) - http://stealthpuppy.com/sequencing-google-chrome-15

I put the UserData folder outside of the package by using the launch commands noted above and used a mixture of 'Master_Preferences' (https://support.google.com/chrome/a/answer/187948) and Chrome GPO settings (added to the registry in the sequence not through AD GPO) to acheive the desired configuration.


Hope that helps,


Answered 09/16/2013 by: dunnpy
Red Belt

  • Hello Dunnpy, thanks for your help, i was able to sequence the app, however the ONLY issue now is at the first launch I get the prompt "Google Chrome was not shut down properly- would you like to restore" i want to suppress this as i don't want my users to see this message at first launch. It should ideally show my desired home page without any prompt.. Any help is appreciated. Thank you!
  • Did you launch during sequencing to create FB1? I didn't on my sequence and I've had no issues.
    I'm sure that shutdown prompt is part of either the user preferences file (which you won't have sequenced if you've followed the recipe), the master_preferences file or a registry key.

    Check your sequence, I'm sure it's an obviously named entry and remove it.
  • Hi... i haven't launched the app while sequencing, i have a USER DATA folder which i copied from a older version, i am copying this folder to %locallappdata% in prelaunch script. The Prompt which i get shows a tab which was closed forcefully (thats the page which i mentioned in preference file as my home page). Hope i am clear.
  • Check the preference file in the USER DATA folder - I think there's a flag in there to say whether it was shut down correctly.

    I think you've captured that in your file and that's why it's showing it.

    Post your preferences file if you think it will help.
  • Just a part of my Preference file..

    "session": {
    "restore_on_startup": 4,
    "restore_on_startup_migrated": true,
    "urls_to_restore_on_startup": [ "https://myadp.adpcorp.com/" ]
    "sync_promo": {
    "startup_count": 6,
    "user_skipped": true,

    "view_count": 6
  • What I'm thinking of is:

    "exit_type": "Normal",
    "exited_cleanly": true,

    If you manually set exit_type to "Crashed" you can recreate the error you receive.
  • Thanks for all your support, i have found the cause for this prompt "Improper Shutdown" i had to delete the folder from %Localappdata% while sequencing it. I deleted Google and Crash Reports folder from local app. Thank you so much
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ