Video Screencast Help

Endpoint Management Community Blog

Showing posts tagged with Installing
Showing posts in English
Ludovic Ferre | 03 Dec 2009 | 3 comments

 Finally (look at the modified date on the file and you'll understand what I mean :D) R12 is out of the door and available on SolutionSam:

http://www.solutionsam.com/solutions/6_0/altiris_ns_6_0_sp3_kb46763.exe

The Release notes are on the AKB [here's the link] but here are some information that can be gleamed from SolutionSam itself:

  • File size is 13,140 KB
  • Modified Date is 22/10/2009

Additionally there are a few fixes that I reported for my customer or that I know will fix some outstanding issues:

  • The Inventory forwarding data verification schedule now functions correctly. Previously, it did not work with large data sets [that's a strange issue we found with my customer back in R6 time frame when the first 20,000 entries...
Ludovic Ferre | 27 Nov 2009 | 0 comments

The week end is coming! And so is winter. Tomorrow I'll probably drop in at an Ubuntu 9.10 install party, but that's about it for IT during the week-end.

Now looking back I can say this week was rich with problems and solutions, and a steady backlog of tiny cases that are queuing up (to be resolved).

What was very interesting this week:

ianatkin | 04 Nov 2009 | 7 comments

Two days ago, Symantec posted security advisory SM09-015 -Symantec Altiris Deployment Solution and Notification Server Management Web Console Browse and Save File ActiveX Overflow.

This vulnerability announcement refers to activeX controls downloaded when accessing the web consoles for Notification Server and Deployment Server. These activeX controls have buffer overflow vulnerabilities which can be exploited should any Altiris Administrator/Worker (who uses the web consoles) visit a malicious website, or possibly open a maliciously crafted HTML email which calls the control. The vulnerability potentially allows unauthorised code execution within the security context of the user's browser.

Although the number of machines hosting these vulnerable DLLs is reserved to computers Altiris...

B_Raj | 27 Oct 2009 | 1 comment

I’m here with 10 Questions & Answers to describe some of the basic things we need to take care while we approach to repackage an application.

 1.How do you Customize the vendor MSI?

 Vendor MSI’s should not be re-packaged or edited. Create a transform file to customize the vendor MSI. 

  • Some vendors supply utilities to customize their MSI behavior. Where this is the case, such utilities should be first considered as the appropriate method of customizing the MSI.  For example, use Microsoft’s Custom Installation Wizard  to customize the Office XP suite.  

2.When will you create a new MSI wrapper/ Wrapper Script?

This technique can be used in scenarios in which the installation program is not in MSI format and a setup capture is not appropriate.

Example:  Service packs and security patches

3.How do you treat INI files while repackage an...

B_Raj | 27 Oct 2009 | 0 comments

The table below lists some of  the language IDs for which the Windows Installer has

localized resource strings.

 

LangID           (Hex)              ACP                (Abbr)           Language (country)

 

 1025                 401                1256                ARA               Arabic (Saudi Arabia)

 1027         ...

B_Raj | 27 Oct 2009 | 3 comments

Greetings!!

My intention by publishing this post is to help the newbies to understand the basics about packaging and repackaging technologies.And ofcurse for those who prepare for interviews !! :-)

 1.What is Application Packaging?

Simply Application packaging means,the process of Creation of an Installation Program for a Software. Or we can say it as creation of a setup file. Setup.exe is an installation file, a program that puts all of the files and registry keys in the right places so that everything works correctly.

  2.What is Application Repackaging?

The process of creating a customized installation using an already packaged installation is termed as Re-packaging.

The setup routine can sometimes be very complex and open to user error especially when thousands of repeat installations are required in a corporate environment. In such environments reliability and repeatability are crucial.

Re-...

B_Raj | 26 Oct 2009 | 0 comments

While we deal with large windows installer packages, time required to install the package is one of the key factor in measuring the efficiency\quality of the package.

I’m briefing  here about some of the techniques that can be used to reduce the installation time of a MSI package.

Using MSIFASTINSTALL Property

The MSIFASTINSTALL property can be used to reduce the time required to install a large Windows Installer package. The property can be set on the command line or in the Property table to configure operations that the user or developer determines are non-essential for the installation.

How MSIFASTINSTALL Property will help to reduce the time?

1. This property helps to skip creating system restore point action in MSI install sequence.

2. This property helps to skip calculating the space requirements action in MSI install sequence. (Filecost)

Thus,if the developer is sure...

B_Raj | 25 Oct 2009 | 0 comments

Msispy is an utility which comes along with Windows installer SDK. If you want to troubleshoot a MSI package in component level or feature level, I will recommend this tool as the best option for repackagers.It provides a nice GUI and command line utilities which makes it very user friendly.

MsiSpy provides a component level view of the products and features installed on a system, using either an MSI Package, or the registry information. Msispy also displays the status of each, and allows you to partially or completely re-install missing or damaged items. You  can also re-configure any product or feature, selecting the install level, and specifying whether to install it locally or run it from a network server.

 Some of the main features are;

  1. It allows you to open an MSI package and display all information about it.
  2. It display information about all the products installed on the computer.
  3. Allows you to load a...
B_Raj | 24 Oct 2009 | 0 comments

This error is due to an error in Directory table of the MSI.

Generally occurs while a directory entry that references something non existent as its parent. If you ignore the ICE 03 validation error (Similar to the below mentioned Eg.) while developing the MSI,During the installation you will be getting the “Internal Error 2705. Directory” error.

Eg: of an ICE 03 error :

Orca validation reports an ICE03 error: “Not a valid foreign key; Table:Directory, Column: Directory_Parent, Key ):newfolder1″

 This error can be fixed by editing the Directory table.The wrong entries in the ‘Directory table’ will be highlighted in red colour.

Steven Grove | 29 Sep 2009 | 2 comments

I have just started a new job in a new place with new people. We have a 16 blade HP server to migrate all services to in the neat future. As of now, multiple services are running on the same servers with no (nada, zip, zero) redundancy. They know it, and they have been trying to get it up but DIACAP has taken all their time. I will chronicle my trials and tribulations on my journey to migrate the Console services and images to a new blade.