Office 365 Monitoring

Hi All,
MS released MP for Monitoring Office 365, In my environment office 365 is in Cloud , Can you please guide me how can i monitor office 365 with the help of MP

Hi,
As far as I know, SCOM 2012 can be used to monitor Azure, so I think with the Office 365 management pack we should be able to monitor Office 365 in cloud.
The management pack can be download here:
http://www.microsoft.com/en-ca/download/details.aspx?id=43708
Please go through the management pack guide before using it.
Regards,
Yan Li
Regards, Yan Li

Similar Messages

  • Office 365 monitoring using SCOM

    Looks MS has released MP for office 365 , Did any one imported and configured alert ? 
    What are the pre-request to configure alert ?
    http://www.microsoft.com/en-us/download/details.aspx?id=43708

    This MP is a little annoying as you'll get a critical alert for any Resolved Incident entries still showing on the Microsoft O365 status pages. Until Microsoft expire these entries off from their side, you're stuck with the alert. If you manually close
    the alert, it gets recreated as it's still present on the O365 side.
    This means you're left with a bunch of unnecessary critical alerts clogging up your Active Alerts, such as:
    Resolved Incident EX8319: False positive for Exchange Online (ServiceRestored)
    Resolved Incident EX8318: False positive for Exchange Online (ServiceRestored)
    Resolved Incident EX8312: Post-incident report published for Exchange Online (ServiceRestored)
    Resolved Incident EX8267: Post-incident report published for Exchange Online (ServiceRestored)
    Resolved Incident LY7139: False positive for Lync Online (FalsePositive)
    Active Incident SP9188: False positive for SharePoint Online (ExtendedRecovery)
    Active Incident SP9208: Extended recovery for SharePoint Online (ExtendedRecovery)
    Active Incident SP9187: Service restored for SharePoint Online (ExtendedRecovery)
    Active Incident SP8367: Service restored for SharePoint Online (ExtendedRecovery)
    Resolved Incident IS9202: Service restored for Identity Service (ServiceRestored)
    Resolved Incident MO9196: Service restored for Office 365 Portal (ServiceRestored)
    Resolved Incident FO8317: Post-incident report published for Exchange Online Protection (PIRPublished)
    Resolved Incident MO8285: Service restored for Office 365 Portal (ServiceRestored)
    Resolved Incident MO8287: Post-incident report published for Office 365 Portal (ServiceRestored)
    Resolved Incident EX8268: False positive for Exchange Online (ServiceRestored)
    Resolved Incident MO8253: Service restored for Office 365 Portal (ServiceRestored)
    Resolved Incident MO8370: Post-incident report published for Office 365 Portal (ServiceRestored)
    Resolved Incident EX9215: Service restored for Exchange Online (ServiceRestored)
    Resolved Incident EX8343: Post-incident report published for Exchange Online (ServiceRestored)
    Of that lot, I regard only four of those to be Critical, the rest should be in the Informational section.
    Bear in mind too that this is per O365 subscription, so if you happen to look after a number of clients with O365 subscriptions, you're going to get multiples of those. Flood city.
    They need to further enhance the Office 365 Monitoring API to make it more granular so that things can be properly categorised.
    Oh, and the folder should be called Microsoft Office 365, not just Office 365. :-/

  • Office 365 Monitoring using SCOM 2012 R2

    http://www.microsoft.com/en-us/download/details.aspx?id=43708
    We have imported MP for O365 and added the new subscription (with Global Administrator permissions using Office 365 admin )after that we got an alert like below:
     Connection to EndPoint Service failed
    Any idea what would be the issue here?
    Sengo

    Hi,
    It's the correct page response "EndPoint not found", if you try to access the  https://office365servicehealthcommunications.cloudapp.net/shdtenantcommunications.svc
    page.
    The blank username and passwords are Ok as well, but be careful to edit your credentials from the subscription page, as they are not changed in this case in the Office365 Run As Account, looks like a bug. Therefore, edit them only through
    the Accounts menu, or create a new subscription.
    The management pack communicates exactly to the mentioned above page only, it's not possible to use IPs, as they could be changed at MS servers side. The host should be whitelisted in case if you have firewalls\proxy. At the same time, depending
    on your network\proxy\subscription configurations, possible issues could exist because of certificates and authorization at different levels.
    In case of proxy - the Office 365 Proxy Run As Account should be configured. It's automatically created during installation of MP, but the account with Internet access should be added there. Take in attention that using the Office365 Run As
    Account does not work out. Therefore the separate Windows account should be created and used as the Office 365 Proxy Run As Account, even if it's the same as the Office365 Run As Account. When using the proxy account, one of the Monitoringhost.exe
    processes works under this account. If the proxy account is not configured, this process works under the system account. The proxy account was not documented in Office365 MP manual.
    Don't change the default name of created Office 365 Run As accounts, somehow it affects the connection monitor.
    Hope it helps :)
    Natalya
    Hi Natalya,
    Thanks for this post. Indeed my SCOM server is behind a proxy. Let's say my Office 365 account is called "SCOM.O365" - it appears under Administration - Accounts under Basic Authentication, with the "friendly" name of "Office 365
    Run As Account_xxxxx". Do you mean I create a second account under "Windows" (it would be Active Directory based) also called "SCOM.O365" that the MP will use for proxy, and the MP will automatically run MonitoringHost.exe with this
    AD account? 
    thanks!

  • Office 365 MP Config Issue - Account doesn't have administrator permissions

    SCOM 2012 R2 RU3 | Windows Server 2012 R2
    I just configured this MP in the environment using the following references: 
    Office 365 MP Operations Guide
    Reference 1
    Reference 2
    In addition I've configured the Office 365 Subscription Proxy secure reference.
    When looking in the SCOM console I only see one error: 
    Source:   Office 365 Monitoring 
    Full Path Name:    Office 365 Monitoring 
    Alert Monitor:    Office 365 Connection State monitor 
    Created:    1/14/2015 4:42:56 PM 
    Account doesn't have administrator permissions
    Knowledge:     View additional knowledge... 
    Summary
    The monitor oversees the availability connection to Office 365 API EndPoint.
    Causes
    An error state is caused by having issues with connecting to Office 365 API EndPoint. It can be caused by:
    • Issues with global connection to Office 365 API EndPoint
    • Credentials for Office 365 Subscription's account are not correct
    • Office 365 Subscription's account is not allowed to getting data from Office 365 EndPoint API
    I've verified that the account is able to log into the server, has the _identifier, and global admin permissions in the Office 365 admin console. 
    Wondering if there's anything I may have missed. 
    Any responses appreciated.

    Verify that a proxy account is domain account.
    Also check below office 365 MP Guide
    http://www.microsoft.com/en-us/download/details.aspx?id=43708
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"Mai Ali | My blog:
    Technical | Twitter:
    Mai Ali

  • Office 365 x64 Click-to-Run Not Automatically Updating from Network Share

    We are piloting Office 365 x64 and pointing the clients to a network share (see config file below) for updates.  When we subsequently download the updates to the share the clients will not automatically install them.  If we manually do so from
    within an app (File > Account > Update Options > Update Now) it works fine.  The ACL and Sharing permissions allow Everyone and Domain Computers read-only access (in addition to some other ancillary accounts).  I've tried manually running
    the Office Automatic Updates from Task Scheduler and left the box running overnight.  I've rebooted, logged back on, closed and opened the app several times.  Nothing happens, just always sits at the current version.
      Anyone have any ideas?
          Thanks,
             Bryan
    Here's the UpdateURL registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Configuration\UpdateUrl = \\<SERVERNAME>\Office_365\Pilot
    ProPlusx64.xml:
    <Configuration>
    <Add OfficeClientEdition="64" >
    <Product ID="O365ProPlusRetail">
    <Language ID="en-us" />
    </Product>
    </Add>
    <Updates Enabled="TRUE" UpdatePath="\\<SERVERNAME>\Office_365\Pilot\" />
    <Display Level="None" AcceptEULA="TRUE" />
    <Logging Name="OfficeSetup.txt" Path="%temp%" />
    <Property Name="AUTOACTIVATE" Value="1" />
    <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
    </Configuration>
    Here's what I think is the log file:
    Timestamp Process TID Area Category EventID Level Message Correlation
    05/01/2015 11:21:11.061 OFFICECL (0x550) 0x554 Click-To-Run Telemetry aqkhc Medium {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","ExeVer":"15.0.4615.1002","SecuritySessionId":"0","ModulePath":"C:\Program Files\Microsoft Office 15\ClientX64\OfficeClickToRun.exe","CommandLine":"/service","Bitness":"64","IntegrityLevel":"0x4000"}
    05/01/2015 11:21:11.061 OFFICECL (0x550) 0x554 Click-To-Run Telemetry aqkhe Medium {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","OSVersion":"6.1","SP":"1","ProductType":"1","ProcessorArch":"9","Locale":"1033"}
    05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annt7 Medium ProcessPool::Initialize - Initializing Main Process Pool
    05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annuf Medium SystemProcessPool::DoInitialize - Initializing System Process Pool
    05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run anntv Medium ConfigurationManager::Initialize - Initializing ConfigurationManager
    05/01/2015 11:21:11.061 OFFICECL (0x550) 0x568 Click-To-Run annt4 Medium Pipeline::Initialize - Initializing pipeline with PipelineServerName: "ClickToRun_Pipeline" and InstallationPath: "C:\Program Files\Microsoft Office 15"
    05/01/2015 11:21:11.154 OFFICECL (0x550) 0x568 Click-To-Run annt1 Medium Orchestration::Initialize - Initializing Orchestration
    05/01/2015 11:21:11.201 OFFICECL (0x550) 0x568 Click-To-Run annto Medium ApiServer::Initialize - Initializing ApiServer for endpoint: C2RClientAPI_Server_System
    05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annty Medium ExecutionContext::QueueScenario - Set executing scenario to UPDATE
    05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annuz Medium TaskFactory::TryLoadScenario - Start loading UPDATE scenario
    05/01/2015 11:24:50.661 OFFICECL (0x550) 0x828 Click-To-Run annu0 Medium TaskFactory::TryLoadScenario - Loading UPDATE scenario is successful
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run amavh Medium ScenarioController::Initialize - requested display level: False
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run annua Medium ProcessPool::QueueTaskItem - Task SCENARIO:{AC2F0D89-6518-48E9-A0D9-EF039C456034} is being scheduled to run in this process
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0x828 Click-To-Run aoicd Medium ExecutionContext::QueueScenario - Successfully queue scenario UPDATE.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annua Medium ProcessPool::QueueTaskItem - Task UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0} is being scheduled to run in this process
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annvj Medium Worker::TaskExecutionThreadProc - Task SCENARIO:{AC2F0D89-6518-48E9-A0D9-EF039C456034} completed with TaskState TASKSTATE_EXECUTING.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {AC2F0D89-6518-48E9-A0D9-EF039C456034} complete event is handled by task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf6c Click-To-Run apm4n Medium TaskGroup::Finalize - Task AC2F0D89-6518-48E9-A0D9-EF039C456034 is not finished.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry amb0n Medium TaskUpdateDetection::ApplySettings: Beginning Update Scenario. {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","TargetVersion":"UNDEFINED","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskState":"TASKSTATE_EXECUTING","UpdatePathType":"CUSTOM","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE","TriggeringUI":"UNDEFINED","TaskCaller":"SCHEDULEDTASK"}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry aoh6s Medium TaskUpdateDetection::Execute: Ending Update scenario, task trigger source disabled. {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskState":"TASKSTATE_EXECUTING","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE"}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annvj Medium Worker::TaskExecutionThreadProc - Task UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0} completed with TaskState TASKSTATE_FAILED.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4b Medium Task::DoHandleWorkerCompleteEvent - Setting Task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0) Task State to (TASKSTATE_FAILED)
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run aqkg7 Medium Task::DoHandleWorkerCompleteEvent - No event is specified for task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0)
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run Telemetry apm4e Medium Task::HandleTaskStateFailed - Handling TaskState (TASKSTATE_FAILED) for task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0). {"SessionID":"bfe53625-5d12-4e1a-b3b4-2d8e88b0d108","GeoID":"244","Ver":"15.0.4615.1002","InstallID":"C5912794-7300-4A10-840B-575B03DB98F8","TaskState":"TASKSTATE_FAILED","TaskId":"77176F9C-873B-4A7D-8051-EBEB52DDE8B0","TaskType":"UPDATEDETECTION:{77176F9C-873B-4A7D-8051-EBEB52DDE8B0}","Scenario":"UPDATE"}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {77176F9C-873B-4A7D-8051-EBEB52DDE8B0} complete event is handled by task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {AC2F0D89-6518-48E9-A0D9-EF039C456034}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4a Monitorable Task::DoCancel - Can't cancel task (77176F9C-873B-4A7D-8051-EBEB52DDE8B0) because it is in TASKSTATE_FAILED state
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (57173191-24E0-42E1-96F4-914AF8CFD1D5) in TASKSTATE_NOTSTARTED, set to Cancelled.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (AA63EED2-70B9-4E21-952C-9CFB09EC37C0) in TASKSTATE_NOTSTARTED, set to Cancelled.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {D1506E3F-4B2A-41D3-913B-FA3E889CE20D}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {539BA5C1-BC18-4D11-AF61-CF6EDC58DC33}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (D1E1E548-917D-4D75-8AE5-FC76856C66DC) in TASKSTATE_NOTSTARTED, set to Cancelled.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {9A54EEBA-7B8D-4BD5-8EFE-D21E58FFFEE3}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {9C141B7D-2B22-4C33-9C5C-F6F3394AD19E}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {501487AD-0A47-419D-AF30-B9E616A4579B}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {0270BAF9-3CE0-46EE-A3FE-099ABC06BC14}
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (F0E5AF5D-5D82-4370-A2A6-C064CBC39247) in TASKSTATE_NOTSTARTED, set to Cancelled.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 0270BAF9-3CE0-46EE-A3FE-099ABC06BC14.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 501487AD-0A47-419D-AF30-B9E616A4579B.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm39 Medium Task::DoCancel - Task (A5E75ADF-8BF1-44C4-8900-1BE6070EB609) in TASKSTATE_NOTSTARTED, set to Cancelled.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 9C141B7D-2B22-4C33-9C5C-F6F3394AD19E.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 9A54EEBA-7B8D-4BD5-8EFE-D21E58FFFEE3.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 539BA5C1-BC18-4D11-AF61-CF6EDC58DC33.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task D1506E3F-4B2A-41D3-913B-FA3E889CE20D.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task AC2F0D89-6518-48E9-A0D9-EF039C456034.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task AC2F0D89-6518-48E9-A0D9-EF039C456034.
    05/01/2015 11:24:50.676 OFFICECL (0x550) 0xf70 Click-To-Run annt0 Medium ExecutionContext::ResetExecutingScenario - Reset executing scenario

    Hi,
    I replied in the other thread:
    http://social.technet.microsoft.com/Forums/office/en-US/e9e6be40-fb92-4734-9f94-9dee5599b1d8/office-365-pro-plus-2013-update-wont-apply-automatically?forum=officeitpro#c156ed8c-f65c-450c-9e0f-85f0de513c20
    It seems when the install finished it added an extra Office\Data to the path. My path should be \\hsbswpush02\GPsoftware\o365\Office\Data\15.0.4551.1005
    but it shows
    \\hsbswpush02\GPsoftware\o365\Office\Data\Office\Data15.0.4551.1005
    If I edit the path and delete the extra Office\Data Office 365 ProPlus updates from my network location. I cannot figure out why it is adding the extra Office\Data to the path.
    My config file looks like this:
      <Updates Enabled="TRUE" UpdatePath="\\hsbswpush02\GPsoftware\o365\Office\Data" />
    have you tried omitting the \Office\Data element, from the Updates element ?
    http://technet.microsoft.com/en-us/library/jj219426.aspx#BKMK_UpdatesElement
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Error during the migration of Lync 2013 onpremise user to Office 365 Lync

    Hi,
    I am trying to migrate a Lync 2013 onpremise user to Office 365 Lync in a Hybrid environment.
    I am connecting to the Lync server from my machine with the following commands
    $lyncOptions = New-PSSessionOption -SkipRevocationCheck -SkipCACheck -SkipCNCheck
    $lync = New-PSSession -ConnectionUri https://lyncserver/ocspowershell -SessionOption $lyncOptions -Authentication NegotiateWithImplicitCredential
    Import-PSSession $lync
    In the next step I am trying to migrate the user to the Office 365 Lync:
    Move-CsUser -Identity "username" -Target 'sipfed.online.lync.com' -HostedMigrationOverrideUrl 'https://admin1e.online.lync.com/HostedMigration/hostedmigrationservice.svc'
    After that I get a warning message due to to migration to a previous version which I accept.
    WARNING: Moving a user from the current version to an earlier version (or to a service version) can cause data loss.
    Confirm
    Move-CsUser
    [Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): y
    Then I am getting the following error message:
    Can not load Live Id module. Make sure correct version of Live Id Sign-in assistant is installed.
        + CategoryInfo          : NotSpecified: (:) [Move-CsUser], CommonAuthException
        + FullyQualifiedErrorId : Microsoft.Rtc.Admin.Authentication.CommonAuthException,Microsoft.Rtc.Management.AD.Cmdle
       ts.MoveOcsUserCmdlet
        + PSComputerName        : lyncserver
    Tried to Google it but found nothing.
    As far as I can see it is complaining about the Live ID Sign-in assistant, which is installed (the 64bit version) on my computer but not on the remote server. Does it need to be installed on the server as well?
    Thanks for the answers in advance.
    Regards,
    Akos
    Akos_DB

    This error related to reporting services, you need to verify that reporting services is installed on these instances.
    Secondly, you didn't need to create this instance manually then setup monitoring role. delete this instance from shared storage and try again to setup rule using different instance name and it will create automatic on shared storage.
    You can also refer below link
    http://windowspbx.blogspot.com/2012/07/aaa-donotpost-install-lync-standard.html
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

  • Management Pack for Office 365

    Is there Management Pack for Office 365 for Operating Manager 2012 R2/

    Hi,
    Monitoring Office 365 using System Center Operations Manager (SCOM)–Management Pack
    http://www.agileit.com/news/monitoring-office-365-using-system-center-operations-manager-scom-management-pack/
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • I am getting the error Installation came back with 17002 when installing Office 365 ProPlus from a network share

    I have gotten this error several times, but It works fine on most machines
    Here is the most recent example of the log file:
    Timestamp Process TID Area Category EventID Level Message Correlation
    08/08/2014 11:28:29.131 SETUP (0xef8) 0x1964  Click-To-Run amaxp Medium BaseConfigure::TryGetConfiguration: EULA's have been accepted. 
    08/08/2014 11:28:29.134 SETUP (0xef8) 0x1964  Click-To-Run aoh85 Medium AdminConfigure::HandleStateAction: Configuring an install/crosssell scenario. 
    08/08/2014 11:28:29.136 SETUP (0xef8) 0x1964  Click-To-Run aqdco Monitorable TryCheckNetworkCost::HandleStateAction: Failed to initialize NetworkCostManager for http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675.
    Assuming low cost and proceeding. 
    08/08/2014 11:28:29.136 SETUP (0xef8) 0x1964  Click-To-Run aoh9i Medium TryGetVersionDescriptor::HandleStateAction: Getting Cab: v64_15.0.4631.1002.cab 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anwv6 Medium Descriptor::Load: Reading Available value from descriptor: 15.0.4631.1002 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run amawt Medium Descriptor::Load: Prereq Node exists. Being parsing it. 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anwv7 Medium Descriptor::Load: Reading Bootstrapper value from descriptor: 15.0 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run amax8 Medium TryGetVersionDescriptor::HandleStateAction: Descriptor contains Prereqs. Run them now. 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed. 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anwwb Medium IsNativeValidator::CheckPreReq: returning: 1. 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed. 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run an8w1 Medium O15BetaValidator::CheckPreReq: Validator has version descriptor 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run an8w6 Medium O15BetaValidator::CheckPreReq: No Office 15 installation detected. Prereq check passes. 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run an8xa Medium O15BetaValidator::CheckPreReq: returning: 1. 
    08/08/2014 11:28:30.131 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed. 
    08/08/2014 11:28:30.146 SETUP (0xef8) 0x1964  Click-To-Run anwwn Medium SXSValidator::CheckPreReq: Cross bitness test passed. 
    08/08/2014 11:28:30.146 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anwwp Medium BootstrapperValidator::CheckPreReq: returning: 1. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run an8w0 Medium ClientValidator::CheckPreReq: returning: 1. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anwwe Medium DiskSpaceValidator::CheckPreReq: Free disk space is sufficient. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run anhmm Medium Prereq::PrereqsFailed: No prereqs have failed. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run aoh9n Medium TryGetClient::HandleStateAction: Installation path is: C:\Program Files\Microsoft Office 15 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run amaya Medium TryGetClient::HandleStateAction: Looking for existing client. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run amayd Medium TryGetClient::HandleStateAction: Did not find an existing client. Downloading a new one. 
    08/08/2014 11:28:30.147 SETUP (0xef8) 0x1964  Click-To-Run aon8l Medium TryGetClient::HandleStateAction: Getting Cab: i641033.cab 
    08/08/2014 11:28:30.643 SETUP (0xef8) 0x1964  Click-To-Run Telemetry amawv Medium MonitoredScope::ExecuteUnderStopWatch: TryGetClient::HandleStateAction: Getting Cab. Approximate duration: 499 milliseconds. 
    08/08/2014 11:28:30.643 SETUP (0xef8) 0x1964  Click-To-Run amaye Medium TryGetClient::HandleStateAction: Found C2R Client in extracted cab. 
    08/08/2014 11:28:30.643 SETUP (0xef8) 0x1964  Click-To-Run aoh9t Medium TryLaunchClient::HandleStateAction: Launching OfficeClickToRun.exe with parameters: scenario=unknown acceptalleulas="True" cdnbaseurl="http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675"
    productreleaseid="none" culture="en-us" baseurl="http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675" lcid="1033" platform="x64" version="15.0.4631.1002" updatebaseurl="\\server\share\Office365"
    updatesenabled="True" productstoadd="O365ProPlusRetail_en-us_x-none" trackedduration=499 
    08/08/2014 11:41:30.450 SETUP (0xef8) 0x1964  Click-To-Run apx75 Monitorable TryLaunchClient::HandleStateAction: C2R Client returned failing error code 17002 
    08/08/2014 11:41:30.450 SETUP (0xef8) 0x1964  Click-To-Run aoh72 Medium ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0 
    08/08/2014 11:41:30.450 SETUP (0xef8) 0x1964  Click-To-Run aoh9z Medium AdminBootstrapper::Main: Installation came back with 17002. 
    08/08/2014 11:41:30.450 SETUP (0xef8) 0x1964  Logging Liblet aqc99 Medium Logging liblet uninitializing. 
    Anyone have any ideas what is causing it?
    I don't think it is permissions as I have seen on some forums because the share has read/execute permissions for domain users and domain computers

    Hi,
    Are you deploying Office 365 with the latest Office Deployment Tool? Try to download the latest version of ODT from below link, then try again:
    http://www.microsoft.com/en-us/download/details.aspx?id=36778
    A similar issue was resolved here, you might want to have a look:
    http://social.technet.microsoft.com/Forums/en-US/eeb7b577-7868-487a-851d-a6d8c1c6bbda/office-c2r-installation-error-17002?forum=officeitpro
    BTW, Microsoft Office 365 Community > Forums > Deploy Office 365
    is a better source for this kind of problem and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us.
    Thanks,
    Ethan Hua CHN
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • Office 365 Management Pack - SCOM 2007

    Hi All,
    Can anyone please point me to an official link on SCOM 2007 R2 Management Pack for
    Office 365. Just wondering if the below link is the right one which I am reffering to
    http://www.systemcentercentral.com/scom-monitoring-office-365/
    Also, the one which is available for download in "Microsoft Download center" (http://www.microsoft.com/en-ca/download/details.aspx?id=43708)
    is designed for SCOM 2012 family, not for SCOM 2007 R2
    Appreciate your help...
    Faizan

    Although this MP is not the official document on monitoring Office 365 using SCOM 2007 R2, it original came from
    http://blogs.technet.com/b/momteam/archive/2011/07/29/monitoring-office-365-using-operations-manager.aspx which has a higher reputation and reliable source for Microsoft solution. At last, it is high recommend that you should test it on your testing
    environment before roll out to production environment.
    Roger

  • Office 365 files api with php not responding.

    I am trying to access OneDrive for Business using the office 365 rest api. Our code is in php and we can access email, contacts etc fine but the files api doesn't return any kind of response to our requests. We already have a combine access token from
    the consent process. I do get a Unknown SSL protocol error in connection to ... error from curl but thats all. Can anyone help?

    Hi,
    As this question is more relate to Office 365 and PHP development, I suggest you post it to Office 365 or PHP Forum, you will get more help and confirmed answers from there.
    Or use the Fiddler to monitor the requests and responses data.
    http://www.telerik.com/fiddler
    Best Regards
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Announcing new activity logging and reporting capabilities for Office 365

    Announcing new activity logging and reporting capabilities for Office 365We are pleased to announce the rollout of new activity logging and reporting capabilities for Office 365, including the Office 365 activity report, comprehensive logging capability, PowerShell command or cmdlet and a preview of the Office 365 Management Activity API.Thisnew capability provides you increased transparency, allowing you to monitor and investigate actions taken on your data, and comply with laws and regulations.Office 365 activity reportThe Office 365 activity report enables you to investigate a user’s activity by searching for a user, file or other resource across SharePoint Online, One Drive for Business, Exchange Online and Azure Active Directory, and then download the activities to a CSV (comma separate values) file. You can filter by date range,...
    This topic first appeared in the Spiceworks Community

    Hi,
    Do you have any specific questions? We'll certainly try to help you, but we won't do your homework for you. That wouldn't help you learn at all.
    I recommend looking over the learning materials here, they're quite good for getting started with PowerShell:
    http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx
    Don't retire TechNet! -
    (Don't give up yet - 13,085+ strong and growing)

  • Exchange Connector 3.0 not processing Office 365 mailbox

    Hi,
    I have Service Manager 2012 SP1 configured with Exchange Connector 3.0. The mailbox to be monitored is in Office 365. everything was running fine last week until I removed the federation trust and connectors from our On-premise Exchange servers as part of
    the On-premise Exchange server decommissioning process to remove the Exchange Hybrid configuration.
    Now the Exchange Connector does not monitor the mailbox of the configured user in the "run as account", no new incidents are displayed when users sent an email to the run as account. No errors are logged in the Event Viewer for the Exchange Connector.
    Any suggestions?

    Hi,
    Set up the detailed logging and then see in the Operations Manager's log what happens when the Exchange Connector is running.
    Cheers,
    Marat
    Site: www.scutils.com  Twitter:
    LinkedIn:
    Graveyard:

  • Question About Migrating to Office 365

    After a cutover migration from Exchange 2010 to Office 365, what is involved in cancelling the migration and rolling back to the on-premises Exchange 2010?

    Ed is correct, however if you have not already migrated to O365 you might want to test a single mailbox migrating and rolling back as;
    I ran across this post the other day
    https://social.technet.microsoft.com/Forums/exchange/en-US/20c46273-e95d-4836-b2a7-903f649282a6/mailbox-default-settings-restore-possible-?forum=exchange2010
    Of course this could just be a strange anomaly that you will not experience, however its definitely something to watch/tests and of course monitor the link above to see if a resolution is found.
    If you experience the same thing you may want to open a case with MS to resolve
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
    2007 --> 2010 --> 2013 with Lucid8's
    DigiScope

  • Outlook 2010 slow on Office 365

    We have a network with a mix of Outlook 2007, 2010 and 2013 clients.  These were all recently moved from SBS Exchange 2007 to Office 365.
    Some but not all Outlook 2010 clients are experiencing slow performance.  Sending a mail can take up to one minute.  With attachments, the sends can take several minutes.  Clicking on a folder can result in Outlook becoming unresponsive
    for minutes.  This affects users with large and small OST files.
    Outlook 2007 and 2013 users don't seem to be affected.   We have tried creating new profiles and applying MS Updates with no success

    Try to collect the process monitor log when this issue occur.
    Additionally, some users found that this issue disappeared if they turn off their security programs, you may also have a try.
    Flynn

  • Cannot click in search mail and people field using Office 365

    As of this week, four of the users in our school have reported that they cannot click within the search mail field using Office 365. Happens on Macs running 10.8 and 10.9 when using Firefox version 28. When they try using Google Chrome they can use the email search function.
    Is anyone else having this issue? Any ideas? I updated to the latest versions of Flash and Java same result.
    Thank you!

    Hi CT_Dave, I do know that search api can have alot of dom elements on them and that scripts on a page can be prevented from running. However, for Office 365 specifically I do not know what kind of search they have.
    You can monitor the search page by looking in the web console to see if there are any specific errors that may be causing this issue.
    In the about:config, please also make sure javascript is enabled.
    # In the address bar, type "about:config" (with no quotes), and press Enter.
    # Click "I'll be careful, I promise"
    # In the search bar, search for "javascript.enabled" (with no quotes).
    # Right click the result named "javascript.enabled" and click "Toggle". JavaScript is now disabled.
    To Re-enable JavaScript, repeat these steps.

Maybe you are looking for