Picking up but not scanning

[esullivan]

Got lansweeper installed yesterday, got the VBS script in our GP, when people login it IS adding them, however they are staying in the "never scanned" section. I try to "trigger" scan, but it still won't. Our Windows firewall is off (had that problem in my test domain LOL). I went into the console and changed the trigger scan action from "myserver" to "the actual name of our server", still nothing.

What am I doing wrong?

[Hemoco]

This is what you should change :

DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19973 09:00:11 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
19974 09:00:11 (0) **        - REMOVED ACE:
19975 09:00:11 (0) **          ACEType:  &h0
19976 09:00:11 (0) **                    ACCESS_ALLOWED_ACE_TYPE
19977 09:00:11 (0) **          ACEFlags: &h0
19978 09:00:11 (0) **          ACEMask:  &h1
19979 09:00:11 (0) **                    DCOM_RIGHT_EXECUTE
19980 09:00:11 (0) **
19981 09:00:11 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19982 09:00:11 (0) **    Removing default security will cause some operations to fail!
19983 09:00:11 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
19984 09:00:11 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19985 09:00:11 (0) **
19986 09:00:11 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19987 09:00:11 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
19988 09:00:11 (0) **        - REMOVED ACE:
19989 09:00:11 (0) **          ACEType:  &h0
19990 09:00:11 (0) **                    ACCESS_ALLOWED_ACE_TYPE
19991 09:00:11 (0) **          ACEFlags: &h0
19992 09:00:11 (0) **          ACEMask:  &h1
19993 09:00:11 (0) **                    DCOM_RIGHT_EXECUTE
19994 09:00:11 (0) **
19995 09:00:11 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19996 09:00:11 (0) **    Removing default security will cause some operations to fail!
19997 09:00:11 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
19998 09:00:11 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19999 09:00:11 (0) **
20000 09:00:11 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
20001 09:00:11 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
20002 09:00:11 (0) **        - REMOVED ACE:
20003 09:00:11 (0) **          ACEType:  &h0
20004 09:00:11 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20005 09:00:11 (0) **          ACEFlags: &h0
20006 09:00:11 (0) **          ACEMask:  &h1
20007 09:00:11 (0) **                    DCOM_RIGHT_EXECUTE
20008 09:00:11 (0) **
20009 09:00:11 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20010 09:00:11 (0) **    Removing default security will cause some operations to fail!
20011 09:00:11 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
20012 09:00:11 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.

run DCOMCNFG.EXE on the computer and check the security.

[Hemoco]

With which account is your service running?

[esullivan]

Lansweeper wrote:
With which account is your service running?

A domain admin account.

[Hemoco]

Could you post your errorlog.txt file please.
When you click on the computer, do you see anything in the error tab?

[esullivan]

Lansweeper wrote:
Could you post your errorlog.txt file please.
When you click on the computer, do you see anything in the error tab?

2/17/2009 3:59:54 PM : Database connection successful, starting up service

Yes ALL of my PC's are getting:

Wmierror Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) BAASCANNER2 (10.26.222.96) 2/18/2009 10:09:57 AM

I have looked at the support link to fix that, but all the settings are correct. I have tried to use the WMIdiag but it's very confusing.

19899 09:00:11 (0) ** WMIDiag v2.0 started on Wednesday, February 18, 2009 at 08:57.
19900 09:00:11 (0) ** 
19901 09:00:11 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
19902 09:00:11 (0) ** 
19903 09:00:11 (0) ** This script is not supported under any Microsoft standard support program or service.
19904 09:00:11 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
19905 09:00:11 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
19906 09:00:11 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
19907 09:00:11 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
19908 09:00:11 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
19909 09:00:11 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
19910 09:00:11 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
19911 09:00:11 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
19912 09:00:11 (0) ** of the possibility of such damages.
19913 09:00:11 (0) ** 
19914 09:00:11 (0) ** 
19915 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19916 09:00:11 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
19917 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19918 09:00:11 (0) ** 
19919 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19920 09:00:11 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'BROADWAY\ESULLIVAN' on computer 'ESULLIVANLAP'.
19921 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19922 09:00:11 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
19923 09:00:11 (0) ** INFO: => 1 incorrect shutdown(s) detected on:
19924 09:00:11 (0) **          - Shutdown on 23 December 2008 15:17:25 (GMT+6).
19925 09:00:11 (0) ** 
19926 09:00:11 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
19927 09:00:11 (0) ** Drive type: ......................................................................................................... IDE (VMware Virtual IDE Hard Drive).
19928 09:00:11 (0) ** There are no missing WMI system files: .............................................................................. OK.
19929 09:00:11 (0) ** There are no missing WMI repository files: .......................................................................... OK.
19930 09:00:11 (0) ** WMI repository state: ............................................................................................... N/A.
19931 09:00:11 (0) ** BEFORE running WMIDiag:
19932 09:00:11 (0) ** The WMI repository has a size of: ................................................................................... 8 MB.
19933 09:00:11 (0) ** - Disk free space on 'C:': .......................................................................................... 1198 MB.
19934 09:00:11 (0) **   - INDEX.BTR,                     1392640 bytes,      2/18/2009 7:50:58 AM
19935 09:00:11 (0) **   - INDEX.MAP,                     744 bytes,          2/17/2009 4:35:47 PM
19936 09:00:11 (0) **   - OBJECTS.DATA,                  6823936 bytes,      2/18/2009 7:50:58 AM
19937 09:00:11 (0) **   - OBJECTS.MAP,                   3416 bytes,         2/17/2009 4:35:47 PM
19938 09:00:11 (0) ** AFTER running WMIDiag:
19939 09:00:11 (0) ** The WMI repository has a size of: ................................................................................... 8 MB.
19940 09:00:11 (0) ** - Disk free space on 'C:': .......................................................................................... 1196 MB.
19941 09:00:11 (0) **   - INDEX.BTR,                     1392640 bytes,      2/18/2009 7:50:58 AM
19942 09:00:11 (0) **   - INDEX.MAP,                     744 bytes,          2/17/2009 4:35:47 PM
19943 09:00:11 (0) **   - OBJECTS.DATA,                  6823936 bytes,      2/18/2009 7:50:58 AM
19944 09:00:11 (0) **   - OBJECTS.MAP,                   3416 bytes,         2/17/2009 4:35:47 PM
19945 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19946 09:00:11 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
19947 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19948 09:00:11 (0) ** DCOM Status: ........................................................................................................ OK.
19949 09:00:11 (0) ** WMI registry setup: ................................................................................................. OK.
19950 09:00:11 (0) ** WMI Service has no dependents: ...................................................................................... OK.
19951 09:00:11 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
19952 09:00:11 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
19953 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19954 09:00:11 (0) ** WMI service DCOM setup: ............................................................................................. OK.
19955 09:00:11 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
19956 09:00:11 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
19957 09:00:11 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
19958 09:00:11 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
19959 09:00:11 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
19960 09:00:11 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
19961 09:00:11 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
19962 09:00:11 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
19963 09:00:11 (0) **    fail depending on the operation requested.
19964 09:00:11 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
19965 09:00:11 (0) ** 
19966 09:00:11 (0) ** WMI ProgID registrations: ........................................................................................... OK.
19967 09:00:11 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
19968 09:00:11 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
19969 09:00:11 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
19970 09:00:11 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
19971 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19972 09:00:11 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19973 09:00:11 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
19974 09:00:11 (0) **        - REMOVED ACE:
19975 09:00:11 (0) **          ACEType:  &h0
19976 09:00:11 (0) **                    ACCESS_ALLOWED_ACE_TYPE
19977 09:00:11 (0) **          ACEFlags: &h0
19978 09:00:11 (0) **          ACEMask:  &h1
19979 09:00:11 (0) **                    DCOM_RIGHT_EXECUTE
19980 09:00:11 (0) ** 
19981 09:00:11 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19982 09:00:11 (0) **    Removing default security will cause some operations to fail!
19983 09:00:11 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
19984 09:00:11 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19985 09:00:11 (0) ** 
19986 09:00:11 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
19987 09:00:11 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
19988 09:00:11 (0) **        - REMOVED ACE:
19989 09:00:11 (0) **          ACEType:  &h0
19990 09:00:11 (0) **                    ACCESS_ALLOWED_ACE_TYPE
19991 09:00:11 (0) **          ACEFlags: &h0
19992 09:00:11 (0) **          ACEMask:  &h1
19993 09:00:11 (0) **                    DCOM_RIGHT_EXECUTE
19994 09:00:11 (0) ** 
19995 09:00:11 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19996 09:00:11 (0) **    Removing default security will cause some operations to fail!
19997 09:00:11 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
19998 09:00:11 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
19999 09:00:11 (0) ** 
20000 09:00:11 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
20001 09:00:11 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
20002 09:00:11 (0) **        - REMOVED ACE:
20003 09:00:11 (0) **          ACEType:  &h0
20004 09:00:11 (0) **                    ACCESS_ALLOWED_ACE_TYPE
20005 09:00:11 (0) **          ACEFlags: &h0
20006 09:00:11 (0) **          ACEMask:  &h1
20007 09:00:11 (0) **                    DCOM_RIGHT_EXECUTE
20008 09:00:11 (0) ** 
20009 09:00:11 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
20010 09:00:11 (0) **    Removing default security will cause some operations to fail!
20011 09:00:11 (0) **    It is possible to fix this issue by editing the security descriptor and adding the ACE.
20012 09:00:11 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
20013 09:00:11 (0) ** 
20014 09:00:11 (0) ** 
20015 09:00:11 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
20016 09:00:11 (0) ** DCOM security error(s) detected: .................................................................................... 3.
20017 09:00:11 (0) ** WMI security warning(s) detected: ................................................................................... 0.
20018 09:00:11 (0) ** WMI security error(s) detected: ..................................................................................... 0.
20019 09:00:11 (0) ** 
20020 09:00:11 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
20021 09:00:11 (0) ** Overall WMI security status: ........................................................................................ OK.
20022 09:00:11 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
20023 09:00:11 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
20024 09:00:11 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
20025 09:00:11 (0) **   'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
20026 09:00:11 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
20027 09:00:11 (0) **   'select * from MSFT_SCMEventLogEvent'
20028 09:00:11 (0) ** 
20029 09:00:11 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
20030 09:00:11 (0) ** WMI ADAP status: .................................................................................................... OK.
20031 09:00:11 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
20032 09:00:11 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
20033 09:00:11 (0) ** WMI GET operations: ................................................................................................. OK.
20034 09:00:11 (0) ** WMI MOF representations: ............................................................................................ OK.
20035 09:00:11 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
20036 09:00:11 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
20037 09:00:11 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
20038 09:00:11 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
20039 09:00:11 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
20040 09:00:11 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
20041 09:00:11 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
20042 09:00:11 (0) ** WMI static instances retrieved: ..................................................................................... 1026.
20043 09:00:11 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
20044 09:00:11 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
20045 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20046 09:00:11 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
20047 09:00:11 (0) **   DCOM: ............................................................................................................. 23.
20048 09:00:11 (0) **   WINMGMT: .......................................................................................................... 2.
20049 09:00:11 (0) **   WMIADAPTER: ....................................................................................................... 0.
20050 09:00:11 (0) ** => Verify the WMIDiag LOG at line #19477 for more details.
20051 09:00:11 (0) ** 
20052 09:00:11 (0) ** # of additional Event Log events AFTER WMIDiag execution:
20053 09:00:11 (0) **   DCOM: ............................................................................................................. 0.
20054 09:00:11 (0) **   WINMGMT: .......................................................................................................... 0.
20055 09:00:11 (0) **   WMIADAPTER: ....................................................................................................... 0.
20056 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20057 09:00:11 (0) ** WMI Registry key setup: ............................................................................................. OK.
20058 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20059 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20060 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20061 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20062 09:00:11 (0) ** 
20063 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20064 09:00:11 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
20065 09:00:11 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20066 09:00:11 (0) ** 
20067 09:00:11 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!.  Check 'C:\DOCUMENTS AND SETTINGS\ESULLIVAN\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_ESULLIVANLAP_2009.02.18_08.57.26.LOG' for details.
20068 09:00:11 (0) ** 
20069 09:00:11 (0) ** WMIDiag v2.0 ended on Wednesday, February 18, 2009 at 09:00 (W:58 E:17 S:1).

[LB]

I am having the exact same problem.

Hello,

Say I just installed Lansweeper and got the GPO in place. (With the help of a senior tech here) I am having the problem of it reading the user and the PC, but counting them as not scanned. Also its not pulling up their service tag numbers or any hardware info.

Any help?

Many thanks.

Lyle