We are big proponents of using the right tool for the job and when it comes to migrations from file shares and on-premises SharePoint we often recommend the Sharegate Desktop application. Just head over to your favorite search engine and type “lift and shift SharePoint migration” to see why we like to use utilities to avoid the lift and shift approach. Migration best practices aside, as the title of this post suggests there was something a little wonky going on with one of our customers migrations. One of the other reasons we like Sharegate so much is its ease of use as it allows the customer to perform many of the tasks without our assistance which saves them consulting dollars but when issues arise, we are usually able to solve them quickly, this was no exception. Continue reading “Sharegate Desktop: An unexpected error occurred: This file is currently not available for use on the computer”
Cloud computing has revolutionized business operations, and is becoming the nearly universal adopted model for IT infrastructure. In fact, the 2018 State of the Cloud survey found that 96% of organizations use cloud services in some form or another, providing today’s organizations with a host of benefits, including greatly reduced operational costs and increased inter-connectivity via a secured network.
However, moving from mainframe to cloud presents a variety of challenges, and many organizations still rely heavily on legacy mainframe systems and outdated technologies for a large portion of their operations. Below we’ll outline a few of the more common challenges related to full scale cloud adoption, while also providing other some potential solutions. Continue reading “Potential Risks of Cloud Migration”
I have been working with EF Code First Migrations for a while but until recently had not used it for updating more than a local development database. As I discovered, it is actually pretty easy to run your migrations against different databases. The update-database command has an optional switch for a ConnectionStringName. However, if you are using web.config transformations to manage connection strings for different environments, you may only have one connection string name, with the environment specific connection string being defined in each transform. I’ll explain how I am getting around that.