Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Endpoint Management Community Blog

Showing posts tagged with Altiris Client Management Suite
Showing posts in English
ShaneB | 26 Feb 2013 | 0 comments

https://www.publicsector.shidirect.com/Webinars/SeminarRegister.aspx?SeminarSeriesId=813

 

I just wanted to post this event on the connect page and see if anyone else from the user group planned on attending?  WKU will have a few folks there.

ohzone - CherylPeterson | 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 different devices across your organization or...
Sumit G | 15 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-...

Kavitha Gowda | 12 Feb 2013 | 0 comments

ServiceDesk Pack 7.5 for IT Analytics 7.1 SP2 User Guide is now live at the following location:

http://www.symantec.com/docs/DOC5639

 

ohzone - CherylPeterson | 08 Feb 2013 | 0 comments

Kwizda, a leading Austrian pharmaceutical company, needed to streamline management and lower costs associated with managing some 900 clients and virtual servers. To further complicate the issue, the clients and servers were scattered across sixteen sites. Kwizda turned to Altiris Client Management Suite from Symantec to address these challenges. As a result, Kwizda has lowered the time required to upgrade to the latest edition of Windows by 40 percent, reduced its investment in unnecessary software licenses and maintenance, and enabled the team to troubleshoot systems 20 percent more quickly. To learn more about Kwizda’s successful implementation of Altiris products, check out this link http://bit.ly/XMwdpw  

Tim.Jing | 07 Feb 2013 | 2 comments

Great call today, Altiris support is like a box of chocolate, unless you are nice to some people and they can get you connected with the right people.

Chatted for a while with Thomas Baird today, he's brilliant like Brent Bishop. 2 of the smartest Altiris guys I've ever had a chance to working with. So on with the items of the day. 

We narrowed our top production issues to 3 main items, with a bunch of sub-issues that I sent to Symantec in an email hoping to have the DS team address with some efficiency. 

 

Issue 1. Machines gets a Device not capable at times. So the issues stems from inventory more than SBS as we originally thought. The NSE processing as Inventory vs Initial Deploy. So Changes were made to initial deploy and testing continues I will say now image to existing machines do work(See issues 3 for more details) but new machines remains to be tested. So the beta solution is fake a InitialDeployment task and get the NSE...

Tim.Jing | 07 Feb 2013 | 0 comments

A lot of questions for Altiris support today. The product is piloting very well to this point with the exception being the Deployment Solutions.

The amount of issues with the product, the oddness of the logic in execution hopefully will be answered by someone in the DS team on a scheduled call today. There is a list of items I'm hoping to get answers for.

1. Hierarchy, why certain things replicate and what for. like Images built for a Child NS server does not replicate up, but the resource guid does. So you can see it at the parent but not assign it as a job.

2. Imaging, lots of issues with the supported method and mechanism that it performs to connect a WinPE machine to a known Guid.

3. PXE or now changed Symantec Boot Services. It behaves badly, and other than restarting services no details or documentations on any possible tweaks.

4. x86 for WinPE has broken Firm files.

5. Replication of PXE configs does not always work.

6....

Tim.Jing | 06 Feb 2013 | 1 comment

Fixed a few things yesterday if you are keeping up with this still. The PXE/WinPE loading issue is working for now. but our cases with Symantec is stacking up.

There are 5 open cases which all seemed to be shuffled around from technician to technicians. When I get time I will be calling the duty manager to escalate them to the DS team as they are almost all DS related.

So the new issues:

Some machines does not always boot in to WinPE. They just wont do it even with a SBS rebuild and only on some jobs. Unfortunately this happened to one of my image machines. It imaged fine on Child Server 1's Site server 1. But will not boot in to PXE on Child server 2's Site server 2.

When an image is captured. Which means we had to force the machine to shutdown after the Syprep. They delete the image capture job and apply a Image capture task. Well now the Image Deploy job will not allow us to populate the Serial # after selecting the image. Look at the red...

Tim.Jing | 05 Feb 2013 | 0 comments

This feels like being smacked at every turn. So Monday morning fresh start, we did get ghost image to work last Friday right?

  1. First up, huge issues, GhostUser account keeps sitting there after imaging. Someone has to go hit the OK button to the GP related Eula for the Ghost job to finish(What ever that task is?) So basically no automation.
  2. Second, 2 of the other Child NS's will not keep pxe running.

Cases put in to Symantec, of course it will be at least a day before we get anyone on the phone. So Google, and Connect it is.

By 3PM, we found the cause of both issues.

1. GhostUser does not log in. There is a new version of DeployAnywhere that resolves this, and it's a known issues since 4-17-2012, why is this not in MP1??? So look and get the files from this link below if you have the same issue.

...

Tim.Jing | 04 Feb 2013 | 4 comments

Finally got Image deploy to work where it would take the computer name in the console!

It starts with Using ghost(Which is crap IMO). Then Using Symantec's built in Capture image job, then deploy. And you have to use 64bit PE because there is a known issue where 32bit PE does not have Firm which causes the unattended.xml to not get copied, and the job would hang and fail after imaging.

So today, more image testing with 32 bit, and throwing out all the great logic we had planned with this product.

 

Original logic:

Image x -> Script in the correct agent installer(hierarchy) -> Copy local all base sw -> Boot to windows and use unattend.xml to install all software and agent.

 

Now it's back to:

Ghost-> Tasks->

 

So the big hurdle. Since Ghost is doing it's thing in the back ground, we have no way to manipulate the agent(It configures to the aprents server the image...