There are several things to consider before clicking that “Launch” button in the AWS (Amazon Web Services) console. The more you plan and take into consideration ahead of time, the more you can save yourself a few headaches down the road. I will go over some fundamental best practices to consider before launching your EC2 instance. These topics will cover storage, security, backup/recovery, and finally management. Continue reading “Best Practices for AWS EC2”
One of the more interesting challenges contractors for public sector clients have is working with older versions of software. On a recent project involving an integration of a solution I’d written using Microsoft Dynamics CRM 2016 and SharePoint 2010, I found myself struggling with an issue around capturing a digital signature.
As a straight SharePoint development project, this can be fairly routine: leverage Microsoft Word and its implementation of signature blocks, similarly leverage SharePoint’s out-of-the-box (OOTB) workflow for collecting signatures, and you’re basically done.
However, the client in question was less than enthusiastic about SharePoint as a platform in general and, because of that, and a few other design criteria, the bulk of the solution wound up being built in Dynamics CRM and SharePoint was largely a simple document repository.
So, how do you not re-invent the wheel for digital signatures and still keep most of your smarts on the Dynamics CRM side? [Bear in mind the production environment where this was going to be enabled was very locked down. Farm solutions were prohibited, so even if you wanted to write your own custom workflow using .NET workflow, you couldn’t because that requires a farm solution.]
We have the OOTB workflow already and we can associate it with the document library in question, but what we really needed was the ability to notify CRM when that workflow completed. Answer: SPWorkflowEventReceiver.
As a team transitions to using Scrum and Agile, finding the proper sprint duration is likely something they will not give enough thought to. The team will likely just pick an arbitrary duration and set about to make that work. That is certainly one way to do it, but there is a real danger that this initial sprint duration becomes the norm without a second thought. I would caution against this idea. I find that it is important to understand how the scheduling works for sprints, and what a sprint of a given duration actually contains.
Microsoft improved many features in Windows Server 2012 R2 compared to Windows 2008. Once you install Windows Server 2012, you will notice these new changes just by looking at the new management interface which provides administrators the ability to centralize the system. In this post, I will continue with my 3-part series in this second post: Installing the Domain Controller.
- How to Install Windows Server 2012 R2 Standard (Part 1) (If you haven’t yet, read Part 1 before continuing here)
2. Installing the Domain Controller (the current post)
3. Join the Domain