Assign assets to their right scanning server based on IP scan ranges

[klaus]

This report shows you all assets that aren't assigned to the right scanning server based on IP range scanning configuration.

select *
From tblAssets
  Inner Join (Select tsysIPScanRanges.Servername As servername,
        Convert(numeric(18),ParseName(tsysIPScanRanges.Ipstart, 4) +
        Right('000' + IsNull(ParseName(tsysIPScanRanges.Ipstart, 3), ''), 3) +
        Right('000' + IsNull(ParseName(tsysIPScanRanges.Ipstart, 2), ''), 3) +
        Right('000' + IsNull(ParseName(tsysIPScanRanges.Ipstart, 1), ''),
        3)) As ipstartnumeric,
        Convert(numeric(18),ParseName(tsysIPScanRanges.Ipend, 4) + Right('000' +
        IsNull(ParseName(tsysIPScanRanges.Ipend, 3), ''), 3) + Right('000' +
        IsNull(ParseName(tsysIPScanRanges.Ipend, 2), ''), 3) + Right('000' +
        IsNull(ParseName(tsysIPScanRanges.Ipend, 1), ''), 3)) As ipendnumeric
      From tsysIPScanRanges where enabled = 1) As tsir On tblAssets.IPNumeric >=
    tsir.ipstartnumeric And tblAssets.IPNumeric <= tsir.ipendnumeric
Where tblAssets.Scanserver <> tsir.servername

If you want to automatically fix that, you can run this on a daily basis. But you should make sure that you don't have any overlapping IP scanning ranges. (see my other report in this forum).

update tblassets
set tblassets.scanserver = tsir.servername
From tblAssets
  Inner Join (Select tsysIPScanRanges.Servername As servername,
        Convert(numeric(18),ParseName(tsysIPScanRanges.Ipstart, 4) +
        Right('000' + IsNull(ParseName(tsysIPScanRanges.Ipstart, 3), ''), 3) +
        Right('000' + IsNull(ParseName(tsysIPScanRanges.Ipstart, 2), ''), 3) +
        Right('000' + IsNull(ParseName(tsysIPScanRanges.Ipstart, 1), ''),
        3)) As ipstartnumeric,
        Convert(numeric(18),ParseName(tsysIPScanRanges.Ipend, 4) + Right('000' +
        IsNull(ParseName(tsysIPScanRanges.Ipend, 3), ''), 3) + Right('000' +
        IsNull(ParseName(tsysIPScanRanges.Ipend, 2), ''), 3) + Right('000' +
        IsNull(ParseName(tsysIPScanRanges.Ipend, 1), ''), 3)) As ipendnumeric
      From tsysIPScanRanges where enabled = 1) As tsir On tblAssets.IPNumeric >=
    tsir.ipstartnumeric And tblAssets.IPNumeric <= tsir.ipendnumeric
Where tblAssets.Scanserver <> tsir.servername

[Esben_D]

Thank you for sharing your reports. I'm sure some people will find them helpful.

Just as an FYI, since there are different configuration tabs for each scanning server, the best practice is to configure the correct scanning target to the preferred scanning server.

This alternative method is not officially supported, but that doesn't mean it doesn't have it's uses 😉

[klaus]

Thanks Charles. Just to point out why I am doing this. AD scanning and LSPush scanning do have an effect on the scanning server per asset. Now if we don't have the assets bound to their closest scanning server, this affects deployment timings. We have scanning servers in all different time zones.
This query corrects the situation for us. Scanning server configuration is identical, but great you pointed that out

Charles.X wrote:
Thank you for sharing your reports. I'm sure some people will find them helpful.

Just as an FYI, since there are different configuration tabs for each scanning server, the best practice is to configure the correct scanning target to the preferred scanning server.

This alternative method is not officially supported, but that doesn't mean it doesn't have it's uses 😉