Tech Blog

Please stop the Probe service and go to Probe\bin folder and execute > startdms.bat and check if the probe starts properly or not.Please check what error you get here ? Also, if there is a DBServer FAILED error, please execute the RepairDB.bat from the Probe\bin folder and then try to start the probe from command prompt

Changing the IP address of service console in ESX 3.x Damian Murdoch comes through again, this time, helping us change the IP address of the service console in VMware's ESX Server 3.x. If you want to change the IP address of the service console in ESX 3.x you can using a command in the service console. To change the IP address of the ESX 3.x host, you need to change the configuration of the vswif. By default this is vswif0 and this is assumed in this document. Login to the service console with root permissions, either by using root or doing a su - to get the permissions. Once in the service console runt the command "esxcfg-vswif -d vswif0". This command deletes the existing vswif0. Don't worry if you get a message about nothing to flush. Then you need to run the command to change the ip address, subnet mask and broadcast address. They are also specified in that order when the command is given. An example command is below. "esxcfg-vswif -a vswif0 -p Service\ Conso...

step by step anleitung. Funktioniert bestens http://vmprofessional.com/index.php?content=2k3resize

Method 2 – Using Vmware Converter (http://www.vmware.com/download/converter/) to shrink or extend a disk When you use Converter to copy a VM it will transfer the data to the destination server by one of two ways. If you do not change the disk size or increase the size of your original disks then it does a block level clone of the drive. If you reduce the size of your original disks it instead does a file level clone of the drive. • Download and install Converter on the VM that you want to resize the drives, reboot after the install completes • Start Converter application, click the Import Machine button • Click Next at the Welcome screen and then Next again at the Source screen • Select ‘Physical Computer’ and click Next o Select “This Local Machine” and click Next • At the Source Data screen select your volumes and change “Maintain Size” to “Type Size in GB” and enter your new disk size and click Next • At the Destination screen click Next • Select “Import this machine to a Vmware ESX...

SSH Security SSH is a commonly used UNIX and Linux command shell that lets you remotely log in to the service console and perform certain management and configuration tasks for ESX Server 3. SSH is used for secure logins and data transfers because it offers stronger protection than other command shells. In this ESX Server 3 release, the SSH configuration is enhanced to provide a higher security level. Key features of this enhancement include: Version 1 SSH protocol disabled – VMware no longer supports Version 1 SSH protocol and uses Version 2 protocol exclusively. Version 2 eliminates certain security issues present in Version 1 and provides you with a safer communications interface to the service console. Improved cipher strength – SSH now supports only 256‐bit and 128‐bit AES ciphers for your connections. Limits on remote logins as root – You can no longer remotely log in as root. Instead, you log in as an identifiable user and either use the sudo command to execute specific opera...

Please stop the Probe service and go to Probe\bin folder and execute > startdms.bat and let me know if the probe starts properly or not.Please check what error you get here ? Also, if there is a DBServer FAILED error, please execute the RepairDB.bat from the Probe\bin folder and then try to start the probe from command prompt and let me know the response.

die Probe des opmanager msp edition konnte den zentralen Server nicht finden. Das Problem war, dass im automatisch generierten ZIP File der ServerName des Central Servers hinterlegt ist. Dieser ist aber meist nicht verwendebar, da der zentrale Server beim Service Provider steht. Das File .\AdventNet\ME\probe\conf\NOCServerDetails.xml muss wie unter beschrieben angepasst werden, dann funktioniert die Verbindung. (Vorausgesetzt sind natürlich auch entsprechend offere Ports) NOCServerName=" SERVERNAME.DOMAIN.CH" NOCServerPort="443" DMSID="RICHTIGEID"