Endpoint Management Community Blog

Work around for making office 2007 work on servers with terminal services enabled

WiseUser | 22 Oct 2009 | 0 comments

When we try to install office 2007 which is 32 bit installation on a windows server with terminal services enabled you will be getting the following errors

Error Information :

Loaded Dll : \\sbc-netapp01\Install\microsoft\Sv_office_ent_2007\Enterprise.WW\OSETUP.DLL.
Catalyst version is : 12.0.4518.1014
JobExecutionMode is InstallExecutionMode.
Error: failed MsiEnumProducts ErrorCode: 2(0x2).
Catalyst execution finished: 02/08/2008 10:44:24. Return code: 30015. Exception caught: ErrorCodeOnly.
PERF: TickCount=544812 Name=RunSetup Description=End function

Solution or work around suggested for this problem

Open Terminal Services Configuration.
Click Server Settings.
Right-click Permission Compatibility, and then click Properties.
Click to select the...

Using System Search Option in Wise package Studio to Check for .net Framework 2.0

WiseUser | 13 Oct 2009 | 2 comments

How to Check for prerequisite Microsoft .Net framework 2.0 installed on the machine before installation ?

1. Define a Property Name as DOTNET2 in the properties section to Null
2. In System Search Add -> Registry and do the following
   Property - DOTNET2
   Operation - Read raw value from registry
   Root - HKEY_LOCAL_MACHINE
   Key -SOFTWARE\Microsoft\.NETFramework\policy\v2.0
   Value Name - 50727

3. Go to Launch Condition - Build the condition

DOTNET2="50727-50727"

For Checking .net version 1.0

Regvalue name is SOFTWARE\Microsoft\.NETFramework\policy\v1.1

Value is "3706-4322"

How to Customize Office 2007 Deployments

WiseUser | 06 Oct 2009 | 1 comment

1. Create your Office customization by running

setup.exe /admin

Which will open up the Office Customization tool

2. Select Create a new Office Professional Plus 2007 option

3. Take the settings as you want in the following set of options available

a) Setup
b) Features
c) Additional Content
d) Outlook

4. Save the resulting msp in the same directory

5. Run the setup.exe with following option

setup.exe /admin office.msp

Tips to update the patches

If we get any updates, say any patches from Microsoft then place it in Updates folder

Setup.exe has a logic to read and execute the newly found msp files from the Updates folder

How to self register the dll

WiseUser | 17 Sep 2009 | 1 comment

How to register a dll using Msiexec.exe /y and Msiexec.exe /z

1. Go to File Section where the file is present
2. Double click the file
3. Goto Self registration tab
4. Selct the registration Method as "Use order Specified below"
5. Hit ok

Goto MSi Script section and you can find corresponding custom action for registeration .

Why we do this type of dll\ocx registration Compared to self reg table is ?

If the dll registration gets wrongly captured in the self reg table then it will throw error upon installation . When we install using the above suggested method then it wont throw any error if dll is not getting registered.

MSI Script Sequences

nac | 17 Sep 2009 | 1 comment

Many times we interfere with the MSI script sequence in InstallExecute sequence, AdminExecuteSequence, advertised sequence, InstallUISequence, AdminUISequence. Following lists will be helpful in maintaining proper sequence.

It's not necessory that sequence number should be like this only but order is suggested to be the same.

InstallExecuteSequence

...

Action	Condition	Sequence
LaunchConditions		100
AppSearch

Windows Installer Error 1603 is a generic machine-specific issue

WiseUser | 15 Sep 2009 | 0 comments

Error 1603 is a generic machine-specific issue .

One or more of the following fixes may resolve the error .

This error is known to occur on computers that do not have enough disk space for the installation.

The temp directory is not clean.

A certain file on the machine is locked. To fix this: Close all applications running in the background.

Reboot your computer.

Run the installation again.

Error 1622 during uninstallation and installation

WiseUser | 15 Sep 2009 | 0 comments

Msi error 1622 during an installation and uninstallation of an msi .

Cause : Error in writing a log file

Example : This Error may occur if we give a folder which is not present during installation or uninstallation

Msiexec /i Xtrader.msi /l*v c:\temp\install\ins.log

If you don't have a folder install under c:\temp the msiexec.exe may throw an error 1622

In order to overcome this issue create a folder before installation or uninstallation or use the existing folder say c:\temp .

CS3 Before Installing CS4 release of fireworks Software

WiseUser | 11 Sep 2009 | 0 comments

How to Uninstall CS3 Before Installing CS4 release of fireworks

1. Copy the uninstall.xml to "%TEMP%\XML\uninstall.xml"

2. Check for the existence of C:\Program Files\Common Files\Adobe\Installers\bbef028176efa5abf0233d3e1747be8

3. Run the Setup.exe --mode=silent --deploymentFile="%TEMP%\XML\uninstall.xml" --skipProcessCheck=1

1402 Error During Uninstallation of Certain MSI Products

WiseUser | 09 Sep 2009 | 1 comment

Scenario when this happens :

When we perform Uninstallation of an msi using a deployment tool when the user is not logged in \ non admin user is logged in

Error Log says :

Product: Roxio Media Manager -- Error 1402.Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Roxio\\Preference. System error 87. Verify that you have sufficient access to that key, or contact your support personnel. Error 1402.Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Roxio\\Preference. System error 87. Verify that you have sufficient access to that key, or contact your support personnel.

Solution :
Opening up the specific registry keys for the users .HKEY_LOCAL_MACHINE\SOFTWARE\Roxio

How to add .NET 2.0 SP2 to the Prerequisites drop-down list

JohanH | 28 Aug 2009 | 3 comments

This topic was discussed here, but I discovered today that there actually is a way to edit the list of MSI files and .NET runtime options on the prerequisites page in Wise Installation Studio 7 (build 7.3.0.259). I wanted to add .NET 2.0 SP2 Framework to the prerequisites, which you by the way can download here.

I copied the Framework setup to a folder that I created in: <Wise installation directory (usually C:\Program Files\Altiris)>\Wise\Windows Installer Editor\Stub\DOTNET2.2.30729

DOTNET2.2.30729 was the folder that I created.

The different versions shown on the prerequisites page is picked from an ini file in the Windows Installer Editor directory. It is named dotnet.ini.

I added the following section to dotnet.ini:

[...

Endpoint Management Community Blog

Links

About Endpoint Management Community Blog

Filter by:

Blog Tags