Skip to main content

How many Virtual Machines do you currently have?



This indeed can grow if unchecked.

"Right now people are bringing up machines without management knowing – in my company we had 12 added without my knowledge," he said. "We see a lot of customers trying to balance their VM count – they're losing control of it. It's like the server sprawl we saw 10 or 15 years ago.

"My concern is people will bring up unlicensed machines, and that's a big fine for willful infringement."

He suggested this could even be one reason why Microsoft has sought to limit the number of times a Windows license can be moved from server to server as part of a VM.


Well what kind of a manager are you anyways to not have a track of the machines (Virtual or Physical) in your environment? I think this Register story is merely a sales pitch to sell yet another auditing software. While you're on this FUD-Train, buy our software!

Remember, admins will never allow (virtual or physical) machines to grow in their environment. Why? Simple, its them who has to administer them!

Anyways read here.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op