To recall a message in Outlook 2007:
. Click the Sent message folder.
. Open the message you want to recall.
. On the Message tab, in the Actions group, click Other Actions.
. Click Recall This Message.
. Click Delete unread copies of this message.
. Click OK.
This feature only available on Exchange as an email server and Outlook 2007 as a client and through MAPI connection.
Comments rss
TrackbackWhen you want to give the Domino server a new identity and then (optionally) change it back to its original identity, follow the steps below.
| Part 1: Give an existing Domino server a new identity |
1) Exit the Domino server if it is running.
2) Copy notes.ini from the Domino program directory to a backup directory.
3) Move names.nsf from the Domino data directory to a backup directory.
4) Move all IDs from the Domino data directory to a backup directory.
5) Edit the notes.ini in the Domino program directory by removing all but the top four lines and save the file.
The notes.ini should look similar to this:
[Notes] NotesProgram=C:\Program Files\Domino Directory=C:\Program Files\Domino\data KitType=2
6) Move all mail files from the \Data\Mail directory to a backup directory.
7) Rerun setup, creating new IDs.
Launch the Domino server to confirm the new server identity/configuration works.
At this point, the existing Domino Administrator client (as well as the Notes and Designer client) is going to be looking at the original configuration information when launched (original admin’s ID, Server info in the client notes.ini, administration preferences, etc.), so you will also want to backup the original client configuration and then rerun setup on the client to avoid configuration mismatches after you have changed the identity of the Domino server.
In other words, you want to re-setup the client so that it looks up the new administrator and configures to the new server settings.
| Part 2: Reconfigure Domino Administrator to match the settings of the new server configuration |
1) Exit the Domino Administrator client if it is running.
2) Move the admin’s ID (user.id by default) from the \Notes\Data directory to a backup directory.
3) Move names.nsf from the \Notes\Data directory to a backup directory.
4) Move the other user-specific client files - bookmark.nsf, desktop6.ndk, cache.ndk, and domadmin.nsf (this is where the administration preferences in the Admin client are stored) - to a backup directory.
5) Copy notes.ini from the Notes program directory to a backup directory.
6) Edit the notes.ini in the Notes program directory by removing all but the top four lines and save the file.
The notes.ini should look similar to this:
[Notes] NotesProgram=C:\Program Files\Domino Directory=C:\Program Files\Domino\data KitType=1
7) Rerun setup, using the new administrator’s name and new home server information.
Launch the Domino Administrator client to confirm that the new configuration settings work.
9) Explore the new server with the Domino Administrator client.
| Part 3: (Optional) Restore original identity of the server |
1) Exit the Domino server if it is running.
2) Move newly created IDs to a backup directory.
3) Move newly created names.nsf to a backup directory.
4) Move newly created notes.ini to a backup directory.
5) Replace original IDs, notes.ini, names.nsf and mail files.
6) Launch the Domino server. This should be the original server and configuration.
| Part 4: (Optional) Restore original Administrator client settings (corresponding to server) |
1) Exit the Domino Administrator client if it is running.
2) Move newly created IDs to a backup directory.
3) Move newly created names.nsf, bookmark.nsf, desktop6.ndk, cache.ndk and domadmin.nsf to backup directory.
4) Move newly created notes.ini to backup directory.
5) Replace original IDs, notes.ini, and names.nsf.
6) Launch the original server.
7) Launch the Domino Administrator client. You should be able to connect as the original administrator and view the original server using the Domino Administrator client.
Comments rss TrackbackWhen you want to make significant changes to the configuration of your Domino server without reinstalling Domino, follow these steps:
1) Exit the Domino server if it is running.
2) Copy names.nsf from the Domino\Data directory to a backup directory. (Note: This is a backup precaution.)
3) Copy notes.ini from the Data directory to a backup directory. (Note: This is a backup precaution.)
4) In the notes.ini in the Domino program directory, remove all but the top four lines, and then save and close the file.
The notes.ini should look like this:
[Notes] NotesProgram=C:\Program Files\Domino Directory=C:\Program Files\Domino\data KitType=2
5) Launch the Domino server to rerun setup. At this point all you are doing is repopulating the notes.ini and creating a new names.nsf a. Select the option to use an existing server ID file
b. Choose to use an existing certifier ID file.
c. Type in the same Domino domain name when prompted.
d. Choose to use an existing administrator ID file.
6) Complete any remaining screens and finish the setup routine. Make the desired changes to the configuration as you progress through the setup routine.
7) The new configuration settings will be implemented when you start the Domino server.
Comments rss TrackbackWhen you suspect a faulty server setup, follow the steps below to rerun the Domino server setup routine.
1) Exit the Domino server if it is running.
2) Move names.nsf from the Domino program directory to a backup directory.
3) Copy notes.ini from the Data directory to a backup directory.
4) In the notes.ini in the Domino program directory, remove all but the top four lines, save and close the file.
The notes.ini should look like this:
[Notes] NotesProgram=C:\Program Files\Domino Directory=C:\Program Files\Domino\data KitType=2
5) Launch the Domino server to rerun setup. At this point all you are doing is repopulating the notes.ini and creating a new names.nsf. a. Select the option to use an existing Server ID file (use the existing ID files for each of these steps).
b. Choose to use an existing certifier ID file.
c. Enter the same Domino domain name when prompted.
d. Choose to use an existing administrator ID file.
6) Complete the setup screens and finish the setup routine.
7) Start the Domino server and see if the problems you were experiencing are corrected.
If the problem(s) is resolved, quit the Domino server and rename the new notes.ini in the \Data directory and move the original notes.ini back into the \Data directory. If the problem returns, the issue was caused by the original notes.ini. Replace the original notes.ini with the newly created notes.ini. A comparison between the old and new version of the notes.ini files might reveal the cause of the issue.
9) If the problem remains resolved after replacing the new notes.ini with the original notes.ini, rename the new names.nsf and restore the original names.nsf. If the problem returns, the issue was caused by the original names.nsf. Replace the original names.nsf with the newly created names.nsf.
A comparison between the documents in the old and new versions of the names.nsf file might reveal the cause of the issue.
Comments rss TrackbackThis minimalistic guide shows how to install Domino 7.0.2 on Ubuntu 8.0.4 server or workstation. I did this on Ubuntu 7, but did not write everything down, which meant learning/searching for the information once more. Please let me know if you have better ways of doing this!
$ sudo useradd -m domino
$ sudo groupadd domino
$ sudo passwd domino
Domino uses some libraries that is not installed by the standard Ubuntu installation.
$ sudo apt-get install libstdc++5
$ sudo apt-get install libxmu6
$ sudo apt-get install libxp6
$ sudo apt-get install libxp-java
$ sudo apt-get install libxtst6
Unpack the installation file (my is named S7.0.2.tar) and run the linux/domino/install script as root. Use default settings (except user, enter domino), use “Manual setup”.
$ tar -xvf S7.0.2.tar
$ cd S7.0.2/linux/domino
$ sudo install
Since you installed as root, the files is owned by root. I guess if install was run as the domino user, this step would not be required.
$ sudo chown -R domino /local/notesdata
$ sudo chgrp -R domino /local/notesdata
$ sudo chown -R domino /opt/ibm
$ sudo chgrp -R domino /opt/ibm
Stop your local firewall or open 1352 in the local firewall. If you are using shorewall, you can do your own Notes macro. Change the port from 80 to 1352 in the macro.Notes file.
$ sudo cp /usr/share/shorewall/macro.HTTP /usr/share/shorewall/macro.Notes
$ sudo gedit /usr/share/shorewall/macro.Notes
Add the following (depending on setup…) to /etc/shorewall/rules:
Notes/ACCEPT net $FW
Stop any mail, web, ldap services, so that Domino does not conflict on ports. Remember to disable those you don’t need or disable the Domino services that you don’t need.
$ sudo /etc/init.d/postfix stop
$ sudo /etc/init.d/courier-imap stop
$ sudo /etc/init.d/courier-imap-ssl stop
The server script uses /bin/sh, relink sh to bash that normally links to /bin/dash.
$ sudo rm /bin/sh
$ sudo ln -s /bin/bash /bin/sh
I got many “Command not found” errors when starting the server first time. After some research, I found that the script requires gawk in sd.sh:
$ sudo apt-get install gawk
$ su notes
$ DISPLAY=:0.0
$ export DISPLAY
$ cd /local/notesdata
$ /opt/ibm/lotus/bin/server -listen
If you want to add a server with existing IDs, put the certifier ID, the server ID and the admin ID in the notesdata directory on the server. Run the Remote Server Setup utility on a client. Usually in Start\Lotus Applications\Remote Server Setup. Configure as a normal setup.
To be able to start Domino on startup, restart it and shutdown when system restarts, you can download domino init.d-script and put in /etc/init.d. Restart the server to see if it works.
$ cd /etc/init.d
$ sudo wget http://johankanngard.net/wp-content/uploads/2008/07/domino
$ sudo chmod +x domino
$ sudo chown domino domino
$ sudo chgrp domino domino
$ sudo update-rc.d domino defaults
$ sudo shutdown -r now
Use a Notes client and test that the server is up and running. To see if the server is running on the server, you use telnet.
$ ps a | grep server
4505 pts/0 Ss+ 0:00 su - domino -c /opt/ibm/lotus/bin/server
You can also try connecting to the server locally with telnet using:
$ telnet localhost 1352
Trying 127.0.0.1...
Connected to localhost.
Escape character is \\\\\\\\\\\\\\\'^]\\\\\\\\\\\\\\\'.
Comments rss TrackbackInstructions for installing the IBM Lotus Domino Server 7 on Debian 4 GNU/Linux:
* Install gawk
apt-get install gawk
ln -s /usr/bin/gawk /bin/gawk
* Create a group named notes and a user notes in that group with
useradd -m notes
or
groupadd notes
useradd -g notes -d /home/notes notes
* Unpack the installation files
tar xvf c84w5na.tar
* Enable the X sessions for other users
xhost +
(if you are worried about security you can use X authorizations for this, you can
take a lock to the X documentation to see how you can do this more securely)
* Test the X permissions for a root session
su -
DISPLAY=:0
export DISPLAY
xcalc
(if you don’t see the calculator application something is missing !)
* Execute the setup script as root
su -
export DISPLAY=:0
cd linux
./install
(This script is in the linux directory of the files you just unpack)
* Follow the installation instruccions for default
(Of course you may choose a custom installation but considere they may require
extra pre tasks before executing the setup script)
* After the setup script is complete you may startup the Server Configuration Wizard as
su - notes
DISPLAY=:0
export DISPLAY
cd /local/notesdata
/opt/ibm/notes/bin/server
* Follow the default Server Configuration Wizard instructions
(You may choose a custom configuration here too but depending on them you may
riquired extra pre tasks before configure the server)
* Start the Domino Server
su - notes
DISPLAY=:0
export DISPLAY
cd /local/notesdata
/opt/ibm/notes/bin/server
(The second time you issue this command the script will see that the server is already configured and start it. If you want to reconfigure the server or do special initializations consult the Domino Server documentation)
* Enjoy your Domino Server on Debian 4 GNU/Linux !
NOTES:
* I have some packages already installed in Debian that may vary from a default Debian installation like the libstd packages or the gcc and make packages.
* If you have configured the SMTP mail services on the Domino Server you will need to disable an already active mail server in Debian with
/etc/init.d/postfix stop
or
/etc/init.d/exim4 stop
(If you want to disable the mail services for a default system boot, you may use update-rc.d)
Comments rss TrackbackYou should now already be aware that Microsoft provide Exchange 2003 tools all in one handy place on the main Exchange site. After all, it has been mentioned on this blog before, you know!
However, I’d like to share with you a nice description of each tool, along with a direct link to that tool. It’s great to have this information all on one link!
Use the Add Root Certificate tool to add your own root certificate onto your Pocket PC device. For security, organizations often wish to use secure connections (SSL) when syncing or accessing a server. A number of Pocket PC 2002 applications use root certificates and SSL. If your organization prefers to use its own root certificate, you must install a custom root certificate on to the device. This tool will help you do so. Please note that this tool is for Pocket PC 2002 devices only. Pocket PC 2003 devices do NOT require a tool to install certificates.
Use Address Rewrite to rewrite return e-mail addresses on outgoing messages sent from a third-party mail system to Exchange, and destined for external or Internet addresses. This feature is similar to the Exchange 5.5 tool, ReRouteViaStore. Address Rewrite enables address rewrite on each SMTP virtual server. The intent of this feature is to rewrite addresses only for mail coming from the partner/subsidiary company (externally SMTP submitted) coming into your company’s e-mail servers and then going out to the Internet. Address Rewrite is useful in merger or acquisition scenarios in which you want all e-mail addresses to reflect the parent company’s name.
Use Exchange 2003’s enhanced ArchiveSink to log all message and recipient details of an e-mail message for incoming and outgoing messages on an Exchange server. ArchiveSink, a diagnostic tool, is a custom script that enables message archiving. When message logging is enabled, ArchiveSink will create an additional XML file for each message that is archived.
Use the Authoritative Restore tool to force a restored directory database to replicate to other servers after restoring from a backup. This tool allows you to restore one server (the server with the most recent pre-mistake backup) rather than all servers. With the Authoritative Restore tool, object versions and USNs can be advanced on all writable objects held by that directory so that the data held on the backup appears to be more recent than any copy held by other servers. You can receive assistance using this tool from Microsoft Product Support Services.
Importer for Lotus cc:Mail Archives
Use the Importer for Lotus cc:Mail Archives tool to import cc:Mail archive files to folders in an Exchange 2003 mailbox store or to one or more personal folder (.pst) files. After you install the archive importer, you can import all cc:Mail archives yourself or you can distribute the archive importer program (Ccmarch.exe) to users who need to import their own cc:Mail archive files. The archive importer imports cc:Mail archive files containing e-mail messages directly from users’ desktops to Exchange folders.
Disable Certificate Verification
Use the Disable Certification Verification tool to allow users with Windows Mobile devices to connect to Exchange servers without verifying the root certificate authority against the certificate trust list on the device. The device still uses SSL to connect to Exchange, but the Exchange Certificate check allows certificates from un-trusted certificate authorities to be used without generating errors.
Use the DNS Resolver tool to simulate the SMTP service’s internal code-path and print diagnostic messages that indicate how DNS resolution is proceeding. The tool must be run on the computer where the DNS problems are occurring. DNS Resolver works only on Exchange servers running Windows Server 2003.
Use the Error Code Lookup tool to determine error values from decimal and hexadecimal error codes in Microsoft Windows operating systems. The tool can look up one or more values at a time. All values on the command line will be looked up in Exchange’s internal tables and presented to you. If available, informational data associated with the value or values will also be shown.
Exchange Server Stress and Performance 2003
Use Microsoft Exchange Server Stress and Performance (ESP) 2003, a highly scalable stress and performance tool for Exchange 2003, to simulate large numbers of client sessions by concurrently accessing one or more protocol servers. ESP includes multiple modules that you can use to simulate a wide variety of protocols and loads. You can run modules concurrently from multiple hosts, thereby more realistically simulating physically separate client machines. There is no limit to the number of computers on your network that can host ESP modules.
Inter-Organization Replication
Use the Inter-Organization Replication tool to replicate free and busy information and public folder content between Exchange organizations. The tool allows for the coordination of meeting, appointments, contacts, and public folder information between disjointed Exchange organizations. The tool consists of two programs: the Replication Configuration program (exscfg.exe), and the Replication service (exssrv.exe). The Replication Configuration program creates a configuration file for setting the replication frequency, logging options, folders to be replicated, and accounts to be used. The Replication service continuously updates information from one server (designated as the Publisher) to one or more Exchange servers (designated as Subscribers).
Use Exchange Server Deployment tools and documentation to lead you through the entire Exchange Server 2003 installation or upgrade process. To ensure that all of the required tools and services are installed and running properly, it is recommended that you run Exchange 2003 Setup through the Exchange Server Deployment Tools. When you use Exchange Server Deployment Tools, you can run specific tools and utilities to verify that your organization is ready for the Exchange 2003 installation.
Mailbox Merge Wizard (ExMerge)
Use the Mailbox Merge Program to extract data from mailboxes on a Microsoft Exchange Server and then merge this data into mailboxes on another Microsoft Exchange Server. The program copies data from the source server into Personal Folders (.PST files) and then merges the data, in the Personal Folders, into mailboxes on the destination server. The ability to merge data to and from an Exchange Server makes this program an invaluable tool with a variety of uses- especially during disaster recovery. The program can also replace existing data instead of merging new data if specified by the Administrator. Mailbox Merge has some limitations. Please read the tools documentation before using this program.
Use the GUID Generator to generate globally unique identifiers, or GUIDs, that you can use to identify your ActiveX classes, objects, and interfaces. The GUID is copied to the Clipboard in one of four different formats for insertion into your application’s source code.
Use Jetstress to verify the performance and stability of a disk subsystem prior to putting an Exchange server into production. Jetstress helps verify disk performance by simulating Exchange disk Input/Output (I/O) load. Specifically, Jetstress simulates the Exchange database and log file loads produced by a specific number of users. You use Performance Monitor, Event Viewer, and ESEUTIL in conjunction with Jetstress to verify that your disk subsystem meets or exceeds the performance criteria you establish. After a successful completion of the Jetstress Disk Performance and Stress Tests in a non-production environment, you will have ensured that your Exchange 2003 disk subsystem is adequately sized (in terms of performance criteria you establish) for the user count and user profiles you have established. It is highly recommended that the Jetstress user read through the tool documentation before using the tool.
Use Microsoft Exchange Server Load Simulator (LoadSim) 2003 as a benchmarking tool to simulate the performance load of MAPI clients. LoadSim allows you to test how a server running Exchange 2003 responds to e-mail loads. To simulate the delivery of these messaging requests, you run LoadSim tests on client computers. These tests send multiple messaging requests to the Exchange server, thereby causing a mail load. LoadSim is a useful tool for administrators who are sizing servers and validating a deployment plan. Specifically, LoadSim helps you determine if each of your servers can handle the load to which they are intended to carry. Another use for LoadSim is to help validate the overall solution.
Information Store Viewer (MDBVU32)
Use Information Store Viewer (also called MDBVu32) to view or set details about a user’s message storage files, which consist of the private information store, the personal folder file (.Pst), the public store and the offline folder file (.Ost). The Information Store Viewer shows the properties available for each message, how you can use them, and in what format they appear.
The Exchange 2003 Management Pack extends the capabilities of Microsoft Operations Manager by providing specialized monitoring for servers running Exchange 2003. This Management Pack includes a definition of health for an Exchange 2003 Server and will raise an alert to the administrator if it detects a state which requires intervention.
Use MTA Check, a command line tool, to check the MTA database consistency of Exchange message transfer agent (MTA) and to repair the MTA database if necessary. MTA Check will analyze and correct problems in the MTA. Run MTA Check if you suspect corruption in the MTA database or see errors written in the Event Log.
SMTP Internet Protocol Restriction and Accept/Deny List Configuration
Use the SMTP Internet Protocol Restriction and Accept/Deny List Configuration to programmatically set or view Internet Protocol (IP) restrictions on an SMTP virtual server and to add or remove IP addresses from your global accept or deny lists. Microsoft Exchange 2003 provides connection and relay control for its Simple Mail Transfer Protocol (SMTP) virtual servers. Additionally, Exchange 2003 provides connection filtering that allows you to configure IP addresses from which you want to accept connections or from which you want to always deny connections. These settings are configured in global accept and deny lists in Connection Filtering. An administrator can use these controls to limit the computers that can connect to a virtual server or that can relay e-mail to outside the Exchange organization.
Up-To-Date Notifications Troubleshooting
Use the Up-to-Date Notifications troubleshooting tool to solve common notification issues. An administrator can input user and administration information (on the default page of this application). The information page shows the user’s device information (a list of devices the user has, what delivery method and address the device uses) to help an administrator narrow down notification issues that the user might be having. The tool also allows an administrator to send test e-mail to the specified devices.
Use WinRoute to determine the link state routing information as known to the routing master. The WinRoute tool connects to the link state port, TCP port 691, on Exchange 2000 or 2003 server and extracts the link state information for an organization. The information is a series of GUIDs that WinRoute matches to objects in Active Directory, connectors and bridgehead servers, and presents in human-readable format. This tool should be the first step in troubleshooting routing in an Exchange 2000 and Exchange 2003 mail-handling environment.
Comments rss Trackbackhttp://technet.microsoft.com/en-us/library/aa998291.aspx
Add-ADPermission “Mailbox” -User “Domain\User” -Extendedrights “Send As”
http://www.digwin.com/tip-how-to-managing-send-as-permission-in-exchange-2007-sp1
http://theessentialexchange.com/blogs/michael/archive/2008/01/18/Exchange-Server-Caches.aspx
http://technet.microsoft.com/en-us/library/dd421860.aspx
http://technet.microsoft.com/en-us/library/bb684892.aspx
http://theessentialexchange.com/blogs/michael/archive/2008/01/18/Exchange-Server-Caches.aspx
http://technet.microsoft.com/en-us/library/aa998291.aspx
http://www.shudnow.net/2007/08/12/send-on-behalf-and-send-as/
http://groups.google.com/group/microsoft.public.exchange.admin/browse_thread/thread/fa7ddddb4d29699d
Comments rss Trackback Comments rss TrackbackControlling Group Policy Security Settings Refresh and Application
Using Group policy to Deploy Outlook 2007
http://www.petri.co.il/use-windows-group-policy-deploy-outlook-2007-exchange-ad.htm
How to enforce Microsoft Outlook cached mode via group policy
http://searchexchange.techtarget.com/tip/0,,sid43_gci1164852,00.html
Best way to setup Outlook 2003 through Group Policy
http://exchangeexchange.com/forums/t/605.aspx
http://www.vivace.f9.co.uk/wsh.htm
Windows Server 2003 - Replmon Support Tool Utility
http://www.computerperformance.co.uk/w2k3/utilities/replmon.htm
Repadmin Overview
http://technet.microsoft.com/en-us/library/cc755360.aspx
http://www.trainsignal.com/Exchange-Server-2007-Training-P22.aspx
How to deploy customized Outlook 2003 security settings to client computers by using the “Outlook virus security settings” Group Policy setting
http://support.microsoft.com/kb/885682
Office 2003 Service Pack 3 Administrative Template (ADM), OPAs, and Explain Text Update
http://www.microsoft.com/downloads/details.aspx?FamilyID=BA8BC720-EDC2-479B-B115-5ABB70B3F490&displaylang=en
2007 Office system Administrative Template files (ADM, ADMX, ADML) and Office Customization Tool version 2.0
http://www.microsoft.com/downloads/details.aspx?familyid=92D8519A-E143-4AEE-8F7A-E4BBAEBA13E7&displaylang=en
Office 2003 Editions Resource Kit Tools
http://www.microsoft.com/downloads/details.aspx?familyid=4BB7CB10-A6E5-4334-8925-3BCF308CFBAF&displaylang=en
How to force Update group policy on all machines in the network
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Q_22756260.html
Comments rss Trackback