3.1 |
|
Unable to Adopt Best of Breed for Particular Functions and Roles |
3.2 |
|
Less Negotiating Leverage Due to Public Commitment to a single-OS environment |
3.3 |
|
May Not Have Access to Software Titles That Are Only Available on Other Platforms |
3.4 |
|
Future Directions and Product Priorities May Become Out of Sync With Needs |
3.5 |
|
New Hardware Features or Products May Not (Yet) Be Supported in Windows |
3.6 |
|
More Challenging to Address Very-High-Availability Requirements (More Than 99.9% Uptime for Applications) |
3.7 |
|
Harder to Reach High-End, Single-System (Scale-Up) Performance |
3.8 |
|
Risks of Unexpected and Unbudgeted Shifts in License Fees and Conditions |
3.9 |
|
Microsoft May Miss a Major Technology Shift and Be Late to Address It |
3.10 |
|
Shorter Hardware Obsolescence Period Leads to More-Frequent Upgrades |
3.11 |
|
Microsoft Has to Consider the Impact on Huge Installed Bases When Considering Radical Innovation |
3.12 |
|
Migration Costs if Moving From Multiple OS Types to All-Windows |
3.13 |
|
Unable to Use Non-Windows Server for Some Services to Reduce the Number of Client Access Licenses |
3.14 |
|
License Costs Can Be Much Higher, Especially Against Open-Source Alternatives |
3.15 |
|
Security Can Be Weakened Since a Common Defect Can Be Exploited to Attack All Servers |