Is It Overreacting to Be Upset About a VM Deployed Without Notification?
September 15, 20255 answers
Asked byTechSavvy21
I'm the IT/ERP Manager at a small business with 60-70 employees across four locations. We have an MSP that helps us with our tech needs under a co-management agreement. Recently, I had a meeting with their Director of Customer Service because they've been making changes without keeping me in the loop, which has been frustrating.
Afterward, I met with their lead technician who mentioned several new software tools they're planning to introduce, including Nodeware, which I thought was cloud-based and meant to be tested first. However, when I checked our Hyper-V hosts later, I discovered an unauthorized VM running Nodeware—a Linux server—deployed directly on our production host without my prior knowledge.
This is the first time they've done this, and I feel it crosses a line since all previous tools had been cloud-based. If they had just informed me, it wouldn't have been an issue. I plan to bring this up with my COO but wondered if I'm overreacting about their lack of communication here.
It sounds like this may be more of a communication issue than anything else. Maybe the technician thought you were already informed? Still, it’s best to clarify the change approval process moving forward to avoid similar situations in the future.
TeamPlayer_88: Good point. Setting clearer expectations could prevent misunderstandings.
CuriousGeorgeX: Definitely. Maybe a follow-up meeting could clarify roles and improve future communication!
Reply to this answerITGuru_99
It really comes down to the specifics of your agreement with them. If they're acting outside those bounds, then definitely something needs to be addressed. That said, I used to work for an MSP, and we had a pretty laid-back approach with clients who had their own IT. Sometimes communication just falls through the cracks, but a heads-up would have been courteous for sure!
DevOpsNinja: Totally agree. The MSP should have a level of communication, especially for someone like you who's responsible for the network.
NetworkWhiz: Exactly, it's all about common courtesy. Proper communication helps avoid issues down the line.
Reply to this answerChangeManager_Pro
You definitely need to establish a formal change management process. Having clear protocols can prevent issues like this from happening again. Your internal team and the MSP should be on the same page about deploying anything affecting your production environment.
SysAdminMaster: That’s a great point! I've seen the same issue, and formalizing communication can really save a lot of headaches.
ITConsultant4Life: Agreed. Without clear change management, it's just a recipe for disaster.
Reply to this answerIT_Pete
I wouldn’t say you’re overreacting, but I understand the frustration. Check your contract specifics. If the MSP had to deploy a VM for new tools, it should have been communicated clearly. This is a prime example of why establishing a well-defined communication process is critical.
ChangeIsGood: Right? It’s all about ensuring everyone is informed and on the same page.
IT_Explorer: Exactly! And if they failed to follow proper procedure, it's worth discussing with your COO.
Reply to this answerSarah_MSPSupport
As someone who works with an MSP, I can't stress enough the importance of getting written approval for any deployments. Every change should ideally be approved beforehand to avoid any misunderstandings, especially in a co-managed agreement like yours.
TechieMike: That makes sense. In our setup, any change to the infrastructure needs to go through an approval process as well.
AdminWiz: Exactly! It's crucial for both parties to maintain trust and control.
TeamPlayer_88: Good point. Setting clearer expectations could prevent misunderstandings.
CuriousGeorgeX: Definitely. Maybe a follow-up meeting could clarify roles and improve future communication!