Outlook Profiler 2.6 Series Instruction Manual

Transcription

1 Outlook Profiler 2.6 Series Instruction Manual Copyright GOFF Concepts LLC. All rights reserved. GOFF Concepts assumes no responsibility for errors or omissions in this document; nor does GOFF Concepts make any commitment to update the information contained herein. * Other product and corporate names may be trademarks of other companies and are used only for explanation and to the owners benefit, without intent to infringe. Outlook Profiler Page 1

2 Contents Installing Outlook Profiler Configuring Outlook Profiler Outlook Profiler specific options Manually editing the ini file Outlook Special options Outlook client specifics Deploying Outlook Profiler Citrix and Terminal server notes Technical Information Warning Office365 and Hosted Exchange Outlook Profiler Page 2

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 with profiler.exe to load a custom ini or one that is located in a different directory. Outlook Profiler Page 3

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 Microsoft Outlook. You must configure each version of Outlook separately. There are very few global Outlook options. Thus after configuring Outlook 2016's Exchange server name, do the same for Outlook 2010 etc. 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 Exit when the logged on username is the same as an Outlook profile name. Outlook Profiler Page 4

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 Outlook Profiler Page 5

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 does 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 Only use this value on the advice from Support. AddEqualOnMailboxName Tries to find an exact match when two users have similar names, such as johna and johna2. If this causes issues in your environment there is no harm to disable this feature. Outlook Profiler Page 6

7 Outlook Special options Outlook Profiler allows you to customize each version of the Outlook 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 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 created 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 and thereby 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 accounts This option along with the other skip types (HTTP, IMAP, etc) allow for users to have other services in their profile without Profiler removing them. Outlook Profiler Page 7

8 Outlook client specifics Outlook Profiler allows for easy management of all Outlook client versions in your company from one ini file. At the time of writing, Outlook 2016, 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 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 Outlook Profiler and newer remove any existing Exchange services prior to adding or modifying. Only one Exchange service entry is supported. 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. Outlook Profiler Page 8

9 Deploying Outlook Profiler Outlook Profiler will manage all Outlook 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 :END Outlook Profiler Page 9

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 KB Outlook Profiler Page 10

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 tries to 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 so that they are not seen. * In some environments Outlook Profiler can not create the profile or add additional mailboxes unless the LegacyExchangeDN value is used. It is formatted like: /o=domanname/ou=first administrative group/cn=recipients/cn=%username%. You may 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 accessible and the user is logged on and already authenticated. * 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. Peditor.exe * After adding, removing, or editing a PST entry, the drop down list box for the delivery location will not show the changes. Close and reopen the current peditor.exe form in question to see the updated changes. * A POP3, IMAP, or HTTP account that does not have a PST entry will show the Deliver new mail to option with a MAILBOX prefix. Therefore, note that if you are adding an Internet account to a profile you should also add a PST file entry and set that as the default location for Outlook to open and work as expected. Outlook Profiler Page 11

12 WARNING 201 This warning occurs when Outlook Profiler cannot connect directly (via RPC) to the Exchange Server with Outlook 2013 and older clients. It may safely be ignored if you re using Hosted Exchange or the user is nonauthenticated and you re already aware of that. Things to consider. Non-authenticated user For environments where the Exchange server is accessible (via RPC and therefore not truly hosted) but the logged on user still needs to supply a username and password, then make sure that EncryptDataBetweenOutlookExchange is set to what the Exchange Server expects. For Exchange Server the default is an encrypted connection (EncryptDataBetweenOutlookExchange=1). Note that you may set LoginUsername to control what the user sees for their username. or \ symbol must be present (example: LoginUsername=user@domain). LegacyExchangeDN mismatching In some environments the LegacyExchangeDN (/o=domanname/ou=first administrative group/cn=recipients/cn=johndoe) string will not allow Outlook Profiler to connect correctly. Use Adsiedit or ADExplorer to retrieve this value (see video on website) and set MailboxName= to use whatever is actually set in AD. Make sure the string is correct if you used AD migration software. There are at least three ways of retrieving values from Office365 or Exchange without looking at AD or when AD is not in sync. 1. Run this command from the Exchange Management Shell: Get-mailbox ft ExchangeGUID,UserPrincipalName > guid_table.txt 2. Visiting the following website: 3. Using Outlook itself: With Outlook open, right-click on the icon in the system tray while still holding down the left CTRL key. Choose Test AutoConfiguration then enter an address. Leave everything else blank, and check only Use AutoDiscover. In the Results tab, look for Server or other data fields. Outlook Profiler Page 12

13 Office365 and Hosted Exchange Outlook Profiler can automatically create Outlook profiles that connect to Microsoft Office 365 and other hosted servers. Choose the method that best matches your environment. Active Directory option 1 If your AD environment has two way sync with Office 365, then this method is the simplest. The ExchangeGUID value is stored in AD and can therefore be accessed via Outlook Profiler. In some instances you can use the value outlook.office365.com in place of the actual ExchangeGUID. Need to know The ExchangeGUID is stored as msexchmailboxguid. It will be present when using an on premises Exchange server or when two way sync with Office 365 has been preformed. You will use the ExchangeGUID combined with the domain to create the Personalized Server ID. A suitable Mailbox name value can be found in more than one AD location. Sometimes the environment variable %username% when expanded by the PC, might match the mailnickname (Exchange Alias), and can be used. Failing that, try Mail, userprincipalname, or LegacyExchangeDN. Step 1: Edit the profiler.ini file and set ReadActiveDirectory=1. Leave GetActiveDirectory set to the defaults. Step 2: Set the ExchangeGUID and Mailbox name. Try setting ExchangeServerName=outlook.office365.com first. Failing that, use msexchmailboxguid as shown. ExchangeServerName=%AD_msExchMailboxGuid%@domain.com MailboxName=%AD_userPrincipalName% Step 3: Enable Anonymous Authentication and Outlook Anywhere (aka Outlook over HTTP) like so: EncryptDataBetweenOutlookExchange=0 LogonNetworkSecurity=3 ConnectExchangeUsingHTTP=1 ConnectWithNetwork=1 ExchangeServerProxyName=outlook.office365.com ConnectUsingSSLOnly=1 MutuallyAuthenticateSessionSSL=1 PrincipalNameProxyServer=msstd:outlook.com AuthenticationConnectingExchangeProxy=0 Note: Sometimes you must set MailboxName to be %AD_Mail% or try %AD_LegacyExchangeDN%. Use whatever works in your environment. For Outlook 2016, ExchangeServerName can be set to AUTO. Outlook Profiler Page 13

14 Exchange remote PowerShell option 2 When AD does not have the information you need, you can run a PowerShell script that provides all the necessary information to create a profile for Office 365. The output can be stored in a CSV file and then you can store them in AD to be read by Outlook Profiler. Need to know The ExchangeGUID and LegacyExchangeDN values are the ones necessary to create a functioning profile using this method. Step 1: running the PowerShell commands From a Windows 7/8/10 workstation run PowerShell as administrator and execute the following commands. You ll be prompted for your Office 365 credentials. Note, it will take several minutes to download all the mailbox information depending on the speed of your network. When the script is finished it will output a CSV mailbox.txt file in the current directory. Step 2: Add the values from the mailbox.txt file to your local Active Directory. Edit profiler.ini and set ReadActiveDirectory=1. Step 3: Set the ExchangeGUID and Mailbox name. Try setting ExchangeServerName=outlook.office365.com first. Failing that, use msexchmailboxguid as shown. ExchangeServerName=%AD_msExchMailboxGuid%@domain.com MailboxName=%AD_LegacyExchangeDN% Step 4: Enable Anonymous Authentication and Outlook Anywhere (aka Outlook over HTTP) like so: EncryptDataBetweenOutlookExchange=0 LogonNetworkSecurity=3 ConnectExchangeUsingHTTP=1 ConnectWithNetwork=1 ExchangeServerProxyName=outlook.office365.com ConnectUsingSSLOnly=1 MutuallyAuthenticateSessionSSL=1 PrincipalNameProxyServer=msstd:outlook.com AuthenticationConnectingExchangeProxy=0 Note: Since Office 365 profiles are usually remotely connected and thus the user is not pre-authenticated, you may optionally set the user name field the user will see when opening Outlook like so: LoginUsername= %AD_userPrincipalName%. Outlook Profiler Page 14

15 AutoDiscover client inside Outlook Profiler option 3 This is not a recommended option for production. However, it can be useful for debugging the environment since Outlook Profiler itself can query AutoDiscover natively. Need to know The AutoDiscover server developed by Microsoft is a redirecting, password restricted Web service that replies in XML when the final endpoint is found. The AutoDiscover client inside of Outlook Profiler therefore passes the username and password using HTTP digest protocol over an SSL connection. The Profiler client handles the low level details, however, you do need to specify the correct endpoint. Step 1: Finding the correct AutoDiscover URL Visit the testconnectivity.microsoft.com URL. Select the Office 365 tab. Then choose the Outlook Autodiscover option. Enter an address and Microsoft Account. They are probably the same value. After filling out the password, click Perform Test. When the test is complete, click Expand All. There is a lot of data shown, however, search the page for " The actual url will be something like: Step 2: editing the profiler.ini file Edit the profiler.ini file and set ReadActiveDirectory=1. Set the AutoDiscover URL you found above: AutoDiscoverURL= Next, you need to set the ini AutoDiscover = value. You could use something like %username %@domain.com or %AD_userPrincipalName%. Step 3: Set the ini AutoDiscover = value to something like %AD_userPrincipalName% or %username %@domain.com. Step 4: Set the ini AutoDiscoverPassword= value to the user's password. Prompt the user for it if necessary. Step 5: Enable Anonymous Authentication and Outlook Anywhere (aka Outlook over HTTP) like so: EncryptDataBetweenOutlookExchange=0 LogonNetworkSecurity=3 ConnectExchangeUsingHTTP=1 ConnectWithNetwork=1 ExchangeServerProxyName=outlook.office365.com ConnectUsingSSLOnly=1 MutuallyAuthenticateSessionSSL=1 PrincipalNameProxyServer=msstd:outlook.com AuthenticationConnectingExchangeProxy=0 Outlook Profiler Page 15