ShareFile Dashboard

Admin or Employee Dashboard

User-added image

What’s New Notifications – Useful tips and recent product news will be displayed here. You may close these alerts.

Recent Files – Five recently accessed files will be displayed here.

Share Files and Request Files – If you are an Employee user with access to the File Box, Share and Request buttons will be available here. Users without File Box access can only use Share and Request files on files and folders already uploaded to the ShareFile account.

Create New User – If you have permission to manage employee and/or client users, you can use this button to create new users on the account. Click here for more information on creating users.

Quick Jump To – This menu will display shortcuts to your Personal Folders, Shared Folders, Favorites, and What’s New notifications. If you do not have access to Personal Folders, that option will be missing.

Tutorials and Helpful Links – This menu displays useful videos and support articles for managing and using your ShareFile account. Use the drop-down to view different content.

Client Dashboard

Clients users will also receive a modified version of the Dashboard – clients can only view the following Dashboard menus: Welcome, Recent Files, Quick Jump To Shared Folders, and Favorites.

Click to view higher resolution

User-added image

Profile Picture

You can upload an avatar to customize your account. Your avatar will appear in the Dashboard, as well as in any Address Book or user list within the ShareFile web application.

You can upload a picture at the Dashboard, or in your Personal Settings > Edit Profile menu.

Note – Very large profile pictures will be downsized to fit automatically.

User-added image


Customize the Dashboard

Use the Edit Dashboard button to turn certain Dashboard components on or off. (Currently, this can only be done on a user-by-user basis, and cannot be applied to the entire account or to other users.)

User-added image


To move or reposition a Dashboard pane, click and hold near the section Title and drag the pane to the desired location.

Note: Changes to Dashboard tile placement are cache-based and not persistent across browsers.

User-added image

Dashboard Tutorials and Permissions

The Tutorials module is dynamic and will adjust according to your user permissions. Links and videos related to features or functions that you do not have permissions for will not be shown.

In the screenshot below, you can see the difference between a user with permission to manage employees and access account-wide settings, and a user without.

User-added image

Related:

7014745: Sending TNEF/Rich-Text appointments from Exchange to GroupWise

Checking Exchange Administrative TNEF/Rich-Text settings :

Having said this, some ways you can check/configure if Exchange 2010 TNEF/Rich-Text is set as “ENABLED” for outgoing messages to remote domains or GroupWise contacts :

In the Exchange Management Console, under the “Organization Configuration”, Hub Transport, Remote Domains tab, Both Default and GroupWise, Message Format tab, “Exchange rich-text format” section. If the setting is set to “Always use”, you will have the problem described in this document. If this setting is listed as “Never use”, you should not have this issue, unless something else in Exchange or Outlook is overriding this setting. If the setting is “Determined by individual user settings”, then the Outlook SENDER will determine if TNEF/Rich-Text is used for the outgoing message or appointment.

Another location in the Exchange Management Console to check for this setting is :

Under the “Recipient Configuration”, Mail Contact, “Properties” of individually synchronized or configured external GroupWise users, “Use MAPI rich text format”, can be set to “Never”, “Always”, “Use Default Settings”. These latter 3 settings have the same meaning as described above.

*** NOTE: For Exchange 2013 (or Exchange 2010) Administrative changes for TNEF/Rich-Text settings: ***

With the new version of Exchange, version 2013, this type of attribute change for remote domain contacts (like GroupWise users), can only be made in the Exchange Powershell command line interface. If you have created an Exchange remote domain, that represents a GroupWise system , and have created remote domain contacts in your Exchange Admin Center Web site, and if you are experiencing the issue described in this document, you can disable TNEF/Rich-Text, and resolve this issue, by issuing these powershell commands:

** Note: These below commands also happen to work for Exchange 2010. **

Set-RemoteDomain -Identity <yourRemoteDomainName> -TNEFEnabled $false

Restart-Service MsExchangeTransport

To check if this setting took place, you can execute this powershell command:
Get-RemoteDomain -Identity <yourRemoteDomainName> | Select TNEFEnabled

OR

If you don’t want to change this setting for an entire remote domain level, you can change this TNEF/Rich-Text setting at an individual remote domain contact level by this command, but be aware if the remote domain contacts are ALL GroupWise users, then it makes more sense to use the above listed command to change this setting at a remote domain level :

Set-MailContact “<FirstNameOfContact> <LastNameOfContact>” –UseMapiRichTextFormat Never

To check the existing setting for this attribute for remote domain contacts or to check if the setting took place issue the command :

Get-MailContact “<FirstNameOfContact”> <LastNameOfContact>” | where {$_.UseMapiRichTextFormat –eq “never”}

*******************************************************************

Checking Outlook client TNEF/Rich-Text settings :

How to Control TNEF in Messages

You can control TNEF by three methods:

Global – If you change your default e-mail format to plain text or Hypertext Markup Language (HTML), it helps to make sure that TNEF is not sent unless an Outlook feature needs it.

Per Recipient – You can specify in the recipient’s e-mail address to not send TNEF so that a recipient always receives plain text versions of the message.

Per Message – When you compose a new message, or replying to a received message.

Method 1: How to make a Global Change for TNEF

For Microsoft Outlook 2010 and Outlook 2013:

To turn off TNEF, follow these steps:
1. Click the File tab, click Options, and then click Mail.
2. In the Compose in this message format list, click Plain Text or HTML, and then click OK.

For Microsoft Office Outlook 2007:

Follow these steps to turn off TNEF:

1. On the Tools menu, click Options, click the Mail Format tab.
2. In the Compose in this message format list, click Plain Text or HTML, and then click OK.

For Microsoft Office Outlook 2003 and earlier versions of Outlook:

Follow these steps to turn off TNEF:

1. On the Tools menu, click Options, and then click the Mail Format tab.
2. In the Send in this message format list, click Plain Text or HTML, and then click OK.

Method 2: How to make a Per Recipient Change for TNEF
For Outlook 2010:

In the Contacts Folder:

To turn off TNEF, follow these steps:

1. Open the recipient’s record in the Contacts folder.
2. Double-click the recipient’s email address.
3. The Contact Card appears. Click View more options for interacting with this persona, and then click Outlook properties.
Choose Send Plain Text only in the Internet Format list.

For Outlook 2007 and earlier versions:

In the Contacts Folder

Follow these steps to turn off TNEF:

1. Open the recipient’s record in the Contacts folder.
2. Double-click the recipient’s e-mail address.
3. Choose Send Plain Text only in the Internet Format box.

In the Personal Address Book

Note Personal Address Books (.pab) can no longer be created or used in Outlook 2007.

Use the following steps to turn off TNEF:

1. Locate the recipient in the Personal Address Book.
2. Double-click the recipient’s e-mail address.
3. Click to clear the Always send to this recipient in Microsoft Exchange Rich Text Format check box, and then click OK.

Method 3: How to make a Per message change for TNEF

For Outlook 2010 and Outlook 2013:

To turn off TNEF, follow these steps:

1. Open a new mail message, or click Reply on a received message.
2. On the Format Text tab, click HTML or Plain Text.

For Outlook 2007:

Use the following steps to turn off TNEF:

1. Open a new mail message, or click Reply on a received message.
2. On the Options tab, click HTML or Plain Text.

For Outlook 2003 and earlier versions of Outlook:

Use the following steps to turn off TNEF.

1. Open a New mail message, or click Reply on a recently received message.
2. On the Mail Format toolbar, click to select Plain Text or HTML from the dropdown menu.

One last comment:
Some customers wonder when 1 single iCAL meeting request in Outlook is SENT to say 10 GroupWise recipients, yet 5 will see the problem and 5 will not see this problem. How could this be ?, should they all see the problem or all not see the problem if the Outlook user sent 1 meeting request ? :

Answer:
When Exchange encodes and sends out the iCAL appointment, it is not just sending 1 mime message that represents the iCAL appointment, it sends multiple mime messages based in part on the individual recipient TNEF/Rich-Text configuration settings noted above. 5 GroupWise users could be configured to send rich-text and 5 other GroupWise users could be configured to send out with no rich-text.

Related:

7022537: GAL never syncs to GMS

This document (7022537) is provided subject to the disclaimer at the end of this document.

Environment


GroupWise Mobility Service 2014 R2 Support Pack 1

Situation

Add users to the GroupWise system and the Global Address List never updates on GMS therefore you cannot add the user to GMS.

Resolution

1. Login to the GroupWise Admin Console

2. Go to the Post Office that contains the GMS Address Book User

3. Go to the Settings tab

4. Ensure that Create Deltas is enabled under the Address Book Update Settings section

Additional Information


On the GMS server in the groupwise-agent.log file you will see the address book sync process start, but the “lastSequence” number never increments.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7019079: Using LDAP to Login to RetainServer When GroupWise No Longer Installed

You can use LDAP to eDirectory. Here are the steps:

1. Configure LDAP authentication in the GroupWise module inside the RetainServer admin UI.

2. Go to the Management menu in the RetainServer navigation pane and select “Groups“. Edit the “default” group and set the “Authentication Method” to “LDAP authentication (GW)” and mark the box, “Use Exclusively“.

2. Edit …/RetainServer/WEB-INF/classes/config/misc.properties.

3. Search for “custom.ldap.enable“, which should take you down to the bottom section of the file.

4. Edit the following lines to read as follows:

custom.ldap.enable=1

custom.ldap.attributes.requested=mail

custom.ldap.attributes.bind=email

custom.ldap.debug=1

custom.ldap.class=com.gwava.authenticate.gw.AlternativeGWLDAPAuthentication

5.Restart Tomcat.

NOTE: User then must login to RetainServer using their full GroupWise email address (user@domain.com). For example, jdoe@xyzcompany.com.



Custom LDAP Settings Explained

Many of these settings cannot be used. They are there for use in the future when this feature is more fully developed. Features for future use that do not offer any functionality or if not fully understood are greyed out.

custom.ldap.enable= 0 | 1 (default = 0).

When set to 0 (default), Retain follows the normal GWLDAP Authentication path (where GroupWise is installed and running) and ignores the custom.ldap settings below.

Set to 1 to enable

custom.ldap.class=[className] (default = com.gwava.authenticate.gw.CustomLDAPAuthenticatorMethod).

The class of the modified java code. Keep it at the default.

custom.ldap.search=[LDAPQuery, using as placeholder for future]

Default is (&(objectClass=Person)(mail=)) Changing this for initial release is not supported.

DO NOT ENTER

custom.ldap.useuid=0 | 1 (default = 0).

If on, expects to have a UID entry. Otherwise currently expects to see an email entry in LDAP.

The name of the attribute is specified and bound elsewhere.

Set to 0.

custom.ldap.applicationuid=0 | 1 (default = 0).

Use if you are supplying an application UID not an internalUID.

It only matters when custom.ldap.useuid=1.

Set to 0.

custom.ldap.emailsystem=gw | exchange | etc (default = gw).

The type of messaging system this applies to. Initially only gw is supported.

Leave it at the default of “gw”.

custom.ldap.attributes.requested=[comma delimited list] (default = mail)

This is a list of LDAP attributes you want requested. It is the user object’s LDAP attribute name from eDirectory (and future, Active Directory, and others).

Case may matter depending on the LDAP server. For a standard GroupWise system, this is GUID, mail,or nGWObjectID. The mail attribute returns the user’s Internet email address.

If requesting multiple attributes, list them in a single line separated by commas with no spaces between the attribute names and the commas (i.e., mail,nGWObjectID).

Recommended to leave at the default of mail.

custom.ldap.attributes.bind=[comma delimited list] (default = email)

This is a list of Retain address book attributes. These attributes correspond with actual field names in the Retain database’s t_abook field. Any one of the following can be listed and they are case sensitive:

This list must be exactly the same number of attributes as listed in the custom.ldap.attributes.requested and needs to be in the order in which you want each attribute to match. For both attributes (LDAP and Retain), the value in the attribute listed in the first position should match the value in the other attribute. Each item in ..attributes.bind maps to the LDAP attribute specified in ..attributes.requested, meaning that Retain will try to match what is returned from the custom.ldap.attributes.requested list with the custom.ldap.attributes.bind list; thus, they should also be in the order in which they should be mapped. If you want the LDAP attribute of mail to map to the Retain attribute of email, they both should be listed at the first item in their respective lists.

EXAMPLE:

If custom.ldap.attributes.requested reads has mail,nGWobjectID, then the custom.ldap.attributes.bind line must read email,mailbox in that order so that mail maps to email and nGWobjectID maps to mailbox. If those values do not match, this will not work; thus, if John Doe’s Internet email address (mail attribute) were jdoe@xyzcompany.com, then the Retain database’s email attribute should also read jdoe@xyzcompany.com or else it will not be able to make a match. Likewise, if nGWobjectID were “jdoe”, then the Retain database’s mailbox attribute better have “jdoe”.

Recommended to leave at the default of email.

custom.ldap.debug=0 | 1 (default = 0)

Set to “1” to generate more diagnostic logging in the RetainServer log.

Related:

Too many New View Container name collisions. View will not be created.

Details
Product: Exchange
Event ID: 1269
Source: MSExchangeSRS
Version: 6.0
Component: Site Replication Service
Symbolic Name: DIRLOG_ORG_TOO_MANY_COLLISIONS
Message: Too many New View Container name collisions. View will not be created.
   
Explanation
The Address Book view could not create a unique relative distinguished name after 100 attempts.
   
User Action
Delete the parent Address Book view container, and then rebuild it.

Related:

Entry ‘%1’ has invalid or expired e-mail certificates. These certificates will not be included in the offline address list for ‘%2’. – %3

Details
Product: Exchange
Event ID: 9323
Source: MSExchangeAdmin
Version: 6.5.7596.0
Message: Entry ‘%1’ has invalid or expired e-mail certificates. These certificates will not be included in the offline address list for ‘%2’. – %3
   
Explanation

This Warning event occurs if the Microsoft® Exchange System Attendant (MSExchangeSA) discovers an invalid or expired certificate when it tries to generate an offline address list.

You can deploy certificates to users to enable them send and receive digitally signed or encrypted e-mail messages. The certificates that are specified in the event description section will not be included in the offline address list.

   
User Action

To resolve this problem, renew or remove the expired certificate. To do this, follow these steps:

  1. Start Exchange System Manager, expand Recipients, and then click the All Global Address Lists container.

  2. In the details pane, right-click the address list that is mentioned in Event 9323. For example, right-click Default Global Address List.

  3. Click Properties.

  4. On the General tab, click Preview.

  5. Locate and then double-click the affected user account that is mentioned in Event 9323.

  6. Click the Published Certificates tab.

  7. Locate and then select any expired certificate, and then click Remove. To view detailed information about the certificate, click View Certificate.

  8. Click OK, and then close the Address List Preview dialog box.

  9. If the users require new or updated certificates from Active Directory, configure Certificate Autoenrollment for Exchange Server certificates. For more information, see Certificate Autoenrollment in Windows Server 2003.

For more information about how Exchange handles certificates when it generates an offline address book, see the Exchange Server Team Blog article OAB certificate filtering.

The content of each blog and its URL are subject to change without notice. The content within each blog is provided “AS IS” with no warranties, and confers no rights. Use of included script samples or code is subject to the terms specified in the Microsoft Terms of Use.

Related:

No Personal Address Book entries were migrated for user ‘{user name}’.

Details
Product: Exchange
Event ID: 1055
Source: MSExchangeMig
Version: 6.0
Component: Migration Wizard
Symbolic Name: CCMAIL_EXPORT_BADPARAMS_PAB_WARN
Message: No Personal Address Book entries were migrated for user ‘{user name}’.
   
Explanation
Personal Address Books (PABs) were available for cc:Mail users after version 8.3. The user may not have a PAB, or the address book could not be migrated.
   
User Action
If the user does have a PAB, verify that the installed version of Export.exe utility supports the /PAB command-line switch.If the user does not have a PAB, this message can be ignored.

Related:

OALGen encountered error %1 while initializing the offline address list generation process. No offline address lists have been generated. Please check the event log for more information. %2

Details
Product: Exchange
Event ID: 9334
Source: MSExchangeAdmin
Version: 6.5.7596.0
Message: OALGen encountered error %1 while initializing the offline address list generation process. No offline address lists have been generated. Please check the event log for more information. %2
   
Explanation

This Error event indicates that OALGen experienced a specific error when initializing the offline address list generation process. Your clients will not be able to download offline address lists until you resolve this problem. This Error event can occur after you install Microsoft® Exchange Server 2003 Service Pack 1 (SP1).

An event that relates to MSExchangeSA event 9334 is MSExchangeSA event 9330. MSExchange SA event 9330 indicates that OALGen cannot connect to Active Directory®. OALGen must be able to connect to Active Directory to generate offline address lists.

   
User Action

For information about how to resolve MSExchangeSA event 9334 and MSExchangeSA event 9330, see Microsoft Knowledge Base article 905802, Event IDs 9334, 9330, and 9175 are logged when you try to generate an offline address book after you install Exchange Server 2003 Service Pack 1.

For information about troubleshooting offline address book issues, see the TechNet Support WebCast, How to troubleshoot Offline Address Book issues in Microsoft Exchange Server.

You can use the Offline Address Book Integrity (OABInteg) tool to troubleshoot offline address list problems. For information about how to use the OABInteg tool, see Microsoft Knowledge Base article 907792, Description of the Offline Address Book Integrity (OABInteg) tool.

For best practices for administering offline address lists, see Offline Address Book Best Practices Guide.

Related:

OALGen skipped some entries in the offline address list ‘%1’. To see which entries are affected, event logging for the OAL Generator must be set to at least medium.- %2

Details
Product: Exchange
Event ID: 9327
Source: MSExchangeSA
Version: 6.5.7596.0
Message: OALGen skipped some entries in the offline address list ‘%1’. To see which entries are affected, event logging for the OAL Generator must be set to at least medium.- %2
   
Explanation

This Warning event is logged when Microsoft® Exchange Server cannot download one or more entries of an offline address list. You can learn more about the root cause of this error by examining the Application log for related events.

   
User Action

To resolve this error, do one or more of the following:

  • Increase diagnostic logging, and then examine the event log for MSExchangeSA events that are logged before and after MSExchangeSA event 9327.

    To increase diagnostic logging:

    1. In Exchange System Manager, double-click Servers, right-click a server, and then click Properties.

    2. On the Diagnostic Logging tab, under Services, select MSExchangeSA.

    3. In Categories, click OAL Generator.

    4. In Logging level, select Maximum.

  • Use the Offline Address Book Integrity (OABInteg) tool to diagnose and resolve generation issues. Active Directory®-related issues, such as replication problems, latency, and stale information, can frequently cause the OAB file generation process to fail. You can use the OABInteg tool to scan Active Directory for these types of issues. For information about how to use the OABInteg tool, see Microsoft Knowledge Base article 907792, Description of the Offline Address Book Integrity (OABInteg) tool.

For more information about troubleshooting offline address book issues, see the TechNet Support WebCast, How to troubleshoot Offline Address Book issues in Microsoft Exchange Server.

For best practices for administering offline address lists, see Offline Address Book Best Practices Guide.

Related:

Couldn’t build the Address Book hierarchy table. Will try to rebuild the hierarchy table again in %1 minutes.

Details
Product: Windows Operating System
Event ID: 1161
Source: Active Directory
Version: 5.0
Symbolic Name: DIRLOG_BUILD_HIERARCHY_TABLE_FAILED
Message: Couldn’t build the Address Book hierarchy table. Will try to rebuild the hierarchy table again in %1 minutes.
   
Explanation

Active Directory could not build the Address Book hierarchy table. The next attempt will occur after the specified time has elapsed. Address Book searches will be disabled on this domain controller during this interval. Attempts to build the Address Book hierarchy table will continue until the task is completed.

   
User Action

No user action is required.

Related: