Repackaging ZENworks Legacy Files

[sfirmston]

We are currently evaluating AdminStudio 7.5 as we are about to move away from using ZENworks 4.0 and would like to be able to convert our applications from AXT/AOT files into MSI files.

The problem I'm having is that when I convert AXT/AOT files that have registry entries only the Keys come across and not the values. This happens when using either an AXT or AOT file.

Any help would be appriciated as I really like the product and would like to use it but this would be a major problem as we have 300+ apps that we need convert and at least 60% would have registry entries in them.

Thanks

Sean.

[David_Thornley]

Is there a sample AXT that you can post which will reproduce this behavior. I'd like to take a look at this to make sure we are not running into some format issues in the conversion tool.

Thanks
David

[sfirmston]

Here is a sample of an AXT file that when imported only seems to find the Keys and not the values. I'm hoping I'm just doing something wrong as the tool looks great but when testing with Wise Package Studio, which doesn't look as good, it will import the AXT files fine.

AXT_FILE 3.1

[Application Name]
Value=Skip_DSN

[Application Caption]
Value=Skip DSN

[Application Path]
Value= 47 NULL

[Application Flags]
Flag=Install Only
Flag=Always Distribute Application
Flag=Run As System User
Flag=Not a Disconnectable Application

[Application Platform]
Flag=Windows NT

[Filter OS Version]
Type=Windows NT
Major Version=-1
Minor Version=-1
Revision Version=-1
Flag=Greater Than or Equal

[Registry Key Create]
Flag=Write Always
Key=HKEY_LOCAL_MACHINE\SOFTWARE

[Registry Key Create]
Flag=Write Always
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC

[Registry Key Create]
Flag=Write Always
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI

[Registry Key Create]
Flag=Write Always
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources

[Registry Key Create]
Flag=Write Always
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Skip

[Application Icon Order]
Value=0

[Registry Value Create]
Type=String
Flag=Write Always
Flag=Always Distribute Setting
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources
Name=Skip
Value=SQL Server

[Registry Value Create]
Type=String
Flag=Write Always
Flag=Always Distribute Setting
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Skip
Name=Database
Value=Skip

[Registry Value Create]
Type=String
Flag=Write Always
Flag=Always Distribute Setting
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Skip
Name=Description
Value=Skip Database

[Registry Value Create]
Type=String
Flag=Write Always
Flag=Always Distribute Setting
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Skip
Name=Driver
Value=C:\WINNT\System32\SQLSRV32.dll

[Registry Value Create]
Type=String
Flag=Write Always
Flag=Always Distribute Setting
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Skip
Name=Server
Value=mis

[Registry Value Create]
Type=String
Flag=Write Always
Flag=Always Distribute Setting
Key=HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Skip
Name=Trusted_Connection
Value=Yes

[Application Association Flags]
Flag=Start Menu

[David_Thornley]

There is an issue in the AdminStudio converter in parsing the Create Registry Value sections when the section contains multiple Flag entries. Registry sections that only contain a single flags entry are migrated properly. I will create a bug report for this issue so that it can be fixed in the next release. The tracking number for this issue is IOC-000047740.