Q. Will this product work in a Citrix or
Terminal server environment?
A. Yes. There are a few things to watch out for:
1. You must not nor have ever installed Outlook Exchange
and Exchange Server on the same machine.
2. There may be an issue with the exchange system
manager tools on the server.
3. Boxes locked down to the point that Outlook Profiler
will not run.
4. With Outlook Exchange as a published app you must
call Outlook Profiler through a batch file. In other
words publish a batch file that calls Outlook Profiler.
5. Corrupted installations of Outlook. Be sure and test
for the fix listed below. |
| |
Q. Why does Outlook Profiler exit almost
immediately and does not write to the log file when I
have logging enabled?
A. To verify this issue, 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 article:
http://support.microsoft.com/?id=820865 |
| |
Q. I only want to change or modify the
exchange server name. How?
A. Edit the "profiler.ini" manually and set the
"ModifyExchangeServerNameOnly=1" key. Please note that a
more sophisticated utility is available for this that
also corrects additional mailboxes that the profile may
have access to (exchange server exchange profile update
tool). Please contact support for this utility. |
| |
Q. Can I use %username% for a signature
file?.
A. Yes. Create your signature files using Peditor.exe
naming them the username you want. Next edit
"profiler.ini" file manually and set
"SignatureNewMessages" or "SignatureRepliesForwards" to
"%username%". Please note that Outlook 2003 uses a
different ini file entry. See the "Technical
Information" information in the help file for details. |
| |
Q. How do I set "Show this folder as an
e-mail Address Book" for my contacts folder?
A. This option is set automatically by Outlook itself
after connecting to the exchange server. Outlook
Profiler will not reset that check mark. Previous
versions of Outlook Profiler were resetting the Outlook
Address Book service. |
| |
Q. How do I start Outlook Profiler from a
login script? It is just reporting an error.
A. Outlook Profiler will not be able to verify who is
logged in until the login script has finished for
Windows 9x. To help accomplish this, first create a bat
file (we will call it profiler.bat) with the following
line in it:
\\Server\Share\profiler.exe
Then add the following at the very bottom of your login
script:
call \\Server\Share\profiler.bat
:END
For Windows 9x workstations , set the "Delay Start" to a
value that you suspect the user's desktop will be
available to Outlook Profiler. Create Outlook profile at
logon done! |
| |
Q. If Outlook Profiler is ran from a network
share they receive the following error: "The login did
not succeed, either because one or more of the
parameters to profile were invalid, or because there
were too many sessions open already."
A. This is because the OS being used is Windows 9x. Edit
the "Delay Start" option in the "profiler.ini" file to
be 4 seconds or greater. Now you can automate Outlook
profiles as with NT based systems. |
| |
Q. Will Outlook Profiler honor my ini file
when I upgrade to a new version?
A. No. |
| |
Q. Sometimes Outlook Profiler will generate
the error "can not set data for 001e3d0a" on Windows 95
workstations and on Windows 98 workstations it will
create a profile for 00a0a000a00a02223... Why?
A. This has been handled properly with 1.6.7. Useful
information however has been preserved below.
Windows 9x workstations may have up to four separate
passwords.
1. A "Windows login password" (this is not the Domain
login, this one is used to separate user's preferences)
2. Screen Saver Password
3. Microsoft network services password ( if using a
Microsoft Domain Controller )
4. Network services from other vendors password, such as
Novell.
The one causing these errors is the "Windows login
password". It creates an encrypted password cache file
in the Windows directory with a .PWL (username.pwl)
filename extension. The first time a user logs into
windows, a dialog box prompts them to create this
password, if they choose to leave both fields blank they
will never see it again ( unless the .pwl file gets
deleted ). However, if they enter a password in both
fields they will be prompted to enter this in each time
( in addition to the Domain password if on a network ).
Solution: Disable the "Windows login password".
Add this key to the Registry:
[HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Network]
"DisablePwdCaching"=hex:01,00,00,00 |
