Outlook Profiler 2.5 Series Instruction Manual

13 

Loading....

Loading....

Loading....

Loading....

Loading....

Full text

(1)

Outlook Profiler 2.5 Series

Instruction Manual

(2)

Contents

Installing Outlook Profiler . . . 3

Configuring Outlook Profiler . . . 4

Outlook Profiler specific options . . . 4

Manually editing the ini file . . . 6

Outlook Special options . . . 7

Outlook client specifics . . . 8

Deploying Outlook Profiler . . . 9

Citrix and Terminal server notes . . . 10

Technical Information . . . 11

(3)

Installing Outlook Profiler

Using the provided installer

Run setup.exe on any machine. The installer is a file extractor and does not make changes to the system. After successful extraction, using the product will consist of familiarizing yourself with four files: peditor.exe,

profiler.ini, profiler.exe, and profiler.key. Optionally, you may need to work with profiler.log until you get settings working as you wish.

After creating and customizing your profiler.ini file (explained in the Configuring Outlook Profiler section) you will need to copy the above mentioned files (except for peditor.exe) to a location accessible by your users. The files can be placed just about anywhere you wish. A public share for login scripts, local machine with registry key set to start automatically, linked from an Intranet web page, or carried about on a usb key.

File descriptions

Profiler.exe

Outlook Profiler program executable; profiler64.exe is for use with x64 versions of Outlook.

PEditor.exe

GUI tool for editing the profiler.ini file.

Profiler.key

License key file for profiler.exe. When you receive your license key from sales, create a blank profiler.key file and copy only the actual key text into the file. Place this file in the same directory that profiler.exe resides in.

Profiler.ini

Configuration file that profiler.exe reads. Place this file in the same directory that profiler.exe resides in. Optionally you may use a command line option to profiler.exe to load a custom ini or one that is located in a different directory.

(4)

Configuring Outlook Profiler

Execute peditor.exe and you will be presented with options for how Outlook Profiler reacts globally as well as options for each version of Outlook Exchange.

You must configure each version of Outlook Exchange separately. There are very few global Outlook Exchange options. Thus after configuring Outlook 2013's Exchange server name, do the same for Outlook 2003. You do not need to configure versions of Outlook that are not installed in your network.

Options that are grayed out are currently not developed or are mimicking the way Outlook Exchange grays out an option that is dependent upon another option. Options that are labeled Special are extensions to the Outlook screens that GOFF Concepts have added.

Outlook Profiler specific options

Delay Start

The number of seconds before Outlook Profiler should start creating the profile. If Outlook Profiler is being started from a login script then in very rare cases Outlook Profiler may try to create a profile before the Windows desktop has been created. Choose an estimated time when you suspect the last login script has executed and the desktop will be available as advised by Support.

Logging Enable

Measured in kilobytes. At the end of Outlook Profiler's execution it will check the size of the log file. If it exceeds the size specified it will clear the file contents.

Show Splash Screen

Displays a window letting the user know something is happening. Outlook Profiler will be completely invisible if disabled.

Profile name to create or modify

If Outlook Profiler has not determined (by another means) the profile name to use, then set this value to be the fall back profile name. If you know ahead of time that your environment has named profiles Outlook Default

then use that value here. It is recommend to standardized on %username%.

Modify Default Profile if found

For situations where the default profile name is unknown or not standard across the enterprise. Setting this option will ensure that the profile name the logged on user is most likely using gets modified.

Exit if profile was previously modified by Outlook Profiler

Exit if Outlook Profiler has ever successfully created or modified the profile.

Exit if logged on username identical to a profile name

(5)

Exit if any Profile is found

If any profile is found (HKEY_CURRENT) then Outlook Profiler will exit.

Recreate instead of modify profiles

When the name of the profile to use has been determined (or manually set); if this profile already exists it will be deleted first. Normally you should allow Outlook Profiler to modify profiles. Only recreate if your profiles are having problems.

Modify Exchange server name only

Causes Outlook Profiler to migrate the profile to the new Exchange server. This primarily means references to an OST file and Additional Mailboxes if present. In the case of the OST file, Profiler will attempt to create a new OST file named "MailboxName_ExchangeServerName.ost". If the Exchange server is unavailable or unauthenticated, the additional mailboxes will not be migrated.

Command line options for profiler.exe

The command line supports specifying custom ini and log file locations. Place quotes around any paths with spaces. Example: profiler.exe -i \\server\share\profiler.ini -l “\\server\share name\MyLog.log”

(6)

Manually editing the ini file

Using notepad (notepad2 or notepad++ recommended) or a similar text editing application you can change some values that peditor.exe will not show. Use care with the profiler.ini file as keys are case sensitive and values should not end in spaces etc.

AllowUserSettings

Allows for a comma separated list of existing ini options to be entered. These options will not be set by Outlook Profiler thus allowing the user to have their custom settings honored.

Example:

AllowUserSettings=ShowThisAddressListFirst,AlwaysCheckSpellingBeforeSending

PromptUsernamePassword

(7)

Outlook Special options

Outlook Profiler allows you to customize each version of Outlook Exchange client differently for maximum flexibility. Outlook Profiler functions like a snapshot tool in that once you configure your profiler.ini file and

profiler.exe reads that file then the Outlook Exchange client will be configured just that way. Because of this aspect there are special options within peditor.exe labeled Special.

Special options prevent or add controls to profiler.exe so that it works as expected. An example would be PST file handling. Since Outlook Profiler is a snapshot tool, if you unchecked Skip configuring PST files then Outlook Profiler would rip out PST file references if the user had any on their own making their Outlook look just like your profiler.ini file. This option comes enabled by default thus preventing Outlook Profiler from adding or removing PST file references.

Skip configuring PST files

Allow users to keep their PST file references and paths. Note that when Outlook Profiler removes a PST entry it does not delete the file itself.

Append PST entries only

PST files configured will be added to the profile if not present and any existing PST files the user's has configured will be preserved.

Remove PST entries

A comma separated list of full paths to PST files that should be removed from the profile.

Prompt if more than one profile exists

If another profile is found the user will be prompted to choose which one the next time Outlook is launched.

Ignore Signatures

If unchecked, Outlook Profiler will copy files residing in the SigSources/Outlook20** directory to the local PC and add the correct reference to Outlook Exchange to use these signature files. Files of the same name will be overwritten. Read the Outlook client specifics section of this document for ini format details. View the how to video on the website for additional information.

Skip configuring POP3 email accounts

This option along with the other skip types (HTTP, IMAP, etc) allow for users to have other services in their profile without you removing them.

(8)

Outlook client specifics

Outlook Profiler allows for easy management of all Outlook Exchange client versions in your company from one ini file. At the time of writing, Outlook 2013, 2010, 2007, 2003, XP, 2000, and 97 are supported. The following entries list technical issues and cases for different versions of Outlook Exchange.

Outlook 2013 - 2003

The ini file entry for Signatures is in the following format:

Signatures=AnAccountName,ASig4New,ASig4Reply,bEnable. The AnAccountName field will always be

Microsoft Exchange for standard environments if the Exchange service is present. For Outlook 2003 and older it is Microsoft Exchange Server. In the case of POP3 accounts it should be whatever you named the account as it appears in the More Settings dialog box.

Outlook 2013 - 2010

Outlook Profiler 2.4.0.4 and newer remove any existing Exchange services prior to adding or modifying. Only one Exchange service entry is supported.

Outlook 2013 - 2007

When configuring a POP or IMAP account, from the More Settings/Advanced Tab if a connection type of SSL is used Outlook Profiler will set the value to Auto.

Outlook 2003

Customer Feedback Options are set to No, I don't wish to participate. This prevents the icon asking for info from appearing in the system tray. There is no ini file option to change this.

– A Special option exists for Outlook 2003 named Default format for future PSTs. It allows you to control the type of PST file a user can create. Select which option you want pre-highlighted or removed

completely.

Outlook 2000

– After Outlook 2000 is installed for the first time, at least one profile needs to be created manually by a local administrator to set some system wide variables. If using Ghost Images or similar be sure

technicians have done this at least once.

– The first time Outlook 2000 is opened after profiler.exe has configured the profile the mailbox will show Mailbox - =%username% where %username% is their logged on name. This will correct itself the second time Outlook is opened.

(9)

Deploying Outlook Profiler

Outlook Profiler will manage all Outlook Exchange client installations in your network from one ini file. Simply place profiler.exe, profiler.ini, and profiler.key in a central location accessible to all your users. In the case of locked down directories, enable file level permissions on a blank profiler.log file.

Network login scripts

To run Outlook Profiler, network login scripts are easy.

VB script:

' Setup vb environment Dim objShell, objEnVar

Set objShell = CreateObject("WScript.Shell")

' Uncomment for XP Service Pack 2

' set objEnVar = objShell.Environment("PROCESS") ' objEnVar("SEE_MASK_NOZONECHECKS") = 1 ' run Outlook Profiler

objShell.Run "\\server\share\profiler.exe", 1, true ' Uncomment for XP Service Pack 2

' objEnVar.Remove("SEE_MASK_NOZONECHECKS") Set objEnVar = Nothing

Set objShell = Nothing

Batch:

If you want to use a batch script, first make a custom profiler.bat. Inside profiler.bat:

REM Only one line in profiler.bat … the path to Outlook Profiler \\server\share\profiler.exe

inside: login.bat

REM Use the call keyword and make this the last thing executed in login.bat call \\server\share\profiler.bat

(10)

Citrix and Terminal server notes

Outlook Profiler is the perfect compliment to this environment. However, there are few things to be aware of:

* Outlook Profiler will have trouble executing if the Exchange System Manager Tools are present.

* Ensure HKEY_CURRENT_USER sections of the registry are readable and writable by Outlook Profiler.

* With Outlook as a published app you must call Outlook Profiler through a batch file. Publish a batch file that calls (runs) Outlook Profiler then Outlook.

* Corrupted installations of Outlook Exchange or Microsoft Office. Be sure and test for the fix listed below.

* Outlook Profiler may exit almost immediately and not write to the log file. If this occurs create a profile manually. Open Outlook and if you are able to connect to your Exchange server then leave Outlook open for at least 30 seconds. If you see a dialog pop up then read this KB820865.

(11)

Technical information

Outlook Profiler makes use of the underlying MAPI subsystem. Below are some special things to be aware of.

Profiler.exe

* Outlook Profiler must connect to the Exchange server specified before it will create or update the profile. It uses the logged in user's network credentials to accomplish this task. For hosted Exchange or non-authenticated server scenarios some settings cannot be configured (Additional Mailboxes, Address Book, Default Store). * If the logged on user does not have a domain account or an Exchange account then Outlook Profiler may cause a login prompt asking for login, domain, and password. Outlook Profiler will attempt to close these prompts automatically.

* In some environments Outlook Profiler can not create the profile or add additional mailboxes unless the LegacyExchangeDN value is used. Download getmailboxes.exe from the product website to determine this value. It is formatted like: /o=DomanName/ou=first administrative group/cn=Recipients/cn=

%username%. You may also use Adsiedit or ADExplorer to retrieve this value. View the how to videos on the

website if you need additional information. When you have obtained the correct value set MailboxName= to this string.

* Setting the default store, configuring additional mailboxes, and setting address book properties can not be accomplished unless the Exchange server is present and authenticated.

* Outlook Profiler is only tested with Outlook 2013, Outlook 2010 SP2, Outlook 2007 SP3, Outlook 2003 SP3, and Outlook XP SP3.

* If Outlook is running while Outlook Profiler is executing, Outlook Profiler will attempt to close Outlook automatically. If this fails the profile will become corrupted.

* If ModifyExchangeServerNameOnly fails for any reason (no profile found to modify) a new profile will be created with settings from the ini file.

* GroupWise or Exchange System Manager tools must not be present on the machine running profiler.exe. * Windows 7 systems with WebDav (msonsext.dll) present are not supported.

(12)
(13)

WARNING 201

This warning occurs when Outlook Profiler cannot connect directly (via RPC) to the Exchange Server. It may safely be ignored under the following conditions.

Hosted Exchange

When using a hosted Exchange server (like Office365) ensure that Anonymous Authentication and Outlook Anywhere (aka Outlook over HTTP) settings have been set. Here is a sample configuration:

ExchangeServerName=ExchangeGUID@domain.com MailboxName=UPN@domain.com LogonNetworkSecurity=3 EncryptDataBetweenOutlookExchange=0 ConnectExchangeUsingHTTP=1 ConnectWithNetwork=1 ExchangeServerProxyName=outlook.office365.com ConnectUsingSSLOnly=1 MutuallyAuthenticateSessionSSL=1 PrincipalNameProxyServer=msstd:outlook.com AuthenticationConnectingExchangeProxy=0

To make Outlook Profiler get the ExchangeGUID (aka Personalized Server ID) set these ini values: AutoDiscoverURL=https://server/Autodiscover/Autodiscover.xml

AutoDiscoverEmail=UPN@domain.com AutoDiscoverPassword=password

Manually (or via scripting) get the ExchangGUID:

1. Run this command from the Exchange Management Shell:

Get-mailbox | ft ExchangeGUID,UserPrincipalName > guid_table.txt

2. Visit the following website:

https://testconnectivity.microsoft.com

3. With Outlook open right-click on the icon in the system tray while still holding down the left CTRL key. Choose "Test E-mail AutoConfiguration" then enter an email address. Leave everything else blank, and check only "Use AutoDiscover". In the Results tab, look for "Server”.

Non-authenticated user

For environments where the Exchange server is accessible (via RPC aka not hosted) but the logged on user still needs to supply a username and password, then make sure that EncryptDataBetweenOutlookExchange is set to

Figure

Updating...

References

  1. KB820865
Related subjects :