Home > Reviews > NSMC 4.0
 
 
NSMC 4.0
by Bob Kelly

Page 5 of 6

1 | 2 | 3 | 4 | 5 | 6

AppDeploy.com
            search engine keywords: deployment, remote, installation, software,
            applications, updates, hotfixes, hot fixes, hotfix, service pack,
            sp1, sp2, sp3, sp4, sp5, sp6, IE, Microsoft, SMS, installer,
            install, pdf, package, definition, file, script, KiXtart, kix,
            logon, logoff, bat, NT, shell, batch, installation software,
            software installation, remote installation, installer, wise
            installer, SMS installer, window installer, windows installer, 
            ghost image, imageing, drive image, drive image pro, 
            warez drive image, drive image download, drive image powerquest,
            powerquest drive image, warez drive image, appz, drive image 3, imaging software, disk imaging software, free imaging software, perl script, vb script, free script, shell script

Software Distribution

For those that have embraced Group Policy for deployment and have taken the steps necessary to migrate all their deployment packages to MSI files- you’ll be well prepared to take advantage of NSMC’s deployment features. Yes, packages must be in Windows Installer format for deployment using NSMC. Need for an MSI formatted deployment package has always been a glaring shortcoming of Group Policy and it is largely considered as key driver to move toward a more robust system. INSYSTEK does soften the blow by providing documentation including helpful documentation such as their paper on how to go about wrapping a legacy setup.exe into an MSI package using InstallShield Express.

The "Add Package Wizard" lets you specify an MSI path, command line options, any dependency files, a name and description. From there, the package is copied to the package servers you have specified and the package is available for assignment to one or more managed devices.

For actual package distribution you must have a Package Server and a Distribution Server. A Package Server holds packages, while a Distribution Server holds the packages and is the point for distribution to systems. These two sites can be separate.

When scheduling the package for distribution, there are some great features for redistribution in the event of failure (see image at right).

Performance and Availability Monitoring

With NSMC’s performance and availability monitoring features, you can stay ahead of potential network issues, proactively monitor services and processes. By creating monitoring policies, you can choose what you want to watch, at what interval and what values dictate a harmless, warning, minor, critical, or fatal situation. You can then specify pager, email and audio alerts for each of these thresholds.



This can be a very handy feature, allowing administrators to be notified of low disk space, excessive paging, or anything else you might associate with performance monitoring.
 

[Page 5 of 6]     1 | 2 | 3 | 4 | 5 | 6