Showing posts with label Microsoft. Show all posts
Showing posts with label Microsoft. Show all posts

Friday, June 14, 2013

Optimizing Microsoft Exchange for the Enterprise, Part II: Hub Transport Server and Lync-SharePoint Integration

Exchange Server 2010 is one of the most flexible and robust products in managing the messaging infrastructure of the organization. It includes a considerable number of features that help control the way emails are exchanged within the premises of the company. While the default setup provides a functional setup, it is worth looking at other features to get the most of this product. In this two-part white paper, we explore these features and take a look at how they can be implemented on top of a standard installation of Exchange servers in the organization. Part 1 examines, Optimizing the Mailbox Server Role and Optimizing the Client Access Server (CAS). Part 2 looks at Optimizing the Hub Transport Server, Miscellaneous Features, and Lync- SharePoint Integration.

The Hub Transport Server, which is responsible for the mail flow in the organization, features very specific settings
that allow Exchange administrators to define how e-mail is routed, and also applies on-the-fly policies to
that e-mail. This not only allows the sending and receiving of e-mail from the internal world, but also to and
from the Internet.

Transport rules are the mechanism that allows e-mail to be modified while in transit. This can be applied to a
message that is going through the Hub Transport Server role. Transport rules can be applied based on filters and
conditions, and can be used for multiple purposes.

Apply disclaimers to messages
Prevent certain types of viruses by patterns
Filter confidential information and apply Rights Management Services templates
Track and archive messages that are sent or received from specific users
Redirect inbound or outbound messages for inspection
Prevent communication between specific groups or users

A transport rule is configured through the Exchange Management Console (Organization Configuration->
Hub Transport-> New Transport Rule) or Exchange Management Shell, using the following sample cmdlet
and parameters.

New-TransportRule -Name 'Rule1' -Priority '0' -Enabled $true -from 'user1@contoso.com' -SentTo
'user2@contoso.com' -BlindCopyTo 'executives@contoso.com'

In this instance, e-mail is copied to specific users when user1 sends an e-mail to user2. More complex settings
with appropriate rule priorities can also be set up.

Address lists are a collection of mail objects that can be seen through Outlook clients or OWA when an end-user
selects a recipient. Address lists are populated to end devices through address book policies that are essentially
a collection of address lists. This feature makes it possible to apply filters to generate custom address lists, and
then create address book policies to different user groups in the organization.

While it is possible to use the default settings, an organization would probably need to create different policies,
depending on the way the organization is logically segmented. For instance, an acquisition or merger can occur
and, by default, users will see mail objects from both organizations, even if they are legally independent, and
they don't communicate. By creating custom address lists, these lists will be smaller and will contain only mail
objects that end-users are sending mail to.

It is possible to configure these settings through the Exchange Management Console (Organization Configuration->
Mailbox-> Address Lists tab. Once the Address lists are configured, you can create a policy
through the Address Book Policies tab.

SMTP connectors need to be configured when mail flows to other organizations or the Internet. They allow the
e-mail to be received from the outside world as well. Internal e-mail is also routed through SMTP connectors;
however, these are stored in Active Directory (AD) and cannot be seen from the management console.

Receive connectors

By default, Exchange can receive e-mails from authenticated senders only through default and client connectors.
If an organization needs to receive e-mail from the Internet, it must allow anonymous types of connections to
the Exchange servers.

It is beneficial to create multiple receive connectors and then define more granular authentication methods,
depending on who is sending e-mail to Exchange.

For example, since e-mail coming from the Internet comes from unauthenticated servers, you can define a
smart host or relay agent that receives the e-mail directly from the Internet, and then configure authentication
between that relay agent and your Exchange hub servers. All e-mail from the relay would be redirected to your
Exchange servers, allowing for greater security on internal servers, as no unauthenticated connection is accepted
on Hub servers.

Another reason we can create multiple SMTP receive connectors is because internal devices, such as printers
and faxes, access Exchange often. These devices all have different authentication settings; thus, you can be more

flexible with authentication in connectors and IP filtering. This way, you are preventing unauthenticated users
connecting to your SMTP servers and anonymously sending e-mail.

Send connectors

It is necessary to create send connectors manually, and preferable to choose to send to a smart host in a DMZ
(such as an Edge server or any other SMTP server solution) rather than sending e-mail directly on the Internet
from the Hub server (through DNS).


View the original article here

Wednesday, June 12, 2013

Optimizing Microsoft Exchange in the Enterprise Part I: Optimizing the Mailbox Server Role and the Client Access Server

Exchange Server 2010 is one of the most flexible and robust products in managing the messaging infrastructure of the organization. It includes a considerable number of features that help control the way emails are exchanged within the premises of the company. While the default setup provides a functional setup, it is worth looking at other features to get the most of this product. In this two-part white paper, we explore these features and take a look at how they can be implemented on top of a standard installation of Exchange servers in the organization. Part 1 examines, Optimizing the Mailbox Server Role and Optimizing the Client Access Server (CAS). Part 2 looks at Optimizing the Hub Transport Server, Miscellaneous Features, and Lync- SharePoint Integration.

The mailbox server role is one of the most critical components of Exchange. It is the location where the user's data is stored. It is also a key component in the proper functioning of the following:

Hosting of public folder databases;
E-mail address policies and address lists;
Retention policies and messaging record management;
Offline Address Book generation server role.

While the standard setup creates the default mailbox database and allows storage of e-mails, additional features can be used to ease the administration of different types of objects, turn on archival for user mailboxes or implement high availability and failover clustering in the design.

The default storage location of the mailbox database, as well as the logs, is the system drive. For performance and better recovery, it is recommended to move these components on separate physical drives or locations within a SAN. A minimum RAID level, such as RAID1 or RAID5, will provide fault tolerance for that data.

The databases and logs can be moved within the Exchange Management Console (Organization Configuration-> Database Management-> Right-click on database-> Move database path) or with the following sample cmdlet:

Move-DatabasePath -Identity 'Marketing' -EdbFilePath 'D:\DBs\Marketing.edb' -LogFolderPath 'D:\DBs\ Marketing'

Databases will be dismounted while the move operation is in progress.

Exchange Standard Edition supports five database instances, while the Enterprise Edition supports 100. It is recommended to use smaller databases - fewer users are affected in the case of an outage, backup and restore is quicker, more granularity when it comes to applying quotas, and much more.

Resources mailboxes are practical for managing meetings and booking different types of resources, such as projectors, rooms, whiteboards, and other type of equipment. This feature permits the automatic management of the resources through the Resource Booking Attendant, as well as other numerous options that allow administrators to granularly control how resources can be used and scheduled in meetings.

Prior to using resource mailboxes, in a legacy environment, we would create a generic Active Directory (AD) account that would then be treated as the resource object, or we can create specific calendars in public folders, from where management of these objects would be done. Now, a type of mailbox exists exclusively for that purpose.

With resource mailboxes, a specific type of object is created within the organization, and then used in meeting requests of users though Outlook or Outlook Web App. Instead of using a generic account for managing these types of operations, a resource mailbox allows for the creation of a specific type of user account in AD that is disabled after creation.

Key features of the resource mailboxes include the following:

Specify who can use resource objects and exceptions when it comes to users that can override approval of delegates (resource in-policy and out-of-policy meeting requests)
Ability to specify objects found in a specific conference room that users can see through the description of the resource in their Exchange client (resource custom properties)
Control meeting requests though the Exchange client without having to add the resource mailbox as an additional mailbox in Outlook (resource delegates)
Ability to specify properties of a room or resource, such as duration, conflicts, room capacity, etc. (resource policies)
Change common options of the resource mailbox through the Exchange Control Panel

It is possible to create new mailbox resource objects through the Exchange Management Console or through the Exchange Management Shell using the following examples:

Conference room

New-Mailbox -Room -Name 'Room1' -Alias 'Room1' -UserPrincipalName 'Room1@contoso.com' -First- Name 'Room' -LastName '1'

Projector

New-Mailbox -Equipment -Name 'Projector1' -Alias 'Projector1' -UserPrincipalName 'Projector1@contoso. com' -FirstName 'Projector' -LastName '1'

It is also possible to convert an existing legacy room resource account into a resource mailbox using the following command:

Set-Mailbox "LegacyRoom1" -Type Room

Dynamic distribution groups are useful when membership of users change often in e-mail groups. A static distribution group gets its members assigned manually by the recipient administrators. In contrast, dynamic distribution groups take advantage of AD attributes to automatically assign memberships to users by defining filters and conditions.

For instance, when an employee changes function or department, an administrator changes the corresponding attributes in AD, and the user account's membership to an e-mail group also changes without direct interaction to the group properties.

We can use very specific filters to fulfill different business requirements, such as sending e-mail to all users in a specific location, or to accounts that share some information in common.


View the original article here

Sunday, June 9, 2013

Microsoft SQL Server 2012: What to Expect

Microsoft SQL Server 2012 has many great new features that will allow you to develop higher performing, more scalable next-generation applications using more than just relational data. Although this release will be a little early for many customers, the fact that the features are largely incremental in nature should reassure users that Microsoft is building on the established foundation of SQL Server 2008. Using the same architecture and management tools, you will be able to smoothly upgrade your systems and skills based on the need for the new features and according to your own schedule.

Three underlying themes categorize the SQL Server 2012 release:

Mission Critical Confidence
Breakthrough Insight
Cloud On Your Terms

In this white paper, we will explore just some of the new features under each theme to give a feel for the capabilities of the upcoming release. Other features, while too numerous to describe here, are documented on the Microsoft web site at http://www.microsoft.com/sql. You can also download a pre-release version of the software or Community Technology Preview (CTP) from the same location.

AlwaysOn for High Availability and Disaster Recovery
Project "Apollo" provides column compression and performance gains
Organizational compliance with enterprise-wide security controls

Before SQL Server 2012, we had four options for High Availability (HA), namely, Server Clustering, Database Mirroring, Log Shipping, and Peer-to-Peer (P2P) Replication. Each solution had its pros and cons. Clustering and Mirroring provided automatic failover. Log Shipping and P2P provided load balancing. Log Shipping would provide the ability to create multiple read-only "secondaries" dispersed over great geographical distances for Disaster Recovery (DR) sites. A common solution was to define a Server Cluster for HA combined with Log Shipping for DR known as HADR. Database Mirroring would only allow one Mirror, and it would not be available until failover. Log Shipping and Replication did not have automatic failover. Replication also can require complex administration.

SQL Server 2012 effectively combines the pros of each of these solutions with its AlwaysOn feature. With AlwaysOn, you will have the automatic failover of Mirroring at the Database level but with the added ability to create multiple secondaries for read-only load balancing. AlwaysOn will provide HADR and Load Balancing in one effective solution.

SQL Server 2008 introduced Data Compression at the Row and Page Levels to provide not only storage savings but also, surprisingly, performance gains based on less I/O. In SQL Server 2008 R2, the VertiPaq technology allowed massive Column-level compression in conjunction with the PowerPivot add-in. In SQL Server 2012, the new column-store index, as part of Project Apollo, will provide the same massive column-level compression within the Database Engine itself. Data Warehouse queries against Star or Snowflake schemas will be optimized to give potential performance gains and storage savings in the order of 100 times improvement.

On the security front, new features in SQL Server 2012 include the ability to create user-defined server roles. This allows specific permissions to be applied to groups of logins instead of using the fixed server roles or having to give permissions directly to each login.

Another interesting security feature is the Contained Database that allows a database to be moved or copied to a new instance without having the dependency on login objects. Users can connect to the database without authenticating a login at the Database Engine-level. Effectively, the database becomes self-contained and removes the normally tricky situation of orphaned users. However, the Contained Databases option has to be specifically enabled at the instance level, an existing database needs to be converted to be Contained, and the users need to be migrated to become Contained Database Users. There exist some specific security threats that relate uniquely to Contained Databases (documented in SQL Server 2012 Books Online), but if you need a database to be easily portable, the benefits may outweigh the drawbacks.

The SQL Audit feature, which was introduced in SQL Server 2008 Enterprise Edition, allows Server- and Database- level auditing without the need for DDL or DML Trigger, giving a more efficient method of auditing that is built in to the Database Engine. SQL Server 2012 allows new features such as filtering audit output and now supports Server level audits for all SQL Server editions.

SSAS 2012: VertiPaq, BI Semantic Model, and PowerPivot
Consistent data via Data Quality Services
Parallel Data Warehouse and Reference Architectures

SQL Server 2008 R2 introduced support for PowerPivot through Excel 2010 and SharePoint 2010 using its VertiPaq technology for massive column compression. This allowed advanced users to develop their own Business Intelligence solutions via Excel or Sharepoint. The Vertipaq technology allowed literally hundreds of millions of rows of data to be imported and analyzed efficiently on the client via Excel and on the Server via Sharepoint. Based on the popularity of the technology, SSAS 2012 enables Vertipaq on the server-side within Analysis Services itself in a new configuration option named Tabular Mode that supports the BI Semantic Model (BISM).


View the original article here

Saturday, June 8, 2013

Microsoft System Center Configuration Manager 2007 SP2, R2, R3: Making Sense of the Three Versions

Microsoft has engaged in a continual process of upgrading, enhancing, and improving its System Center Configuration Management server since its release several years ago. At this point, organizations who plan to use the product for Operating System Deployment must seriously consider an upgrade to Service Pack 2, or they lose the ability to support Windows 7 workstations. Service Pack 2 is also a necessity for the organization wishing to take full advantage of Out of Band Management.

The fourth edition of Microsoft's System Management Server was released in August, 2007 with a new name, System Center Configuration Manager (SCCM), making it part of the System Center brand, along with a considerable package of enhancements extending the SMS 2003 product. Since the initial release of SCCM, there have been two service packs, an R2 version, and the beta version of R3. Keeping track of which iteration is necessary for which feature is a daunting task that has been complicated by the R3's continued beta status and the v.Next product that has been demonstrated at Microsoft's MMS and TechEd events. In this white paper, we will go through the components of each variety of the product that is often called ConfigMgr in an effort to clear up the confusion around this very valuable piece of management software.

In broad strokes, SMS and its re-named child provide an enterprise with the ability to centrally deploy applications and operating systems, inventory software and hardware, manage the distribution of updates and patches, and permit the reporting of each of those crucial components. As a replacement for SMS 2003, SCCM 2007 brought with it several brand-new features including Desired Configuration Management, Wake on LAN, and Network Access Protection.

Desired Configuration Management (DCM) provided an organization with the ability to analyze and compare their existing computers against a previously created standard. Wake on LAN allowed the deployment of applications and patches to a machine that is a low power state. Network Access Protection permits an organization to exclude non-compliant machines from gaining access to the network.

Additionally, a significant number of capabilities that had been introduced as Feature Packs in SMS 2003 were now included in the SCCM 2007 standard deployment, including Operating System Deployment, Asset Intelligence, and Mobile Device Management. In many ways, SCCM 2007 was the natural progression of a solid and mature product. The new and enhanced capabilities made a good business case for an upgrade for SMS 2003 users and for the adoption of the product for those using other tools or were attempting to gain a better grasp of their environment.

In May of 2008, the first Service Pack of SCCM 2007 was released. It provided some new features such as Out of Band Management, support for Soft Grid (now App-V) applications, as well as enhancements to Asset Intelligence and license management capabilities. By introducing the entirely new Out of Band Management capability, which allowed for the control of systems that were powered off or in a low power state, Microsoft signaled that it would continue its strategy of adding significant components to the ConfigMgr product through the interim service packs and releases.

At the end of August 2008, Microsoft released the R2 version of ConfigMgr 2007 to market. As a new "version," it was made available without additional cost to SCCM customers who participated in the Software Assurance program. Release 2 came with an updated help file, which continues to prove quite useful, in addition to new capabilities previously unavailable in SCCM 2007.

As a feature pack, R2 provided five new capabilities. Foremost is support for SQL Reporting Services, which enables the level of extensibility that many enterprises demand. Additionally R2 allows for integration with Microsoft's Forefront Client Security (FCS) application, allowing the usage of Desired Configuration Management packs to leverage the capabilities of the anti-virus and anti-spam of FCS. The third new feature is Client Status Reporting, which can assess the health of client machines. Also provided is true App-V 4.6 support for the newly labeled Soft-Grid system. Last, but certainly not least, are the improvements to Operating System Deployment, which include the ability to deploy the OS to computers without first adding them to the ConfigMgr database and the ability to use multicasts for OSD.

Perhaps the most powerful feature of the NT 6.x operating systems (Vista, Server 2008, and Windows 7) is their new BIOS-agnostic approach to deployment. In short, an image created on or for a Dell Computer could be deployed without modification to a Lenovo or a Hewlett-Packard. That was hardly the case with the previous Microsoft operating systems as images made for Dell 620s could not be deployed to Dell 630s. Unfortunately, Microsoft's initial NT 6.0 end user OS ran into substantial "market resistance" from the enterprise user. While I was an early proponent of Vista, that OS suffered some drawbacks. Now, with Windows 7, we finally had something we could whole-heartedly support. With a Release to Market to essentially coincide of that of Windows 7, ConfigMgr 2007 SP2 was launched.


View the original article here

Saturday, April 27, 2013

Microsoft Convergence 2013: Crossing the 'T's; dotting the 'I's

First, once again, an apology to Microsoft and to those of you who like reading this stuff, for the lateness of this post on Convergence, which was well over a month ago. I'm on the road so much and had to finish the Watchlist and cry, cry, whine, whine, so I'm sorry.

But I can move on if you can.

As those of you who read my stuff know, I place a good deal of stock on the annual user conferences that software vendors put on. I think that they both reflect the state of the vendor and, at the same time, are indicators of the future of the vendor. You can see what progress they made, what promises they kept, and what problems they have by comparing where they were a year ago with where they currently stand.

The vendors feel the same as me. They spend millions of dollars putting these things on, making them their show of shows each year. They court customers and analysts and intermingle with their guests in what is often a highly orchestrated "experience" that is designed down to the positioning of the lights to provide an ambiance that is feel-good in nature, even when the news might not be as good.

Each vendor chooses the canvas and the colors of the paint they want to apply to that canvas. It varies from year to year — it can range from splashy and spectacularly vivid to more brown toned and muted, soothing rather than exciting. Whatever the choice, it is both deliberate and something that can make or break the company's efforts for the year.

This year, Microsoft was ubiquitous Windows 8 blue — a somewhat muted blue — and, folks, that was a good thing.

Where last year at Convergence, it was user experience and user interface and Windows 8 and all color and light and enthusiasm (and rightfully so), this year is more customer experience and the presence of Windows 8 in a ubiquitous fashion. It was/is just there.

What this means for Dynamics CRM, I'll get into in a minute in this shorter-than-normal and late blog post. First, a look at the conference itself, not the messaging.

First, as I do every year, because I am in awe every year, I want to thank what I think is the best AR team in the industry: The folks from Waggoner Edstrom who work with the Dynamics CRM team. Umran Hasan, Lisa Perazzoli, Lourdes Rios Salazar, Anne Goldman, Leslie Boelter, and Meg Hollis deserve the designation. They take care of business, and they are professionals to the nth degree, but not to the exclusion of being warm and personable individuals. They are the textbook for AR and IR.

That's saying a lot, because being excellent at influencer relations (IR) isn't an easy thing — it's a relatively new approach to the more traditional analyst relations, and involves understanding the newer dynamics in the market when it comes to interacting with influencers, be they institutional analysts, independent advisors, or journalists. Plus, influencers can occasionally be snippy and sometimes feel entitled. So dealing with us ain't easy, and yet they make it that way. Thank you so much for doing that — not just once, but year after year.

Microsoft understands the importance of conferences, and, as I said in last year's Convergence post, it deliberately keeps things to an "intimate" size — this year, the number was 12,000. Needless to say, that's a relative number. But the key to its approach is to create a highly personalizable and personable experience for each attendee, despite the still rather large size. It isn't a high-energy experience. It is wise enough to know that this isn't its forte. It had a local band doing heavy and light rock, and it was a solid cover band with good vocalists and good musicians. But that was the feel of the conference. Solid.

To its credit, it knows that on the level of energy, no one is going to successfully compete with Salesforce and Dreamforce. Interestingly, except for one slightly snippy comment about a vendor's new messaging, the conference (thank God) was devoid of competitive misanthropy.

Dynamics in general and Dynamics CRM in particular is clearly playing an increasingly important role in the Microsoft product pantheon. Just to be clear, Convergence is a business apps conference, so business apps clearly are going to be front and center — and mentioned a lot more than, say, Office 365. But it's what's said and done between the lines that is meaningful at conferences like Convergence, and the message this year is clear: Customers first. Windows 8 is already a landscape fixture, so it no longer has to be emphasized — it just "is". And Microsoft is moving aggressively onto the competitive stage with Dynamics, so look out, Salesforce, SAP, Oracle, and others in the marketplace.

Why would I say that?

Because I want to.

OK, OK, not enough. So here's what I'm thinking. About a year ago, Microsoft coaxed Bob Stutz to take over CRM at the company. A great move. For those of you who don't know who that is, he is something of a technology legend in the CRM world, being the strategic architect (not the technical one) of Siebel and of the first true SAP CRM release: SAP CRM 2007.

He has been tasked at Microsoft in bringing Microsoft Dynamics CRM into the 21st century. It has been a serviceable, even good product focused on SFA and customer service. But it lacked quite a bit. It was missing marketing automation, it was missing a true social layer, and it lacked any kind of native customer analytics.

In its original incarnations, since the target markets in the earliest days of Dynamics CRM were small and midsized businesses, it could get by with what it had because it had a ubiquitous name and enough functionality in the two areas that customers in those markets cared about initially.

But, about two years ago, it decided to go upmarket and thus those missing pieces in combination with the navigability and the scalability of what it had became an issue that it had to solve in order to reach out to the enterprise.

Last year, to compound and resolve some of that, it introduced Windows 8 to great fanfare with a focus, even with the business applications, on usability, user experience, user interface, and customer experience. This was an advantage in that it normalized Microsoft Dynamics CRM with an interface that was contemporary, interesting, and highly navigable. It compounded the difficulties, too, because of the adoption difficulties Microsoft had with Windows 8 in its incipient stages. It added a layer of learning to the CRM suite that added work to the learning curve.

Let me point one thing out here before I move on and address some of you who might be Windows 8 naysayers or, more importantly, who are dissing Microsoft because the sales of Windows 8 aren't as high as (you) expected.

Microsoft is in this for the long run. This is a long-term play on its part because it understands that changing the paradigm to one appropriate to the 21st-century approach to person-machine interaction.

While none of this was any different from last year to this year, the messaging around the business applications at Convergence was no longer focused on Windows 8 and usability — but around the customer and the work that Dynamics CRM (and other Dynamics apps) enabled for those customers. It's playing it smart and, given the emphasis on customer experience, a corollary emphasis on customers, while generically always right, is specifically called for in this period — and in this (Microsoft) instance.

The level of progress for CRM in the last year for Microsoft can be game changing for the company. Dynamics CRM, if Microsoft is willing to give it the chance it should, can and should become the leading element of its business suite, given the progress made. But that's a non-trivial IF that I'll get to in a few. I'm not going to speak to the changes that it has made in the technology foundation, nor in the interface until what it is calling the Orion release drops in Q3 2013. This promises the mobile and Windows 8 versions of Microsoft Dynamics CRM. Microsoft Dynamics CRM is a work in progress (with an emphasis on the word "progress" and it is impressive in many ways. Why? Patience, grasshoppers), but I do want to speak to its two acquisitions, which are both very important to Microsoft's future in the CRM world.

The progress that Microsoft has made is not only in the utter reformation of the Dynamics CRM product, but also in the intelligence of its acquisitions to fill holes that have long existed in the portfolio. The acquisition of the integrated marketing management suite — Marketing Pilot (now Microsoft Dynamics Marketing) — was a truly intelligent move. The application, which has about two thirds of the functionality of Aprimo, is as close to its doppelganger as it is going to find. It is a great acquisition, but it needs a lot of TLC to make it a great part of the suite.

If you take a look at the functionality, it is dizzying. Ranging from the more traditional marketing automation functionality like campaign management and email marketing to the more complex management functions like collaborative project management and even not-obvious back-end functions like expense management and budgeting, you begin to see how rich the application suite really is, and, if used fully, would be able to handle all but the largest enterprises — and I'm not sure that is even a fair statement. It might be able to handle the largest ones.

Aye, but there's the rub. Most marketers don't need all that functionality, and even with the revamped Windows 8ish interface — a vast improvement over the original pre-acquisition one — it can be a confusing mischigas ("mess" for those of you not fluent in Yiddish) and actually achieves a level of "too much choice". But there is no reason to dumb it down, either, because as you go up the enterprise-scale food chain, the increased functionality becomes necessary.

As of now, which to be fair is version one, the way that you access Marketing Pilot is via a connector to the Dynamics CRM suite (which is fine, for now) but doesn't solve the "too, too much" conundrum.

But, surprise, surprise, my big-mouthed, highly opinionated self has a solution.

Integrate it fully into the Dynamics CRM Suite. Don't leave it as an independently connected product. That way, it's not on-premises only; it's in the cloud, and Dynamics CRM is a full-blown suite.

Provide a basic marketing edition with Dynamics CRM that has all the fundamental functionality available — marketing automation, email marketing, etc.

Make the rest premium business services that you can subscribe to. This means that as a business grows and it starts needing to, say, manage resources, you can turn on the functionality by paying an extra whatever bucks per month per user for the additional capabilities. It sounds easy; it isn't. But it is the way that I think that Marketing Pilot gets to be part of the Microsoft suite that both makes it one of the better in the marketplace and monetizes it.

Do these things, and Marketing Pilot's acquisition becomes a steal at any price.

The Microsoft acquisition of Netbreeze works. It works because of how it intends to use it. Netbreeze, for those of you who don't know it, which would be most of you, is a Swiss company of seriously intelligent scientists who built a highly functional, modestly deep, user-friendly customer/social analytics product that actually can provide you with useful information — the kind that is usable for insights. Its greatest strength is its ability to do sentiment analysis in 28 languages, including several different writing systems (Arabic, Cyrillic etc). But even though the product is certainly a good entry in the marketplace, the value for Microsoft comes, not in the product per se, but in the intended use — its game plan.

If it had intended to buy the product so that it could make it part of a product portfolio, an offering, it would have been stupid acquisition at any price. It's not really built for that, and up against some of the deeper products in the space (eg, Clarabridge, NextPrinciples, the customer-facing analytics products of SAS, Oracle, SAP), it would not do well. But, instead, Bob Stutz and team acquired them for a different reason — one that not only makes sense, but it is actually the ideal approach to both the market, and to support the strengths of Netbreeze's offering. It is going to integrate it as a layer across the entirety of Dynamics CRM and give it away free of charge as the "social analytics" layer of the Dynamics CRM platform.

To Microsoft's credit, this wasn't a dramatic conference. The message that came through loud and clear this year is that it is proceeding with its initiative launched in 2012 to change the way people compute and to provide businesses with what they need to accommodate that change — and, of course, deal with the way that customers have been changing for the last decade.

Are there things that it can do? Of course there are. If you want to see what they are, read its Watchlist review of about a month ago. Beyond that, how it handles Marketing Pilot is going to be an important piece of its ability to provide a "right-sized" offering for multiple different target groups. All in all, it is on the right track to not only continue to be a major player, but also to reassert its position in the CRM market as one of a small handful of vendors that could be a good choice for any company, regardless of size.

We'll check back later this year to see how it's doing.

Seriously.


View the original article here