Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Best Practice
Showing posts in English
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....

Ram Champion | 16 Apr 2009 | 0 comments

Hi Connect Members,

Here tool for remote diagnostic tool which has improved features. It allows you to connect remotely Altiris to view configurations and troubleshoot.

Link for tool https://kb.altiris.com/article.asp?article=45023&p=1

Regards
"RAM CHAMPION"

Scot Curry | 14 Apr 2009 | 4 comments

Hi Connect Packagers.  I have agreed to speak at the San Diego Endpoint Management & Security User group.  They have asked me to talk about Advanced Packaging topics.

There are a couple of things that come to mind:  Driver Installation, Self Registration (DON'T DO IT), Upgrades and Patches.

If you were coming to an Advanced Packaging presentation, what would you like / expect to see.

Thank you for your input.

R-Vijay | 12 Apr 2009 | 0 comments

While both deferred and immediate custom actions can run in the context of the user initiating the installation, only deferred custom actions can run elevated using the system context.

Deferred custom actions can only be sequenced between the InstallInitialize and InstallFinalize actions in execute sequence tables. Immediate custom actions, on the other hand, can be sequenced anywhere within any of the sequence tables. Deferred custom actions are not executed immediately. Instead they are scheduled to run later during the execution script. The execution script isn't processed until the InstallExecute, InstallExecuteAgain, or InstallFinalize action is run.

Deferred custom actions cannot access the installation database. In fact, deferred custom actions have very limited access to the installation session because an installation script can be executed outside of the installation session that created it. Immediate custom actions have access to the installation...

WiseUser | 03 Apr 2009 | 5 comments

Best way to register a dll which is part of the package is ,

Go to Files section in Wise Package Studio

Select the dll  -> Double click the dll - > go to self registeration ->

Select the Registration method -> Use order specified below...

These steps will result in auotomatic self registration in the package using

Msiexec.exe /y & /z for registeration \ unregister the dll.

kewidogg | 02 Apr 2009 | 0 comments

There are two ways you can get the client to report to the correct console.

These solutions assume you have a remote client installed, and that it is targeting a console other than the closest one:

Stop the Ghost Service

  • Click Start > Control Panel > Administrative Services > Services
  • Scroll down to any Symantec products. Click the Symantec product and click "Stop the service".

Delete pubkey.crt and dnscache.txt

  • Browse to C:\Program Files\Symantec\Ghost and delete the pubkey.crt and dnscache.txt files.

Start the Ghost Service

  • Click Start > Control Panel > Administrative Services > Services
  • Scroll down to any Symantec products. Click the Symantec product and click "Start the service".

You can reset the client:

Once the service is restarted, the client will search for the nearest console.

Copy the pubkey from the new...

kewidogg | 02 Apr 2009 | 5 comments

This can occur when you do not have enough space on the C:\ drive. Even though the ISO might be created to a external or shared network device, the boot wizard still creates files temporarily to the C:\ drive.

Simple Solution:

Remove files to clear up space on the C:\ drive, and try to create the ISO again.

Advanced Solution:

NOTE: Symantec does not provide support for modifying the registry. Please modify at your own risk.

First, back up your registry. Open the registry, and go to File > Export... and save the registry to a safe location.

To solve the issue, you can direct all temporary files to another location (such as a mapped drive, or external USB device).

Browse to the key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

And modify the key:

TEMP (the default location it is set to is %SystemRoom%\Temp)

Modify this key to point to your external or shared...

Terry Cutler | 30 Mar 2009 | 0 comments

Perhaps a better question is - How can the current Intel vPro Technology combined with existing management\security solutions help protect client systems?

This is not an attempt to scare or over-generalize the reality of security threats such as the Conficker worm.  The intent is directed to how a real-world situation can be addressed.  The suggestions below assume Intel vPro Technology is already configured within your environment - thus you are ready and able to use the out-of-band management technology in connection with existing "in-band" management tools.

 An overview of the Conficker worm is available online. The following are a few examples:

carubin | 26 Mar 2009 | 2 comments

I cut my teeth in the Altiris world with Deployment Server and it still is my preferred way of managing the workstations in our environment.  I like the speed and the instant feedback.  Today, though, I encountered a situation that made me glad I had NS in my toolkit.

We needed to add an internal web site to the list of trusted sites.  You can do this through a registry entry but the entry is to HKEY_Current_User.  In DS there was no way that I could think of to touch this key but in NS I just set the job to run for all users of the machine and voila problem solved.

Raman | 23 Mar 2009 | 0 comments

Well here is a document that covers all the scripts that are required for Microsoft ADS, I hope to be informative for you.

Regards

Raman