Thursday, 26 July 2012

Windows 7 and "network neighbourhood"

Windows 7 and "network neighbourhood"


1. Click Start menu and open Control Panel.
2. Open "Network and Sharing Center" and click "Change advanced sharing settings" option in the left panel.
3. In domain profile, please select "Turn on Network discovery" and save the settings.
4. Click Start menu
5. Click "Start", go to run, type "services.msc" (without quotation marks) in the open box and press Enter.
6. Click Continue button to verify the administrator permission.
7. Right click Computer Browser Service and choose Properties.
8. On General tab click Start.
9. Choose Automatic next to Startup type.
10. Click OK.

Further Changes:
  • Make sure that remote registry service is set to auto start
  • TCP/IP advanced properties: enable Netbios over TCP/IP

Windows 7 "interactive state" issue with McAfee Anti Virus

Windows 7 "interactive state" issue with McAfee Anti Virus


Having looked at the logs, Windows Server 2008 was not allowing NAI ePO Agent MSI to run, having looked the Framepkg.exe copies the content of the agent to Program Data and runs the package from Programs Data.

What I did was to Copy the content of EPO Agent to Program Data and run Framepkg.exe from the command line with the following parameters

Windows 7 auto-logon

 Windows 7 auto-logon

 
  • Click on Start and then enter the following command in the search box: netplwiz
  • Press the ENTER key.

Disable "old" physical NIC in machines that have been virtualized

Disable "old" physical NIC in machines that have been virtualized

 Follow these steps to sort it out:

How to upgrade the free version of ESXI

How to upgrade the firmware without the paid products


The primary way to manage an ESXi system is via Windows. To this end, you will need the VMware vSphere CLI package (available from the VMware website) installed as well as the vSphere GUI client. Both are available for Windows; however, only the first is also available for Linux. The GUI client will not allow you to upgrade the firmware of ESXi, which is why you need the CLI tools (but you do need the GUI client to manage/shutdown/suspend the virtual machines in order to do the upgrade). So, because the client only runs on Windows, you will either need a Windows system available, or a virtualized Windows install on another machine that is separate from the ESXi host.