Other members of your domain do not consider your managed domain identity to be trusted in Groove (915628)


The information in this article applies to:

  • Groove Enterprise Management Server 2.0
  • Groove Enterprise Management Server 2.1
  • Groove Enterprise Management Server 2.5
  • Groove Enterprise Management Server 3.0
  • Groove Enterprise Management Server 3.1
  • Groove Workspace 2.5 Preview Edition
  • Groove Workspace 2.5 Professional Edition
  • Groove Workspace 2.5 Project Edition
  • Groove Workspace 2.5 Standard Edition
  • Groove Virtual Office 3.0 File Sharing Edition
  • Groove Virtual Office 3.0 Professional Edition
  • Groove Virtual Office 3.0 Project Edition
  • Groove Virtual Office 3.0 Trial Edition
  • Groove Virtual Office 3.1 File Sharing Edition
  • Groove Virtual Office 3.1 Professional Edition
  • Groove Virtual Office 3.1 Project Edition
  • Groove Virtual Office 3.1 Trial Edition

SYMPTOMS

Other members of your Groove domain do not consider your managed domain identity to be trusted in Groove Workspace or in Groove Virtual Office.

CAUSE

This issue occurs when one of the following conditions is true:
  • You set the listing for the local network directory to something other than All Contact Information or Full vCard. In this case, other Groove clients cannot examine the vCard to display a trust icon.
  • Your identity information contains certain strings that are reserved for use as vCard labels. In this case, Groove cannot process the identity information to determine that your identity is trusted.

RESOLUTION

To resolve this issue, change the listing option, or remove the invalid strings from the identity information.

MORE INFORMATION

The strings that you cannot use in an identity field are as follows:
  • ADR
  • BEGIN
  • E-mail
  • END
  • FAX
  • FN
  • HOME
  • INTERNET
  • N
  • PAGER
  • PREF
  • ORG
  • POSTAL
  • TEL
  • TITLE
  • URL
  • VCARD
  • VERSION
  • VOICE
  • WORK
Note These labels are case sensitive. Therefore, you can use lowercase and mixed-case versions of these strings. Additionally, strings that contain these strings do not cause the issue. For example, both "Home" and "Number" are permissible strings.
Modification Type:MajorLast Reviewed:6/9/2006
Keywords:kbprb kbExpertiseInter kbtshoot KB915628 kbAudKnowledgeWorker
©2004 Microsoft Corporation. All rights reserved.