Launch Conditions Help Restrict Your Install to Certain Situations

Launch Conditions are a useful tool in restricting your installation to only run under certain circumstances.

Also called Install Conditions, these are one or more conditions that must be met in order for your installation to run. For example, you can test for a specific operating system or minimum system requirements. If the conditions do not evaluate to True at run time, an error message is displayed and the product is not installed.

The first place you can set restrictions for your installation is on the Installation Requirements page of the Project Assistant. Have look at the screenshot below.

Setting Launch Conditions in the Project Assistant

Setting Launch Conditions in the Project Assistant



This page is convenient as it allows you to quickly set which Windows systems your installation can run on. You can also require that some of the more common software packages are installed in order for your installation to continue.

When you set a Launch Condition here, it will automatically create an Install Condition property for you in the General section of the General Information view. Here is a screenshot of that.

Setting Launch Conditions in the General Information view

Setting Launch Conditions in the General Information view



The difference between using the General Information view as opposed to the Project Assistant for this is that, in the General Information view, you will have to use the Product Condition Builder to create the condition. Whereas in the Project Assistant, the Install Condition, or Launch Condition, is created for you.

Remember Launch Conditions the next time you want to restrict your installation to only run on certain Windows systems.

 

Webinar Coming Up on Windows XP Migration for Enterprises

If your company is dragging it’s feet on migrating from Windows XP, then you might be interested in an upcoming webinar. I read an article that related this:

research indicates that 28% of all enterprises still need to migrate over 50% of their applications to a Windows 7 environment.”

That makes sense. My mother was in the hospital last month, and each room had a computer in order for the staff to do patient charting. I looked at quite a few different systems around the hospital and they were all running Windows XP SP3. Plus, I live in the capital of this state and I’ve noticed a lot of state government systems are still running XP SP3.

If you’re interested, you can register for the webinar on April 17, 2014 at 8:00am PST. People from different companies will share what their companies went through during their migration from Windows XP to Windows 7.

You can register here:

Insights, Discussions and Best Practices in the Continuous Evolution of Software and Applications in the Enterprise

 

Report Shows Software Makers Not Automating Their Licensing

Flexera conducted a survey and issued a report entitled, Application Usage Management Survey: Software Licensing & Market Risk – A New Perspective for ISVs. Gee, that’s a long title and the report is a bit boring. But, I will summarize it for you.

The report was compiled from three surveys, one targeted at independent software vendors (ISVs), one for intelligent device manufacturers and one for end-user organizations that use enterprise software.

Summary

The report shows that software makers don’t understand software licensing and they’re paying a price for it.

  • 65% of software makers haven’t implemented automated licensing management systems.
  • 37% of software makes report difficulty enforcing their licensing rules in virtual enviornments.
  • 53% of sofware makers believe their customers are using some of their software beyond what they paid for.
  • 69% of software makers have a problem when their company merges with another company because the code bases of their products are different.

What does this mean for all of us? One thing is you can be sure software makers are going to make it so you can’t buy a desktop copy of their software and then also use it on multiple virtual machines. They want to be paid for every instance of their software, no matter whether it’s on a desktop or a virtual machine.