Technology and troubleshooting.

Thursday, August 25, 2016

Cisco webex recorder is not opening in windows 7

This tutorial describes How to fix Cisco WebEx recorder is not opening in windows 7.

My Scenario:-
We are using Cisco WebEX recorder to capture the Screen. Its not using frequently when ever their is a need they capture desktop screen and review it later. I received call a from a user that Cisco Webex recorder app is not opening but the player is functioning fine.

Troubleshooting:-
Uninstall and reinstall the Cisco WebEx Program still same issue persist.
I realized that their is a problem with recent windows patches applied in the user machine.

Solution:-
After uninstall Windows Update KB3164035 Cisco WebEx recorder is open like a charm
For more information Visit Microsoft KB Portal

I hope this information is useful for you. Please forgive any typos or incomplete sentences.
Share:

Monday, August 22, 2016

Error: No suitable device found: no device found for connection

This tutorial describes How to fix Bringing up interface eth0:  Error: No suitable device found: no device found for connection 'System eth0'.
 




My Scenario:-

I Successfully converted my Linux Centos 6.5 physical box into virtual environment using VMware VCenter Converter standalone. After the P2V conversion all the services are running perfectly expect network adapter eth0 is not started. I realized there is some problem with network adapter.  Identified eth0 retain physical server MAC address that is the cause of the error[Error: No suitable device found: no device found for connection 'System eth0'.].

Error:-
no device found for connection System eth0
 [root@server1 ~]# service network restart
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface Auto_Ethernet:  Active connection state: activated
Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/1
                                                           [  OK  ]
Bringing up interface eth0:  Error: No suitable device found: no device found for connection 'System eth0'.
                                                           [FAILED]
Solution:-

Replace the Virtual machine MAC Address to fix Bringing up interface eth0:  Error: No suitable device found: no device found for connection 'System eth0'.

Physical server MAC:- 00:0C:29:4E:8D:DD
Virtual server MAC:-  00:0C:29:D0:C9:FE

Step #1: Command to find Physical sever MAC address:-
[root@server1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
Step #2: Command to find current Virtual server MAC address:-
[root@server1 ~]# ifconfig
 
Step #3: Command to replace the MAC address
[root@server1 ~]#sed -i "s/00:0C:29:4E:8D:DD/00:0C:29:D0:C9:FE/g" /etc/sysconfig/network-scripts/ifcfg-eth0
                                                [OR]

Manually replace the MAC address In line HWADDR replace a Virutal MAC address
[root@server1 ~]#vi /etc/sysconfig/network-scripts/ifcfg-eth0
 Before changes eth0:-

    DEVICE=eth0
    TYPE=Ethernet
    UUID=20bc39e1-d299-4a98-a4a2-4c1500c583ef
    ONBOOT=yes
    NM_CONTROLLED=yes
    BOOTPROTO=none
    IPADDR=x.x.x.x
    PREFIX=24
    GATEWAY=x.x.x.x
    DNS1=8.8.8.8
    DEFROUTE=yes
    IPV4_FAILURE_FATAL=yes
    IPV6INIT=no
    NAME="System eth0"
    HWADDR=00:0C:29:4E:8D:DD
    LAST_CONNECT=1453452600
    DNS2=8.8.4.4
    USERCTL=no

After changes eth0:-

    DEVICE=eth0
    TYPE=Ethernet
    UUID=20bc39e1-d299-4a98-a4a2-4c1500c583ef
    ONBOOT=yes
    NM_CONTROLLED=yes
    BOOTPROTO=none
    IPADDR=x.x.x.x
    PREFIX=24
    GATEWAY=x.x.x.x
    DNS1=8.8.8.8
    DEFROUTE=yes
    IPV4_FAILURE_FATAL=yes
    IPV6INIT=no
    NAME="System eth0"
    HWADDR=00:0C:29:D0:C9:FE
    LAST_CONNECT=1453452600
    DNS2=8.8.4.4
    USERCTL=no

Press ESC[Character] and then type :wq! to apply changes or Abort :q!

Step #4: Restart the Linux box and restart the network service to apply changes.
[root@server1~]# init 6
[root@server1~]# service network restart
Still if your facing the issue. Change the NM_CONTROLLED yes to no in eth0. Restart the Linux box and restart the network service. once everything is back to normal change the NM_CONTROLLED no to yes and Restart the Linux box and restart the network service.
service network restart
I hope this information is useful for you. Please forgive any typos or incomplete sentences.
Share:

Saturday, August 13, 2016

How to Switch GUI to Core and Core to GUI in Windows 2012R2 [Powershell]

This tutorial describes How to Switch Core to GUI and GUI to Core in Windows 2012R2 using Powershell.

Switch GUI to Core in Windows 2012 R2 using Powershell:-

Open > CMD > type "powershell" It will Switch to powershell terminal.
Import-Module Servermanager
Uninstall-WindowsFeature Server-GUI-Shell, Server-Gui-Mgmt-Infra -restart

Switch GUI to Core in Windows 2012 R2 using Powershell

Switch Core to GUI in Windows 2012 R2 using Powershell:-

Open > CMD > type "powershell" It will Switch to powershell terminal.
Import-Module Servermanager
Install-WindowsFeature Server-GUI-mgmt-infra, Server-GUI-Shell -restart

Switch Core to GUI in Windows 2012 R2 using Powershell

Video:-



  I hope this information is useful for you. Please forgive any typos or incomplete sentences.

Share:

Monday, August 8, 2016

VMware vCenter Converter Standalone [converter.fault.FileIOFault] Error

This tutorial describes How to fix VMware vCenter Converter Standalone errors An error occurred while opening a virtual disk. Verify that the converter server and the running source machines have a network access to the source destination ESX/Esxi hosts and converter.fault.FileIOFault.

VMware vCenter Converter Standalone

   
Our company brought a brand new VM servers and we have so many physical servers running in Linux & Windows and the virtualization task is assigned to me. 

My server details:-

Physical Server:- 
System Manufacturer: IBM
System Model: IBM eServer x3400
BIOS: Phoenix ServerBIOS 3 Release 6.1.U  
Processor: Intel(R) Xeon(R) CPU           E5405  @ 2.00GHz (8 CPUs), ~2.0GHz
Memory: 16382MB RAM  

RAID: 10
OS: Windows server (Windows Server® 2008 R2)

Virtual Server:-  
Dell R630, RAID 10

Let me move onto my scenario. I had installed VMware VCenter Converter standalone into my IBM Windows server. I open up the converter software and start up converting the job. I have passed all the stage except the last stage. I got an error "An error occurred while opening a virtual disk. Verify that the  converter server and the running source machines have a network access to the source destination ESX/Esxi hosts" I do a ping and telnet to ensure the connectivity between source machine and Destination Vcenter machine. There is no issue between source and destination ends but my ESXi hostname is not resolved. So, I've added VM Servers host entry on the windows server.

Error:-
An error occurred while opening a virtual disk. Verify that the  converter server and the running source machines have a network access to the source destination ESX/Esxi hosts
Resolution:- 
You must point the VCenter and ESXi IP address and hostname on the windows machine and converter server.

How to add the host entry in Windows
Click start > All Programs >  Accessories> Notepad.
Click File > Open. In the filename field type this path :- "C:\Windows\System32\drivers\etc\hosts"
Click Open.
Point your ESXi and Vcenter hostname with IP address

Example

192.168.2.200    Vcenter.domain
192.168.2.201    ESX-01
.domain 

Make the necessary changes to the file.
Click File > Save to save your changes.

I have successfully fix the error:- An error occurred while opening a virtual disk. Verify that the converter server and the running source machines have a network access to the source destination ESX/Esxi hosts. Again i start up the P2V conversion process i got an second error while converting the physical box. This time error is Failed: An error occurred during the conversion:'converter.fault.FileIOFault'. I tried 2-3 attempts but still the conversion process is failed and i realized there is something wrong. Finally i got a fix for this error "An error occurred while opening a virtual disk. Verify that the  converter server and the running source machines have a network access to the source destination ESX/Esxi hosts"


Error:-  converter.fault.FileIOFault

converter.fault.FileIOFault

Resolution:- 
Go habit always take a backup copy before editing anything.
Take a backup of the converter-worker.xml file. By default, this file is located at:
To disable SSL encryption:
Windows 7/Server 2008 and Later – C:\ProgramData\VMware\VMware vCenter Converter Standalone
Window Vista, XP and 2003, 2008 Server - %ALLUSERSPROFILE%\VMware\VMware vCenter Converter Standalone
In older Windows versions – %ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone
 

Open the converter-worker.xml file using a text editor(Notepad).
 Locate the tag pair <useSsl></useSsl>. It is located inside the <nfc> tag and has a value of true.
 Change the value to false.
 Save and close the file.

Before (converter-worker.xml):-

<nfc>
   <readTimeoutMs>120000</readTimeoutMs>
   <useSsl>
true</useSsl>
   <useOptimizeLazyZero>true</useOptimizeLazyZero>
   <!-- Delay is specified in milliseconds, -1 denotes the default.
   <acceptTimeoutMs>-1</acceptTimeoutMs>
   <requestTimeoutMs>-1</requestTimeoutMs>
   <readTimeoutMs>-1</readTimeoutMs>
   <writeTimeoutMs>-1</writeTimeoutMs>
   <fssrvrReqTimeoutMs>-1</fssrvrReqTimeoutMs>
   <fssrvrWriteTimeoutMs>-1</fssrvrWriteTimeoutMs>
   <maxRecvRetries>-1</maxRecvRetries>
   -->
</nfc>

Before (converter-worker.xml):-

<nfc>
   <readTimeoutMs>120000</readTimeoutMs>
   <useSsl>false</useSsl>
   <useOptimizeLazyZero>true</useOptimizeLazyZero>
   <!-- Delay is specified in milliseconds, -1 denotes the default.
   <acceptTimeoutMs>-1</acceptTimeoutMs>
   <requestTimeoutMs>-1</requestTimeoutMs>
   <readTimeoutMs>-1</readTimeoutMs>
   <writeTimeoutMs>-1</writeTimeoutMs>
   <fssrvrReqTimeoutMs>-1</fssrvrReqTimeoutMs>
   <fssrvrWriteTimeoutMs>-1</fssrvrWriteTimeoutMs>
   <maxRecvRetries>-1</maxRecvRetries>
   -->
</nfc>


 Restart the VMware vCenter Converter Standalone Worker service on the machine.


Lots of failure conversion. I have been successfully converted my Windows server (Windows Server® 2008 R2) 
 P2V_Windows_Server_2008_R2_Success
  I hope this information is useful for you. Please forgive any typos or incomplete sentences.
Share: