Wyse Device Manager
I'm trying to get Wyse Device Manager (WDM) to silently install. From the files that I've downloaded it appears to be an Installshield Installer, but running setup /r /f1c:\setup.iss only partially populates the record file.
There is also a Setup.ini with the following information pre-populated:
[Startup]
AppName=Wyse Device Manager
ProductGUID=EEB7C80D-4810-485A-940E-FEC42A3F9DBF
CompanyName=Wyse Technology Inc.
CompanyURL=http://www.wyse.com
ErrorReportURL=http://www.installshield.com/isetup/ProErrorCentral.asp?ErrorCode=%d : 0x%x&ErrorInfo=%s
MediaFormat=1
LogMode=1
Skin=setup.isn
Resource=_Setup.dll
SmallProgress=Y
SplashTime=5
CheckMD5=Y
CmdLine=
ShowPasswordDialog=N
EngineVersion=11.50.0.43969
EngineBinding=1
[Languages]
Default=0x0009
count=1
key0=0x0009
So I really have a couple of questions that need answering:
1. How can I find out the additional information that needs to be writen to the .iss file? The generic information, I.E the welcome screens etc seem to get writen ok to the record file, but any custom windows don't.
2. Someone suggested I could complete the Setup.ini file with the additional information needed to complete the install, again, how or where can I find the correct syntax for the file?
Or would it be better to repackage this product?
Thanks in advance for any information given
There is also a Setup.ini with the following information pre-populated:
[Startup]
AppName=Wyse Device Manager
ProductGUID=EEB7C80D-4810-485A-940E-FEC42A3F9DBF
CompanyName=Wyse Technology Inc.
CompanyURL=http://www.wyse.com
ErrorReportURL=http://www.installshield.com/isetup/ProErrorCentral.asp?ErrorCode=%d : 0x%x&ErrorInfo=%s
MediaFormat=1
LogMode=1
Skin=setup.isn
Resource=_Setup.dll
SmallProgress=Y
SplashTime=5
CheckMD5=Y
CmdLine=
ShowPasswordDialog=N
EngineVersion=11.50.0.43969
EngineBinding=1
[Languages]
Default=0x0009
count=1
key0=0x0009
So I really have a couple of questions that need answering:
1. How can I find out the additional information that needs to be writen to the .iss file? The generic information, I.E the welcome screens etc seem to get writen ok to the record file, but any custom windows don't.
2. Someone suggested I could complete the Setup.ini file with the additional information needed to complete the install, again, how or where can I find the correct syntax for the file?
Or would it be better to repackage this product?
Thanks in advance for any information given
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
AngelD
16 years ago
Sounds like the setup is a regular wrapper.
Launch setup.exe and see if it extract any MSI in the %temp% folder.
Launch setup.exe and see if it extract any MSI in the %temp% folder.
Posted by:
willytheweel
15 years ago
ORIGINAL: AngelD
Sounds like the setup is a regular wrapper.
Launch setup.exe and see if it extract any MSI in the %temp% folder.
no this is not a common wrapper. I have the same problem with a silent install of WDM 4.5.3
Does anybody has a solution for installing WDM unattended? That installation creates an local user "rapport" and creates a website in IIS. I can handle this with an snapshot and config the IIS with vbs scripts, but i need to know exactly what kind of configuration the setup.exe make.
willy
Posted by:
anonymous_9363
15 years ago
I can handle this with an snapshot and config the IIS with vbs scripts, but i need to know exactly what kind of configuration the setup.exe make.SSSSssssoooooo...use a snapshot. I don't how much clearer you could get than a compl;ete capture of every file and registry change.
Posted by:
willytheweel
15 years ago
ORIGINAL: VBScab
SSSSssssoooooo...use a snapshot. I don't how much clearer you could get than a compl;ete capture of every file and registry change.
yes, but this is an setup.exe with aktiv components. While installation, the setup.exe connect to a remote Oracle database and transfers files via ftp from remote to the IIS ftp server, creates a local Rapport user with an password i dont know, creates a website in IIS and configure the IIS also. This are the thinks i know while installing, but how about the other things which cannot snapshot, like ntsf user rights etc.
What i need is a way to install this Wyse device Manager (WDM) Version 4.5.3.4 silent and unattended with the original setup.exe and not snapshoted
thank
willy
Posted by:
anonymous_9363
15 years ago
All of that stuff could be scripted and then incorporated into a package but, if you don't want to go that route, I don't think you have any other option than to talk to the vendor. Do they have a forum or knowledgebase?
Posted by:
willytheweel
15 years ago
ORIGINAL: VBScab
All of that stuff could be scripted and then incorporated into a package but,
Yes its all possible maybe, but i have not all the information i need for that to do this
if you don't want to go that route, I don't think you have any other option than to talk to the vendor. Do they have a forum or knowledgebase?
yes they have and i will send the application owner from that Wyse a mail to contact the Vendor.
willy
Posted by:
willytheweel
15 years ago
So now its fact. Wyse doesnt support an unattended installation. thats too bad for a company like that.
Now i need to capture the application. Does anybody know what kind off changes the setup.exe do? Like IIS or Security or ftp ?
willy
Now i need to capture the application. Does anybody know what kind off changes the setup.exe do? Like IIS or Security or ftp ?
willy
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.