I would say yes. Systems administrators can also use vagrant for testing our own environments. Say you want to test your puppet manifests against a known standard configuration - you could `vagrant up` an entire testing system environment.

Additionally, part of a systems administrators job is supporting the systems that the staff use. Vagrant still falls within this scope.

So a blanket ban on vagrant is not a good idea. As with most things, looking at the question in-context before making a decisions is the way to go.

-----

As per our very own [on-topic FAQ][1]:

> If your question is about:
>
> - managing the hardware or software of servers, workstations, storage or networks
> - tools used for administering, monitoring, or automating these
> - deployment to and management of third-party provided information technology platforms

I believe that Vagrant fits these three requirements. It's software for workstations, it's a tool for automation, and it's about deployment and management of third party technology platforms!

> and is not about:
> 
> - consumer workstations or networking (which belong on our sister site, Super User)
> - working with a service provider's management interface, such as cPanel
> - product, service, or learning material recommendations
product licensing inquiries or legal advice
> - career, salary, personnel, employment, or formal education
> - unauthorized use or misuse of IT systems

It is none of those things either.

  [1]: http://serverfault.com/help/on-topic