Posts Tagged ‘Search’

There are three ways to forward mail from one user to another in Exchange

  1. Exchange Forwarding Most Common – Done by Administrator
  2. Inbox Rule – Done by User
  3. Hub Transport Rule – Done by Administrator

1 and 3 can be checked easily and there will be references of when this is done and not done usually in tickets , however users can enable Inbox rules by themselves then contact your later to disable the forward.

Here is how to check for forwarding or redirecting rules on mailbox in 365

 foreach ($i in (Get-Mailbox -identity %USERNAME%))
{ Get-InboxRule -Mailbox $i.DistinguishedName | where {$_.ForwardTo} | fl MailboxOwnerID,Name,ForwardTo }
  foreach ($i in (Get-Mailbox -identity %USERNAME%))
{ Get-InboxRule -Mailbox $i.DistinguishedName | where {$_.ReDirectTo} | fl MailboxOwnerID,Name,RedirectTo}

To Disable
Disable-InboxRule -Identity "%NAME OF RULE%" -Mailbox "%USERNAME"
 
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

You can make a change to the WorkSpace description (add a full stop to the description or other characters), save it, and then reverse the change, and save it, it to force a WorkSpace to be re-indexed.

This will update the time stamp on the WorkSpace and the Indexer should pick it up to be indexed.

WorkSite Connector service is only looking for the EDITWHEN or EDITPROFILEWHEN column in the MHGROUP.DOCMASTER table

https://support.imanage.com/forums/showthread.php?t=1660&highlight=workspace

 

If changing this does not get this Workspace in the indexer it seems your connector might be broken , make sure you update to the latest version ( connector.jar )

 

 

If you have a batch of workspaces you can also do this through SQL:

To check if you are running UTC go to the below registry path on your iManage Servers
HKEY_LOCAL_MACHINE\SOFTWARE\Interwoven\WorkSite\imDmsSvc
UTC In Use = N
Or:
UTC In Use = Y

If this key does not exist 

Run this query in SQL

SELECT 'GETDATE() ', GETDATE(); 
SELECT 'GETUTCDATE() ', GETUTCDATE();

Check both the times , and update a workspace name ( by adding a full stop at the end and deleting ) and then use a select query to see which time is closer to see if it’s using UTC or not

SELECT *FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'


Check the PRJ_NAME matches your WorkSpace Description.

If you are UTC In Use = N, ( not ) use the below.

To update the WorkSpace for re-indexing:

UPDATE MHGROUP.DOCMASTERSET EDITPROFILEWHEN = GETDATE()FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'

If you are UTC In Use = Y, ( Yes ) use the below.

To update the WorkSpace for re-indexing:


UPDATE MHGROUP.DOCMASTERSET EDITPROFILEWHEN = GETUTCDATE()FROM MHGROUP.DOCMASTER DWSJOIN MHGROUP.PROJECTS PWS ON DWS.DOCNUM = PWS.DOCNUMWHERE PWS.PRJ_NAME LIKE '%name of workspace%'

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

PowerShell logoRecently we need to search a load of servers locally for files that existed ( lingered ) on peoples local user proflile

Get-ChildItem -Recurse -Force \\servername\c$\Users\*\AppData\Local\Temp | Where-Object {$_.Name -like "[email protected]*.tmp"} | Export-CSV C:\TempFiles.csv -Append

We then needed to search roaming directories mapped on a file server , I tried to use the above for this command replacing the directory location with a roaming file server location replace * with Users again, however I was getting “Get-ChildItem : Access is denied” with UnauthorizedAccessException , probably because query is too generic! To limit this down, I used the following pipe to query the list of users and then check each folder after

Get-ChildItem "\\domain.local\dfs\location\*" | ForEach-Object {
 
Get-ChildItem -Recurse -Force $_"\AppData\Roaming\Software"   | Where-Object {$_.Name -like "[email protected]*.tmp"}} | Export-CSV C:\Files.csv -Append

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Can't-open-this-itemWhen opening email from a Find / Search in Outlook 2003 you get “can’t open this item”

Is you use custom forms this is due to the custom form cache filling up and needing to be cleared , below code will do this is you copy and paste it into a VBS file

'Robert Sparnaaij [MVP-Outlook]
'http://www.howto-outlook.com

 
 
'Close Outlook socially
WScript.Echo "Close Outlook and press OK"
 
'Close Outlook forcefully
strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colProcessList = objWMIService.ExecQuery _
("Select * from Win32_Process Where Name = 'outlook.exe'")
For Each objProcess in colProcessList
objProcess.Terminate()
Next
 
'Set Profile Path
Set oShell = CreateObject("WScript.Shell") 
sCurrUsrPath = oShell.ExpandEnvironmentStrings("%UserProfile%")
Set objFSO = CreateObject("Scripting.FileSystemObject")
 
'Verify whether the Forms Cache exists and delete it 
If objFSO.FolderExists(sCurrUsrPath & "\Local Settings\Application Data\Microsoft\Forms") Then
      WScript.Echo "The Forms Cache has been found and will be cleared."
      Const DeleteReadOnly = True
      objFSO.DeleteFolder(sCurrUsrPath & "\Local Settings\Application Data\Microsoft\Forms"), DeleteReadOnly
      WScript.Echo "The Forms Cache has been cleared succesfully. Start Outlook and check whether the form works now."
 
  Else
 
WScript.Echo "Cannot find the Forms Cache. It has been cleared already. Start Outlook and check whether the form works now."
 
End If

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)