.1724 12:06:19 (0) ** WMIDiag v2.2 started on mercredi 11 novembre 2015 at 12:06. .1725 12:06:19 (0) ** .1726 12:06:19 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007. .1727 12:06:19 (0) ** .1728 12:06:19 (0) ** This script is not supported under any Microsoft standard support program or service. .1729 12:06:19 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all .1730 12:06:19 (0) ** implied warranties including, without limitation, any implied warranties of merchantability .1731 12:06:19 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance .1732 12:06:19 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors, .1733 12:06:19 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for .1734 12:06:19 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits, .1735 12:06:19 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of .1736 12:06:19 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised .1737 12:06:19 (0) ** of the possibility of such damages. .1738 12:06:19 (0) ** .1739 12:06:19 (0) ** .1740 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .1741 12:06:19 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ---------------------------------------------------------- .1742 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .1743 12:06:19 (0) ** .1744 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .1745 12:06:19 (0) ** Windows Vista - Service pack 2 - 32-bit (6002) - User 'PC-DE-CLIENT\ADMINISTRATEUR' on computer 'PC-DE-CLIENT'. .1746 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .1747 12:06:19 (0) ** Environment: ........................................................................................................ OK. .1748 12:06:19 (0) ** There are no missing WMI system files: .............................................................................. OK. .1749 12:06:19 (0) ** There are no missing WMI repository files: .......................................................................... OK. .1750 12:06:19 (0) ** WMI repository state: ............................................................................................... N/A. .1751 12:06:19 (0) ** AFTER running WMIDiag: .1752 12:06:19 (0) ** The WMI repository has a size of: ................................................................................... 29 MB. .1753 12:06:19 (0) ** - Disk free space on 'C:': .......................................................................................... 21107 MB. .1754 12:06:19 (0) ** - INDEX.BTR, 3506176 bytes, 07/11/2015 10:29:33 .1755 12:06:19 (0) ** - MAPPING1.MAP, 82312 bytes, 07/11/2015 10:29:33 .1756 12:06:19 (0) ** - MAPPING2.MAP, 82312 bytes, 07/11/2015 09:59:32 .1757 12:06:19 (0) ** - OBJECTS.DATA, 26804224 bytes, 07/11/2015 10:29:33 .1758 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .1759 12:06:19 (2) !! WARNING: Windows Firewall Service: .................................................................................. STOPPED. .1760 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .1761 12:06:19 (0) ** DCOM Status: ........................................................................................................ OK. .1762 12:06:19 (1) !! ERROR: WMI registry setup: .......................................................................................... DISABLED! .1763 12:06:19 (0) ** => The WMI service automatic startup is DISABLED! .1764 12:06:19 (0) ** - It is a best practice for manageability purposes to start .1765 12:06:19 (0) ** the WMI service at computer startup (automactic startup). .1766 12:06:19 (0) ** => The service startup state can be changed with the SERVICES MMC snap-in. .1767 12:06:19 (0) ** or with the the command: .1768 12:06:19 (0) ** i.e. 'SC.EXE CONFIG WINMGMT START= AUTO' .1769 12:06:19 (0) ** Note: The SC.EXE command is available in the Windows Resource Kit. .1770 12:06:19 (0) ** => You can also check the registry key setup further in this report. .1771 12:06:19 (0) ** .1772 12:06:19 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)! .1773 12:06:19 (0) ** - Security Center (WSCSVC, StartMode='Disabled') .1774 12:06:19 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled') .1775 12:06:19 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well. .1776 12:06:19 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but .1777 12:06:19 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped, .1778 12:06:19 (0) ** this can prevent the service/application to work as expected. .1779 12:06:19 (0) ** .1780 12:06:19 (0) ** RPCSS service: ...................................................................................................... OK (Already started). .1781 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .1782 12:06:19 (0) ** WMI service DCOM setup: ............................................................................................. OK. .1783 12:06:19 (0) ** WMI components DCOM registrations: .................................................................................. OK. .1784 12:06:19 (0) ** WMI ProgID registrations: ........................................................................................... OK. .1785 12:06:19 (0) ** WMI provider DCOM registrations: .................................................................................... OK. .1786 12:06:19 (0) ** WMI provider CIM registrations: ..................................................................................... OK. .1787 12:06:19 (0) ** WMI provider CLSIDs: ................................................................................................ OK. .1788 12:06:19 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK. .1789 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .1790 12:06:19 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED. .1791 12:06:19 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context. .1792 12:06:19 (0) ** i.e. You can start your scripts or WMIC commands from an elevated command .1793 12:06:19 (0) ** prompt by right clicking on the 'Command Prompt' icon in the Start Menu and .1794 12:06:19 (0) ** selecting 'Run as Administrator'. .1795 12:06:19 (0) ** i.e. You can also execute the WMI scripts or WMIC commands as a task .1796 12:06:19 (0) ** in the Task Scheduler within the right security context. .1797 12:06:19 (0) ** .1798 12:06:19 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED. .1799 12:06:19 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative .1800 12:06:19 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer .1801 12:06:19 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote .1802 12:06:19 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group. .1803 12:06:19 (0) ** .1804 12:06:19 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED. .1805 12:06:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED! .1806 12:06:19 (0) ** - REMOVED ACE: .1807 12:06:19 (0) ** ACEType: &h0 .1808 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1809 12:06:19 (0) ** ACEFlags: &h0 .1810 12:06:19 (0) ** ACEMask: &h3 .1811 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1812 12:06:19 (0) ** DCOM_RIGHT_ACCESS_LOCAL .1813 12:06:19 (0) ** .1814 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1815 12:06:19 (0) ** Removing default security will cause some operations to fail! .1816 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1817 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1818 12:06:19 (0) ** .1819 12:06:19 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED. .1820 12:06:19 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED! .1821 12:06:19 (0) ** - REMOVED ACE: .1822 12:06:19 (0) ** ACEType: &h0 .1823 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1824 12:06:19 (0) ** ACEFlags: &h0 .1825 12:06:19 (0) ** ACEMask: &h7 .1826 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1827 12:06:19 (0) ** DCOM_RIGHT_ACCESS_LOCAL .1828 12:06:19 (0) ** DCOM_RIGHT_ACCESS_REMOTE .1829 12:06:19 (0) ** .1830 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1831 12:06:19 (0) ** Removing default security will cause some operations to fail! .1832 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1833 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1834 12:06:19 (0) ** .1835 12:06:19 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED. .1836 12:06:19 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED! .1837 12:06:19 (0) ** - REMOVED ACE: .1838 12:06:19 (0) ** ACEType: &h0 .1839 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1840 12:06:19 (0) ** ACEFlags: &h0 .1841 12:06:19 (0) ** ACEMask: &h7 .1842 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1843 12:06:19 (0) ** DCOM_RIGHT_ACCESS_LOCAL .1844 12:06:19 (0) ** DCOM_RIGHT_ACCESS_REMOTE .1845 12:06:19 (0) ** .1846 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1847 12:06:19 (0) ** Removing default security will cause some operations to fail! .1848 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1849 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1850 12:06:19 (0) ** .1851 12:06:19 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED. .1852 12:06:19 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED! .1853 12:06:19 (0) ** - REMOVED ACE: .1854 12:06:19 (0) ** ACEType: &h0 .1855 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1856 12:06:19 (0) ** ACEFlags: &h0 .1857 12:06:19 (0) ** ACEMask: &h1F .1858 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1859 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .1860 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .1861 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .1862 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .1863 12:06:19 (0) ** .1864 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1865 12:06:19 (0) ** Removing default security will cause some operations to fail! .1866 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1867 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1868 12:06:19 (0) ** .1869 12:06:19 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED. .1870 12:06:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED! .1871 12:06:19 (0) ** - REMOVED ACE: .1872 12:06:19 (0) ** ACEType: &h0 .1873 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1874 12:06:19 (0) ** ACEFlags: &h0 .1875 12:06:19 (0) ** ACEMask: &h1F .1876 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1877 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .1878 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .1879 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .1880 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .1881 12:06:19 (0) ** .1882 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1883 12:06:19 (0) ** Removing default security will cause some operations to fail! .1884 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1885 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1886 12:06:19 (0) ** .1887 12:06:19 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED. .1888 12:06:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED! .1889 12:06:19 (0) ** - REMOVED ACE: .1890 12:06:19 (0) ** ACEType: &h0 .1891 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1892 12:06:19 (0) ** ACEFlags: &h0 .1893 12:06:19 (0) ** ACEMask: &h1F .1894 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1895 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .1896 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .1897 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .1898 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .1899 12:06:19 (0) ** .1900 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1901 12:06:19 (0) ** Removing default security will cause some operations to fail! .1902 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1903 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1904 12:06:19 (0) ** .1905 12:06:19 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED. .1906 12:06:19 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED! .1907 12:06:19 (0) ** - REMOVED ACE: .1908 12:06:19 (0) ** ACEType: &h0 .1909 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1910 12:06:19 (0) ** ACEFlags: &h0 .1911 12:06:19 (0) ** ACEMask: &h1F .1912 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1913 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .1914 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .1915 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .1916 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .1917 12:06:19 (0) ** .1918 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1919 12:06:19 (0) ** Removing default security will cause some operations to fail! .1920 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1921 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1922 12:06:19 (0) ** .1923 12:06:19 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED. .1924 12:06:19 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED! .1925 12:06:19 (0) ** - REMOVED ACE: .1926 12:06:19 (0) ** ACEType: &h0 .1927 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1928 12:06:19 (0) ** ACEFlags: &h0 .1929 12:06:19 (0) ** ACEMask: &h1F .1930 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1931 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .1932 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .1933 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .1934 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .1935 12:06:19 (0) ** .1936 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1937 12:06:19 (0) ** Removing default security will cause some operations to fail! .1938 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1939 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1940 12:06:19 (0) ** .1941 12:06:19 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED. .1942 12:06:19 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED! .1943 12:06:19 (0) ** - REMOVED ACE: .1944 12:06:19 (0) ** ACEType: &h0 .1945 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1946 12:06:19 (0) ** ACEFlags: &h0 .1947 12:06:19 (0) ** ACEMask: &hB .1948 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1949 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .1950 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .1951 12:06:19 (0) ** .1952 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1953 12:06:19 (0) ** Removing default security will cause some operations to fail! .1954 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1955 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1956 12:06:19 (0) ** .1957 12:06:19 (0) ** DCOM security for 'Windows Management Instrumentation' (Launch & Activation Permissions): ........................... MODIFIED. .1958 12:06:19 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED! .1959 12:06:19 (0) ** - REMOVED ACE: .1960 12:06:19 (0) ** ACEType: &h0 .1961 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1962 12:06:19 (0) ** ACEFlags: &h0 .1963 12:06:19 (0) ** ACEMask: &h1F .1964 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1965 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .1966 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .1967 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .1968 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .1969 12:06:19 (0) ** .1970 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1971 12:06:19 (0) ** Removing default security will cause some operations to fail! .1972 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1973 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1974 12:06:19 (0) ** .1975 12:06:19 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED. .1976 12:06:19 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED! .1977 12:06:19 (0) ** - REMOVED ACE: .1978 12:06:19 (0) ** ACEType: &h0 .1979 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1980 12:06:19 (0) ** ACEFlags: &h0 .1981 12:06:19 (0) ** ACEMask: &h1F .1982 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .1983 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .1984 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .1985 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .1986 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .1987 12:06:19 (0) ** .1988 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .1989 12:06:19 (0) ** Removing default security will cause some operations to fail! .1990 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .1991 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .1992 12:06:19 (0) ** .1993 12:06:19 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED. .1994 12:06:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED! .1995 12:06:19 (0) ** - REMOVED ACE: .1996 12:06:19 (0) ** ACEType: &h0 .1997 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .1998 12:06:19 (0) ** ACEFlags: &h0 .1999 12:06:19 (0) ** ACEMask: &h1F .2000 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .2001 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .2002 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .2003 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .2004 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .2005 12:06:19 (0) ** .2006 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .2007 12:06:19 (0) ** Removing default security will cause some operations to fail! .2008 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .2009 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .2010 12:06:19 (0) ** .2011 12:06:19 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED. .2012 12:06:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED! .2013 12:06:19 (0) ** - REMOVED ACE: .2014 12:06:19 (0) ** ACEType: &h0 .2015 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .2016 12:06:19 (0) ** ACEFlags: &h0 .2017 12:06:19 (0) ** ACEMask: &h1F .2018 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .2019 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .2020 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .2021 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .2022 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .2023 12:06:19 (0) ** .2024 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .2025 12:06:19 (0) ** Removing default security will cause some operations to fail! .2026 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .2027 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .2028 12:06:19 (0) ** .2029 12:06:19 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED. .2030 12:06:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED! .2031 12:06:19 (0) ** - REMOVED ACE: .2032 12:06:19 (0) ** ACEType: &h0 .2033 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .2034 12:06:19 (0) ** ACEFlags: &h0 .2035 12:06:19 (0) ** ACEMask: &h1F .2036 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .2037 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .2038 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .2039 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .2040 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .2041 12:06:19 (0) ** .2042 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .2043 12:06:19 (0) ** Removing default security will cause some operations to fail! .2044 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .2045 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .2046 12:06:19 (0) ** .2047 12:06:19 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED. .2048 12:06:19 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED! .2049 12:06:19 (0) ** - REMOVED ACE: .2050 12:06:19 (0) ** ACEType: &h0 .2051 12:06:19 (0) ** ACCESS_ALLOWED_ACE_TYPE .2052 12:06:19 (0) ** ACEFlags: &h0 .2053 12:06:19 (0) ** ACEMask: &h1F .2054 12:06:19 (0) ** DCOM_RIGHT_EXECUTE .2055 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_LOCAL .2056 12:06:19 (0) ** DCOM_RIGHT_LAUNCH_REMOTE .2057 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL .2058 12:06:19 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE .2059 12:06:19 (0) ** .2060 12:06:19 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee. .2061 12:06:19 (0) ** Removing default security will cause some operations to fail! .2062 12:06:19 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE. .2063 12:06:19 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'. .2064 12:06:19 (0) ** .2065 12:06:19 (0) ** .2066 12:06:19 (0) ** DCOM security warning(s) detected: .................................................................................. 0. .2067 12:06:19 (0) ** DCOM security error(s) detected: .................................................................................... 15. .2068 12:06:19 (0) ** WMI security warning(s) detected: ................................................................................... 0. .2069 12:06:19 (0) ** WMI security error(s) detected: ..................................................................................... 0. .2070 12:06:19 (0) ** .2071 12:06:19 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR! .2072 12:06:19 (0) ** Overall WMI security status: ........................................................................................ OK. .2073 12:06:19 (0) ** - Started at 'Root' -------------------------------------------------------------------------------------------------------------- .2074 12:06:19 (0) ** WMI permanent SUBSCRIPTION(S): ...................................................................................... NONE. .2075 12:06:19 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE. .2076 12:06:19 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)! .2077 12:06:19 (0) ** - Root, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2078 12:06:19 (0) ** .2079 12:06:19 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)! .2080 12:06:19 (0) ** - Root, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2081 12:06:19 (0) ** - Root, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2082 12:06:19 (0) ** - Root/subscription, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2083 12:06:19 (0) ** - Root/DEFAULT, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2084 12:06:19 (0) ** - Root/CIMV2, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2085 12:06:19 (0) ** - Root/CIMV2/Security, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2086 12:06:19 (0) ** - Root/CIMV2/Applications, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2087 12:06:19 (0) ** - Root/nap, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2088 12:06:19 (0) ** - Root/SECURITY, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2089 12:06:19 (0) ** - Root/WMI, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2090 12:06:19 (0) ** - Root/directory, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2091 12:06:19 (0) ** - Root/directory/LDAP, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2092 12:06:19 (0) ** - Root/SecurityCenter, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2093 12:06:19 (0) ** - Root/Microsoft, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2094 12:06:19 (0) ** - Root/Microsoft/HomeNet, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2095 12:06:19 (0) ** - Root/aspnet, 0x80070422 - Le service ne peut pas être démarré parce qu'il est désactivé ou qu'aucun périphérique activé ne lui est associé.. .2096 12:06:19 (0) ** .2097 12:06:19 (0) ** WMI GET operations: ................................................................................................. OK. .2098 12:06:19 (0) ** WMI MOF representations: ............................................................................................ OK. .2099 12:06:19 (0) ** WMI QUALIFIER access operations: .................................................................................... OK. .2100 12:06:19 (0) ** WMI ENUMERATION operations: ......................................................................................... OK. .2101 12:06:19 (0) ** WMI EXECQUERY operations: ........................................................................................... OK. .2102 12:06:19 (0) ** WMI GET VALUE operations: ........................................................................................... OK. .2103 12:06:19 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED. .2104 12:06:19 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED. .2105 12:06:19 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED. .2106 12:06:19 (0) ** WMI static instances retrieved: ..................................................................................... 0. .2107 12:06:19 (0) ** WMI dynamic instances retrieved: .................................................................................... 0. .2108 12:06:19 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0. .2109 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .2110 12:06:19 (0) ** .2111 12:06:19 (0) ** 17 error(s) 0x80070422 - (WBEM_UNKNOWN) This error code is external to WMI. .2112 12:06:19 (0) ** => Errors starting with 0x8007 are Win32 errors, NOT WMI errors. More information can be found .2113 12:06:19 (0) ** with the 'NET.EXE HELPMSG ' command, where is the last four hex digits (0x0422) .2114 12:06:19 (0) ** converted in decimal (1058). .2115 12:06:19 (0) ** - NET HELPMSG 1058 .2116 12:06:19 (0) ** .2117 12:06:19 (0) ** ---------------------------------------------------------------------------------------------------------------------------------- .2118 12:06:19 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 2 KEY(S)! .2119 12:06:19 (1) !! ERROR: Unexpected registry key value: .2120 12:06:19 (0) ** - Current: HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Start (REG_DWORD) -> &h4 .2121 12:06:19 (0) ** - Expected: HKLM\SYSTEM\CurrentControlSet\Services\winmgmt\Start (REG_DWORD) -> &h2 .2122 12:06:19 (0) ** From the command line, the registry configuration can be corrected with the following command: .2123 12:06:19 (0) ** i.e. 'REG.EXE Add "HKLM\SYSTE