cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
ukaussi
Engaged Sweeper
Is there a reason why LS does ot pull the Operating System field from AD when it scans?

I ask as we are comeing to the final few months of upgrading to Windows 7 for 4000 pc's and knowing an accurate number of what is left and where would be helpful.

Unfortunately, we have NetMotion being used on many mobile users and those pc's cannot be scanned as ports are blocked and our HO will not allow LSPush at this time so it seems logical to pull OS from AD.

Also, our AD scanning pulls 3290 computers but when I run an AD scan using ADManager it pulls 3545 computers from the exact same OUs, why would this be?
1 ACCEPTED SOLUTION
Hemoco
Lansweeper Alumni
Is there a reason why LS does not pull the Operating System field from AD when it scans?

We stopped scanning this value because in many cases the results were incorrect (different from the real operating system).

Also, our AD scanning pulls 3290 computers but when I run an AD scan using ADManager it pulls 3545 computers from the exact same OUs, why would this be?

When you start active scanning it looks back for computers seen in the last 14 days.
Disabled computer accounts are ignored.

You can use scheduled scanning on the OU to get all computers (also the ones not seen in 14 days)

View solution in original post

5 REPLIES 5
Hemoco
Lansweeper Alumni
Is there a reason why LS does not pull the Operating System field from AD when it scans?

We stopped scanning this value because in many cases the results were incorrect (different from the real operating system).

Also, our AD scanning pulls 3290 computers but when I run an AD scan using ADManager it pulls 3545 computers from the exact same OUs, why would this be?

When you start active scanning it looks back for computers seen in the last 14 days.
Disabled computer accounts are ignored.

You can use scheduled scanning on the OU to get all computers (also the ones not seen in 14 days)
ukaussi
Engaged Sweeper
Lansweeper wrote:
Is there a reason why LS does not pull the Operating System field from AD when it scans?

We stopped scanning this value because in many cases the results were incorrect (different from the real operating system).



Can we enable this on our server/version?

If not, is there a way to edit the OS field or "OScode" value for each of the "not scanned" assets as this field is not editable on the mass edit screen?
Hemoco
Lansweeper Alumni
ukaussi wrote:
Can we enable this on our server/version?

This is not possible unfortunately.

ukaussi wrote:
If not, is there a way to edit the OS field or "OScode" value for each of the "not scanned" assets as this field is not editable on the mass edit screen?

You can manually edit the OScode field in the tblAssets database table, though this is not supported. Your changes will likely be overwritten upon rescanning as well.
ukaussi
Engaged Sweeper
Lansweeper wrote:

You can manually edit the OScode field in the tblAssets database table, though this is not supported. Your changes will likely be overwritten upon rescanning as well.


Just to clarify, will they be overwritten by "not scanned" if LS is unable to scan the asset?
Hemoco
Lansweeper Alumni
ukaussi wrote:

Just to clarify, will they be overwritten by "not scanned" if LS is unable to scan the asset?

This field will not be overwritten (OScode)