NOTE: This steps are to be performed by the
administrator from a workstation having access
to network folders.
What you need?
- The Attachment
Manager Admin tool, namely, AssistMyTeam.AttachmentManagerAdmin.exe
which is made available to Enterprise
license holders. If you don't have it,
- A network attachments repository
- Another network shared folder
for storing the pre-configured settings XML
file e.g., \\Server\Deployment
Extract the AssistMyTeam.AttachmentManagerAdmin.exe
application that you had received as part of
your Enterprise license to a local disk in your
system. We recommend that you place this file in
a permanent location for future use (in the case
that you want to modify the pre-configured
settings in later date). You can create a
shortcut to this .exe to your desktop for quick
As this is the first time running this tool on
your system, it will show you the 'New
Settings' dialog option. Here, you can
choose to start with a new settings or connect
to or load an existing setting XML file (AttachmentManagerSettingsInfo.xml).
Choose 'New Settings' option and click
Enter your enterprise license to authenticate.
Only when the authentication succeeds, the tool
will allow you to perform the pre-configuration
of the settings for all users.
Step 4. Configure the team
settings that would be pushed to all
systems on the network.
a) Single Global file folder (Network
Folder) to store all the detached
Specify a global network
folder that will act as the root for storing all
detached files. It is very important that this
folder path be accessible to all users on the
network. If required, adequate permissions must
be granted for each user on this folder such
that the add-in can create new subfolder or place
new files into the chosen network folder. E.g.,
pre-configured setting is pushed to every system
on your office network, the Attachment Manager
add-in of each user will create new subfolders
beneath the root network folder having the name
of the user. For example, if the user of the
system is 'Monica Lewis', a new subfolder
'\\Server\Attachments\Monica Lewis' would be created
automatically and any detached attachments by
that user would be stored on this particular
b) Follow Outlook
If this option is enabled,
the add-in will output the
detached files into subfolders similar to
hierarchical ordering of the Outlook folder. For
instance, if the
email is located in the personal Inbox
(MonicaLewis@assistmyteam.local > Inbox)
attachments from that email will
be detached to folder path
Such dynamism provides for an organized way of
storing and filing attachments in subfolders
which is easier to navigate, find and access
files quickly and intuitively.
For example, here is a screenshot of an
email in Inbox (MonicaLewis@assistmyteam.local > Inbox)
after detaching the attachments:
And here is the screenshot of the folder
hierarchy that is dynamically created by
the add-in to store the detached files.
c) Allow user to define custom file
repository folder for individual Outlook
If this option is enabled,
the add-in will provide
individual user with support for
specifying a separate attachment folder
for each Outlook folder, even if the
administrator had pushed a
pre-configured Network folder folder.
This allows for the user to specify a
local folder to detach the attachments
from emails for a particular Outlook
folder, bypassing the admin's choice.
this option is disabled, user will not
be able to change the destination folder
and instead will continue to use the
admin specified network folder.
d) Overwrite Policy.
You can choose what kind of
overwrite policy would the add-in follow
when it encounters that the detached
file already existed in the particular
network folder. By default, the 3rd
option 'Keep the Original file and
using random numbers to the original
name, generate a new unique file' is
e) For deploying
settings to other systems on the
This is the network folder path
where the admin preconfigured settings
and enterprise license are stored in the
form of a XML file 'AttachmentManagerSettingsInfo.xml'.
And the installation setup file 'AttachmentManagerSetup.exe'
for Attachment Manager should be placed
in the same folder as this XML file for
pushing the pre-configured settings and
license to other systems. This means,
individual user needs to run the 'AttachmentManagerSetup.exe'
directly from this network folder to
install Attachment Manager add-in to
their respective system. And only this
way, the pre-configured settings and
license set by the administrator will be
inherited to the local system
automatically without any additional
you can also distribute the setup.exe
along with the XML file (say in a zip
file) to each user. And user can then
extract both these files to a local
folder and the run the setup to install
Attachment Manager on his/her system.
And this technique will also apply the
admin pre-configured settings and
license to that system automatically.
In a nutshell,
as long as the setup.exe can access the
XML file 'AttachmentManagerSettingsInfo.xml'
in the same directory, the
pre-configured settings/license would be
pushed to the current machine
automatically when the add-in is
What if the
user had already installed Attachment
Manager add-in without the presence of 'AttachmentManagerSettingsInfo.xml'?
In this case, the user needs to go
Outlook > Attachment Manager toolbar >
Settings panel > Others tab, and
feed the direct UNC network path of the
Doing so, the add-in would inherit and
apply the pre-configured
settings/license to the local system.
This is how the
settings panel on the user's Attachment
Manager add-in would like when the
pre-configured settings and license is
pushed to other systems:
once the pre-configured settings are
applied to the Attachment Manager add-in
installed on the local system, the user
can't change or overwrite those settings
from the settings panel. This way,
administrator can make sure the
Attachment Manager add-ins on all
systems behave and operate in the same
You will find
additional settings under the 'Naming
Scheme' and 'Extensions' tabs
that you can configure and push to other