Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Features
Showing posts in English
Ram Champion | 03 Jun 2009 | 0 comments

Hi Connect Members,
This documant covers basic information about Windows 2008 cluster technologies concepts and new features that are introduced in Windows 2008 clusters.


R-Vijay | 05 May 2009 | 5 comments

Hi Folks, I have made a 12 minutes long video, which explains the File/Registry Virtualization Phenomenon, its limitation and benefits along with a small demo.I have also attached the executable which i have used in this video. You can try the same too..!!

Refer to the link below.,

Kindly check the same and let me know your comments on this.

adtlink | 04 May 2009 | 3 comments

The beta for Data Connector 7.0 is now available for download. As part of the 7.0 release, we have moved the Connector functionality into the Symantec Management Platform and it is no longer a standalone solution. The functionality will now be available to all solutions and customers.

Highlights of this release include:

  • Import Organizational Views and Groups - This allows you to create and populate new Organizational View and Groups structures from any of the data sources that Connector supports.
  • User Interface/Usability updates - The User Interface has been re-factored to help with usability and make connector integrations even easier.
  • Virtual Data Classes - A Virtual Data Class allows you to federate data into the Notification Server CMDB. This is done by creating a key from a resource type in the CMDB to an external source. You can then reference data from the other data source without importing the data. This data can then be used in...
jnaef | 04 May 2009 | 0 comments

Slides from:

Expanding on Altiris - Mike Langford

Benifits of the Ghost and Deployment Solution Convergence - Symantec

Intorduction to WorkFlow - Incendio

Randall Newnham | 28 Apr 2009 | 0 comments

There are some hardware setups that require using a different version of WIndows PE than WIndows PE 2.0, which is what the Ghost Boot Wizard in Ghost Solution Suite 2.5 uses. The disadvantage to using custom Windows PE boot disks is that some options that are available in the boot wizard are either not available, or it is not intuitive to include. One of these features is DeployAnywhere, the Ghost utility for injecting drivers into a machine after an image is deployed. This method will allow you to use that feature even if you have to use a different PE environment.

How to add DeployAnywhere:

1. Add this file to the PE environemnt:

C:\Program Files\Symantec\Ghost\GhDplyAw32.exe

2. Add this folder to the PE environment:

C:\Documents & Settings\All Users\Application Data\Symantec\Ghost\Template\common\windrivers

This provides the executable and the drivers necessary for evaluating and retargeting. Here is the...

R-Vijay | 27 Apr 2009 | 2 comments

Hi Guys, I have made a 10 minutes video explaining the basics of UAC and its improvements w.r.t Windows 7.
Find the link below for more information,

 Please do check and let me know your comments.

Mohammad Bamya | 20 Apr 2009 | 1 comment

Once the client machine boots up into the PreOS it will need an IP address to communicate with the Ghost Cast Server, and by default that IP address will come from the DHCP. When there is no DHCP server, the client machine will not get any IP address, hence, the machine will not be able to communicate with the Ghost Cast Server.

To force the PreOS WinPE or WinPE-512 to use a static IP address:

  1. Go to "\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\winpe\ghost" for WinPE and "\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\winpe-512\ghost" for WinPE-512
  2. Remove the read only from start.bat
  3. Edit start.bat using the notepad and add the following line between x: and cd \ghost

    netsh int ip set address local static

    (IP address of with a Subnet Mask of and a Default Gateway of would be set on...

jloubser | 18 Apr 2009 | 3 comments

One of the most frustrating things I have encountered using Altiris for software deployment purposes is that in order for me to push a number of packages to any given target device such that the packages require to be installed in a specified order, I would have to create a sequential software delivery task.
Creating this as a once off or even two or three times is not an issue, but when I become twenty or thirty times with no end in sight then it gets real old real quick.

What I suggest is that a mechanisim be put in place to rank the created packages and that the installation order would then depend upon the ranking the package was given.

For example, say I build a new device and that that device due the the area it is to be employed in requires 20 different applications to be installed before delivery. The build team could then either via the software portal or whatever other mechanisim select the 20 applications required for the installation and press the...

jloubser | 18 Apr 2009 | 2 comments

Of the things I miss the most when working with the Altiris suite the following two things are pretty close to the top of the list:
Customisable user message screens which may be associated per deployment task type. In other words, I don't want to have to create such type things to be part of my deployment package. A simple interface which allows me to communicate with my target audience with reference to what is about to happen on their device would be most useful. Connected to this is the lack of ability to have a countdown timer which may be associated with the task in question. For example, I deploy a certain job which requires the user to click on ok. The problem with this is that most users will just ignore this message, putting it into the background. What would be most useful is if I can set a timer on the job such that if the user has not clicked on ok within the set timeframe the job then automatically executes. This accompanied with a visible countdown box which...

jamesmax | 16 Apr 2009 | 0 comments

In my search to improve my arsenal of Altiris products, I wanted to know when some of the new 7.0 products were being released. First, I download the installer for the Altiris Client Management Suite. I looked at the requirements page and saw the requirements are “Windows 2003 Server or better”. So, I prepared a Windows Server 2008 (64 bit and 32 bit) VM to test it on. It didn't install on either. After trying it and speaking with technical support, I found out that The Altiris Client Management Suite, as of right now, works only a Windows 2003 Server 32-bit. They said that you should be able to install it on Windows Server 2008 in the near future (probably this summer - time will tell).

Once you run the installer,  it will install the Symantec Installation Manager....