Phoenix BIOS Editor 2.0.18 or Phoenix BIOS Editor 2.2.0.1 or Phoenix BIOS Editor 2.2.1.3. ![]() Well instead using the host's DMI information, it is also possible to use your own DMI via editing VMware's Phoenix BIOS with You are the only one I have found that might understand what im trying to do. Subject: Private Message: have any thoughts about this ? Some minutes ago, I cleaned up my VMware private message folder and I found this: Pain to benefits ratio is too far out of whack in my opinion.Ĭonsider awarding points for "helpful" and/or "correct" answers. ![]() Try to explain why you did that when the company gets a virus that the patch would have protected it from. OR, they think your host system has the patch, which it doesn't, leaving your system vulnerable. Not the least of which is when a patch needs to be deployed that conflicts with something on the VM, but the IT people don't know, so you get it and the other items you're running on that VM get messed up. If you're trying to mask the VM to seem like you're actual system it's going to present issues later. We could also better keep track of deployed software so that things were better managed. It actually made life easier for us to know that the target was a VM and not a physical system. IF we also installed the agent (for collecting inventory as well as other things like remote control, software deployment, etc.) then it would show the target as being a VM and we could then better support them as well as know if we needed to target that system for updates or not. I was the LANDesk administrator at one of my previous jobs where we had several users with VMware Workstation installed. ![]() This will present them with additional issues, later, if not sooner. Do your companies IT people actually want you to mask your VM? If so, then that means the system grabbing the inventory information will think it has duplicate records, and delete one of them.
0 Comments
Leave a Reply. |