Video Screencast Help
Search Video Help Close Back
to help

Endpoint Management Community Blog

Showing posts in English
Tim.Jing | 22 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.

 

ianatkin | 20 Feb 2013 | 0 comments

Spent the last couple of hours looking into an issue with the Altiris 6 Helpdesk. As I couldn't find the issue reported elsewhere, and its bitten me before I thought I'd just pop this in the blog.

In summary,  be aware that for practical purposes the limit for attachment filenames in the Altiris Helpdesk is 63 characters.  If you are using Microsoft Exchange for your enterprise email services, internal users mailing into the helpdesk with attachment filenames exceeding this limit will have their attachment silently dropped.

The evidence of a ticket having a dropped attachment is found in ticket history: it will state that ‘the following attachments were added:’ in the incident update without stating the filename (as would normally be the case).

The workaround we put in place is to have helpdesk email going to an mailbox which is then automatically forwarded to the helpdesk. This allows our...

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

Ludovic Ferre | 20 Feb 2013 | 0 comments

One of my customer reported a problem that caused one of their child nothing server to run at 100% CPU and consume almost all memory (out of 32GiB available).

I first looked at the timing (it was reported last Friday) and I thought this was possibly linked to the PMImport release as last week we had Patch Tuesday (so we released the PMImport Wednesday and replicated it to the child server Thursday evening.

But this was not it. First the memory ballooning problem happened on 3 different processes: the w3wp pools for the Altiris-NS-Agent and TaskManagement as well as the AeXSvc itself.

With all three processes running we would see large chunks of memory being released in a clean drop and go right back up in after nice curve. This was because the 3 processes were fighting for the scarce memory resources and causing each other to have to be scavenged every now and then.

Stopping on of the application pool pegged the memory to ~12 GiB for each of the other...

Sumit G | 19 Feb 2013 | 0 comments

Hi Firends,

In this blog, I have attached the Symantec PcAnywhere Best Practices and Troubleshoot. Hope it help to you.

Symantec pcAnywhere™ Solution 12.6.7 Release Notes

 

Article:DOC5350

 | 

Created: 2012-02-15

 | 

Updated: 2012-07-17

 | 

Article URL http://www.symantec.com/docs/DOC5350

 

About the pcAnywhere 12.5 SP4 and pcAnywhere Solution 12.6.7 releases

 

Article:DOC5442

 | 

...

Tim.Jing | 19 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...

Ludovic Ferre | 18 Feb 2013 | 0 comments

Based on demand I have updated both the PatchAutomation [1] and ZeroDayPatch [2]downloads with a few additional features that allow the user to better control which bulletins are handle and how to invoke the tools.

Here are the new feature command line details:

/config=<file path>
    Reads the file at the provided path and parses each line for com-
    -mand line options. Here is a sample config file content:
      /severity=critical
      /custom-sp=CWoC_GetAllBulletins
      /vendor=google
      /dryrun
      /debug

/custom-sp=<sp_name>
    This option allows the user to specify a custom stored procedure to
    be called during the execution. The stored procedure may be present
    on the database (if not the automate will return with no errors) and
    must contains the following columns that are used and needed:
      * _resourceguid [Software bulletin guid]
      * released [Software bulletin release date]
      * bulletin [Bulletin...
ohzone | 15 Feb 2013 | 1 comment

The Endpoint Management team is gearing up to celebrate another successful event at Symantec Vision. Filled with new sessions and the same 1:1 access to Product Management and Development, it’s time to register and start customizing your Vision Experience.

This year, Vision is all about the extras—including new types of breakout sessions and hands-on labs, expanded networking opportunities, and even more flexibility to customize your Vision experience. You might even win the chance to choose your own Grand Prize. So register now, and then visit the Vision website to:

  • Explore the Vision Session Catalog. Then choose sessions that will help you embrace BYOD and support all the...
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.

 

:)

 

Sumit G | 19 Feb 2013 | 0 comments

Best Practices articles of Symantec Software Management 7.1

 

Symantec Software Management 7.1 Best Practices, Part 1
 
https://www-secure.symantec.com/connect/articles/symantec-software-management-71-best-practices-part-1
 

Symantec Software Management 7.1 Best Practices, Part 2
 
https://www-secure.symantec.com/connect/articles/symantec-software-management-71-best-practices-part-2
 

 
Symantec Software Management 7.1 Best Practices, Part 3
 
https://www-secure.symantec.com/connect/articles/symantec-software-...