DocsOpen UN-Integration::MSWord::Windows Registry

For MSWord and other applications using ODMA integration to DocsOpen (or other ODMA compliant DMS, if any...) ODMA is "activated" in the registry under:

[HKEY_CLASSES_ROOT\ODMA32]

If you remove that key and all it's subkeys then DMS is unintegrated.
This can be done by manually merging a registry file that looks like:

Windows Registry Editor Version 5.00

[-HKEY_CLASSES_ROOT\ODMA32]

Merging that file can be done in a BAT file with the line:

regedit /s [filename].REG

Webview::Windows XP::AD Logon

Continuing saga from previous posting....
When you use Webview interface to Elite time entry and passthrough authentication -
"Pre-Windows 2000" account must exactly match the Elite userid - also case sensitive
and
The case with which the user logs on does not matter (like it does for Elite.)

Elite::Windows XP::AD Logon

When security passes through XP/AD logon to Elite it is case sensitive and will fail if the user doesn't capitalize properly.
If the elite userid is all in lower case, then the user's "Pre-Windows 2000" account must be in all lower case AND the user must key in all lower case when they logon.
Of course if you have multiple "pass through" security applications that have this issue then you will have to change either the elite userid or the userid in the other application to match and then match that to the "Pre-Windows 2000" account.

Aint ya glad you use directory services.... Don't ya wish everybody did?

MSWord::DocsOpen

DOCS Open - Word - "Microsoft Visual Basic: Ambiguous name detected: TMPDDE"
In DOCS Open, when you start Microsoft Word, the following error message may appear:

"Microsoft Visual Basic: Ambiguous name detected: TMPDDE."

This issue also occurs when you attempt to open documents from the Quick Retrieve window or when you save Word documents.

OtherKeywords: temp dde, MS, launching, launch, 97, 2000, 2002, XP



--------------------------------------------------------------------------------
Resolution:
A temporary macro file is created upon opening Word and is then automatically deleted. Occasionally when Word is opened, this file is not deleted. The error message appears when Word attempts to write a new temporary macro file, and one already exists.

Steps to eliminate the error:

1. Open Word.
2. Select Tools>Macro>Macros.
3. Browse through the list of macros and delete any .TMPDDE macros.
4. Close and then reopen Word.

The error message should not appear. (If you are still receiving the error message, check for viruses on all Microsoft Word files being used. An infected file could corrupt the NORMAL.DOT template file and the TMPDDE file.)

NOTE: If you do not locate any TMPDDE macros, (the TMPDDE macro may not be visible through Tools>Macro on the Word toolbar), one of the following options will resolve this issue:

Delete the TMPDDE macro from the MS Word Global Template (NORMAL.DOT) file; this will require you to open the NORMAL.DOT macro template file in Visual Basic within Word and modify it to remove the TMPDDE macro section.

OR

Rename the MS Word Global Template (NORMAL.DOT) file; note that Word must be closed before you can perform this action.

For more information about this issue, please consult the following article on Microsoft's Web site: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q174966

MS Cluster Servers

How do I monitor MS Cluster server applications?
I really don't know. There appear to be no really good, thorough methods.
- Can watch to see if the cluster service fails - that would be a problem, but doesn't happen when an application fails over.
- Can poll for events in the event log. There aren't any good, specific event id's to watch for. Could monitor for several events that might indicate some kind of problem, but wouldn't indicate a specific problem occurred. This could work if we identified the pattern of events when a node brings a service online.
- Can monitor the existence/free space of the Q: drive on the node that is supposed to be the primary machine in the cluster. When drive Q: goes away we can know when the cluster group has failed over. However in a 2 node active-active configuration this would not tell us when the application running on node 2 failed over to node 1 (if node 1 owns the cluster group.)

It would be nice if there were performance monitor "counters," SNMP MIB's, WMI, or some other exposure of the status of each resource on a cluster server. This would provide alerting possibilities for "abnormal" situations. I understand there is some API that cluster administrator was built on, but writing my own cluster administrator with alerting capability is not attractive. Neither is sitting 24 hours a day and watching cluster administrator to find out whan an app fails over.

Outlook::OST to PST

http://hellomate.typepad.com/exchange/tools_utilities/index.html

OST to PST
Here's a useful addition to your toolbox... it's a tool that will create a PST from an orphaned OST file