Force Active Directory user scan

[bsalvaggio]

We updated a majority of our AD users yesterday so their Department and Job Title would be correct... Trying to see that in Lansweeper and not getting those changes... Is there a way to force an update?

[cjmusa]

Ok - learning a lot about the different errors - RPC and WMI errors.

A couple of general questions and then I have included my WMI error report for one of the "RED" machines to see if I can better understand the reasons for the WMI errors:

No doubt Lansweeper can access XP boxes with fixed IP addresses. What has been your experience with needing to turn "on" NETBIOS over TCIP/IP under WINS in when windows boxes have fixed IP Addresses?

While the WMI error report indicates problems, and Lansweeper provides a link to a script to fix ...70005 errors, I don't like running a script without knowing what it does. Is there a way to see or know what the script is doing to fix the WMI erros?

Since we operate on an isolated network and unless Microsoft has automatically turned the firewall back on as part of the Microsoft Update process, our Firewalls are turned off. The machine listed below originally had the XP Firewall turned On, so we received RPC errors at first. Then once the Firewall was turned off, errors reduced to ...70005 and this is where the machine sits at this point in time. Since our Firewall is turned off, Lansweeper references on the website along with articles associated with setting up the Firewall, Group Policy Management, and 3rd party firewall issues should not need to be used to correct RPC errors. Is this correct.

Here is the WMI report on a problem machine that lists the .....70005 error.

Thanks for the help

19853 15:29:26 (0) ** WMIDiag v2.0 started on Saturday, January 16, 2010 at 15:27.
19854 15:29:26 (0) **
19855 15:29:26 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - January 2007.
19856 15:29:26 (0) **
19857 15:29:26 (0) ** This script is not supported under any Microsoft standard support program or service.
19858 15:29:26 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
19859 15:29:26 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
19860 15:29:26 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
19861 15:29:26 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
19862 15:29:26 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
19863 15:29:26 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
19864 15:29:26 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
19865 15:29:26 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
19866 15:29:26 (0) ** of the possibility of such damages.
19867 15:29:26 (0) **
19868 15:29:26 (0) **
19869 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19870 15:29:26 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
19871 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19872 15:29:26 (0) **
19873 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19874 15:29:26 (0) ** Windows XP - No service pack - 32-bit (2600) - User 'EEE-DRAFTING\VENTURA' on computer 'VENTURA2'.
19875 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19876 15:29:26 (0) ** Environment: ........................................................................................................ OK..
19877 15:29:26 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #0).
19878 15:29:26 (0) ** Drive type: ......................................................................................................... SCSI (WDC WD16 00AAJS-00B4A0 SCSI Disk Device).
19879 15:29:26 (0) ** There are no missing WMI system files: .............................................................................. OK.
19880 15:29:26 (0) ** There are no missing WMI repository files: .......................................................................... OK.
19881 15:29:26 (0) ** WMI repository state: ............................................................................................... N/A.
19882 15:29:26 (0) ** BEFORE running WMIDiag:
19883 15:29:26 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
19884 15:29:26 (0) ** - Disk free space on 'C:': .......................................................................................... 132782 MB.
19885 15:29:26 (0) ** - INDEX.BTR, 1335296 bytes, 1/16/2010 12:42:32 PM
19886 15:29:26 (0) ** - INDEX.MAP, 704 bytes, 1/16/2010 12:42:32 PM
19887 15:29:26 (0) ** - OBJECTS.DATA, 6324224 bytes, 1/16/2010 12:42:32 PM
19888 15:29:26 (0) ** - OBJECTS.MAP, 3228 bytes, 1/16/2010 12:42:32 PM
19889 15:29:26 (0) ** AFTER running WMIDiag:
19890 15:29:26 (0) ** The WMI repository has a size of: ................................................................................... 7 MB.
19891 15:29:26 (0) ** - Disk free space on 'C:': .......................................................................................... 132780 MB.
19892 15:29:26 (0) ** - INDEX.BTR, 1335296 bytes, 1/16/2010 12:42:32 PM
19893 15:29:26 (0) ** - INDEX.MAP, 704 bytes, 1/16/2010 12:42:32 PM
19894 15:29:26 (0) ** - OBJECTS.DATA, 6324224 bytes, 1/16/2010 12:42:32 PM
19895 15:29:26 (0) ** - OBJECTS.MAP, 3228 bytes, 1/16/2010 12:42:32 PM
19896 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19897 15:29:26 (0) ** Windows Firewall: ................................................................................................... NOT INSTALLED.
19898 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19899 15:29:26 (0) ** DCOM Status: ........................................................................................................ OK.
19900 15:29:26 (0) ** WMI registry setup: ................................................................................................. OK.
19901 15:29:26 (0) ** WMI Service has no dependents: ...................................................................................... OK.
19902 15:29:26 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
19903 15:29:26 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
19904 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19905 15:29:26 (0) ** WMI service DCOM setup: ............................................................................................. OK.
19906 15:29:26 (2) !! WARNING: WMI DCOM components registration is missing for the following EXE/DLLs: .................................... 6 WARNING(S)!
19907 15:29:26 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{7A0227F6-7108-11D1-AD90-00C04FD8FDFF}\InProcServer32)
19908 15:29:26 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{D71EE747-F455-4804-9DF6-2ED81025F2C1}\InProcServer32)
19909 15:29:26 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\FASTPROX.DLL (\CLSID\{ED51D12E-511F-4999-8DCD-C2BAC91BE86E}\InProcServer32)
19910 15:29:26 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{4C6055D8-84B9-4111-A7D3-6623894EEDB3}\InProcServer32)
19911 15:29:26 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{A1044801-8F7E-11D1-9E7C-00C04FC324A8}\InProcServer32)
19912 15:29:26 (0) ** - C:\WINDOWS\SYSTEM32\WBEM\WBEMPROX.DLL (\CLSID\{F7CE2E13-8C90-11D1-9E7B-00C04FC324A8}\InProcServer32)
19913 15:29:26 (0) ** => WMI System components are not properly registered as COM objects, which could make WMI to
19914 15:29:26 (0) ** fail depending on the operation requested.
19915 15:29:26 (0) ** => For a .DLL, you can correct the DCOM configuration by executing the 'REGSVR32.EXE <Filename.DLL>' command.
19916 15:29:26 (0) **
19917 15:29:26 (0) ** WMI ProgID registrations: ........................................................................................... OK.
19918 15:29:26 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
19919 15:29:26 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
19920 15:29:26 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
19921 15:29:26 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
19922 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
19923 15:29:26 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19924 15:29:26 (1) !! ERROR: Actual trustee 'NT AUTHORITY\NETWORK SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
19925 15:29:26 (0) ** - ACTUAL ACE:
19926 15:29:26 (0) ** ACEType: &h0
19927 15:29:26 (0) ** ACCESS_ALLOWED_ACE_TYPE
19928 15:29:26 (0) ** ACEFlags: &h2
19929 15:29:26 (0) ** CONTAINER_INHERIT_ACE
19930 15:29:26 (0) ** ACEMask: &h1
19931 15:29:26 (0) ** WBEM_ENABLE
19932 15:29:26 (0) ** - EXPECTED ACE:
19933 15:29:26 (0) ** ACEType: &h0
19934 15:29:26 (0) ** ACCESS_ALLOWED_ACE_TYPE
19935 15:29:26 (0) ** ACEFlags: &h12
19936 15:29:26 (0) ** CONTAINER_INHERIT_ACE
19937 15:29:26 (0) ** INHERITED_ACE
19938 15:29:26 (0) ** ACEMask: &h13
19939 15:29:26 (0) ** WBEM_ENABLE
19940 15:29:26 (0) ** WBEM_METHOD_EXECUTE
19941 15:29:26 (0) ** WBEM_WRITE_PROVIDER
19942 15:29:26 (0) **
19943 15:29:26 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
19944 15:29:26 (0) ** This will cause some operations to fail!
19945 15:29:26 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
19946 15:29:26 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19947 15:29:26 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19948 15:29:26 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19949 15:29:26 (0) ** A specific WMI application can always require a security setup different
19950 15:29:26 (0) ** than the WMI security defaults.
19951 15:29:26 (0) **
19952 15:29:26 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19953 15:29:26 (1) !! ERROR: Actual trustee 'NT AUTHORITY\LOCAL SERVICE' DOES NOT match corresponding expected trustee rights (Actual->Default)
19954 15:29:26 (0) ** - ACTUAL ACE:
19955 15:29:26 (0) ** ACEType: &h0
19956 15:29:26 (0) ** ACCESS_ALLOWED_ACE_TYPE
19957 15:29:26 (0) ** ACEFlags: &h2
19958 15:29:26 (0) ** CONTAINER_INHERIT_ACE
19959 15:29:26 (0) ** ACEMask: &h1
19960 15:29:26 (0) ** WBEM_ENABLE
19961 15:29:26 (0) ** - EXPECTED ACE:
19962 15:29:26 (0) ** ACEType: &h0
19963 15:29:26 (0) ** ACCESS_ALLOWED_ACE_TYPE
19964 15:29:26 (0) ** ACEFlags: &h12
19965 15:29:26 (0) ** CONTAINER_INHERIT_ACE
19966 15:29:26 (0) ** INHERITED_ACE
19967 15:29:26 (0) ** ACEMask: &h13
19968 15:29:26 (0) ** WBEM_ENABLE
19969 15:29:26 (0) ** WBEM_METHOD_EXECUTE
19970 15:29:26 (0) ** WBEM_WRITE_PROVIDER
19971 15:29:26 (0) **
19972 15:29:26 (0) ** => The actual ACE has the right(s) '&h12 WBEM_METHOD_EXECUTE WBEM_WRITE_PROVIDER' removed!
19973 15:29:26 (0) ** This will cause some operations to fail!
19974 15:29:26 (0) ** It is possible to fix this issue by editing the security descriptor and adding the removed right.
19975 15:29:26 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19976 15:29:26 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19977 15:29:26 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
19978 15:29:26 (0) ** A specific WMI application can always require a security setup different
19979 15:29:26 (0) ** than the WMI security defaults.
19980 15:29:26 (0) **
19981 15:29:26 (0) ** WMI namespace security for 'ROOT/SERVICEMODEL': ..................................................................... MODIFIED.
19982 15:29:26 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
19983 15:29:26 (0) ** - REMOVED ACE:
19984 15:29:26 (0) ** ACEType: &h0
19985 15:29:26 (0) ** ACCESS_ALLOWED_ACE_TYPE
19986 15:29:26 (0) ** ACEFlags: &h12
19987 15:29:26 (0) ** CONTAINER_INHERIT_ACE
19988 15:29:26 (0) ** INHERITED_ACE
19989 15:29:26 (0) ** ACEMask: &h13
19990 15:29:26 (0) ** WBEM_ENABLE
19991 15:29:26 (0) ** WBEM_METHOD_EXECUTE
19992 15:29:26 (0) ** WBEM_WRITE_PROVIDER
19993 15:29:26 (0) **
19994 15:29:26 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
19995 15:29:26 (0) ** Removing default security will cause some operations to fail!
19996 15:29:26 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
19997 15:29:26 (0) ** For WMI namespaces, this can be done with 'WMIMGMT.MSC'.
19998 15:29:26 (0) ** Note: WMIDiag has no specific knowledge of this WMI namespace.
19999 15:29:26 (0) ** The security diagnostic is based on the WMI namespace expected defaults.
20000 15:29:26 (0) ** A specific WMI application can always require a security setup different
20001 15:29:26 (0) ** than the WMI security defaults.
20002 15:29:26 (0) **
20003 15:29:26 (0) **
20004 15:29:26 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
20005 15:29:26 (0) ** DCOM security error(s) detected: .................................................................................... 0.
20006 15:29:26 (0) ** WMI security warning(s) detected: ................................................................................... 0.
20007 15:29:26 (0) ** WMI security error(s) detected: ..................................................................................... 3.
20008 15:29:26 (0) **
20009 15:29:26 (0) ** Overall DCOM security status: ....................................................................................... OK.
20010 15:29:26 (1) !! ERROR: Overall WMI security status: ................................................................................. ERROR!
20011 15:29:26 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
20012 15:29:26 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 2.
20013 15:29:26 (0) ** - ROOT/SUBSCRIPTION, MSFT_UCScenarioControl.Name="Microsoft WMI Updating Consumer Scenario Control".
20014 15:29:26 (0) ** 'SELECT * FROM __InstanceOperationEvent WHERE TargetInstance ISA 'MSFT_UCScenario''
20015 15:29:26 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
20016 15:29:26 (0) ** 'select * from MSFT_SCMEventLogEvent'
20017 15:29:26 (0) **
20018 15:29:26 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
20019 15:29:26 (0) ** WMI ADAP status: .................................................................................................... OK.
20020 15:29:26 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 1 NAMESPACE(S)!
20021 15:29:26 (0) ** - ROOT/SERVICEMODEL.
20022 15:29:26 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
20023 15:29:26 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
20024 15:29:26 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
20025 15:29:26 (0) ** i.e. 'WMIC.EXE /NODE:"VENTURA2" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
20026 15:29:26 (0) **
20027 15:29:26 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
20028 15:29:26 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
20029 15:29:26 (0) ** WMI GET operations: ................................................................................................. OK.
20030 15:29:26 (0) ** WMI MOF representations: ............................................................................................ OK.
20031 15:29:26 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
20032 15:29:26 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
20033 15:29:26 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
20034 15:29:26 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
20035 15:29:26 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
20036 15:29:26 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
20037 15:29:26 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
20038 15:29:26 (0) ** WMI static instances retrieved: ..................................................................................... 698.
20039 15:29:26 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
20040 15:29:26 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
20041 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20042 15:29:26 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
20043 15:29:26 (0) ** DCOM: ............................................................................................................. 0.
20044 15:29:26 (0) ** WINMGMT: .......................................................................................................... 0.
20045 15:29:26 (0) ** WMIADAPTER: ....................................................................................................... 0.
20046 15:29:26 (0) **
20047 15:29:26 (0) ** # of additional Event Log events AFTER WMIDiag execution:
20048 15:29:26 (0) ** DCOM: ............................................................................................................. 0.
20049 15:29:26 (0) ** WINMGMT: .......................................................................................................... 0.
20050 15:29:26 (0) ** WMIADAPTER: ....................................................................................................... 0.
20051 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20052 15:29:26 (0) ** WMI Registry key setup: ............................................................................................. OK.
20053 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20054 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20055 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20056 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20057 15:29:26 (0) **
20058 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20059 15:29:26 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
20060 15:29:26 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
20061 15:29:26 (0) **
20062 15:29:26 (0) ** WARNING: WMIDiag determined that WMI works CORRECTLY. HOWEVER, some issues were detected. Check 'C:\DOCUMENTS AND SETTINGS\VENTURA.EEE-DRAFTING\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP___.CLI.RTM.32_VENTURA2_2010.01.16_15.26.58.LOG' for details.
20063 15:29:26 (0) **
20064 15:29:26 (0) ** WMIDiag v2.0 ended on Saturday, January 16, 2010 at 15:29 (W:62 E:21 S:2).

[Hemoco]

You can see if you have the correct lstrigger command by typing it in manually from the command prompt.
The mount of scans on the webpage is only updated every 10 minutes.
If you want a "live" view you can look at http://127.0.0.1:9524 on the server.

To solve the "red" computers:
http://www.lansweeper.com/kb/notfound.aspx
http://www.lansweeper.com/kb/accessdenied.aspx

[cjmusa]

Ok so as I have gained some knowledge of Lansweeper, I now have the ability to execute the trigger command from the main browser screen.

I beleive I have everything working as it should because when I ask for trigger a specific machine in my domain, it asks me if I want to run the command and does not give any errors once I request the scan of the specific machine with the trigger button.

It seems to me that if a trigger is executed, one would expect the scan count to increase by one and the last machine contacted entry would change to the machine just triggered. If this is the case, then I see neither event occur when I execute a trigger.

How do I know that the trigger is working?

Also any suggestions on how to get information out of RED machines that are true XP users on the network.

Thanks.

[cjmusa]

It took me awhile to figure out how to access the premium support forum.

My machines are only being recognized by Lansweeper when they are logging onto the domain.

I have had my system running all day and there were a total of five machines logged on:

My Windows 2008 RC2 domain controller that is also running Lansweeper
My Windows 2003 RC2 application server
My network backup machine.
A non active Windows XP user.
A Wyse thin client that is never turned off running XP Embedded.

For over four hours Lansweeper was active and in addition to my 2008 Server, the only other machines recognized were the Non Active User and the Wyse thin client. These two machines (the non active XP user and the Wyse thin client showed up as "RED" users on the Lansweeper reporting tool. 3 scans total were listed in four hours.

So I decided to reboot my 2003 server, my non active WIndows XP user and turned on a number of other XP 32 bit and 64 bit users.

Lansweeper sees them all logon and starts reporting on them right away, so the user that indicates the system is only recognizing the users as they log on appears to be somewhat true.

I also don't understand why I still have two "RED" computer, yes the Wyse was not shutoff, but the original non active WINDOWS XP user who was completely shutoff and restarted still shows "RED".

[Hemoco]

cjmusa wrote:

For over four hours Lansweeper was active and in addition to my 2008 Server, the only other machines recognized were the Non Active User and the Wyse thin client. These two machines (the non active XP user and the Wyse thin client showed up as "RED" users on the Lansweeper reporting tool. 3 scans total were listed in four hours.

Active scanning currently works like this:
When the service is first started it looks for recent seen computers by DC's in the last 4 hours, it then repeats this process every 15 minutes.
Each computer contacts a dc about once a day (even if you don't log off)
So the first time you start the service it might take a while to get everything.
(next version will change this)

[MKroell]

I'm on the same level as PCrockett, We just purchased this but am very disappointed that a computer is only scanned when a user logs on. I was hoping that it scanned all computers in ad at a certian time interval.

[Hemoco]

MKroell wrote:
I'm on the same level as PCrockett, We just purchased this but am very disappointed that a computer is only scanned when a user logs on. I was hoping that it scanned all computers in ad at a certian time interval.

Lansweeper does scan all computers at a certain time interval with active scanning. (even if the user stays logged on)
PCrockett's problem is that he want to update active directory information for computers turned off.

[pcrockett]

Changes made to computer OUs aren't updated in Lansweeper until the systems are booted and a user logs on? I thought active scan was supposed to go through AD periodically updating details from there. I'm now running into this issue when changes are made to offline hardware that are shelved, but lansweeper never updates the changes from AD, thus doesn't update my reports that have some OU filtering. Are there any requests to have this added to the next version? e.g. a periodic (schedulable) AD detail update scan - verifying the same things that are scanned for during the online system scan via LSclient, but instead of waiting for the system to be turned on, just compare the LS database to AD and update from AD?

Without this, our reports are inaccurate when based on any data from AD, (because the AD details are not trustable), and the totals of hardware items are invalid. It's really a must in order to be able to effectively use Lansweeper in our implementation of AD as the centralized management system.

Any workarounds out there or potential resolutions in the new version? Thanks!

[Hemoco]

Yes, but this will only update the logged on users at that moment.

[bsalvaggio]

Something like...

for /f %%x in (comps.txt) do lstrigger LSserver %%x domainName

Contents of the comps.txt file...

compName1
compName2
compName3
....