Do not shut down your firewall to try to start Groove Virtual Office 3.x or Groove Workspace 2.x while the firewall is inactive (915565)

MORE INFORMATION

If you follow these steps when you have trouble starting Groove Virtual Office 3.x or Groove Workspace 2.x, Groove may function as a limited data-sharing program:

1. You shutdown the firewall.
2. You try to start Groove Virtual Office 3.x or Groove Workspace 2.x.
3. You reactivate the firewall.

However, many account functions rely on the same connection that is required to start Groove Virtual Office to the Groove servers or to the Groove Management Server for the organization.

If you cannot start Groove while the firewall is active, the following Groove features may not work as expected:

• You cannot search for contacts in the public Groove directory.
• You cannot publish your contact information to the public Groove directory.
  
  Note If you publish your information before you restart the firewall, the information will be purged after 15 days. This behavior occurs because your account appears inactive to the server that maintains the directory.
• You cannot back up your account to groove.net.
  
  Note You can still back up your account to a file.
• You cannot import your account to another computer by using the multiple computers function to store the account on groove.net.
  
  Note You can still perform this task manually by using a saved account file.
• You cannot use the Passphrase Rest feature.
• There is no automatic detection of the available Groove component updates.
• You cannot send e-mail invitations without using Microsoft Outlook.
• You cannot audit managed devices.

Instead of trying to start Groove while the firewall is inactive, use the information in the following Microsoft Knowledge Base articles:

For more information about how to use Groove through a firewall, click the following article number to view the article in the Microsoft Knowledge Base: For more information about to start Groove, click the following article number to view the article in the Microsoft Knowledge Base: