Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Configuring
Showing posts in English
trb48 | 29 Mar 2007 | 2 comments

I was just reading Universal Silent Switch Finder posted by duijsterj. I really liked the tool because I have spent a lot of time creating what I call Silent Install Packages (and the tool that he mentioned will save me a ton of time in the future).

Basically, if I have to install something I will find out all of the switches I need to use to make it install itself. Here are some resources that I have found that makes creating silent install packages much easier:

stebro | 27 Mar 2007 | 0 comments

Release versions for Endpoint Security Solution are as follows.

6.0 GA - 243
Hot Fix 1 - 244
Hot Fix 2 - 244
6.0 Service Pack 1 – 357

Versions will appear in the Solutions Center as well as the Altiris Agent details. The major version will appear as 6.0 in the solutions center, but 3.2 in the Altiris agent.

For example, 6.0 GA will appear as 6.0.243 in the Solutions Center and 3.2.243 in the Altiris Agent details.

trb48 | 25 Mar 2007 | 6 comments

Do you ever have to push out large software packages to thousands of computers under your care? If you push out a big software package does it always install? Here's a secret that'll help with the heavy lifting.

When I have pushed out large software packages I always ran into the same problem: there was not enough time at night to push the software out and install it. This became a big problem under a tight schedule.

After trying several different work-arounds, I came up with a really simple, yet effective solution:

  • Create a job in Deployment Console that copies the software package to destination computers. This should be done during the day.
  • Create a second job, that is scheduled to run at night. This job will actually install the software.

This way, you can install the software on all of the...

BRING | 25 Mar 2007 | 0 comments

In this day and age, tight security is something we all strive for. As a means to that end, changing the expected lay of the land (using non-standard server ports) is a route some of you are taking to slow down the bad guys. If you've wanted to use these ports in your Altiris client communication, here's the guide.

On the outset, it can seem to be a daunting task. However, a recent article added to the Altiris Knowledge Base can help you get it done.

Titled "Notification Server and Non Standard Ports", this is the step-by-step guide to getting your environment talking a bit more securely.

See KB Article 33867, found at:

trb48 | 23 Mar 2007 | 9 comments

Windows XP comes with a number of cool features -- some of which many of us haven't had time to explore enough to fully understand. One such feature is System Restore. Here's some info about the System Restore feature and a suggestion as to when you might want to switch it off.

System Restore periodically takes a snapshot of your computer. You can use the snapshots to restore your computer to a previous state. Windows automatically and regularly makes snapshots to help save your neck when your computer unexpectedly dies. Some programs will actually create a snapshot before they install themselves -- just in case.

If, for example, you are using SVS to test applications, or your solution to fixing...

Screenbert | 16 Mar 2007 | 0 comments

The network discovery process is a great feature in Altiris, but you can only input ranges to include or exclude one at a time. The console does not have an option to allow you to enter a list of ranges.

To get around this, right-click on the Network Discovery Policy and choose export. Save the XML file to your hard drive and open it with a text editor or an XML editor. Find the include IP or exclude IP range and just add additional ranges.

<include ip="" endMask="" type="range" /> 
<exclude ip="" endMask="" type="range" />

Just be sure to keep the same formatting and also to keep the includes and excludes in their appropriate sections.

After you add all your new inclusions or exclusions right-click on the folder that has your Network Discovery Policies and choose Import. Select the XML file you saved and edited and you now have all your entries.

This is a great time-saver when entering multiple entries...

diluzio | 15 Mar 2007 | 0 comments

Okay, maybe there are times when you don't want users to vote on your knowledge base articles. If you're a member of that club, diluzio has figured out how to tweak the code and eliminate the votes.

As with any changes, make sure you have a good backup first.

Most importantly, make a copy of the ArticleView.ascx, in \Program Files\Altiris\Helpdesk\AeXHD\templates.

Then all you have to do is comment out one line in the ArticleView.ascx template. Comment out the line which starts:


dmorrison | 08 Mar 2007 | 0 comments

In large environments, the notification policy for "Managed computers with zero or more than one Agent Settings Policy applied" can run for a very long time due to the structure of the query populating the e-mail for the policy. The query can time-out and ties up valuable resources. Here's a fix.

Note: this policy should only be enabled on client facing Notification Servers, never on a Notification Server to which inventory has been forwarded.

A more efficient query is at the end of this tech tip. It ran in 6 seconds versus 9+ minutes for the standard Altiris query. Databases with larger numbers of clients, collections and policies will benefit most from the more efficient query.

Here are the steps required to take advantage of the query:

  1. Disable the Altiris policy "Managed computers with zero or more...
Jeanne | 08 Mar 2007 | 1 comment

Let me start this by saying I know how helpful Active Directory (AD) can be. Unfortunately, our network admin has yet to learn this valuable life lesson ;)

We started out with Deployment Solution installed with AClient. We then upgraded to CMS Level 1 and installed a Notification Server since we do not have AD and our network is segmented with VLANs.

The challenge was to get the Altiris Agent deployed to each of the systems without the help of AD. To complicate matters, our systems are locked down with DeepFreeze since we are a college.

One of my staff members wrote a little script to get the systems unfroze and another script to refreeze them. We then created a Rapid Install Package (RIP) and installed the agent in the RIP. This allowed us to get the Agent on all of our lab systems and start using the NS console.

eorme | 15 Feb 2007 | 6 comments

In environments where security is a major issue, many network administrators have elected to not use PXE on their servers. This doesn't mean, however, that Deployment Solution for Dell Servers 2.0 SP1 cannot be used to perform configurations. Follow these steps to create an automation disc which will allow you boot into automation and configure BIOS/BMC/DRAC/RAID or deploy an operating system all without PXE.

I'm using Linux in this example, but WinPE is done in a similar way.

Prerequisites: Deployment Solution for Dell Servers 2.0 SP1 on DS 6.8 or newer.

Step 1: Go to Tools->Boot Disk Creator and create a new configuration.

Step 2: Name your configuration, select Linux, and change the OEM extensions from "<none>" to "<default>". This will inject all of the Dell drivers that are needed in order to boot the Linux automation properly. If you experience difficulties with that image, you may try the "Dell" as an...