When using Microsoft technologies in your enterprise IT stack, you have a few native options for systems monitoring and alerts. Two recent product developments — folding Operations Management Suite (OMS) functionality into Azure Monitor, as well as the release of the new SCOM 2019 — have reignited the debate to determine whether Azure Monitor can entirely replace the long standing, good-old SCOM (System Center Operations Manager).
In a way, I feel this comparison is a bit unfair, like comparing apples with oranges. Ultimately the two products can work together and overlap in order to eliminate monitoring gaps in your environment. So which monitoring solution would work the best for your enterprise? Let’s try to figure out!
When you enter data into Beekeeper Patching Automation, you use the UI to add servers groups, Windows Failover Clusters, and Exchange DAGs. Then, you assign validation tasks to these server groups or clusters. To create the execution job, you assign the server groups or clusters to a schedule. This can be time consuming.
I have created PowerShell scripts to do these tasks. In a series of blog posts, I will share these PowerShell scripts and go over their usage.
The first PowerShell script will export servers from an SCCM collection into a CSV. Then another script will import that CSV to create the appropriate Application groups, Windows Failover Clusters, or Exchange DAGs.
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!
Will we ever get past talking about IaaS vs. PaaS vs. SaaS? Perhaps not. Gartner recently published a list of the Top 10 Trends Impacting IT Infrastructure and Operations for 2019. Sitting at Number 8? Software as a Service (SaaS) denial.
Basically, most organizations have been hyper focused on Infrastructure and Platforms as a Service — migrating to cloud VMs, hiring admins for Azure and AWS ecosystems, learning Kubernetes and Docker.
Meanwhile, shadow IT and the overall enterprise trend is to initially prefer SaaS. Of course, SaaS has made inroads with IT departments even at the enterprise level, especially Office 365. But without Infrastructure and Operations teams taking SaaS seriously, your overall IT environment could be opened up to security risks on top of integration problems, fragmentation, and service delivery concerns.
Are you in SaaS denial? Do you have blinders on as you focus entirely on IaaS adoption or other more pressing matters? Now is the time to get ahead of the SaaS adoption hurdles by being proactive within your IT and operations departments.
Migrating to the cloud? Now is the perfect time to start or continue your digital transformation. There are several methods when it comes to cloud migration. At some point in your cloud journey you’re bound to encounter more than one of them and each of them certainly has its purpose.
But if you aren’t designing in the cloud, for the cloud (which could involve rearchitecting or procuring replacement application components), you’re missing out on many of the biggest advantages of cloud computing.
Here’s why “lift and shift” ends up stifling what could be a transformative cloud migration that sets the stage for your enterprise IT for years to come.
At Green House Data we like to say there’s no “one size fits all” cloud deployment. That’s why we don’t have base package pricing on the website — every VM is right-sized and designed around our client’s applications and business goals. That philosophy applies to every cloud deployment, and the network considerations aren’t exempt.
Depending on your objectives, the intended use of the application in question, and the location of your users and service providers, your network will have different performance and cost implications.
Let’s take a look at how to prepare your network for varying application deployments in the cloud.
Moving to the cloud, changing service providers, upgrading your host hardware, consolidating data centers, or switching to new software — they all might necessitate a database migration.
Moving a database is not a task to be taken lightly, but it can lead to more centralized and efficient management, lower storage costs, and/or reduced license requirements. To minimize your risk and downtime, follow these database migration tips.
The holidays are looming, meaning many DevOps teams are about to have their apps take a beating as hundreds of holiday orders and new device users slam them all at the same time. Whether or not your systems are consumer-focused, there will eventually come a time when the overall load on your servers is pushed to the limit.
Load testing applications in the cloud allows development and testing staff to perform scale testing to see at what point virtual machines need to scale, when to add additional resources like storage or bandwidth, and when a failover solution might be necessary.
By thoroughly performing load tests throughout the DevOps process, your organization eventually lowers costs and your team doesn’t have to scramble during a major event. Here are some best practices when performing cloud-based load testing.
With two different licensing models and several different versions of SQL Server, managing your licensing in a virtualized environment (like a hosted VMware cloud) is no simple matter.
This quick rundown will guide you towards the best licensing choice for your cloud VMs running Microsoft SQL Server.