Sunday, 1 November 2020

This App has been blocked by your system administrator

 


Solution:

1. Go to Regedit

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

Value Name: ConsentPromptBehaviorUser

Value: 3



Friday, 24 July 2020

#WSUS - Remove WSUS completely / Reinstall WSUS with fresh data

1. Run the Powershell command below to uninstall the WSUS:-

Remove-WindowsFeature -Name UpdateServices,UpdateServices-DB,UpdateServices-RSAT,UpdateServices-API,UpdateServices-UI -IncludeManagementTools

2. Remove WSUS database.

For SQL: 

Delete the SUSDB.mdf and SUSDB_log.ldf in SQL database.

For WID (Windows Internal Database):

Delete SUSDB.mdf and SUSDB_log.ldf in C:\Windows\WID\Data.


Monday, 30 March 2020

Reset Root Account Password of VMware vCenter Server Appliance (version 5.5 and 6.0)

1. Reboot the vCenter Server Appliance from vSphere Client.

2. When GRUB bootloader appears, press the spacebar to disable the autoboot.

(You can set Power On Boot delay by edit the vm settings)

3. Press p to access the appliance boot options.

4. Enter teh GRUB password. 

(If the vCenter Server Appliance was deployed without editing the root password in the Virtual Appliance  Management Interface (VAMI), the default GRUB password is vmware. If edited, use last set password in VAMI)

5. Select the VMware vCenter Server Appliance and type e to edit the boot commands.

6. Select kernal boot parameters. (example: kernal /vmlinuz-3.0.101-0 ........... resume=/->)

7. Type e to boot the command.


8. Type init=/bin/bash to the kernal boot options. The hit enter button.

9. Type b to start the boot process.

10. Type passwd root to change the root password.

11. Enter your new root password.

12. Screen show password successfully changed.

13. Type reboot to reboot.

*if you unable to reboot run these commands:

mkinfo /dev/initctl

reboot -f

Thursday, 26 March 2020

VMware consolidation fails. Unable to access file since it is locked

Error: Unable to access file since it is locked
Error: Virtual machine disks consolidation needed.

Cause: Happen while backup running. Backup proxy server doesn't release/delete vm's snapshot properly. Vmdk file locked/used by the backup proxy server or VMware host. 

Solution Method 1: 

1. Go to backup proxy server, edit settings. Check is the vm's vmdk file attached with backup proxy server.

2. Remove the vm's vmdk from backup proxy server. (Remove only. Do Not delete from disk)



Solution Method 2:

1. SSH to VMware host.
2. Find your VM in datastore.

    cd /vmfs/volumes/your datastore name/your VM name

    (you can use Tab key to list all datastore name and VM name)
    (Use " " of \ if path with space. E.g.: cd "vmfs/volumes/datastore1/AD 1" or  cd vmfs/volumes/datastore1/AD\ 1)

3. Use vmkfstools to find the current vmdk owner.
   
    vmkfstools -D your VM name-flat.vmdk

   (you can use Tab key to list all vmdk in your VM folder)



4. Check the owner. The last part is the network MAC address. Search the MAC belong to which host. Once your manage to get it, reboot the host. (You also can kill pid command without reboot the host. Use lsof  |grep vmname command).



5. If your environment too huge with many hosts, you can try use vmfsfilelockinfo command.

    vmfsfilelockinfo -p /vmfs/volumes/your datastore name/your VM name -v your vcenter name
 






Tuesday, 26 March 2019

Set Adobe Reader as default program, override Microsoft Edge as default PDF program

Cause: legacy software installed in Windows 10 computer. 

Solution Method 1:

Uninstall the legacy software. (The most efficient way)


Solution Method 2:

1. First, set Adobe Reader as default program.


2. Export current "running default program" to xml.

    Run powershell or command prompt as administrator. Execute command below:

    Dism /Online /Export-DefaultAppAssociations:C:\TempAA.xml




3. Open the C:\TempAA.xml with notepad. Copy the contents and paste to new notepad, and name as OEMDefaultAssociations.xml 

4. Copy and replace the OEMDefaultAssociations.xml to %systemroot%\system32 (C:\windows\system32). (Do a backup before you replace the original file)

Thursday, 31 January 2019

#.net framework installation did not succeed

Installation did not succeed.
.NET Framework 4.6.2 has not been installed because:
A certificate chain could not be built to a trusted root authority.


Cause: No latest windows update.

Solution:

1. Download this cert http://www.microsoft.com/pki/certs/MicRooCerAut2011_2011_03_22.crt and install in local computer trusted root.





Hope this can solve your problem. Thank you for visit this blog.

Tuesday, 8 January 2019

#Activate Windows via Phone Windows Server 2012/2016 and Windows 10

1. From Run / Command Prompt, type slui 4.


*Other options

slui 2 = Show activation status
slui 3 = Activation via Internet
slui 4 = Activation via phone
slui 5 = Show all activation methods
slui 6 = Activation wizard
slui 7 = Simulate last day activation