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
R-Vijay | 26 Aug 2008 | 0 comments

Have you ever thought about creating installer packages in Visual Studio?

Do visit this below link to have more insights on that.

Topics which are covered in this link are,

  1. Building an MSI File: Visual Studio and Orca
  2. Building a Package
  3. A First Look at Shortcuts
  4. More About Properties
  5. GUIDs: Product, Upgrade, and Package Codes
  6. Into the Package with Programming
neil_rogers | 07 Aug 2008 | 0 comments

In Workflow, the term "Collection" is a term that does not refer to traditional Altiris Collections, unless it has the Altiris icon. If it is a blue file box, then it can be used for array items.

Collections are how array handling is done. If you have a list of computers in an array, and need to add a ticket for each one, then use the component: "For each element in Collection."

It has two output paths: Next Element and Finished. The Next Element is similar to a while or for loop. Just loop it through the rest of the components and back to itself. Inside of that process it can have things like matches or equals rules, Commands, Create or Edit Tickets and then the data path goes back to the For Each element in Collection until it runs out of elements!

There are other handy ways to handle items in arrays or add items to arrays...

MBHarmon | 27 Jun 2008 | 0 comments

In some environments, or for some ticket types, there always needs to be a contact. For those options you can create a validation rule that will require this option.

If creating your validation rule for something such as a "Request" Type just enter it with the following parameters:

Name: Contact must be selected

Comment: Requires workers to enter select a contact when none has been selected.

Display this message: Please select a valid contact. The contact field is blank.

When: Every time incident is saved

When ALL of these are TRUE
 "Type" is not equal to "Request"
 "workitem_contact_id" is the same as "1"

To enter the last line of that parameter just use an <Advanced Condition>

CondorMan | 26 Jun 2008 | 4 comments

There are a few ways to have a batch script wait for a number of seconds. The simplest and most widely available without any additional programs is to use the ping command.

The following is is an example... PING!

ECHO Waiting 5 seconds
PING -n 1 -w 5000 > NUL

scottwed | 03 Jun 2008 | 1 comment

In some situations, your workflow process may need to be split into two or more separate streams. For example, you might need to have three people approve a request before continuing. If you did them sequentially, it would take a lot longer to obtain all the necessary approvals.

Updated: Correction, the parallel tasks are not discarded upon the first path reaching an end point. However, the practice of merging is still extremely important to avoid accidental firing of downstream tasks and data dependencies that may not exist. To implement merging, execute the following steps.

Add the Workflow.Advanced.dll to your project by clicking on the "Import Components" button in the left pane of the Designer interface. Select the highlighted item and click Add.

Nelo | 03 Jun 2008 | 2 comments

There are times where PXE booting seems to take a long time especially with WinPE. After making some changes to the MTU (Maximum Transmission Unit) I was able to download WinPE 1.6 and 2.1 under 20 seconds.

Note: this depends in the speed of the network; all my tests are in a fast network.

Launch PXE Configuration tool and select the Multicast tab.

Change the Packet Size from 768 to 1456. Now this works OK for me and I have seen reports that others had success with this as well. If this does not work revert back to 768.

Finally, click save then...

riva11 | 29 May 2008 | 0 comments

Reading my previous heads up How to manage Blue Screen of Death (BSOD) with a description of BSOD event management, I realized that I missed a common problem for many computers. In fact in Windows XP the usual configuration is an automatic restart in case of some serious system error like the BSOD or other major system errors.

This behavior reduces the time to write down many technical details about the error message shown on the screen. The error message can be helpful for use in troubleshooting. But if you don't disable the automatic shutdown you will not have enough time to write down the problem (and normally you only have few seconds)...

The solution is easy and fast, in few minutes the automatic restart option in Windows XP will be disabled only...

R-Vijay | 21 May 2008 | 0 comments

Here's a beautiful link on "how to interpret Windows Installer logs". This is a very essential and a noteworthy bookmark for every packager and administrator.

PS: Don't miss the Annotated Verbose Installer Log section. it contains a pdf file, which contains a log file generated on Vista.


vortex0007 | 14 May 2008 | 3 comments

The Altiris Notification Server 6.x platform was coded using Microsoft's .NET platform and heavily relies upon ASP.NET for much of the functionality of the product. By tuning the default configuration of ASP.NET, a significant performance improvement can be gained on Altiris Notification Servers.

Note that the following recommendations and settings are referenced in Microsoft's online publications. More information can be found by visiting the following Microsoft MSDN web pages:

"Improving .NET Application Performance and Scalability," Chapter 6,

"Thread Pool Attributes" in Chapter 17, "Tuning .NET Application Performance."...

TilakGovind | 14 May 2008 | 2 comments

If you have to install applications to any other Physical Drive (not network drive) you can do so in the following way.

default INSTALLDIR : C:\Program Files\Dir1

Change to D:\Program Files\Dir1

  1. In the MSI Script create a custom action In "User Interface" just after "Cost Finalize"

    "Set Directory" give it a Name, choose the directory by browsing to ProgramFilesFolder\Dir1 and in the third Blank Space enter "D:\Program Files\Dir1"

  2. Create the same Custom action in "Execute Immediate" just after "Cost Finalize" also

    This installation works fine as long as D: is a valid Drive, it does not work on drives that were created using "Subst.exe" Command.