Endpoint Protection

 View Only

SymantecAudit 

May 10, 2010 02:43 AM

This Powershell script creates a html file containing Computers imported from AD with SEP data added.
This allows one to see which computers are defined but do not have an active Client.

Forum for discussion: https://www-secure.symantec.com/connect/forums/sep-powershell-script-find-computers-defined-not-active

Works in this environment:
Windows 2008 (sp2) for SEPM and MS SQL servers (EDIT: Note code may need to be changed for YOUR version of MS SQL: see below. Work in Progress)
Powershell version 1 (runs on 2 as well, but I keep it 1 compatible)
SEPM 11.0.5

Note on Powershell:
Microsoft has added a safety feature if the Powershell has never run a script, the command to disable is:
set-executionpolicy unrestricted

Statistics
0 Favorited
1 Views
1 Files
0 Shares
0 Downloads
Attachment(s)
zip file
SymantecAudit.zip   3 KB   1 version
Uploaded - Feb 25, 2020

Tags and Keywords

Comments

Jan 04, 2011 03:18 AM

Let us see if I can get help with putting the code(s) I have made @ http://sourceforge.net/projects/sepbabedoda/

Dec 28, 2010 03:35 AM

New versions of SEPM and I will now do an update to the lattest and get this code onto a Subversion Server.

Anybody wanting to help with code and any other Powershell code that can be usefull is welcome.

Probably on SourceForge...

Dec 23, 2010 04:02 PM

Hi Albert.

In the previous article about this tool located here, you asked how to run the script.

As mentioned, you need to adjust the Execution policy to allow the script to run. Then you have two ways of launching the script.

From inside a PowerShell command window run the following line:

 &'C:\path_to_script\script.ps1' 

If you want to run this as a scheduled task or from a shortcut, then use the following:

 powershell.exe "&'C:\path_to_script\script.ps1'" 

In both cases, be aware of the inverted commas and the apostrophes.

Dec 23, 2010 03:53 PM

Thanks very much

Oct 07, 2010 03:40 AM

I hope to make a "refresh" of the code within the next month.

Error 666 TRAP: DB Access kenworth/sem5/sa 
 Invalid object name 'sem5.SEM_AGENT'.
 
See above for alteration in code dependant on MS SQL used.
 
The refresh will include check of DB used to avoid having to change the code.
 
+1 vote for daem0n647 input: thank you.

Oct 06, 2010 11:38 PM

However, I got this scary error message:

 

Use -WhatIf for help ...
Information 0 Get-SEPM-Data -Server kenworth -Database sem5 -Username sa
Error 666 TRAP: DB Access kenworth/sem5/sa 
 Invalid object name 'sem5.SEM_AGENT'.

Aug 10, 2010 05:31 AM

sound good....
i ll check it....

Jun 21, 2010 12:45 PM

About how long would this take to run on a machine with 20k clients and an off box DB?

I anxious to try it.

Jun 15, 2010 03:08 AM

139   $Agent = "$Database.SEM_AGENT"
140   $Client = "$Database.SEM_CLIENT"

to:

$Agent = "$Database.dbo.SEM_AGENT"
$Client = "$Database.dbo.SEM_CLIENT"

Launched on XPSP3/PSh2
SEPM 10.0.6005.562 (6a) on Srv2003EntR2SP2/SQL2005EntSP2

Related Entries and Links

No Related Resource entered.