|
Blog -
Alan's Blog
|
Has your company been hammered by a man-made or natural disaster? If you do not rebuild your technology infrastructure very carefully, you will be re-visited by yet another disaster: This one of legal origin. Your next headaches will be caused by counterfeit or incorrectly licensed copyright protected products loaded on your new systems--and you will not know of their existence until the auditing teams come calling. Even if you are not victim of a disaster--as in simply starting up a new business, you will gain serious cost savings for building a technology infrastructure for your budding company. In these Briefings we give you proven methods for saving money on your new or post-disaster tech purchases while significantly reducing audit risks--both now and in the future.
"The software police and copyright cops just can't wait to audit your company for software piracy and/or license non compliance."
In this Knowledge Briefing Series, Alan Plastow, the founder of The Business Technology Consumer Network, provides you with critical - and very frequently invisible - tips and strategies for reducing costs while protecting your company from software piracy punitive audits and threatened license non compliance litigation.
The so-called software police and copyright cops can -- and do -- offer whistle-blower rewards ranging from (up to) $10,000 to a whopping $1,000,000 in their efforts to locate you. Without the critical software asset management information in this Knowledge Briefing Series, both you and your company are easy audit targets.
"After the financial and personal impact of a disaster, precisely how many people do you suppose will be more than happy to report you or your company in return for a dangled whistle-blower reward?"
The first Knowledge Briefing in the Six Part Series, Natural Disaster Help I, can be found HERE. More to come.
|
|
|
Software Asset Mgt. -
SAM Process
|
Guess what? The warranties for the operating systems and software that you depend on for your livelihood most likely cover essentially nothing. That means the products you paid big money for do not have to actually do anything. They don't have to be compatible with hardware or free of defects and viruses. They can contain known code defects—even internal copyright violations and trap doors. In fact, in some states, these products don't even have to work! The warranties for operating systems and software represent some of the most astounding bits of contractual sharp practices that we business technology consumers have ever permitted to ooze past our collective noses. In this Knowledge Briefing, Alan Plastow excerpts the standard “DISCLAIMER OF WARRANTY” from many common license agreements and discusses how easily you manage to lose your rights.
Have you ever actually read a license agreement? This series of Knowledge Briefings takes a close look at licensing sharp practices and maybe even a few not-so-sharp ones. The clauses we discuss are from many of the actual license agreements to which you or your employees have probably legally bound your corporation. No matter what your company size, licensing documents represent a serious risk to your operations, your reputation, even your livelihood. Throughout the briefing, we provide a commentary about the risks and possible resolutions to the series of clauses we discuss. Let us know what you think.
The full text to this material can be found inside the members’ section: Knowledge Briefings, entitled “When Warranties are Without Warrant!” Sign in—it’s free and the value is becoming more incredible every week.
|
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
| Results 26 - 30 of 67 |
