Microsoft active sysnc

Mixer] => Mixer.exe /startupHKLM\...\Run: [TridTray] => C:\WINDOWS\system32\TridTray.Exe [166400 1999-02-25] () [File not signed]HKU\S-1-5-21-1668751319-4250827956-263943839-1006\...\Run: [WinPatrol] => C:\Program Files\Ruiware\WinPatrol\winpatrol.exe [1231240 2016-11-13] (Ruiware, LLC -> Ruiware)HKU\S-1-5-21-1668751319-4250827956-263943839-1006\...\Run: [HP ENVY 5530 series (NET)] => C:\Program Files\HP\HP ENVY 5530 series\bin\ScanToPCActivationApp.exe [2427400 2014-07-21] (Hewlett Packard -> Hewlett-Packard Development Company, LP)HKU\S-1-5-21-1668751319-4250827956-263943839-1006\...\Run: [ISUSPM] => C:\Program Files\Common Files\InstallShield\UpdateService\ISUSPM.exe [206112 2008-10-24] (Acresso Software Inc. -> Macrovision Corporation)HKU\S-1-5-18\...\RunOnce: [WUAppSetup] => C:\Program Files\Common Files\logishrd\WUApp32.exe [466648 2012-09-21] (Logitech, Inc. -> )HKU\S-1-5-18\...\RunOnce: [FlashPlayerUpdate] => C:\WINDOWS\system32\Macromed\Flash\FlashUtil32_32_0_0_238_pepper.exe -update pepperpluginHKLM\Software\...\AppCompatFlags\Custom\iexplore.exe: [{a9264802-8a7a-40fe-a135-5c6d204aed7a}.sdb] -> Internet Explorer (Enable DEP)HKLM\Software\...\AppCompatFlags\InstalledSDB\{a9264802-8a7a-40fe-a135-5c6d204aed7a}: [DatabasePath] -> C:\WINDOWS\AppPatch\Custom\{a9264802-8a7a-40fe-a135-5c6d204aed7a}.sdb [2011-12-19]HKLM\Software\Microsoft\Active Setup\Installed Components: [ C:\WINDOWS\system32\ieudinit.exe [2009-03-08] (Microsoft Windows -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [>{22d6f312-b0f6-11d0-94ab-0080c74c7e95}] -> C:\WINDOWS\inf\unregmp2.exe [2009-01-30] (Microsoft Windows -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [>{881dd1c5-3dcf-431b-b061-f3f88e8be88a}] -> C:\WINDOWS\system32\shmgrate.exe [2008-04-14] (Microsoft Windows Component Publisher -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [{2179C5D3-EBFF-11CF-B6FD-00AA00B4E220}] -> HKLM\Software\Microsoft\Active Setup\Installed Components: [{22d6f312-b0f6-11d0-94ab-0080c74c7e95}] -> C:\WINDOWS\system32\advpack.dll [2009-03-08] (Microsoft Windows -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [{44BBA840-CC51-11CF-AAFA-00AA00B6015C}] -> C:\Program Files\Outlook Express\setup50.exe [2008-04-14] (Microsoft Windows Component Publisher -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [{44BBA842-CC51-11CF-AAFA-00AA00B6015B}] -> C:\WINDOWS\system32\advpack.dll [2009-03-08] (Microsoft Windows -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [{5945c046-1e7d-11d1-bc44-00c04fd912be}] -> C:\WINDOWS\system32\advpack.dll [2009-03-08] (Microsoft Windows -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [{6BF52A52-394A-11d3-B153-00C04F79FAA6}] -> C:\WINDOWS\system32\advpack.dll [2009-03-08] (Microsoft Windows -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [{73FA19D0-2D75-11D2-995D-00C04F98BBC9}] -> HKLM\Software\Microsoft\Active Setup\Installed Components: [{7790769C-0471-11d2-AF11-00C04FA35D02}] -> C:\Program Files\Outlook Express\setup50.exe [2008-04-14] (Microsoft Windows Component Publisher -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [{8A69D345-D564-463c-AFF1-A69D9E530F96}] -> C:\Program Files\Google\Chrome\Application\49.0.2623.112\Installer\chrmstp.exe [2020-02-27] (Google Inc -> Google Inc.)HKLM\Software\Microsoft\Active Setup\Installed Components: [{8b15971b-5355-4c82-8c07-7e181ea07608}] -> C:\WINDOWS\system32\advpack.dll [2009-03-08] (Microsoft Windows -> Microsoft Corporation)HKLM\Software\Microsoft\Active Setup\Installed Components: [{94de52c8-2d59-4f1b-883e-79663d2d9a8c}] -> HKLM\Software\...\Winlogon\GPExtensions: [{C631DF4C-088F-4156-B058-4375F0853CD8}] -> C:\WINDOWS\System32\cscui.dll [2008-04-14] (Microsoft Windows Component Publisher -> Microsoft Corporation)HKLM\Software\...\Winlogon\GPExtensions: [{c6dc5466-785a-11d2-84d0-00c04fb169f7}] -> appmgmts.dllStartup: C:\Documents and Settings\DAD\Start Menu\Programs\Startup\ZoneAlarm Security.lnk [2017-04-11]ShortcutTarget: ZoneAlarm Security.lnk -> C:\Program Files\CheckPoint\ZoneAlarm\zatray.exe (Check Point Software Technologies Ltd. -> Check Point Software Technologies Ltd.)==================== Scheduled Tasks=============================(If an entry is included in the fixlist, the task (.job) file will be moved. The file which is running by the task will not be moved.)Task: C:\WINDOWS\Tasks\Adobe Flash Player PPAPI Notifier.job => C:\WINDOWS\system32\Macromed\Flash\FlashUtil32_32_0_0_330_pepper.exeTask: C:\WINDOWS\Tasks\Adobe

Entra ID to Active Directory. Tenants such as B2C aren't supported.The group provisioning job is scheduled to run every 20 minutes.Supported scenarios for group writeback with Microsoft Entra Cloud SyncThe following sections describe the supported scenarios for group writeback with Microsoft Entra Cloud Sync.Migrate Microsoft Entra Connect Sync group writeback V2 to Microsoft Entra Cloud SyncGovern on-premises Active Directory based apps (Kerberos) using Microsoft Entra ID GovernanceMigrate Microsoft Entra Connect Sync group writeback V2 to Microsoft Entra Cloud SyncScenario: Migrate group writeback using Microsoft Entra Connect Sync (formerly Azure AD Connect) to Microsoft Entra Cloud Sync. This scenario is only for customers who are currently using Microsoft Entra Connect group writeback v2. The process outlined in this document pertains only to cloud-created security groups that are written back with a universal scope. Mail-enabled groups and DLs written back using Microsoft Entra Connect group writeback V1 or V2 aren't supported.For more information see Migrate Microsoft Entra Connect Sync group writeback V2 to Microsoft Entra Cloud Sync.Govern on-premises Active Directory based apps (Kerberos) using Microsoft Entra ID GovernanceScenario: Manage on-premises applications with Active Directory groups that are provisioned from and managed in the cloud. Microsoft Entra Cloud Sync allows you to fully govern application assignments in AD while taking advantage of Microsoft Entra ID Governance features to control and remediate any access related requests.For more information see Govern on-premises Active Directory based apps (Kerberos) using Microsoft Entra ID Governance .Next stepsProvision groups to Active Directory using Microsoft Entra Cloud SyncGovern on-premises Active Directory based apps (Kerberos) using Microsoft Entra ID GovernanceMigrate Microsoft Entra Connect Sync group writeback V2 to Microsoft Entra Cloud Sync --> Feedback Additional resources In this article

(para clientes y servidores unidos a Windows Server Active Directory)Hacer una copia de seguridad de las contraseñas de cuenta de DSRM en Windows Server Active Directory (para controladores de dominio de Windows Server Active Directory)Hacer una copia de seguridad de las contraseñas de cuenta de administrador local en Windows Server Active Directory mediante Microsoft LAPS heredadoEn cada escenario puede aplicar diferentes configuraciones de directiva.Descripción de las restricciones de estado de unión a dispositivosSi un dispositivo está unido a Microsoft Entra ID o Windows Server Active Directory determina cómo puede usar Windows LAPS.Los dispositivos unidos solo a Microsoft Entra ID solo pueden realizar copias de seguridad de contraseñas en Microsoft Entra ID.Los dispositivos unidos solo a Windows Server Active Directory pueden realizar copias de seguridad de contraseñas solo en Windows Server Active Directory.Los dispositivos unidos híbridos (unidos a Microsoft Entra ID y Windows Server Active Directory) pueden realizar copias de seguridad de sus contraseñas en Microsoft Entra ID o en Windows Server Active Directory. No se pueden realizar copias de seguridad de contraseñas en Microsoft Entra ID y en Windows Server Active Directory.Windows LAPS no admite que se unan clientes al área de trabajo de Microsoft Entra.Establecer la directiva de Windows LAPSPara configurar y administrar la directiva para la implementación de Windows LAPS tiene varias opciones:Proveedor de servicios de configuración (CSP) de Windows LAPSDirectiva de grupo de Windows LAPSMicrosoft LAPS heredadoAdministrar y supervisar Windows LAPSTambién tiene varias opciones para administrar y supervisar Windows LAPS.Entre las opciones para Windows se incluyen:Cuadro de diálogo Propiedades de usuarios y equipos de Windows Server Active DirectoryUn canal de registro de eventos dedicadoUn módulo Windows PowerShell específico para Windows LAPSLas soluciones de informes y supervisión basadas en Azure están disponibles al realizar copias de seguridad de contraseñas en Microsoft Entra ID.Entrada en desuso del producto de Microsoft LAPS heredadoImportanteNOTA: El producto de Microsoft LAPS heredado está en desuso a partir de Windows 11 23 H2 y versiones posteriores. La instalación del paquete MSI de Microsoft LAPS heredado está bloqueada en versiones más recientes del sistema operativo y Microsoft ya no tendrá en cuenta los cambios de código para el producto de Microsoft LAPS heredado.Use Windows LAPS, disponible en Windows Server 2019 y versiones posteriores, y en clientes Windows 10 y Windows 11 compatibles, para administrar contraseñas de cuenta de administrador local.Microsoft seguirá admitiendo el producto de Microsoft LAPS heredado en versiones antiguas de Windows (anteriores a Windows 11 23 H2) en las que ya era compatible. Esa compatibilidad finalizará al final normal del soporte técnico para esos sistemas operativos.Windows LAPS vs. Microsoft LAPS heredadoWindows LAPS hereda muchos conceptos de diseño de Microsoft LAPS heredado. Si está familiarizado con Microsoft LAPS heredado, muchas características de Windows LAPS le serán familiares. Una diferencia clave es que Windows LAPS es una implementación totalmente independiente que es nativa de Windows. Windows LAPS también agrega muchas características que no están disponibles en Microsoft LAPS heredado. Puede usar Windows LAPS para realizar copias de seguridad de contraseñas en Azure Active Directory, cifrar

High (>{$MS.EXCHANGE.DB.FAULTS.WARN} for {$MS.EXCHANGE.DB.FAULTS.TIME})Too much page faults stalls for database "{#INSTANCE}". This counter should be 0 on production servers.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database({#INF.STORE})\Database Page Fault Stalls/sec", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.FAULTS.TIME})>{$MS.EXCHANGE.DB.FAULTS.WARN}AVERAGEInformation Store [{#INSTANCE}]: Log records stalls is too high (>{$MS.EXCHANGE.LOG.STALLS.WARN} for {$MS.EXCHANGE.LOG.STALLS.TIME})Stalled log records too high. The average value should be less than 10 threads waiting.avg(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database({#INF.STORE})\Log Record Stalls/sec", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.LOG.STALLS.TIME})>{$MS.EXCHANGE.LOG.STALLS.WARN}AVERAGEInformation Store [{#INSTANCE}]: RPC Requests latency is too high (>{$MS.EXCHANGE.RPC.WARN}s for {$MS.EXCHANGE.RPC.TIME})Should be less than 50ms at all times, with spikes less than 100ms.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchangeIS Store({#INSTANCE})\RPC Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.RPC.TIME})>{$MS.EXCHANGE.RPC.WARN}WARNINGInformation Store [{#INSTANCE}]: RPC Requests total count is too high (>{$MS.EXCHANGE.RPC.COUNT.WARN} for {$MS.EXCHANGE.RPC.COUNT.TIME})Should be below 70 at all times.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchangeIS Store({#INSTANCE})\RPC requests", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.RPC.COUNT.TIME})>{$MS.EXCHANGE.RPC.COUNT.WARN}WARNINGDatabase Counters [{#INSTANCE}]: Average read time latency is too high (>{$MS.EXCHANGE.DB.ACTIVE.READ.WARN}s for {$MS.EXCHANGE.DB.ACTIVE.READ.TIME})Should be less than 20ms on average.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Reads (Attached) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.ACTIVE.READ.TIME})>{$MS.EXCHANGE.DB.ACTIVE.READ.WARN}WARNINGDatabase Counters [{#INSTANCE}]: Average read time latency is too high (>{$MS.EXCHANGE.DB.PASSIVE.READ.WARN}s for {$MS.EXCHANGE.DB.PASSIVE.READ.TIME})Should be less than 200ms on average.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Reads (Recovery) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.PASSIVE.READ.TIME})>{$MS.EXCHANGE.DB.PASSIVE.READ.WARN}WARNINGDatabase Counters [{#INSTANCE}]: Average write time latency is too high for {$MS.EXCHANGE.DB.ACTIVE.WRITE.TIME}Should be less than 50ms on average.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Writes (Attached) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.ACTIVE.WRITE.TIME})>{$MS.EXCHANGE.DB.ACTIVE.WRITE.WARN}WARNINGDatabase Counters [{#INSTANCE}]: Average write time latency is higher than read time latency for {$MS.EXCHANGE.DB.PASSIVE.WRITE.TIME}Should be less than the read latency for the same instance, as measured by the MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Reads (Recovery) Average Latency counter.avg(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Writes (Recovery) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.PASSIVE.WRITE.TIME})>avg(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Reads (Recovery) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.PASSIVE.WRITE.TIME})WARNINGDomain Controller [{#INSTANCE}]: LDAP read time is too high (>{$MS.EXCHANGE.LDAP.WARN}s for {$MS.EXCHANGE.LDAP.TIME})Should be less than 50ms at all times, with spikes less than 100ms.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange ADAccess Domain Controllers({#INSTANCE})\LDAP Read Time", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.LDAP.TIME})>{$MS.EXCHANGE.LDAP.WARN}AVERAGEDomain Controller [{#INSTANCE}]: LDAP search time is too high (>{$MS.EXCHANGE.LDAP.WARN}s for {$MS.EXCHANGE.LDAP.TIME})Should be less than 50ms at all times, with spikes less than 100ms.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange ADAccess Domain Controllers({#INSTANCE})\LDAP Search Time", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.LDAP.TIME})>{$MS.EXCHANGE.LDAP.WARN}AVERAGEFeedbackPlease report any issues with the template at can also provide a feedback, discuss the template or ask for help with it at ZABBIX forums. This template is for Zabbix version: 5.0 Source: Template App Microsoft Exchange Server 2016 by Zabbix agent activeOverviewFor Zabbix version: 5.0 and higherOfficial Template for Microsoft Exchange Server 2016.This template was tested on:Microsoft Exchange Server, version 2016 CU18Zabbix, version 5.0SetupSee Zabbix template operation for basic instructions.Metrics are collected by Zabbix agent active.1. Import the

Less than 50ms at all times, with spikes less than 100ms.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchangeIS Store({#INSTANCE})\RPC Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.RPC.TIME})>{$MS.EXCHANGE.RPC.WARN}WARNINGInformation Store [{#INSTANCE}]: RPC Requests total count is too highShould be below 70 at all times.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchangeIS Store({#INSTANCE})\RPC requests", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.RPC.COUNT.TIME})>{$MS.EXCHANGE.RPC.COUNT.WARN}WARNINGDatabase Counters [{#INSTANCE}]: Average read time latency is too highShould be less than 20ms on average.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Reads (Attached) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.ACTIVE.READ.TIME})>{$MS.EXCHANGE.DB.ACTIVE.READ.WARN}WARNINGDatabase Counters [{#INSTANCE}]: Average read time latency is too highShould be less than 200ms on average.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Reads (Recovery) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.PASSIVE.READ.TIME})>{$MS.EXCHANGE.DB.PASSIVE.READ.WARN}WARNINGDatabase Counters [{#INSTANCE}]: Average write time latency is too high for {$MS.EXCHANGE.DB.ACTIVE.WRITE.TIME}Should be less than 50ms on average.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Writes (Attached) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.ACTIVE.WRITE.TIME})>{$MS.EXCHANGE.DB.ACTIVE.WRITE.WARN}WARNINGDatabase Counters [{#INSTANCE}]: Average write time latency is higher than read time latency for {$MS.EXCHANGE.DB.PASSIVE.WRITE.TIME}Should be less than the read latency for the same instance, as measured by the MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Reads (Recovery) Average Latency counter.avg(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Writes (Recovery) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.PASSIVE.WRITE.TIME})>avg(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange Database ==> Instances({#INF.STORE}/_Total)\I/O Database Reads (Recovery) Average Latency", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.DB.PASSIVE.WRITE.TIME})WARNINGDomain Controller [{#INSTANCE}]: LDAP read time is too highShould be less than 50ms at all times, with spikes less than 100ms.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange ADAccess Domain Controllers({#INSTANCE})\LDAP Read Time", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.LDAP.TIME})>{$MS.EXCHANGE.LDAP.WARN}AVERAGEDomain Controller [{#INSTANCE}]: LDAP search time is too highShould be less than 50ms at all times, with spikes less than 100ms.min(/Microsoft Exchange Server 2016 by Zabbix agent active/perf_counter_en["\MSExchange ADAccess Domain Controllers({#INSTANCE})\LDAP Search Time", {$MS.EXCHANGE.PERF.INTERVAL}],{$MS.EXCHANGE.LDAP.TIME})>{$MS.EXCHANGE.LDAP.WARN}AVERAGEFeedbackPlease report any issues with the template at can also provide feedback, discuss the template or ask for help with it at ZABBIX forums. This template is for Zabbix version: 6.0 Source: Microsoft Exchange Server 2016 by Zabbix agent activeOverviewOfficial Template for Microsoft Exchange Server 2016.RequirementsZabbix version: 6.0 and higher.Tested versionsThis template has been tested on:Microsoft Exchange Server 2016 CU18ConfigurationZabbix should be configured according to the instructions in the Templates out of the box section.SetupMetrics are collected by Zabbix agent active.1. Import the template into Zabbix.2. Link the imported template to a host with MS Exchange.Note that template doesn't provide information about Windows services state. Recommended to use it with "OS Windows by Zabbix agent active" template.Macros usedNameDescriptionDefault{$MS.EXCHANGE.PERF.INTERVAL}Update interval for perf_counter_en items.60{$MS.EXCHANGE.DB.FAULTS.TIME}The time during which the database page faults may exceed the threshold.5m{$MS.EXCHANGE.DB.FAULTS.WARN}Threshold for database page faults trigger.0{$MS.EXCHANGE.LOG.STALLS.TIME}The time during which the log records stalled may exceed the threshold.10m{$MS.EXCHANGE.LOG.STALLS.WARN}Threshold for log records stalled trigger.100{$MS.EXCHANGE.DB.ACTIVE.READ.TIME}The time during which the active database read operations latency may exceed the threshold.5m{$MS.EXCHANGE.DB.ACTIVE.READ.WARN}Threshold for active database read operations latency

Unified CallManager 5.0(4)، يتوفر المستند على بالنسبة ل Microsoft Office Communication Server 2007 Enterprise Edition المزود بحزمة الخدمة SP1 إلى Cisco Unified Presence 6.0(1) و Cisco Unified Communications Manager 6.0(1)، يتوفر المستند على للحصول على Microsoft Office Communicator 2007، ارجع إلى دليل نشر Microsoft Office Communicator 2007. للحصول على Microsoft Office Communications Server 2007، ارجع إلى دليل إدارة Microsoft Office Communications Server 2007 للحصول على معلومات التكوين. للحصول على وثائق Microsoft Office Communications Server إضافية، ارجع إلى Office Communications Server. إختبار التكامل: قم بتكوين Microsoft Office Communicator لاستخدام هاتف بروتوكول الإنترنت الموحد من Cisco. أستخدم Microsoft Office Communicator للاتصال بهاتف مستخدم آخر. تأكد من أن Microsoft Office Communicator يستخدم هاتف بروتوكول الإنترنت الموحد من Cisco بشكل صحيح. الوصول إلى البريد الصوتي ل Microsoft Office Communicator لا تحتوي لوحة الطلب الموجودة في عميل Microsoft Office Communicator على مفتاح للوصول المباشر إلى البريد الصوتي. ومع ذلك، يمكنك محاكاة الوصول إلى البريد الصوتي بنقرة واحدة عن طريق تكوين مستخدم بريد صوتي عام في Active Directory و Live Communications Server 2005 أو Office Communications Server 2007، وجعل المستخدمين يضيفون هذا المستخدم كجهة اتصال في Microsoft Office Communicator. ويمكن للمستخدمين بعد ذلك إستخدام النقر للاتصال للاتصال بجهة الاتصال للوصول إلى البريد الصوتي. تكوين مستخدم البريد الصوتي العام في Active Directory لمحاكاة الوصول بنقرة واحدة إلى البريد الصوتي في Microsoft Office Communicator، قم بتكوين مستخدم بريد صوتي عام في Active Directory. ملاحظة: إذا تمكن المستخدمون من الوصول إلى البريد الصوتي الخاص بهم باستخدام أرقام تجريبية مختلفة، فيجب عليك إنشاء مستخدم عام منفصل في خدمة Active Directory لكل رقم تجريبي، وإبلاغ المستخدمين بهوية مستخدم البريد الصوتي العام الذي سيتم إضافته كجهة اتصال في Microsoft Office Communicator. في Active Directory، قم بإنشاء مستخدم باستخدام الإعدادات التالية: اسم الحقل إدخال الاسم الأول الصوت اسم العائلة البريد اسم العرض البريد الصوتي رقم الهاتف انقر فوق علامة التبويب إتصالات مباشرة ل