While running VMware Server 2.0.2-203138 on Windows 7, I experienced the following issue:
- Installed guests assigned to VMnet0 can not ping or access any hosts aside from other VMware guests.
- My NIC is a: Realtek RTL8168C(P)/8111C(P) Family PCI-E Gigabit Ethernet NIC (NDIS 6.20)
- In the NIC properties, the VMware Bridge Protocol is enabled.
Guests could see each other and communicate on VMnet0, but cannot ping the host or anything beyond the host.
In Windows 7’s Network and Sharing center, only NIC is listed under “Internet Access”, and VMnet1 and VMnet8 are listed under “No network access,” but this seems to be normal.
From the Start menu, I opened Manage Virtual Networks, and the Summary page told me VMnet0 was supposed to automatically bridge to some adapter. Apparently, it wasn’t doing so.
At the Host Virtual Network Mapping tab, I was able to specify that I wanted VMnet0 to use the Realtek NIC.
After clicking Apply/OK and waiting a bit for VMware and the guests to figure out just what in tarnation had just changed, guest networking began working as expected.
Within my Solaris 10 guest, I then created /etc/resolv.conf, added the two Google DNS servers, and copied /etc/nsswitch.dns to /etc/nsswitch.conf:
# touch /etc/resolv.conf
# vi /etc/resolv.conf
Add the text:
nameserver 192.168.0.1 # my router
nameserver 18.104.22.168 # google
nameserver 22.214.171.124 # google
# cp nsswitch.dns nsswitch.conf
What happens when a significant number of your users use their own devices at work (Bring Your Own Device — BYOD), and an OEM patch breaks the system for those users?
I have talked to several clients that want to move forward with BYOD initiatives, but are predictably cautious. Several have initiated small pilots with the goal of supporting a specific use case (e.g., iPads for c-level executives). Others are more cautious with planning and architecture and have yet to support any BYOD implementation. However, some clients are already using server-hosted virtual desktops (SHVD) to support call center employees that work from home. In some instances, those workers access their virtual desktops from personal PCs.
That leads us to a significant problem that occurred this week. A Windows 7 update broke the VMware View client. You can read about the problem in the VMware KB here. The problem can be resolved by upgrading the View client or by uninstalling the Windows 7 patches noted in the workaround here.
via Windows 7 Update Breaks VMware View Client: An Important Lesson In BYOD.
This is quite a handy tip. I know where I put everything on my Windows machine, and the Library view mostly just gets in the way.
The reader told me that while reconfiguring the navigation pane so that Libraries were not as prominent was a good trick, but what he really wanted to be able to do was to remove Libraries altogether. After a bit of investigation, I discovered that it is possible to remove Libraries from Windows Explorer with a couple of Registry tweaks.
In this edition of the Windows Desktop Report, I’ll show you how to remove Libraries from the navigation pane in Windows 7’s Windows Explorer by editing the registry.
via Remove Libraries from Windows Explorer in Windows 7 | Microsoft Windows | TechRepublic.com.
Cameron Sturdevant presents 10 tips to tune up Windows 7 VMs to run as virtual desktops.
Optimizing Windows 7 for VDI – Windows from eWeek.
Some gotchas in Win 7’s “built-in” security:
For instance, top-end security features like AppLocker, BitLocker, BitLocker to Go and DirectAccess require the more expensive Windows 7 Enterprise version, and also call for Enterprise Assurance or Software Assurance maintenance plans; the features don’t come with the pre-configured PCs sold by HP or Dell.
Some organizations, MacDonald said, have tried to work around this limitation by purchasing Windows 7 Ultimate, a similar edition that also contains all the same security features as Enterprise. Despite being initially more expensive that Enterprise, Ultimate is $100 cheaper per user when factoring in the savings of not purchasing a maintenance plan. However, there are drawbacks to this approach as well.
“Ultimate is officially a consumer version, and comes with a consumer SKU, which means it has consumer-level support. So instead of getting 10 years of support and security patches, you only get five years,” MacDonald said, “and you don’t get volume license activation, so you’d have to manually activate each version.”
via Gartner: Windows 7 security features have strings attached.
If you’ve now using or about to begin switching to Windows 7, Robert Shimonski has written a fairly in-depth overview of Windows 7’s security capabilities, and how to harden the OS, including manual tuning and the usage of security templates from Microsoft.
Regardless of which version of OS you are running, this is a good set of steps to follow to start out fresh, clean, streamlined, and secure:
Step 1 – Installation of Base OS selecting any options during installation the increases security and not selecting unneeded services, options and programs.
Step 2 – Installation of any Administrator toolkits, security tools and needed programs.
Step 3 – Remove services, programs and unneeded software. Disable or remove unused user accounts or groups.
Step 4 – Service Pack update, hot fixes and service packs. Update all installed programs as well.
Step 5 – Run security audit scanner, template, MBSA, etc to assess current security level
Step 6 – Run System Restore and create a restore point. Backup and Restoration application for disaster recovery.
Step 7 – Backup the OS with a way to quickly restore it in the event of disaster.
This list is a simple guide. You can add more steps and extend this list further. This list is not definitive, but a good start in getting an idea of where to start when applying security to Windows 7 after a base installation. If completing a fresh install of Windows 7, then the next step is to remove any unwanted software, services, protocols and programs that you do not want or need running on it. This can be done easily in the Control Panel.
via Windows 7 Security Primer Part 1.