Here's the link below:
http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?culture=en-US&EventID=1032428201&CountryCode=US
Let's enhance our skills.
January 19, 2010
What's New in Microsoft System Center Operations Manager 2007 R2 ?
Microsoft System Center Operations Manager 2007 R2 delivers end-to-end service management of applications and IT services running across your datacenter fabric, providing you greater control and insight into the health and performance of your Microsoft, UNIX, and Linux servers, and the workloads running on them. With Operations Manager 2007 R2, you can reduce the cost of managing your datacenter, and assure delivery of IT services to expected and agreed levels.
Download Operations Manager 2007 R2:
http://technet.microsoft.com/en-us/evalcenter/bb738014.aspx
Enhances application performance and availability across platforms in the datacenter through cross platform monitoring, delivering an integrated experience for discovery and management of systems and their workloads, whether Windows, UNIX or Linux.
Download the Service Level DashboardEnhances performance management of applications in the datacenter with service level monitoring, delivering the ability to granularly define service level objectives that can be targeted against the different components that comprise an IT service.
Increases the speed of access to monitoring information and functionality with UI improvements and simplified management pack authoring. Examples include an enhanced console performance and dramatically improved monitoring scalability (e.g., over 1000 URLs can be validated per agent, allowing scaling to the largest of web-based workloads)
Download Operations Manager 2007 R2:
http://technet.microsoft.com/en-us/evalcenter/bb738014.aspx
Enhances application performance and availability across platforms in the datacenter through cross platform monitoring, delivering an integrated experience for discovery and management of systems and their workloads, whether Windows, UNIX or Linux.
Download the Service Level DashboardEnhances performance management of applications in the datacenter with service level monitoring, delivering the ability to granularly define service level objectives that can be targeted against the different components that comprise an IT service.
Increases the speed of access to monitoring information and functionality with UI improvements and simplified management pack authoring. Examples include an enhanced console performance and dramatically improved monitoring scalability (e.g., over 1000 URLs can be validated per agent, allowing scaling to the largest of web-based workloads)
Basic difference between .MSI and .MST File
Packages (.MSI files)
This is the file that contains the instructions for MSIEXEC.EXE to install the application. The MSI file is a Database file format and is now the preferred application packaging format for the windows platform. Sometimes the MSI file gets too big and some or all of the files are placed in a .CAB file.
Transforms (.MST files)
In the MSI world, if you didn't create the MSI file, you want to keep the MSI file from the developer intact. To make changes beyond what the original MSI does you use a transform. The transform is applied at the time that the MSI package is installed.If you would repackage an application and it would fail, the Original Developer of the application would sometimes refuse to support it since repackaging strips out their installation logic.
If you create your own MSI packages you can also use transforms to change some parameters for each department of your company. That way you have only one package to maintain and nobody can accuse you of doing a better package for one department vs. another.
Note: Transform files are in fact MSI files with a different file extension. The contents of both files are merged together at install time. They are not supposed to add files to the package but there are way. Wise Package Studio does allow adding files using Transforms but they create a CAB file to bring files in without breaking the MSI rules.
This is the file that contains the instructions for MSIEXEC.EXE to install the application. The MSI file is a Database file format and is now the preferred application packaging format for the windows platform. Sometimes the MSI file gets too big and some or all of the files are placed in a .CAB file.
Transforms (.MST files)
In the MSI world, if you didn't create the MSI file, you want to keep the MSI file from the developer intact. To make changes beyond what the original MSI does you use a transform. The transform is applied at the time that the MSI package is installed.If you would repackage an application and it would fail, the Original Developer of the application would sometimes refuse to support it since repackaging strips out their installation logic.
If you create your own MSI packages you can also use transforms to change some parameters for each department of your company. That way you have only one package to maintain and nobody can accuse you of doing a better package for one department vs. another.
Note: Transform files are in fact MSI files with a different file extension. The contents of both files are merged together at install time. They are not supposed to add files to the package but there are way. Wise Package Studio does allow adding files using Transforms but they create a CAB file to bring files in without breaking the MSI rules.
MSI Authoring Tools
MSI Authoring Tools: The below are tools which can be used to edit MSI packages-
•InstallShield Developer
•Wise for Windows Installer
•InstallAware
•AdvancedInstaller
•InstallShield Express
•InstallShield DevStudio
•InstallConstruct
•Instyler EX-it!
•MaSaI Editor
•Setup2Go
•Wise for Visual Studio.NET
•InstallShield Developer
•Wise for Windows Installer
•InstallAware
•AdvancedInstaller
•InstallShield Express
•InstallShield DevStudio
•InstallConstruct
•Instyler EX-it!
•MaSaI Editor
•Setup2Go
•Wise for Visual Studio.NET
InstallShield Command Line Parameters
The following are the InstallShield Command Line Parameters:
/v Passes parameters to MSI package.
/s Causes setup.exe to be silent.
/l Specifies the setup language.
/a Performs administrative installation.
/j Installs in advertise mode.
/x Performs setup uninstall.
/f Launches setup in repair mode.
/w Setup.exe waits for the installation to finish before exiting.
/qn A Windows Installer MSI parameter that causes everything but setup.exe to be silent. This sets the user interface level to zero.
/v Passes parameters to MSI package.
/s Causes setup.exe to be silent.
/l Specifies the setup language.
/a Performs administrative installation.
/j Installs in advertise mode.
/x Performs setup uninstall.
/f Launches setup in repair mode.
/w Setup.exe waits for the installation to finish before exiting.
/qn A Windows Installer MSI parameter that causes everything but setup.exe to be silent. This sets the user interface level to zero.
MSI Repackaging Tools
1. AdminStudio
2. Package Studio
3. WiX
4. InstallAware
5. MSI Studio
6. MAKEMSI
7. Prism Pack
8. WinInstall
9. RapidInstall (Deployment Solution)
10. SMS Installer
11. NetInstall
12. MSI Packager
13. InstallSpy
14. Wise Packaging Studio
2. Package Studio
3. WiX
4. InstallAware
5. MSI Studio
6. MAKEMSI
7. Prism Pack
8. WinInstall
9. RapidInstall (Deployment Solution)
10. SMS Installer
11. NetInstall
12. MSI Packager
13. InstallSpy
14. Wise Packaging Studio
Subscribe to:
Posts (Atom)