Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with 7.x
Showing posts in English
Tim.Jing | 09 Jan 2013 | 2 comments

A few days in to the migration, have some questions came up. So lets go through it.

Our infrustructure is more like 1 huge building than 80 separate sites. The availability of having fiber connected to all the sattalite campuses means we can centrally manage as if they were in the same building. The problem is SMP isnt really designed for that kind of infrustructure. And the few issues we encountered are:

1. The technicians cannot manage the infrustructure in real time from 1 console. The amount of our clients meant we had to use hierchy, which means teh Parent server sees things later(Synch schedule). While all synched machines will be on the Parent server, any new clients will take 24 hours for the Parent console to see. Which means no OOB deployment from the parent Console.

2. Replication of packages maybe required as Task Servers, which means we would have to replicate our packages atleast 5 times(5 Task Servers). We dont need that as our San can handle the...

Rae Landua | 08 Jan 2013 | 0 comments

 

Altrinsic Solutions and NetX are offering a free webinar next week on "The Top Five Tricks to Optimize Your Altiris/SMP Environment." You can learn little-known deployment and configuration methods to fully leverage your Altiris investment.  It's filling up quickly so register now to reserve your spot!

 

 

http://www.netxinc.com/emails/tips_and_tricks_webinar/tipsandtricks.html

Ludovic Ferre | 01 Jan 2013 | 0 comments

Happy New Year Symantec and the Connect Community.

Today I updated my patch toolkit ([1][2]) with version 0.6.7, brining in a couple of features ontop of some project consolidation (nothing visible from the end-user standpoint but I have implementing a generic initializer and a config class that allow me to further consolidate the project codes).

Here are the features implemented in 0.6.7:

  • /severity=<severity>|* now has a wildcard token ("*") that allows users to select any severities instead of only one [available in both ZeroDayPAtch.exe and PAtchAutomation.exe]
  • /custom-sp=<sp_name> allows the user to specify a stored procedure name that will be executed [available in PatchAutomation.exe alone]

What's specially interesting in this case (and in the combination of both features) is that it is now possible to generate a result-set to be used in the tool based on what ever the end user want.

The /...

HighTower | 27 Dec 2012 | 7 comments

At the last couple of Symantec Endpoint Management User Group meetings I talked about a couple of things that can be done to improve the performance of your Symantec Management Platform.  I figured it would be best to summarize them in the group itself:

  1. The first one I mentioned had to do with changing the Kerberos authentication order in the IIS website from Negotiate > NTLM to NTLM > Negotiate
    http://www.symantec.com/business/support/index?page=content&id=TECH156006
     
  2. The second we just ran across this week.  Our 16 core, 24gb RAM SQL server was running a constant 80-90% CPU utilization and we were experiencing frequent deadlocks.  On Sunday, a deadlock/blocking situation corrupted our PMImport and broke Patch.  Very bad things happened.

    In any event, we found that the SQL Tuning guide had been updated by...

Ludovic Ferre | 20 Dec 2012 | 0 comments

I was asked today to help on a long running hierarchy replication task. I pointed my customer to the default report whilst I was searching a hand crafted SQL to do the same, with a slightly friendlier look to it.

I found it, so I sent it to them and I share it with the Community now:

select
		rs._eventTime as 'Event time',
		replace (src.name, '.15-cloud.fr', '') + ' --> ' +
		replace (dst.name, '.15-cloud.fr', '') + 
		case src.name when 'vbox-atrs5.15-cloud.fr' then ' (Down)' else ' (Up)' end as 'Details',
		cast(rs.TotalReplicationCount as varchar) as 'Objects (total)',
		cast (rs.FailedReplicationCount as varchar) as 'Failed',
		cast (rs.DataTransferred as varchar) as 'Size in KiB',
		cast (DATEDIFF(mi, rs.[StartTime], rs.[FinishTime] ) as varchar)AS 'Duration (mins)'
  from...
Tim.Jing | 19 Dec 2012 | 0 comments

If you can imaging a picture of Mount Ranier on a cloudy day. The towering structure is only partialy revealed, clouds camouflage the snow covered cap. leaving one a guess at what could be under the blanket.

We have alot of items to migrate ahead, including:

  1. A DS structure with about 300 packages vendor command lines and MSI built from Wise.
  2. An HII image in Windwos XP that has not changed since 2009.
  3. Wise to Admin Studio conversion.
  4. Windows 7 image.
  5. App Metering to block apps(If the header reading is better than version 6)
  6. Exploring virtual applications with Workspace Streaming.
  7. Mac OS image and software deployment.
  8. Symantec MDM.
  9. Customize console and training for the Desktop and service desk groups.

 

Should be a...

Ludovic Ferre | 17 Dec 2012 | 0 comments

I completed some refactoring and aggregated the 2 related Patch Automation projects [1][2] in the last week and so I can call the 2 programs a toolkit :D.

Some features from the changes are only code related (sharing code between the projects) but there's a major addition to both project: custom patch exclusion.

This is implemented via the database, and it leaves plenty of room for you to choose which bulletins are excluded. The code is written to exclude bulletin by name, from the content of a table or view named "PatchAutomation_Excluded".

And here is a sample implementation, that will prevent duplicate entries in the table and will give some added information (a timestamp when a new exclusion is added):

if exists (select name from sys.objects where type = 'U' and name = 'PatchAutomation_Excluded')
	drop table PatchAutomation_Excluded

create table PatchAutomation_Excluded (
	_id int...
Tim.Jing | 13 Dec 2012 | 10 comments

This will be to document our migration from Symantec Client Managment 6 to SMP CMP 7.1. It is scheduled to be set in motion sometime Jan 2013 with the help of Xcend consulting services which also implemented our 6.x environment.

Our environment:

We are a school district with 80+ remote sites. 25,000+ Windows XP machines, a few Win 7, 300+ Mac's, 6,000+ iPads. We have a centralized datacenter, with fiber connections to each site. We have Cisco networking gear with gigbit connections at most ports, along with Cisco Aironet access points at some campuses.

We use Altiris for all new and existing SO and software automation except for the Apple equipment. The suites used in Altiris are:

Depoyment solution, we have 10 DS 6.9 SP2 servers divided up amoung the sites.

Inventory via NS, we have 3 client facing NS with a report server. Lots of custom reports for compliance and inventory questions.

Patch managment, for desktop and servers.

...

Michael Grueber | 11 Dec 2012 | 6 comments

It is essential to understand how the reports in the Patch Management Solution calculate compliance.  For example, the Compliance by Computer report calculates compliance based on all bulletins applicable to that computer. 

If you download the applicability/detection rules for a particular bulletin and the Patch Management Solution finds that an update associated with that bulletin is applicable to a particular computer but not installed on that computer, that computer is considered to not be in compliance with respect to that bulletin.  This is true even if you have not created any policies to distribute the updates associated with the bulletin to that computer.

While the Patch Management Solution reports provide you with an "absolute" measure of compliance, there may be occasions in which you want to see another view of compliance.  For example, you may want to see the compliance status of a particular computer with...

Ludovic Ferre | 10 Dec 2012 | 1 comment

I was on a Webex with a customer a few week ago because they had a serious issue with the SMP console being very slow.

It's one of my customer, so I was a little surprised given we implemented quite a few fixes. Anyhow, we double check and we could see that the Application Pool was correctly split, and the Task Server workload was nicely off the SMP.

I opened the task manager. It showed the Altiris-NS-Agent w3wp process running at a high CPU

A glance at the Altiris Log Viewer showed the poor thing almost all red (bleeding to death???).

A quick inspection on the error all pointed to the Client Policy request and problems with patch management (SqlDeadlock and exceptions). So I asked the customer (and their partner who was on-site) if they had changed the patch management or if they were doing something.

As it happened they were running the PMImport after having removing unnecessary languages and platforms. As I remembered from past .Net...