vmware: pulizia del sistema a seguito incompleta disinstallazione

Tutorial in lingua inglese per la rimozione di installazione non corretta, dei sistemi vmware . Tale procedura, seguita passo passo, permette la rimozione del prodotto e la possibile re-installazione di una nuova versione , nel ns. caso di VMWare 1.6.0

Cleaning Up After Incomplete Uninstallation on a Windows Host

To troubleshoot an incomplete installation:

1. Be a Local Administrator. Make sure you are logged onto the Windows host as a Local Administrator. (A Domain Administrator imposes the wrong permissions on components the installer must access.)

2. Disable firewalls on protected systems. If your security policy allows this, disable any firewall software you have installed. Some firewalls can interfere with the installation process.

3. Uninstall using Add/Remove Programs > Remove. If the VMware product is still listed in Add/Remove Programs, try rebooting and uninstalling the VMware product:
   a. Reboot the Windows host.
   b. From the Control Panel, select Add/Remove Programs.
   c. Select the VMware product in the list.
   d. Click Remove.
   e. Reboot the Windows host again.
   f. Reinstall the VMware software.

4. Run the VMware registry cleaner script.
   Remember to run this script and the installer when you are logged on as a member of the Local Administrators group.
   The registry cleaner utility removes all registry keys used by the installers for Workstation 3.1, Workstation 3.2, Workstation 4.x, Workstation 5.x, Workstation 6.x, GSX Server 2.x, GSX Server 3.0, GSX Server 3.1, ACE Manager 1.0, ACE 1.0, VmPerl 2.0, VmPerl 3.0, VmCOM 2.0, and VmCOM 3.0.
   If you are running the Workstation 5.x or 6.x installer. Run the installer command with the /c switch, which automatically removes the MSI installer registration information for VMware Workstation.
   VMware-workstation-<version>.exe /c
   For example:
   VMware-workstation-5.0.0-13124.exe /c VMware-workstation-5.5.0-18463.exe /c

5. Reboot. After you run the cleaner script or the installer, reboot. It’s a good idea to reboot after you install or uninstall any programs on your system, and after you run any other programs that make changes to the registry.

6. Try the Microsoft CleanUp utility.
   If this previous steps prove unsuccessful, you might find a utility provided by Microsoft helpful. You can find instructions and a link to the utility in Microsoft knowledge base article 290301 at http://support.microsoft.com/default.aspx?scid=kb;en-us;290301.

7. Clean the registry manually.  See the following section.

Manually Cleaning the Registry

Caution: This procedure involves modifying the registry. Incorrect changes to the registry can leave your system unstable or unable to run. Always back up the registry before editing it, and exercise caution in making changes to the registry. VMware takes no responsibility for problems that might arise.

1. Log onto the Windows host system as the Local Administrator or a member of the Local Administrators group.

2. Stop the following services on the Windows host:
   - VMware Authentication Service
   - VMware Registration Service
   - VMware DHCP Service
   - VMware NAT Service

3. Uninstall the VMware network bridge adapter.
   a. Choose Start > Settings > Network and Dial-up Connections.
   b. Right-click any network adapter icon and choose Properties.
   c. Select VMware Bridge Protocol and click Uninstall.

4. Uninstall all VMware devices.
   a. Right-click My Computer and choose Manage.
   b. Click Device Manager.
   c. Double-click Network Adapters.
   d. Right-click each adapter whose name begins with VMware and choose Uninstall.
   e. Choose Show hidden devices from the View menu.
   f. Double-click Non-Plug and Play Drivers.
   g. Right-click the following devices and choose Uninstall.
   - hcmon
   - VMware Network Application Interface
   - VMparport
   - vmx86
   - VMware Bridge Protocol

5. Delete the program folder in which the VMware product was installed. The default installation directory is C:\Program Files\VMware\. (The drive letter is different if your Program Files folder is on a different drive.) If you have installed only one VMware product, you can delete the entire VMware folder; if you have installed other products, such as VirtualCenter Client, delete only the relevant subfolders for the product you are trying to remove. On a GSX Server machine, you should remove the subfolders for VMware GSX Server, VMware Management Interface, VMware Scripting API, and either VMware Virtual Machine Console or VMware Remote Console.
   Note: If you have stored virtual machines in a folder under the program folder and want to save them, move them to a different folder before you delete the VMware program folder.

6. Delete the application data folder. The default locations are C:\Documents and Settings\All Users\Application Data\VMware\ and C:\Documents and Settings\<username>\Application Data\VMware. If you have installed only one VMware product, you can delete the entire VMware folder; if you have installed other products, such as VirtualCenter Client, delete only the relevant subfolders for the product you are trying to remove. On a GSX Server machine, you should remove the subfolders for VMware GSX Server, VMware Management Interface, VMware Scripting API, and either VMware Virtual Machine Console or VMware Remote Console.

7. Delete the VMware program group folder. The default location is C:\Documents and Settings\All Users\Start Menu\Programs\VMware\. If you have installed only one VMware product, you can delete the entire VMware folder; if you have installed other products, such as VirtualCenter Client, delete only the relevant subfolders for the product you are trying to remove. On a GSX Server machine, you should remove the subfolders for VMware GSX Server, VMware Management Interface, VMware Scripting API, and either VMware Virtual Machine Console or VMware Remote Console.

8. Delete the VMware shortcut icons from the desktop.

9. Delete the files below from the Windows system folder. (Not all systems have all of these files installed.)
   %SystemDrive%\WINNT\system32\vmnat.exe
   %SystemDrive%\WINNT\system32\vmnetbridge.exe
   %SystemDrive%\WINNT\system32\vmnetdhcp.conf
   %SystemDrive%\WINNT\system32\VMNetDHCP.exe
   %SystemDrive%\WINNT\system32\vmnetdhcp.leases
   %SystemDrive%\WINNT\system32\vmnetnat.conf
   %SystemDrive%\WINNT\system32\vmxw2ksetup.dll
   %SystemDrive%\WINNT\system32\vnetprobe.exe
   %SystemDrive%\WINNT\system32\vnetprobelib.dll
   %SystemDrive%\WINNT\system32\vnetinst.dll
   %SystemDrive%\WINNT\system32\vnetlib.dll
   %SystemDrive%\WINNT\system32\vnetlib.exe
   %SystemDrive%\WINNT\system32\drivers\vmnet.sys
   %SystemDrive%\WINNT\system32\drivers\vmnetx.sys
   %SystemDrive%\WINNT\system32\drivers\VMparport.sys
   %SystemDrive%\WINNT\system32\drivers\vmx86.sys
   %SystemDrive%\WINNT\system32\drivers\vmnetadapter.sys
   %SystemDrive%\WINNT\system32\drivers\vmnetbridge.sys
   %SystemDrive%\WINNT\system32\drivers\vmnetuserif.sys
   %SystemDrive%\WINNT\system32\drivers\hcmon.sys
   %SystemDrive%\WINNT\system32\drivers\vmusb.sys
   

10. Delete the __vmware_user__ local user and the __vmware__ local group from the Windows system if they exist.

11. Reboot the Windows host system.

ref http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1308

Tags: ADM, GO, installazione, on, procedura, server, sistema, the, VISTA, VmWare, WIN

Related posts

• Installare vmware ESX 4.0: istruzione passo-passo (0)
• vmware esx: migrazione (0)
• installare VMware vCenter (0)
• Installare VMWare su un server con sistema operativo LINUX – istruzioni passo-passo. (0)
• Tivoli Storage Manager: migrazione dalla versione V5R2 level 0.0 a V5R4 ( appunti ) (0)

Sistema Centralizzato per la gestione delle risorse

Hai mai pensato alla possibilità di accentrare le risorse aziendali: file/dati, programmi, applicazioni, mail, stampanti ecc. tutte  su un’unica macchina ( server ) , che si occuperà di distribuirle sulla rete di pc azienda o su rete remota ?

In questo contesto, l’apertura di una nuova filiale, avviando semplicemente la comunicazione tra il Computer del nuovo utente (sede) e il server, oppure , l’accesso alla registrazione dei documenti di trasporto, di un ipotetico magazziniere, dislocato a diversi Km di distanza dalla sede principale. Rappresentano solo alcuni degli scenari possibili.  In tale situazione veniamo a parlare di infrastrutture Terminal Server, opportunamente integrate con sistemi di sicurezza del traffico dati e inserite in ambiti Vpn .

 

Nell’ottica dello scenario ora esposto, possiamo parlare anche di sistemi per il TELELAVORO.

Esistono due differenti approcci alla questione, che SECOFORMA, propone ai propri clienti: la prima è una soluzione Windows , l’altra Open Source .

Windows: nel contesto di Windows terminal server , il sistema è costituito da un server dalle caratteristiche HARDWARE importanti ( 3 dischi raid , 4 gb ram lmeno ) , con unità nastro per il backup giornaliero dei dati. L’ applicazione sulla quale viene strutturato l’ambiente, è un sistema Windows 2003 server, con LICENZE TERMINAL SERVER opportunamente configurate. Gli user’s si loggano sulla macchina server,  utilizzando il protocollo rdp ( remote desktop ), normalmente presente in ogni sistema operativo e di qui accederanno al loro ambiente di lavoro . L’ambiente di lavoro è a tutti gli effetti il medesimo in uso all’utente standard di windows. Applicativi per l’ufficio ( word,Excel,PowerPoint ), Client Access per la comunicazione e l’interazione con l’ As400, stampanti di rete e  tutte quelle condivise dagli utenti nella rete, Outlook 2003 per il download di posta elettronica ( dal server di posta aziendale o in pop dal web ).

 

La comunicazione dei pc verso il server, verrà garantita attraverso una rete LAN opportunamente bilanciata per supportare il traffico di dati. Si tratta di definire una rete con switch e schede di rete , che supportino preferibilmente UN TRAFFICO LAN a gb PIU’ cavi in cat. 6. Lo scopo di tale soluzione permette di non creare situazioni di “ imbuto “ sulla RETE dei pc.

L’accesso remoto, dei pc verso il server aziendale, puo’ avvenire attraverso sistemi  vpn. Apparati router firewall cisco system, offrono soluzioni di accesso remoto sicure e flessibili. Avviato il client cisco di comunicazione verso la rete locale, il pc remoto avrà da aprire l’rdp e dopo essersi opportunamente loggato potrà accedere alle risorse. La connessione remota potrà altresi avvenire pubbliccando la porta 3389 del Terminal server , in DMZ, opportunamente “ nattato “ su ip pubblico.

Per informazioni approfondite sul servizio Terminal server , Remote desktop, implementazioni con sistemi aperti, scrivi a Secoforma, utilizzando l’apposito form.

Posted By SECOFORMA.

Tags: as400, caratteri, client access, CREARE, GO, hardware, isc, Linux, macchina, on, operativo, pc, rete, server, Sicurezza, sistema, Telelavoro, verona, vpn, WIN

Related posts

• Installare vmware ESX 4.0: istruzione passo-passo (0)
• Consulenza & Web (0)
• vmware esx: migrazione (0)
• Tivoli Storage Manager: migrazione dalla versione V5R2 level 0.0 a V5R4 ( appunti ) (0)
• Lezione di Informatica: menu’ start ( 2.1 ) (0)

Pagina successiva »