When you decide to move your Exchange environment to the cloud, you might be confused to discover that you still need to maintain an on-premises Exchange server. There are several reasons for this, stemming from the migration process and on to Identity Management.
If you’re moving from an active on-premises Exchange deployment, you’ll first configure an interim “Exchange Hybrid” environment which hosts mailboxes within Exchange Online and your local Exchange server. The two locations share namespace, address books, free-busy, calendars, really every Exchange functionality is synced between them. Mail flow and other functions appear to be internal, but might actually be processed and stored in the cloud environment.
Another year successful year has gone by on the Green House Data blog. We're thrilled to surpass 150,000 views in 2018! Thanks for reading our humble blog. In case you missed anything, here are the five top posts from 2018, covering VM performance monitoring, GDPR, and a subject no modern blog should be without…millennials. And more!
Don't forget to tune in after the New Years for more great data center, cloud, and managed IT services content!
Cloud computing has shaken up many IT roles. While daily tasks may not be dramatically different (depending on the IT team member in question), the general trend is an increased focus on hard cloud skills and soft business skills — in other words, discovering how to generate business value out of cloud systems, rather than simply making sure an application or piece of hardware is functioning properly.
We’ve discussed previously how cloud can be difficult for Accounting to classify. But even Human Resources has to adapt. Much has been made of the cloud skills gap as a challenge to hiring the right talent. A shortage of qualified applicants may be real, but if your HR team doesn’t change the actual job descriptions and roles for which they are hiring, they won’t find the skills they need, either.
Here’s how the cloud is changing IT team roles and responsibilities.
DevOps practices have moved past pure software development and into enterprise adoption, facilitating faster updates to applications and associated infrastructure.
The crux of DevOps is the unification of tools and processes between development and operations teams to decrease time to market/deployment and implement continuous improvements throughout the development, testing, implementation, and ongoing maintenance of applications and underlying infrastructure.
Despite widespread DevOps adoption — or at least the majority of surveyed enterprises reporting they have started the journey towards it — many organizations are still struggling. Enter DevOps as a Service. But is DevOps as a Service a legitimate offering? The definition is still evolving, and different MSPs may offer different takes on DevOps-a-a-S.
Bruce is a 45-year-old IT manager, with twenty years experience working for ACME Power. Bruce has three photos on his desk – one of his wife, Linda; one of his kids - Davy and Wendy; and one of Microsoft CEO Satya Nadella. Apart from his laptop, Bruce’s desk is pristine. He walked into the office this morning with a big smile on his face and passed out donuts to his colleagues.
Today has been highlighted in Bruce’s Outlook calendar for weeks. It’s day one of a thorough compliance audit of ACME Power’s application and server infrastructure.