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
Eric Szewczyk | 10 Dec 2008 | 0 comments

THE one-stop for anything and everything relating to Dell Deployment

I'm often asked as a pre-sales Engineer for Symantec, "Where is the best place to find resources for the Deployment Solution for Dell Servers product?" Information such as how-to instructional videos, product documentation, product downloads, Dell resources, links to support, white papers, canned demos, and customer success stories.

We haven't really promoted this site on the community forums as being THE one-stop for all things relating to the Deployment Solution for Dell Servers product. The site is maintained as new information becomes available. So if you haven't checked out the site, please do so and make sure you bookmark it while you're there for safe keeping.

...

Virtualized App Guy | 30 Nov 2008 | 0 comments

The central component of a Deployment System, the Deployment Server manages the Deployment Database, manages communication between the different components, and schedules jobs to run on managed computers.

See details about integrating Altiris Deployment Solution and Altiris Software Virtualization Solution in the Juice article: http://juice.altiris.com/node/39

The Express Console, however, may be virtualized. This is particularly useful if you are administering different servers running different versions of Deployment System.

Jordan Gardner | 18 Nov 2008 | 1 comment

Perhaps you have heard that there was another battery recall announcement made on 10/30/2008 for Sony batteries manufactured from 10/2004 to 6/2005 which affect HP, DELL and Toshiba. While these batteries may have been manufactured some time ago, they may exist in some of the notebook models in your environment today. For a complete list of affected Dell Notebooks you can visit https://www.dellbatteryprogram.com/

Those who have Dell notebooks in their environment will be happy to know that Dell Client Manager pulls enough information to identify batteries by manufacture and manufactured date.

This tech tip includes a DCM 2.2 report which can be imported into any NS running DCM 2.2. Using this report, you can easily identify those...

R-Vijay | 11 Nov 2008 | 0 comments

Here are some component guidelines which you need to follow in your application MSI. This will solve many issues like installation fix and automatic package repairs.

Always remember,

  • HKLM + HKCU in same component are not allowed
  • HKCR + HKCU in same component are not allowed
  • HKCU + Files in same component are not allowed. (Exception where the files are going to user profiles and key path is HKCU key path)

Also, when you design a custom component having HKCR or HKLM components, do check the Auto increment option; this helps the machine maintain a stable state.

Raman | 04 Nov 2008 | 5 comments

Ever had query on Wise Package Studio? Here is the website that will answer your queries. It is designed for the beginner.

http://www.dawnstar.com.au/wpshelp/

Nelo | 29 Sep 2008 | 0 comments

Deployment Solution 6.9 adds a new feature to import/export computers to an XML file.

The XML file contains the computer name, asset tag, serial number, UUID, NICs information. The most useful information is the computer group that the computer is a member.

Importing computers now allows importing an XML file and such file could now be modified to import multiple computers to computer groupings in the Deployment Console.

Import and Export computers is located under the File Menu - Deployment Solution Console.

The following is an example of one computer:

- <?xml version="1.0" encoding="utf-8" ?> 
- <computers ver="14" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" -xsi:noNamespaceSchemaLocation="computers.xsd">
- <computer>
- <name>RACK01C10</name> 
- <...
TilakGovind | 09 Sep 2008 | 2 comments

How can you check to see if an application works with all other files with associated extensions?

After installing the application create one text file on the desktop and create one new folder.
Double Click -> Go to Tools Folder Option -> View

Choose Show all Hidden Files and Folders and uncheck Hidden Extension for known file types
Click Apply and OK.

Now go to that text file and change the file extension related to application then it will change in to that particular application icon.

TilakGovind | 08 Sep 2008 | 9 comments

For some applications which have ODBC drivers, you may question if the application has created an ODBC driver or not? This tip will help you answer that question.

Go to Control Panel > Administrative Tools. Double click ODBC and check User DSN and System DSN and File DSN. If the application used drivers, then there will be entries in any one of the DSN.

OR

After installing the application go to C:\windows \ click ODBC.ini and checks if particular applications need any driver.

TilakGovind | 05 Sep 2008 | 1 comment

There is a situation that happens where we all get confused while working on excluding lists.

Then when you complete a Setup Capture, the resulting package contains both necessary and unnecessary information and entries for the installation. The unnecessary information should be removed so it is important to know which entries are extra and what information is not important.

This is where having a concise Exclusion list becomes invaluable in ensuring that only non-essential keys and files are removed from the MSI.

Exclusion List

An Exclusion list of Files and Registry Keys has been compiled over time and is constantly being amended and updated. The following is said list as it currently stands.

Search the Database for the following list of items below. Go to the Setup Editor > Tables Right Click >...

piyushnasa | 27 Aug 2008 | 5 comments

Many times I come across articles, where people discuss on which to choose WISE Script or VBScript while creating Custom Action in the package. Here are some advantages and disadvantages of both.

While WISE Script is easy to make, I mean takes less effort, VBScript can be very complicated. People who do not know VBScript often find themselves searching for, and copying code from net. WISE Script can be easily written once you have basic understanding of statements. I give this point as an advantage to WISE Script, but people who know how to code in VBScript, will always choose that as an easy option.

Personally, I prefer VBScript over WISE Script because it has some really good advantages. As you might know, we compile WISE Script to an exe and include that in a package. But in doing this, we lose the code which we have written...