Repackaging a Network Client Install
Hi
Hope someone can help me with this as I am out of idea's. I have to repackage an application which is a network client install.
Not seen one of these for a long time, I have an application that you install onto a server share then you run a client install from the share on the client PC and it ask's you to point to the network install during the install, when I try and record the install it doesn't seem to capture the shortcuts it create's on the start menu to the executables on the server share.
I have tried to install the server install and then the client install on the same machine while recording the client install only, this didn't seem to work.
The application uses an installshield exe that I need to repackage to an msi as my deployment tool only supports msi files.
Should I just repackage the client or the whole server install aswell, I am unsure as to how these particular installs work, can someone please give me an insight into this that would be a great help to get me started.
Thanks
pheonixman [:)]
Hope someone can help me with this as I am out of idea's. I have to repackage an application which is a network client install.
Not seen one of these for a long time, I have an application that you install onto a server share then you run a client install from the share on the client PC and it ask's you to point to the network install during the install, when I try and record the install it doesn't seem to capture the shortcuts it create's on the start menu to the executables on the server share.
I have tried to install the server install and then the client install on the same machine while recording the client install only, this didn't seem to work.
The application uses an installshield exe that I need to repackage to an msi as my deployment tool only supports msi files.
Should I just repackage the client or the whole server install aswell, I am unsure as to how these particular installs work, can someone please give me an insight into this that would be a great help to get me started.
Thanks
pheonixman [:)]
0 Comments
[ + ] Show comments
Answers (12)
Please log in to answer
Posted by:
MicrosoftBob
16 years ago
The capture probably did not get the shortcuts because advertised shortcuts must point to files in the MSI - not to a network location.
If you are using Wise, you can manually add the shortcuts in the files section as .LNK files. It then installs them as any other file. Or you can create a non-advertised shortcut and copy and paste the command line from the shortcut that was created.
If you are using some other MSI creation tool, there are probably simliar ways to do the above.
If you are using Wise, you can manually add the shortcuts in the files section as .LNK files. It then installs them as any other file. Or you can create a non-advertised shortcut and copy and paste the command line from the shortcut that was created.
If you are using some other MSI creation tool, there are probably simliar ways to do the above.
Posted by:
pheonixman27
16 years ago
Hi
Thanks for the Reply, I have created the shortcuts as suggested and this worked great.
Thanks again
[:D]
Thanks for the Reply, I have created the shortcuts as suggested and this worked great.
Thanks again
[:D]
Posted by:
anonymous_9363
16 years ago
We're glad it worked out for you. I'm sure MSB would be equally glad if you were to rate his post :)
Posted by:
su.deep
16 years ago
Please help in refrence to network client install
I have the same issue as phoenixman had... with my msi it installs without a problem, it even creats the shortcut and all at the proper place... the issue with mine is when i click the shortcut is looks for the folder where the core is installed and that is the server...the path and location are all good but it just doesnot work.
One thing i found out is if i right click on the shortcut and change the root directory to the network drive it seems to work... is there a alternative remedy for this issue...
I even did try to create a non advertiese short cut with the shortcut pointing to the network drive the WPS tool didn't allow me!!
Thanks in Advance
su.deep
I have the same issue as phoenixman had... with my msi it installs without a problem, it even creats the shortcut and all at the proper place... the issue with mine is when i click the shortcut is looks for the folder where the core is installed and that is the server...the path and location are all good but it just doesnot work.
One thing i found out is if i right click on the shortcut and change the root directory to the network drive it seems to work... is there a alternative remedy for this issue...
I even did try to create a non advertiese short cut with the shortcut pointing to the network drive the WPS tool didn't allow me!!
Thanks in Advance
su.deep
Posted by:
su.deep
15 years ago
Let me explain my issues once again. I have read the reply and I have created a non advertised shortcut. Locally testing of my msi works just fine; i can get the app to run as it is suppose to and the shortcuts are placed where they are suppose to.
My issue arrises only during deployment via SMS. It seems to have the issue on the shortcuts not being in the start/program menu but all the necessary files get installted in c:\programfile\program_name. Am I doing anything wrong here?
Please help!
Thanks
su.deep
My issue arrises only during deployment via SMS. It seems to have the issue on the shortcuts not being in the start/program menu but all the necessary files get installted in c:\programfile\program_name. Am I doing anything wrong here?
Please help!
Thanks
su.deep
Posted by:
aogilmor
15 years ago
please do NOT use the suggestion in post 2- hard coding .lnk files is always a bad idea - for one thing, it's a total black box, and not maintainable.
Instead, in the property table create a property SC that contains your network shortcut location, say s:\programs\app.exe, create another one WkDir and set it to s:\programs\
In your shortcut table, set your target and wkdir fields to these properties.
if you need more details this has actually been covered many times , several on appdeploy, do a google search on WkDir Windows Installer shortcut and you should get some hits
Instead, in the property table create a property SC that contains your network shortcut location, say s:\programs\app.exe, create another one WkDir and set it to s:\programs\
In your shortcut table, set your target and wkdir fields to these properties.
if you need more details this has actually been covered many times , several on appdeploy, do a google search on WkDir Windows Installer shortcut and you should get some hits
Posted by:
su.deep
15 years ago
Thankyou!
Now another issue i have been facing and not being able to resolve is my package is not being able to get deployed via SMS coz its a network install and apperantly its not identifying the network drive say(X:\) where the core of the app is installed. This issue is also with the SMS deployment only. Locally installing in the lab machines works great. Have I underlooked something here?
Now another issue i have been facing and not being able to resolve is my package is not being able to get deployed via SMS coz its a network install and apperantly its not identifying the network drive say(X:\) where the core of the app is installed. This issue is also with the SMS deployment only. Locally installing in the lab machines works great. Have I underlooked something here?
Posted by:
aogilmor
15 years ago
well it shouldn't really need to recognize any drives if it's just a shortcut, it should lay down the shortcut even if the sms install user doesn't have access, iirc I've done this a few times with network shortcuts i didn't have a drive mapped to. Of course if you don't have access the shortcut would not work, but IIRC the shortcut would show up for users that do have access, when they log on and have the drive mapped. Of course it should be installed in the ALLUSERSPROFILE. I assume you have ALLUSERS property set to 1?
it's been a while since i've used the properties to create network shortcuts. if i'm wrong in that case maybe you would have to include hard coded .lnk files which is a sucky solution but if you gotta...
use verbose logging /l*v log file path to get the relevant info in the CreateShortcuts section as to why the sc's aren't created. An important point: in the shortcut table that you include the square brackets for the target property[SHORTCUTPATH] but for the WkDir field you just put in the property name (usually just use WkDir but you can use what you want).
Good luck!
it's been a while since i've used the properties to create network shortcuts. if i'm wrong in that case maybe you would have to include hard coded .lnk files which is a sucky solution but if you gotta...
use verbose logging /l*v log file path to get the relevant info in the CreateShortcuts section as to why the sc's aren't created. An important point: in the shortcut table that you include the square brackets for the target property[SHORTCUTPATH] but for the WkDir field you just put in the property name (usually just use WkDir but you can use what you want).
Good luck!
Posted by:
aogilmor
15 years ago
thanks for letting me know, glad it worked!
gimme some props (ratings)!~
OG
gimme some props (ratings)!~
OG
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.