Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with IT Management Suite
Showing posts in English
andykn101 | 15 Jan 2014 | 0 comments

There is a useful SQL query in TECH183347 to measure queue processing but it doesn't contain descriptions for the Queue numbers, I've added a few CASE statements to do this:

SELECT Queueid As [Queue ID],
 [Queue]=CASE Queueid
 WHEN 0 Then 'Priority'
 WHEN 1 Then 'Fast'
 WHEN 2 Then 'Normal'
 WHEN 3 Then 'Slow' 
 WHEN 4 Then 'Large'
 END, COUNT(Id) AS [THREADS IN USE] 

FROM EventQueueEntry where ProcessingState = 2 
GROUP BY ProcessingState, QueueId order by queueid, ProcessingState
The descriptions are taken from DOC5480: http://www.symantec.com/docs/DOC5480
 
TECH183347: http://www.symantec.com/docs/TECH183347
SK | 31 Dec 2013 | 1 comment

After a clean install of ITMS 7.1.2 MP1.1 v7RU, it was found that it was not possible to create a new CMDB rule as its first dropdown list failed to open.

To workaround this issue, you need to clone a sample CMDB rule and then modify it to suit your needs.

SK | 28 Dec 2013 | 0 comments

Here is a handy SQL query that will allow you to search your database tables for a particular word or words (tested against SQL 2008 R2):

**********************************

CREATE TABLE myTable99 (TABLE_NAME sysname, COLUMN_NAME sysname, Occurs int)
GO

SET NOCOUNT ON

DECLARE @SQL varchar(8000), @TABLE_NAME sysname, @COLUMN_NAME sysname, @Sargable varchar(80), @Count int

SELECT @Sargable = 'enter word or words here'

DECLARE insaneCursor CURSOR FOR
    SELECT c.TABLE_NAME, c.COLUMN_NAME
      FROM INFORMATION_SCHEMA.Columns c INNER JOIN INFORMATION_SCHEMA.Tables t
        ON t.TABLE_SCHEMA = c.TABLE_SCHEMA AND t.TABLE_NAME = c.TABLE_NAME
     WHERE c.DATA_TYPE IN ('char','nchar','varchar','nvarchar','text','ntext')
       AND t.TABLE_TYPE = 'BASE TABLE'

OPEN insaneCursor
 ...

SK | 10 Dec 2013 | 1 comment

The following query has the ability to list all Software Releases and their associated rules or just the rules associated with a specifc Software Release:

SELECT rsr.Name AS [Software Release],rir.Name AS [Rule],rir.[Description] AS [Rule Description]
FROM RM_ResourceSoftware_Release rsr
JOIN ResourceAssociation ra ON ra.ParentResourceGuid = rsr.[Guid]
JOIN RM_ResourceInventory_Rule rir ON rir.[Guid] = ra.ChildResourceGuid
--WHERE rsr.Name = 'specific software release'
ORDER BY rsr.Name ASC

As Applicability and Detection rules are both classed as inventory rules, they do not have their own resource type or class; however, it does appear that detection rule names begin with "Detection Rule for", which should allow you to distinguish between the two.

mszlosarczyk | 09 Dec 2013 | 0 comments

Hi Everyone,

Cloud-enabled Management (CEM) is a new feature that allows you to manage client computers outside the corporate network, even if you do not use a Virtual Private Network. CEM was first introduced with IT Management Suite 7.5.

To make the process of implementation quick and easy, we have prepared a whitepaper that describes the concept, requirements and the process of implementation of Cloud-enabled Management.

You can find the whitepaper at the following URL:
http://www.symantec.com/docs/DOC7049

AndyN | 09 Oct 2013 | 0 comments

Thanks to everyone who attended today's webcast announcing the official launch and availability of Symantec Endpoint Management 7.5 solutions powered by Altiris technology!

Listen to the webcast recording:

https://symantec.webex.com/symantec/lsr.php?RCID=5...

Slides are included with this blog post.

Please also visit our Upgrade to 7.5 page to find data sheets, quickstart cards, videos, and other helpful information:

http://go.symantec.com/altiris75

Additional links that might be useful:

Ludovic Ferre | 06 Oct 2013 | 3 comments

The symantec.pl.xml update for 7.5 has hit SolutionSam.com, so 7.5 is now GA.

Here are some information from the product listing:

file md5  = b8675ec97437e633fbcad1c112a6a557
file size = 15 361 694 bytes
timestamp = 2013-10-03 10:59

And here its the full file list (and handfull as you could guess :D):

Modified:
/solutions/7_5/eipower/7_2_rtm/ei_powersaversolution_7_2_perth.msi
 
Added:
/solutions/7_1/ita/ita_doc/altiris_itanalyticsdocumentation_x64.msi
/solutions/7_5/itms/7_5_rtm/altiris_activitycenter_7_5_x64.msi
/solutions/7_5/itms/7_5_rtm/altiris_activitycenterlanguages_7_5_x64.msi
/solutions/7_5/itms/7_5_rtm/altiris_agentlessinventoryupgrade_7_5_x64.msi
/solutions/7_5/itms/7_5_rtm/altiris_agentlessinventoryupgrade_7_5_x86.msi
/solutions/7_5/itms/7_5_rtm/altiris_assetmanagementcombine_7_5_x64.msi
/solutions/7_5/itms/7_5_rtm/altiris_assetupgrade_7_5_x64.msi
/solutions/7_5/itms/7_5_rtm/...
Santana_Villa | 27 Sep 2013 | 1 comment

REGISTER NOW – ENDPOINT MANAGEMENT 7.5 WEBCAST

Symantec Connect Community Webcast:

Endpoint Management 7.5

REGISTER NOW

Webcast Details:

Wednesday, October 9
11:30 am EDT

Please join us for a special webcast on Wednesday, October 9 for the launch of SymantecTM Endpoint Management 7.5 powered by AltirisTM technology!

We will discuss how Endpoint Management 7.5 solutions will make your job easier, provide a few demo’s, and learn about some of the experiences of early adopters.

Don’t miss this great opportunity to get up to speed on 7.5 and the latest news from Symantec!

REGISTER NOW

michael cole | 31 Jul 2013 | 0 comments

I came across a stored procedure that is quite popular for troubleshooting SQL especially blocking, it's not new but deserves a repost. I tried it against sp_who and sp_who2. It seems that this SP gives a more instant snapshot in better detail. Probably it's best feature is a clickable link to the transact that is running. I could still see block chains better with sp_who2, as you could see the trail of SPID's better. There is a SQL query for finding the lead blocker at http://sqlserverplanet.com/troubleshooting/blocking-processes-lead-blocker

For those that are interested in what the differences are between sp_who and sp_who2, the screen snip below shows the column differences, the hidden difference is that sp_who is documented and thus supported, otherwise they are very similar. SP_WhoIsActive complements them.

Disclaimer

...