Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Deployment Solution
Showing posts in English
Santana_Villa | 26 Mar 2013 | 0 comments

Product or Solution release details includes the following:

  • Version
  • Release Type
  • Release Date
  • End of Life
  • End of Limited Support
  • Last date for patch releases
  • End of Support Life
  • Last date to contact support

To get that information follow the steps below:

  1. Go to Supported Products A-Z  page.
  2. Select the product from the list
  3. On the right side box named “Product Support” select “Release Details”
  4. The information for selected product will be loaded on the main page.
  5. Use the dropdown menu to select the correct version of the product you are looking for.
  6. Example: see direct link to...
ianatkin | 21 Mar 2013 | 0 comments

Good news from Symantec CEO Steve Bennett has arrived in the form of a Customer and Partner letter.

The important bit for us is that Endpoint Management is explictly listed as being a critical part of the Symantec portolio moving forward. This is something which was not clear in the previous company strategy annoucement.

He closes by saying,

"Despite any rumors to the contrary, all of these technologies remain a critical part of our product development and overall portfolio. We believe that through greater alignment of these technologies, Symantec will improve our product integration to help you improve and simplify your end users’ IT experiences"

I'm blogging this out as I know there are many Altiris Administrators out there who will let out a huge sigh of relief on this one.

Kind Regards,

varaprasad_ravuri | 28 Feb 2013 | 0 comments


REM Partition Format Local Disk
REM Create diskpart script file
echo select disk 0 > %ALTIRIS_SHARE%\temp\diskpart%ID%.txt
echo clean >> %ALTIRIS_SHARE%\temp\diskpart%ID%.txt
echo create partition primary align=64 >> %ALTIRIS_SHARE%\temp\diskpart%ID%.txt
echo select partition 1 >> %ALTIRIS_SHARE%\temp\diskpart%ID%.txt
echo active >> %ALTIRIS_SHARE%\temp\diskpart%ID%.txt
echo assign letter=C >> %ALTIRIS_SHARE%\temp\diskpart%ID%.txt
echo format fs=ntfs quick override >> %ALTIRIS_SHARE%\temp\diskpart%ID%.txt 
REM Execute diskpart command 
diskpart /s  %ALTIRIS_SHARE%\temp\diskpart%ID%.txt
REM Delete diskpart script file 
del %ALTIRIS_SHARE%\temp\diskpart%ID%.txt
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...

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




Tim.Jing | 11 Feb 2013 | 0 comments

It feels like my freshman years in the IT business, where there is no fear, not a single worry. Beer and pizza will be there later, and all things will work it's self out.

Well I am lost for words on this product deployment so far. Lots of bells and whistles to see in the Altiris 7.5 SMP, tons of automated actions that you don't have to script to do. Something you can train even beginner IT forayers to use in the console when it comes to software management, Patch and Inventory.

Until you get to the DS, we suddenly have lost our ability to image machines. As in issues on both Notification servers, separate issues, different errors. But bottom line is simply we cant reliably deploy any images.

The issues seems to relate to either timing, or design. The NSE's are supposed to get processed with priorities, and since inventory is one of the least important it becomes at the back of the line. So we went to Initial Deploy as a method for sending a highly...

ianatkin | 11 Feb 2013 | 0 comments

Today I'm taking a break from Shylock woes and instead looking at an issue one of the team raised regarding inconsistent jobs on our deployment server. Specifically, we've got two versions of a script task on our deployment servers where only one should exist. This is a nice task it's one of those jobs which looks horrible to correct, but it's actually easy to correct with just a bit of SQL knowledge.

The embedded script task in question begins with the string 'REM Resolve Shortcuts' so I quickly put together a little SQL to see where the problem lay,

select count(*),script from script_task
where script like 'REM Resolve Shortcuts%'
group by script
The result of this is.
30 REM Resolve Shortcuts using SQLCMD.EXE (v1.2) .....
6 REM Resolve Shortcuts using SQLCMD.EXE (v1.2) .....