Hi Toni,
Based on my experience, this issue may be caused by many aspects. So, we may
need time to do some trouble-shooting steps to narrow down it.
First, I would like to double confirm some detailed points:
======
1. Do you belong to any "excessively large" file sharing workspaces (GFS) or
Groove Standard Workspaces with Files tools? If so, do you know if any large
files (in excess of 500MBs) were placed into these workspaces recently?
2. What's the version of Groove this end user uses, Groove 3.1a 2374 or
other version?
Now, let's focus on this issue. Please refer to the following information
firstly:
=====
As you know, Groove is constantly listening for and processing changes to
the shared spaces of which you are a member. The longer Groove is offline,
the more changes have been queued up. When Groove is first brought back
online it is likely to consume more memory than usual while it processes the
queued deltas. The performance will improve once Groove catches up on the
queue. The time and memory consumption depends on the changes being made,
especially for the file sharing workspaces (GFS).
So, please check the following trouble shooting steps:
=====
1. Make sure that the end user is using the latest version of Groove.
Click Help>About Groove to check whether the build is 3.1a 2374. If the
build number is lower, please visit the following URL to get the latest one:
<
http://www.groove.net/downloads/groove/download-preview.cfm> and try to
install it again. What? the result?
2. Use Grooveclean tool with the -all option to clean and rebuild the
session between the groove client and it's Groove Relay server.
--------------
Note: You need to restore your account after that. So, backup your data is
important:
How to back up accounts and workspaces in Groove
http://support.microsoft.com/?id=907230
Here is a link to a Technote that will show you how to run a GrooveClean -all:
http://www.groove.net/support/kb/detail.cfm/docnum/TCN-00421
What's the result?
3. Please understand that the reason for Groove occupying high CPU resource
is that there must be some workspaces need to synchronize when we start the
Groove.
a. Please check all the workspaces which contain File Tool and the Groove
Folder Synchronization Spaces.
b. For the File Tool workspace, Please make sure that all of your files are
set to "Manual Download" and not automatic.See:
<
http://docs.groove.net/htmldocs/guide/tools/general/documentshare/files3x_download_settings.htm> and test this issue. What? result?
c. Please read over the FAQ's for GFS spaces carefully as the type, size,
and number of files in these spaces can cause sever performance issues:
<
http://www.groove.net/index.cfm?pagename=GFS_FAQ>
If there are suspected workspace, please make sure others are works fine in
them and temporary delete them and restart Groove to test this issue. What?
the result?
Hope it will be hlepful.
Thanks.
Best reagrds,
Shirley