Data is all around us, but it’s becoming increasingly difficult to abstract relevant insights from our data that lead to intelligent action. Last night’s #AzureGovMeetup dove deep into advanced analytics capabilities, and attendees got a firsthand look at how raw data is transformed into actionable insight.

It included highly interactive and demonstration-focused sessions by Microsoft data and cloud experts, as well as AIS’ own CTO and Microsoft MVP, Vishwas Lele. Esri also presented a demo of advanced spatial analytics in the cloud.

          

In case you missed it, AIS livestreamed the demos on Twitter. Watch the videos below and be sure to follow us @AISTeam. (And check out the #AzureGovMeetup hashtag for more photos and insights from the outstanding lineup of experts.) Next month’s Meetup will be Wednesday, May 31 at 6 p.m. RSVP today!

(Don’t miss Part Two and Part Three of this series!)

Early in my web development career, I always tried to avoid deployment work. It made me uneasy to watch other developers constantly bang their heads against their desks, frustrated with getting our app deployed to whatever cloud service we were using at the time. Deployment work became the “short straw” assignment because it was always a long, unpredictable and thankless task. It wasn’t until I advanced in my tech career that I realized why I felt this way.

My experience with deployment activities, up to this point, always involved a manual process. I thought that the time it took to set up an automated deployment mechanism was a lot of unnecessary overhead – I’d much rather spend my time developing the actual application and spend just a few hours every so often on a manual deployment process when I was ready. However, as I got to work with more and more experienced developers, I began to understand that a manual deployment process is slow, unreliable, unrepeatable, and rarely ever consistent across environments. A manual deployment process also requires detailed documentation that can be hard to follow and in constant need of updating.

As a result, the deployment process becomes this mysterious beast that only a few experts on your development team can tame. This will ultimately isolate the members of your development team, who could be spending more time working on features or fixing bugs related to your application or software. Although there is some initial overhead involved when creating a fully automated deployment pipeline, subsequent deployments of the same infrastructure can be done in a matter of seconds. And since validation is also baked into the automated process, your developers will only have to devote time to application deployment if something fails or goes wrong.

This three-part blog series will serve to provide a general set of instructions on how to build an automated deployment pipeline using Azure cloud services and Octopus Deploy, a user-friendly automation tool that integrates well with Azure. It might not detail out every step you need, but it will point you in the right direction, and show you the value of utilizing automated deployment mechanisms. Let’s get started. Read More…

The central focus of DevOps has been the continuous delivery (CD) pipeline: A single, traceable path for any new or updated version of software to move through lower environments to a higher environment using automated promotion. However, in my recent experience, DevOps is also serving as the bridge between the “expectations chasm” — the gap between the three personas in the above diagram.

Each persona (CIO, Ops and App Teams) have varying expectations for the move to public cloud. For CIO, the motivation to move to the public cloud is based on key selling points — dealing with capacity constraints, mounting on-premises data center costs, reducing the Time to Value (TtV), and increasing innovation. The Ops Team is expecting a tooling maturity on par with on-premises including Capacity Planning, HA, compliance and monitoring. The Apps team is expecting to use the languages, tools, and CI process that they are already using, but in the context of new PaaS services. They also expect the same level of compliance and resilience from the underlying infrastructure services.

Unfortunately, as we will see in a moment, these expectations are hard to meet, despite the rapid innovation and cadence of releases in the cloud.

Consider these examples: Read More…

In this video blog, I’ll walk you through building a continuous integration and continuous delivery (CI/CD) pipeline using the latest tools from Microsoft, including Visual Studio Team Services (VSTS) and Azure. The pipeline is built to support a .NET core application, and the walkthrough includes the following steps:

  1. Configuring Continuous Integration (CI) with VSTS Build services
  2. Adding unit testing and validation to the CI process
  3. Adding Continuous Deployment (CD) with VSTS Release Management & Azure PaaS
  4. Adding automated performance testing to the pipeline
  5. Promotion of the deployment to production once validated
  6. Sending feedback on completion of the process to Slack

In a previous blog post, we discussed a quick overview of Continuous Integration and Deployment of .NET applications using Visual Studio Team Services (VSTS). This involved building and deploying regular old .NET applications with VSTS—something that we would definitely expect a Microsoft service to handle. However, there is some lesser-known support that VSTS has for other frameworks, including Java. The Microsoft VSTS website even has a portal page proclaiming their Java support: “Love Java? So do we!

VSTS support for Java build frameworks such as Maven and Ant came in handy for AIS recently, as we were tasked with developing some new features for an older Java desktop application for a federal client. And I will have to say that all of the VSTS tools for Java applications worked flawlessly. We were able to easily add the Java project source code to a Team Foundation Version Control (TFVC) repository hosted online in VSTS. Oracle even has an extension for integrating with a TFVC workspace—allowing us to check in changes right from the JDeveloper IDE. Read More…

SHAREPOINT 2013 END OF SUPPORT DATE

Microsoft will be ending their mainstream support for SharePoint 2013 by April 2018. The SharePoint end of life date for 2013 is 4/10/2018. This means that if you want support past that date, you will need to pay for it. Is your organization prepared? If you’re currently running SharePoint 2013 you should start planning your move to SharePoint 2016 or Office 365.

THE COST OF UNSUPPORTED SOFTWARE

Operating with outdated and unsupported SharePoint Server environment comes at a cost. After April 2018, if you want security and non-security related fixes, you have to purchase support and pay for each fix requested. Avoid the unnecessary fees and upgrade before your product reaches endof support. Once you are unsupported, you also risk data loss. If a corruption of your content databases occurs, are you able to recover your content completely without involving Microsoft?

In addition, there are many productivity enhancements that your users can benefit from migrating to a newer platform. By migrating to Office 365, your users can start taking advantage of new features like OneDrive for Business, Office 365 Groups, Microsoft Teams, Yammer, Microsoft Flow, and PowerApps. By not migrating, you are costing your company money in the form of time and enhanced productivity that your users don’t have today.

HOW LONG DOES IT TAKE TO UPGRADE SHAREPOINT 2013?

No matter how big or small your organization, upgrading SharePoint 2013 can take time — from a couple weeks to even a whole year. The migration time is largely dependent on the amount of content you have and if you are moving to SharePoint 2016 or SharePoint Online/Office 365. Get a head start on upgrading your software by talking to a SharePoint specialist about your budget, timeline, requirements, and goals. The sooner you start your planning, the smoother and easier your migration is going to be.

BENEFITS OF MIGRATING TO OFFICE 365

Once you migrate to Office 365, you no longer have to plan for upgrades every three years to the latest version of SharePoint. Microsoft rolls out new features every three months and you can choose which ones to enable for your enterprise. In addition, Microsoft manages the upgrades for you so you don’t need to dedicate time, money and resources to upgrade and migration efforts.

UPGRADE YOUR OFFICE PRODUCTS TODAY

Don’t run the risk of operating unsafe or compromised software. Contact AIS today to talk to a SharePoint specialist about your options and requirements. We can help you upgrade, migrate, and operate your environment so you never need to worry about outdated and expired software again.

If you need managed services to maintain peak IT network operations, consider us here at Applied Information Sciences. We’ll manage all your IT services for a predictable cost so you can focus on more strategic investments. AIS’ Managed Services Practice provides ongoing responsibility for monitoring, patching and problem resolution for specific IT systems on your company’s behalf.

Capabilities

  • Patching
  • Monitoring
  • Alerting
  • Backup and Restore
  • Incident Response

AIS’ Managed Service Practice has up to 24×7 coverage for initial responses to incidents through a combination of dedicated, part- and full-time staff, both onshore and offshore. AIS prides itself in being on the leading edge of managed services support. Our collaborative, disciplined approach is committed to quality, value, time and budget. Read More…