GoogleDesktopEnt Deployment Issues

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

GoogleDesktopEnt Deployment Issues - Shell Not Loading

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> GoogleDesktopEnt Deployment Issues - Shell Not Loading

Page: [1]

Message

<< Older Topic Newer Topic >>

GoogleDesktopEnt Deployment Issues - Shell Not Loading - 8/25/2008 11:02:43 AM

pglyn-williams

Posts: 65
Score: 0
Joined: 8/10/2001
From: Ontario, Canada
Status: offline

Ok, I need some fresh eyes on this issue to help with some suggestions,

I deployed GoogleDesktopEnterprise to Corporation the other day, along with the Custom .ADM Templates in 3 packages-chained,

1. RemoveOldGoogleDesktop *reboot
2. Install new GoogleDesktopEnt
3. Re-enforce Homepage

Sounds simple, right? It should be,

but now when some clients (not all), login after the 1st step, the desktop doesn't load.

In order to workaround this issue, I have to initiate the installation of GoogleDesktopEnt (step #2 above) to get it working.

Also, looking through the execution history on the client machines, it seems that step#1 goes through fine, but then #2 is execution priority is being bumped by other updates in queue in SMS - even when set to high priority over the other ones??

Also, if the client waits about an hour or two, everything loads up fine and all updates are applied succesfully.

Anyone have any insights they might be able to share in to this issue?

Hopefully this thread also assists others in their pursuits with deploying Google desktop also.

< Message edited by pglyn-williams -- 8/25/2008 11:03:51 AM >

_____________________________

Pierson Glyn-Williams
Systems Management
Region of Peel (HQ)

Post #: 1

RE: GoogleDesktopEnt Deployment Issues - Shell Not Loading - 8/26/2008 11:15:54 AM

rbennett806

Posts: 885
Score: 18
Joined: 6/14/2006
Status: offline

Okay, just tossing some random ideas out there...

Sounds like that uninstall/reboot combo is getting you. Can you create a separate program/package to uninstall the old version (and maybe run a hardware inventory update to reflect this change in SCCM) and then just create a different collection containing the machines that don't have it installed? Then target your installation of the new app at this second collection.

Also, are you sure that the installation of the new version won't remove the old one automatically?

Can you use a VBScirpt wrapper around things to do the uninstall and install of the new one all in one package?

Are you sure you need the reboot after the uninstall?

(in reply to pglyn-williams)

Post #: 2

RE: GoogleDesktopEnt Deployment Issues - Shell Not Loading - 8/26/2008 11:41:01 AM

pglyn-williams

Posts: 65
Score: 0
Joined: 8/10/2001
From: Ontario, Canada
Status: offline

rbennett, suggestions are always appreciated,...here is my response,

the 1st package to removeGoogleDesktop is the potential issue, however considering that after reboot, if you install GoogleDesktop using the run task in TaskManager, it restores the shell and everything continues as it should.

So, somehow, for some reason, the next step #2 isn't kicking off on restart, which should fix the shell issue. **I should mention that after 1-2hrs, everything seems to work itself out - so assuming that the queue is stalling somewhere.

I understand where you are going with isolating the first part and creating a new collection to target the 2nd part, this would potentially help in identifying the issue or even fixing it as a workaround, but I'm a little too far in to the deployment at this time (may help others who are looking to deploy this later).

I was unable to find a way to wrap it all in to one step without a reboot, given the pieces I had available to work with at the time. I'm sure if I spent more time working on it, I could probably create a one package deal, but the 3-step process seemed viable and worked in the past. The chained package never failed before.

So, current status is about 10% of our clients are having this issue (no shell). Half of the 10% have been resolved through the workaround mentioned above by front-line staff, and the other half have yet to turn on their machines (projected failure rate).

300 more calls in to the help desk over the rest of the week is the remainder of this issue (projected). So far, 150 calls a day was the result of this issue. Since this is the tail end of this deployment implementation, there isn't much to be done to resolve - so, my main goal is understanding what happened and where I may be able to pinpoint from the information available.

_____________________________

Pierson Glyn-Williams
Systems Management
Region of Peel (HQ)

(in reply to rbennett806)

Post #: 3