What tool did you use to make the install MSI's? I'm needing to create a custom NC_NET install package.
So far I used InstallShield in 'direct edit mode' to edit the MSI to customize some of the default configs but I'd also like to change the default installation directory which is a bit more involved. I know I can just customize the installdir on the command line but I'd like to customize it even if someone runs the install manually.
Another thing I'd like to customize is the Version Number - it seems all the NC_NET installs report the version as 1.0.1 which makes it hard to track what version is installed on various servers. (i.e. HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\DisplayVersion = 1.0.1 for all versions)
Aside from custom configs + custom path, the main reason I'm needing to make a custom package is to have it run some extra scripts to remove any old NSClient installs first.
I'm debating making a fresh and totally custom InstallScript project but hoping to avoid that just to save time.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ooooo, I just totally extracted the MSI and I see there's a Setup.Rul file :-) Any chance I could get a copy of your installshield project if that's indeed what you used?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The MSI was created using Visual Studio, and the ncnet.exe has a custom installer class built in it.
THe Visual Studio Installe project is very limited and the Version is particular for Dot net 2.0 (not catered to Vista or Server 2008) I will be upgrading NC_Net to Dot net 3.0/3.5 and use the new version of Studio to create a more Vista/server 2008 compatible version of the MSI.
I have not been using the Version # in the project Instead NC_NEt uses the CLientversion command to return the version # that is always accurate to the release. typically I go through 10-20 versions between official releases and it has been easier not to use the Version to the executable. I will consider setting the Version Tag but it is not yet a priority.
The MSI accepts all the standard inputs of MSIInstaller, thus you can set via command line the install path as well as silent. (and posible some other settings)
if you cannot write scrits to use the existing MSI and your pre/post events ,then feel free to create your own MSI, the only problem with that is you may need to rebuild it every time there is a new version. ALSO Please do not ReDISTRIBUTE the version as it may easily fall out of sync with the current build.
The current NC_Net MSI installer does three things:
1) copy files to Install folder
2) copy extra copy to the start menu Item
3) register the exe as a service via the built in installer class inside the exe.
Hope this helps
TOny
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Heya Tony,
What tool did you use to make the install MSI's? I'm needing to create a custom NC_NET install package.
So far I used InstallShield in 'direct edit mode' to edit the MSI to customize some of the default configs but I'd also like to change the default installation directory which is a bit more involved. I know I can just customize the installdir on the command line but I'd like to customize it even if someone runs the install manually.
Another thing I'd like to customize is the Version Number - it seems all the NC_NET installs report the version as 1.0.1 which makes it hard to track what version is installed on various servers. (i.e. HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}\DisplayVersion = 1.0.1 for all versions)
Aside from custom configs + custom path, the main reason I'm needing to make a custom package is to have it run some extra scripts to remove any old NSClient installs first.
I'm debating making a fresh and totally custom InstallScript project but hoping to avoid that just to save time.
Thanks!
Ooooo, I just totally extracted the MSI and I see there's a Setup.Rul file :-) Any chance I could get a copy of your installshield project if that's indeed what you used?
The MSI was created using Visual Studio, and the ncnet.exe has a custom installer class built in it.
THe Visual Studio Installe project is very limited and the Version is particular for Dot net 2.0 (not catered to Vista or Server 2008) I will be upgrading NC_Net to Dot net 3.0/3.5 and use the new version of Studio to create a more Vista/server 2008 compatible version of the MSI.
I have not been using the Version # in the project Instead NC_NEt uses the CLientversion command to return the version # that is always accurate to the release. typically I go through 10-20 versions between official releases and it has been easier not to use the Version to the executable. I will consider setting the Version Tag but it is not yet a priority.
The MSI accepts all the standard inputs of MSIInstaller, thus you can set via command line the install path as well as silent. (and posible some other settings)
if you cannot write scrits to use the existing MSI and your pre/post events ,then feel free to create your own MSI, the only problem with that is you may need to rebuild it every time there is a new version. ALSO Please do not ReDISTRIBUTE the version as it may easily fall out of sync with the current build.
The current NC_Net MSI installer does three things:
1) copy files to Install folder
2) copy extra copy to the start menu Item
3) register the exe as a service via the built in installer class inside the exe.
Hope this helps
TOny