Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with 7.x
Showing posts in English
SK | 21 Jan 2014 | 0 comments

One unfortunate difference between SMP 7.1 and 7.5 is that in 7.1, when you run a report, the SMP records a number of "Altiris.Reporting....." entries in its logs; two of which were high useful:

 

Source: Altiris.Reporting.DataSource.ResourceDataSource.Run
Description: ResourceDataSource returned N rows in 'Table' table

N equates to the number of rows that you report displayed, making it easy to locate the write log records, because immediately below this line will be the actual reports SQL that was used:

Source: Altiris.Reporting.DataSource.ResourceDataSource.Run
Description: ResourceDataSource is running query:

<Reports SQL starts here>

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...

Ludovic Ferre | 18 Nov 2013 | 0 comments

The Deployment Solution Agent (7.x) comes in as an all or nothing bundle. Once installed the agent will run all of its tasks whenever it finds it suitable, without giving administrators a chance to control what should or should not be done.

The iLO inventory is one such task that the Deployment Agent runs everytime the agent is started. Given you can't disabled the inventory process you cannot either prevent the events related to running the task.

This means that if you have 10,000 computers starting on Monday morning all with the Deployment Agent installed you will get 10,000 RILOE Capture Event messages sent to the SMP.

As previously stated with the DS Agent it's an all or nothing deal, but thankfully some Agent built-in feature can be used here to prevent the undesired messages from living the workstation:

The Altiris Agent Transport Filters. These filters are normally delivered to the managed machine with its client policy and are stored in...

ianatkin | 14 Nov 2013 | 0 comments

Today, I'm looking at problem with NS7 inventory.

Whenever Linux automation has a kernel upgrade (which hasn't happened for a while but is about too), one of the steps I do is confirm hardware support. In NS6 I did this by gathering up all the relevent device IDs of the PCI bus for network cards and storage with the following SQL,

 

SELECT * 

FROM...

jon_sharp | 10 Jun 2013

Symantec Deployment Solutions is dependent on the use of pre-boot operating systems in the management of workstation and server systems. The pre-boot environment is delivered to target workstation and server systems via network PXE servers or through the use of physical devices and media. This process has the potential for exposure to possible malicious activity from a person who may have already breached network security, either physically or through a remote network connection, or from a malicious but authorized network user. This paper will address these types of secondary security exposures. ...

Click here to read the full KB.

Rae Landua | 06 May 2013 | 0 comments

ITS & Altrinsic Solutions' free Altiris Deployment webinar is just around the corner! Join Mark England to hear Quagmires Quandries and Snake Pits: Don’t Get Stuck on Deployments on Thursday 5/9/13 at 1pm CDT. Register now to save your spot!  https://www1.gotomeeting.com/register/454827056

Tim.Jing | 21 Feb 2013 | 0 comments

Found out that there is a hidden covert entity existing inside the Symantec Support world where all the product experts converge. They will host sessions with clients when there are issues with the SMP product. Session 2 is coming up soon to address the imaging timing issue.

At this point, looking in to the spy glass, I'd say this is has been a very shaky start which will probably cost me my job.

But we do have a glimmer of hope now with the new resources. There are some clever SQL plays and work around suggested which would make some of the issues go away.

However we are discovering some odd and serious replication problems which hopefully will get solved today.

1. Certain jobs will replicate to one child server, but error when replicated to the other.

2. Full inventory is shown on Child NS, but basic on the parent server.

 

Tim.Jing | 20 Feb 2013 | 0 comments

So you have support on the line, and they have a fix for an issue for you. WebEx session, servers configured service restarted, all good right?

Not so quick, 5 minutes later, complaint about console not longer accessible. 10 minutes after that's resolved, no jobs/tasks will run!

That's the worst moment in IT, when everyone that's never roamed near your cube is now gathering inside or huddled in to an empty space just to spectate. It's like mosh pit thick ring side when Tyson's strolling down the isle, and in my mind, a numbing silence like someone that just got TKO'ed.

Starting from the beginning, we had NSE processing performance issues and a call was made to support to change queue processing size. (TECH183347 ) After the changes, both server seems normal when using the console while remoted to the server. The call ends, and then we found out the console no longer...

Tim.Jing | 18 Feb 2013 | 3 comments

To create a good product it requires lots of talent, great team work, and really good communication. To have a great product, the entire team needs to be focused and driven.

Up to this point, Symantec has some of the best sales people, a good Sales Engineering group, decent technical support team, but where is the communication with the Dev group? How come we never hear from those guys? Are they locked away and not getting the feedback from the users?

This will be our 7th week with the Symantec SMP 7.1 MP1 product, and while 90%+ of the suite is working or workable, we continue to have imaging issues. While i'm optimistic that Symantec has the resources to resolve our issues, it's rather unfortunate that the basic functions do not work out of the box. At least not reliably, which their 6.x version did without any issues. 

So moving on to next week, focusing on the same imaging issue, but with more detailed problems:

1. Deploy Anywhere will...

Tim.Jing | 15 Feb 2013 | 0 comments

With a lot of help from Symantec, we narrowed down some of the issues with image deploy. And it's all timing related, which is another word to say product design?

When a machine that has any changes other than whats already reflected in the database (New machine, existing machine's F8'ed in to a task server, a machine that just had a name change...) The database needs a resource membership update, and this machine is not allowed access by any of the software tasks due to licensing/client not capable.

So lots of Delta Reource Updates for most o the error messages. And more calls to come with Symantec Support.

Check out the screen shot below. This actually means, some jobs ran, but at least 1 failed. And you have to click on everyone to find which one failed.

 

:)