SAP GUI 6.2
Pls has anyone packaged SAP GUI 6.2 before?. I actually need some guide lines on how to start.
Giz
Giz
0 Comments
[ + ] Show comments
Answers (15)
Please log in to answer
Posted by:
neo2000
18 years ago
Sap uses an installer of it's own. I don't know if it's a good idea to package this.
What we did: package a GUI around the original installer, so people "see" something is being installed and do not turn off the workstation or try to start SAP. Looking at the amount of upgrades on SAP (over here anyways.. [;)]) we decided on not to package SAP. Updates are being deployed with a GUI in the form of an MSI, which calls the original installer and commandline. The GUI tells people the setup/update is being run. Tells them to close SAP during the install/update. Makes patching a lot easier and highly reduces the amount of failed installations. Might be something to consider.
What we did: package a GUI around the original installer, so people "see" something is being installed and do not turn off the workstation or try to start SAP. Looking at the amount of upgrades on SAP (over here anyways.. [;)]) we decided on not to package SAP. Updates are being deployed with a GUI in the form of an MSI, which calls the original installer and commandline. The GUI tells people the setup/update is being run. Tells them to close SAP during the install/update. Makes patching a lot easier and highly reduces the amount of failed installations. Might be something to consider.
Posted by:
gizmolala
18 years ago
Am not actually packaging the while SAP GUI 6.2. i only check two of the features. The problem is while packaging, the merge module involved (SQLSVR.MSM) is always giving problems. Don't know if to remove it from the package or leave it. If the msm is included in the package, it brings out an error during installation but if the msm is excluded the package is fine.
Pls any suggestions?
Giz
Pls any suggestions?
Giz
Posted by:
brenthunter2005
18 years ago
Posted by:
gizmolala
18 years ago
Posted by:
brenthunter2005
18 years ago
Posted by:
gizmolala
18 years ago
Posted by:
brenthunter2005
18 years ago
Well, the easiest method would be to just add a new row to the Property table:
SAPWD = sa
Otherwise, if you want to deploy a more secure MSDE you should download the latest setup from http://www.microsoft.com/downloads/details.aspx?FamilyID=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en and follow the instructions in the readme.
SAPWD = sa
Otherwise, if you want to deploy a more secure MSDE you should download the latest setup from http://www.microsoft.com/downloads/details.aspx?FamilyID=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en and follow the instructions in the readme.
Posted by:
gizmolala
18 years ago
Posted by:
brenthunter2005
18 years ago
Posted by:
gizmolala
18 years ago
Posted by:
brenthunter2005
18 years ago
Posted by:
gizmolala
18 years ago
Even this SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE when finished downloading and u want to run the setup it extracted will also bring up that same error.
The funny thing is when i used installshield, i had no probs with the merge modules but iwth Wise package studio 5, loads of problem. We are only allowed to package with Wise package studio.
Giz
The funny thing is when i used installshield, i had no probs with the merge modules but iwth Wise package studio 5, loads of problem. We are only allowed to package with Wise package studio.
Giz
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.