Microsoft_EchangeESM_2003SP2
Hi everyone,
I am currently in the process of repackaging this applicaiton for an unattended install. The install involves running a setup.exe followed by an update.exe.
This is a setup.exe install that calls an msi. However, I was unable to create a transform as there is a silent part of the exe that i could not figure out and is not in the msi. It therefore had to be installed as an exe. This setup.exe has it's own unattended install options. When I put the setup.exe into the command wondow and followed it with a /? I was presented with a list of options for installing. /CreateUnattend filename.ini was the option i used to create the file i was going to use to install the application silently or Unattended at least. To use this filename.ini file I had to place the ini file into the same folder as the setup.exe and use the option /Unattendfile filename.ini. I used the same procedure for the unisntall and created an uninstall.ini.
This is all fine but when i then tried to install this application via a deployment in Tivoli it didn't work. It seems as though I must be logged onto a Domain in order for this install to work. When I tried installing the app when logged on as local administrator locally it wouldn't work.
Does anyone know why this would be or know of a way around it?
Thanks,
Rgds,
Mark
I am currently in the process of repackaging this applicaiton for an unattended install. The install involves running a setup.exe followed by an update.exe.
This is a setup.exe install that calls an msi. However, I was unable to create a transform as there is a silent part of the exe that i could not figure out and is not in the msi. It therefore had to be installed as an exe. This setup.exe has it's own unattended install options. When I put the setup.exe into the command wondow and followed it with a /? I was presented with a list of options for installing. /CreateUnattend filename.ini was the option i used to create the file i was going to use to install the application silently or Unattended at least. To use this filename.ini file I had to place the ini file into the same folder as the setup.exe and use the option /Unattendfile filename.ini. I used the same procedure for the unisntall and created an uninstall.ini.
This is all fine but when i then tried to install this application via a deployment in Tivoli it didn't work. It seems as though I must be logged onto a Domain in order for this install to work. When I tried installing the app when logged on as local administrator locally it wouldn't work.
Does anyone know why this would be or know of a way around it?
Thanks,
Rgds,
Mark
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.