« Previous Next »

Thread: Help with parsing activesync data

Last post 11-13-2009 6:40 AM by wallin. 2 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (3 items)

Sort Posts:

Shortcuts

Search | Active Posts | Unanswered Posts | View all users

  • 10-22-2009, 10:48 AM

    • Ebucel
    • Not Ranked
    • Joined on 10-22-2009, 2:43 PM
    • Posts 2

    Help with parsing activesync data

    Reply Contact

    I copied the information from http://msexchangeteam.com/archive/2006/02/14/419562.aspx

    but It does not output any info:

     

    Statistics:
    -----------
    Elements processed: 762475
    Elements output:    0
    Execution time:     2.25 seconds

     

    is what i get after running the sql with this commandline:

     C:\Program Files\Log Parser 2.2>LogParser.exe -i:IISW3C -o:CSV file:C:\lpar\Hits
    _by_User.sql

    I know we have Iphone users and other activesync devices.

    I want to generate a report that list users, device, last sync, last sync attempt which I thought the SQL i found would do it just doesn't seem to output the data or create the csv file.

     

    Thanks In Advance

  • 10-22-2009, 12:39 PM In reply to

    • Ebucel
    • Not Ranked
    • Joined on 10-22-2009, 2:43 PM
    • Posts 2

    Re: Help with parsing activesync data

    Reply Contact

     I was actually able to get there com addin sql to run and output good data.

    Still I would like to know what i'm missing here.

  • 11-13-2009, 6:40 AM In reply to

    • wallin
    • Not Ranked
    • Joined on 11-13-2009, 11:09 AM
    • Posts 3

    Re: Help with parsing activesync data

    Reply Contact

    A client access server is an IIS server that hosts Exchange-related Web pages. This is important because it means that, like any other IIS server, a client access server creates a daily log of activity in the \Windows\system32\Logfiles\W3SVC1folder. To use this information, you must separate ActiveSync-related log entries from the Outlook Web Access (OWA)-related entries (assuming that the client access server is being used for both purposes). You must then parse the log file entries so the log file data becomes meaningful.

    Fortunately, we get some help from the folks in Redmond on this one. You can actually use the Exchange Management Shell to extract and parse the ActiveSync data from the logs. The only catch is that IIS creates a new log file each day, so you need to know for which date you want to examine Exchange ActiveSync data. You must also create a folder in which you can deposit the extracted data.



    Cheers

    packing supplies
Page 1 of 1 (3 items)
Microsoft Communities