Has anyone successfully packaged Microsoft .NET Framework 2.0?
Hello,
Has anyone successfully packaged Microsoft .NET Framework 2.0, if could you please tell me how? I was able to create a msi, test the install via Nal/Zenworks. But when I log in as another user, open Windows Explorer, go to the C:\Windows folder it reinstalls it’s self. I tried ALLUSERS property =1 and =2 but it still reinstalls it’s self.
thanks
Has anyone successfully packaged Microsoft .NET Framework 2.0, if could you please tell me how? I was able to create a msi, test the install via Nal/Zenworks. But when I log in as another user, open Windows Explorer, go to the C:\Windows folder it reinstalls it’s self. I tried ALLUSERS property =1 and =2 but it still reinstalls it’s self.
thanks
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
williamp
17 years ago
ORIGINAL: Trooper23
Hello,
Has anyone successfully packaged Microsoft .NET Framework 2.0, if could you please tell me how? I was able to create a msi, test the install via Nal/Zenworks. But when I log in as another user, open Windows Explorer, go to the C:\Windows folder it reinstalls it’s self. I tried ALLUSERS property =1 and =2 but it still reinstalls it’s self.
thanks
"Creating" an MSI is, in my opinion, a very bad idea. Microsoft distributes this as an MSI already and modifying it in any way other than with tuner or transform is fraught with risk.
I notice in the MSI that there is an ActiveSetup stub value written. I also notice some HKCU values. Either of those can potentially cause "stuff" to happen when a new user logs on to the machine, and such "stuff" is therefore by design.
To get at the MSI, try this:
dotnetfx.exe /c /t:C:\TEMP\DotNet
This extracts out MSI and supporting installation files to the C:\TEMP\DotNet folder
2. Create Transform to do what you want to do to customize it for your environment
Posted by:
Trooper23
17 years ago
I also tried something similar to that from here; http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/ndp2_dplad.asp
When I tried running the netfx.msi that was extracted from that dotnetfx.exe it errored out and asked that I run the install.exe. The install.exe was not extracted from the dotnetfx.exe. I had to run the dotnetfx.exe, it then uncompressed all the files into the profile\temp folder, I was then able to get the install.exe from the temp folder. When I run the install.exe to run the netfx.msi it starts the install no problem, but I need my msi to start the install not the install.exe.
When installing the app with the MST i created, to go along with the netfx.msi, it errors out with a 1603. I look in the log and it states that this msi must be run using the install.exe.
When I tried running the netfx.msi that was extracted from that dotnetfx.exe it errored out and asked that I run the install.exe. The install.exe was not extracted from the dotnetfx.exe. I had to run the dotnetfx.exe, it then uncompressed all the files into the profile\temp folder, I was then able to get the install.exe from the temp folder. When I run the install.exe to run the netfx.msi it starts the install no problem, but I need my msi to start the install not the install.exe.
When installing the app with the MST i created, to go along with the netfx.msi, it errors out with a 1603. I look in the log and it states that this msi must be run using the install.exe.
Posted by:
bheers
17 years ago
Posted by:
Trooper23
17 years ago
Posted by:
AngelD
17 years ago
Posted by:
Trooper23
17 years ago
I was able to install the .Net Framework 2 using the command line listed above as Admin but not as Power User.
While installing via Power User, it errors out trying to write the
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.EnterpriseServices.dll. Ok simple enough, so I open that component and add Users, Power Users, and Everyone give Full control local permissions. But yet the lock permissions don’t apply.
We deploy via Zenworks and it seems like it’s doesn’t have the system context abilities like SMS or AD would so I’m stuck deploying a EXE. If I deploy the EXE I have 3 dialogs and 1 selection that I must now figure out how to send to the screen.
Any suggestions please?
While installing via Power User, it errors out trying to write the
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.EnterpriseServices.dll. Ok simple enough, so I open that component and add Users, Power Users, and Everyone give Full control local permissions. But yet the lock permissions don’t apply.
We deploy via Zenworks and it seems like it’s doesn’t have the system context abilities like SMS or AD would so I’m stuck deploying a EXE. If I deploy the EXE I have 3 dialogs and 1 selection that I must now figure out how to send to the screen.
Any suggestions please?
Posted by:
Trooper23
17 years ago
Ok I was able to figure out how to deploy the .Net Framework 2.0 via NAL. Unfortunately I could not just deploy the msi, I had to deploy the DOTNETFX.EXE with a command line. Here is the Zenworks install object settings;
Distriburtion Options;
name DOTNETFX.EXE copied to targetdir %WINDIR%\TEMP\ source %SOURCE_PATH%\DOTNETFX.EXE
Path to executable file;
%WINDIR%\TEMP\dotnetfx.exe
Parameters;
/Q /T:%WINDIR%\TEMP /C:"msiexec.exe /i netfx.msi ADDEPLOY=1 /qb!"
Run options:
Select Run as unsecure system user
The way this app works is DOTNETFX.EXE runs and extracts INSTALL.EXE, NETFX.MSI and a ton of DLL and TXT files. Then the INSTALL.EXE runs the NETFX.MSI then the dialogs start.
Enjoy.
Distriburtion Options;
name DOTNETFX.EXE copied to targetdir %WINDIR%\TEMP\ source %SOURCE_PATH%\DOTNETFX.EXE
Path to executable file;
%WINDIR%\TEMP\dotnetfx.exe
Parameters;
/Q /T:%WINDIR%\TEMP /C:"msiexec.exe /i netfx.msi ADDEPLOY=1 /qb!"
Run options:
Select Run as unsecure system user
The way this app works is DOTNETFX.EXE runs and extracts INSTALL.EXE, NETFX.MSI and a ton of DLL and TXT files. Then the INSTALL.EXE runs the NETFX.MSI then the dialogs start.
Enjoy.
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.