Category: How To

When you have updated your ESXi to newer version or patch it but you have some problems with new ESXi, you can revert to previous version easily: Note: Back up your configuration data before making any changes. Further Reading VMware Horizon View Connection (Session) Duration Report vSphere 7 Upgrade Series – Part 2: Hardware Compatibility vSphere 7 Upgrade Series – Part 1: Define Upgrade Path

It’s possible to reset your Windows Sever 2008 / R2 Domain Controller administrator password using your installation CD. Restart your Windows server 2008 DC with the installation CD Choose your language and click next Select your partition and installation version and click Next Click on Command Line Prompt Change directory to the access the system 32 directory. Then your original C:drive is changed to D: or E: depending on the number of drive and partitions you have on that system. Rename the file Utilman.exe to Utilman.exe.bak using the comm and Copy Utilman.exe Utilman.exe.bak.   Using Command Move Cmd.exe Utilman.exe to move CMD.exe file into Utilman.exe. Press O or Y to accept after that restart your Computer normaly   At the user logon screen, press a combination of Windows KEY+U, then the CMD.exe will appear. Type net user “Username””new password”;   Then your system Admin Password is reset. Please don’t forget to rename back Utilman. Exe ->Cmd.exe and Utilman.exe.bak-> Utilman.exe after getting back access.

We have a support team that they need to our assistance about adding their accounts to local administrators group of some computers. My colleagues have to open “Computer Management”, connect to remote computer and add the user to the group. I don’t like this process. The below script helps my colleagues, maybe useful for you as well: Further Reading Run ESXi Commands Via PowerShell And SSH Windows 7 USB Sound Problem On PCoIP How to change the listening port for Remote Desktop

I have to using VPN in my office for connecting to some services and add some routes to my Ubuntu routing table. But the routes will be removed after reboot. So I have to add them manually again. I googled that and find a solution for adding the routes when interface is coming up. You need to create a script under “/etc/network/if-up.d/”, for creating the script, follow the below steps: 1. Create script file by using “cat” command or other text editors: #cat > your-script-file #!/bin/bash route add -net x.x.x.x netmask x.x.x.x gw x.x.x.x route … route … CTRL+D (For saving file) Make the script file as an executable script file: #chmod +x your-script-file Then restart networking service or unplug and plug your network and run “route -n”. If the routes network are available, then the routes will be added to routing table. Note: You script should be saved without “.sh”. I tested it on Ubuntu 14.04. Run the below command for test: run-parts –test /etc/network/if-up.d

This script can help you to clean your users profiles without installing any third party application, you can put it as shutdown or startup script: If you want to run it as scheduled task, you need to run that via batch file with a local administrator account. This batch file create a local administrator account, run the previous script under the user’s privilege and then remove the user. The scripts tested under Windows XP and Windows 7. Further Reading Veeam Backup & Replication – Re-IP Rule on Linux VM Recommended Settings on Windows 10 for VDI

Start Registry Editor. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber On the Edit menu, click Modify, and then click Decimal. Type the new port number, and then click OK. Quit Registry Editor. Restart the computer. Note When you try to connect to this computer by using the Remote Desktop connection, you must type the new port. Maybe you have to set the firewall to allow the new port number before you connect to this computer by using the Remote Desktop connection.

I’m working on a solution that it needs to edit something on virtual machine vmx file. But as you know, vmx file should be removed and re-add from vCenter inventory for apply new configurations. This process is very simple but you have to find your virtual machine datastore and remove the virtual machine from inventory and re-add that again. There is a way for reloading your vmx file without do the above process from ESX/ESXi command line (Tech Support Mode). To reload the virtual machine configuration .vmx file on an ESXi/ESX host from the command line: Log in to the Local Tech Support Mode console of the ESXi/ESX host. Obtain the Inventory ID (Vmid) for the virtual machine by running the command:# vim-cmd vmsvc/getallvmsThe output shows virtual machines which are registered on the ESXi/ESX host. Example output: Vmid   Name                          File                Guest OS                 Version     Annotation 2848   Win2003_storage_performance   [local] Win .vmx    winNetEnterpriseGuest    vmx-07      To be used as a template In this example, the Vmid is 2848. Reload the virtual machine configuration .vmx file...

Finally, Windows 8.1 preview is released on last month and we can test it in our virtual platforms. I want to deploy Windows 8.1 for our Call Center users because Windows 8 has lower IOPS compare to Windows 7. Also it has very faster start-up compare to earlier versions. I had poor performance with USB controller on this version of Windows. xHCI controller (USB 3.0) is default controller for Windows 8. I found solution on VMware KB2057809 and if you are facing with same issue, You should remove current controller and replace it with  EHCI+UHCI controller.

Streaming Application You may get this error when trying to scan a streaming application and the View Connection Server logs may report these errors: 12:35:31,020 ERROR <MessageFrameWorkDispatch> [ws_thinappmgmt] OpenPackage failed, path = \\thinappserver\ThinAppStore\WinSCP\WinSCP.msi. Error details. HRESULT hr = 0x8c420002. Internal error: unable to create API object 12:35:31,022 INFO <TP-Processor1> [ThinAppMSIManager] Application MSI with path:\\thinappserver\ThinAppStore\WinSCP\WinSCP.msi skipped. Reason:Error details. HRESULT hr = 0x8c420002. Internal error: unable to create API object   This issue occurs if all package components are not available during the scanning.   To resolve this issue, confirm that in addition to the application’s .msi file, the directory where the .msi file is located contains all associated .exe and .dat files that were created during the build process. A streaming application has an .msi and an .exe file. If the .exe file is not present the application was not captured with streaming activated, rebuild the application with the MSIStreaming paramater’s value set to 1 in the package.ini file located at the project directory when the package is built. Full Assignment Application If this is Full Assignment application and all the files from the package is in the thinapp repository folder and the logs on the View Connection Server is showing...

Problem ========= Windows 2003/Event 3083 window search Mapi2Handler.1 cannot be loaded EventID:3083 Category: Gatherer Description:The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered Desktop Search Version 4 Analyze ======== The background on this issue is that there are two processes that can index on 64-bit machines. One process is 64-bit and can load 64-bit protocol handlers and the other is a 32-bit process, which can load 32-bit protocol handlers. In this case, since mapi (which is used to index outlook email) is 32-bit only when the 64-bit protocol handler process starts it tries to load the 64-bit version of the non-existent mapi protocol handler. It should call into the WOW64-32 layer to determine that this handler is correctly registered in the other CLSID hive and not display the error. For some reason this check is not passing most likely due to some incompatible vista only flag we are using when calling to WOW64.32 bit applications use [HKEY_CLASSES_ROOT\Wow6432Node\CLSID64 bit applications use [HKEY_CLASSES_ROOT\CLSID Solution Remove Windows Desktop Search or add the following registry entry ===== Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\CLSID{9E175BAF-F52A-11D8-B9A5-505054503030}] @=”Windows Search Service Office Outlook Protocol Handler” [HKEY_CLASSES_ROOT\CLSID{9E175BAF-F52A-11D8-B9A5-505054503030}\InprocServer32] @=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,74,00,25,\ 00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,73,00,\ 73,00,70,00,68,00,2e,00,64,00,6c,00,6c,00,00,00 “ThreadingModel”=”Both” [HKEY_CLASSES_ROOT\CLSID{9E175BAF-F52A-11D8-B9A5-505054503030}\ProgID] @=”Search.MAPI2Handler.1″ [HKEY_CLASSES_ROOT\CLSID{9E175BAF-F52A-11D8-B9A5-505054503030}\VersionIndependentProgID] @=”Search.MAPI2Handler” =====