RE: Re: Retrieving .pst file location

Forums

My Profile

Inbox

Address Book

My Subscription

My Forums

RE: Re: Retrieving .pst file location

Logged in as: Guest

arrSession:exec spGetSession 2,2,2667

	Active Users: There are 0 members and 0 guests.
	Users viewing this topic: none

Printable Version

All Forums >> [Scripting] >> WSH & Client Side VBScript >> RE: Re: Retrieving .pst file location
Do you like VisualBasicScript.com? Link to us and help spread the word about our forum. Thanks!

Page: << < prev 1 [2]

Message

<< Older Topic Newer Topic >>

RE: Re: Retrieving .pst file location - 1/2/2007 4:33:53 AM

chong

Posts: 74
Score: 0
Joined: 12/20/2006
Status: offline

i take it a solution for this dude was never suceeded...im currently researching a similar situation, but it differs from the back up senario. Some of the info below may seem or is completly irrelavent to previous posts o=)

The issue we have with users is that, outlook being outlook, defaultly sets the PST location to "C:\Documents and Settings\user_id\Local Settings\Application Data\Microsoft\Outlook"...and we don't use roaming profile, thus everytime a user logs onto a new PC their outlook is not looking to the PST locations(stored on a centrally stored fileserver)

I found various scripts that search the registry for the filepath of the current users PST file. however, i've no idea how to read HEX and Binary into ASCII or English for that matter.

So, i thought, i know im going to try some scripts and see if they decode the hex into ascii for me, but i didnt get any joy.

Below is a code example found over at outlookcode.com - This GetStorePath procedure extracts the path to a Personal Folders .pst file (or store used for IMAP, HTTP or SharePoint data) from the information embedded in the StoreID. However, looks largely like vba and i was unable to run the script successfully(i have no VB Studio)

See if you gurus can have any luck :)

Function GetStorePath(strStoreID As String)
   Dim intStart As Integer
   Dim intEnd As Integer
   Dim strProvider As String
   Dim strPathRaw As String
   intStart = InStr(9, strStoreID, "0000") + 4
   intEnd = InStr(intStart, strStoreID, "00")
   strProvider = _
     Mid(strStoreID, intStart, intEnd - intStart)
   strProvider = Hex2ToString(strProvider)
   Select Case LCase(strProvider)
       Case "mspst.dll", "pstprx.dll"
           intStart = InStrRev(strStoreID, "00000000") + 8
           strPathRaw = Mid(strStoreID, intStart)
           GetStorePath = Trim(Hex4ToString(strPathRaw))
       Case "msncon.dll"
           intStart = InStrRev(strStoreID, _
                               "00", Len(strStoreID) - 2) + 2
           strPathRaw = Mid(strStoreID, intStart)
           GetStorePath = Trim(Hex2ToString(strPathRaw))
       Case "emsmdb.dll"
           GetStorePath = "Exchange store"
       Case Else
           GetStorePath = "Unknown store path"
   End Select
End Function
Public Function Hex4ToString(Data As String) As String
   Dim strTemp As String
   Dim strAll As String
   Dim i As Integer
   For i = 1 To Len(Data) Step 4
       strTemp = Mid(Data, i, 4)
       strTemp = "&H" & Right(strTemp, 2) & Left(strTemp, 2)
       strAll = strAll & ChrW(CDec(strTemp))
   Next
   Hex4ToString = strAll
End Function
Public Function Hex2ToString(Data As String) As String
   Dim strTemp As String
   Dim strAll As String
   Dim i As Integer
   For i = 1 To Len(Data) Step 2
       strTemp = "&H" & Mid(Data, i, 2)
       strAll = strAll & ChrW(CDec(strTemp))
   Next
   Hex2ToString = strAll
End Function

(in reply to spinnerdog)

Post #: 21

RE: Retrieving .pst file location - 1/19/2007 4:50:44 AM

bromcsan

Posts: 1
Score: 0
Joined: 1/19/2007
Status: offline

First off, beware that Microsoft does not support .pst's over a network connection. That being said, we did just implement a centralized .pst archive server in our network.

Autoarchive location can only be set in PRF's. Group policy will let you do almost everything with Autoarchiving EXCEPT the path lol.

Manual archive location is in the registry, but it's in hexadecimal and very hard to edit.

Our solution, a winbatch ran at the user's desktop that opened Outlook, tabbed to the necessary locations, and entered manual and auto archive locations to point to our network location.

This is for new archives. We brought old archives up to the server during a one month period during our GroupWise to Exchange migration.

(in reply to robiee4u)