#Windows cannot verify the digital signature for this file.

Error:

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damage, or that might be malicious software from an unknown source.

Solution 1:
1. Restart computer and boot into Advanced Boot Options.
(For Windows 7 press F8. For Windows 8 and 10, hold the Shift key and press restart)

2. Select Disable Driver Signature Enforcement

Windows 7

Windows 8/10

 

#Increasing the disk space for the VMware vCenter Server Appliance in vSphere 6.0

1. Open console from vCenter Server. (You also can use SSH to connect)

2. Press Alt+F1 switch to console mode. (To switch back normal mode, press Alt+F2)
3. Enter username and password.

4. Use command below to enable Bash Shell.
    shell.set --enabled true

5. Use the command below to enter Shell mode.
    shell

6. Use the command below to list the disk space
    df -h
 

Example: If  /dev/mapper/log_vg-log  in low disk space,  I going to increase the disk.

7. Use the command below to list the disk partition.
     lsblk

 Example: log_vg-log is under sde partition.

8. Use the command below to identify the disk controller.
     lsscsi

Example: sde in under 0:4 disk controller.

9. Use the vSphere Client or vSphere Web Client to increase the VM disk.
 
Example: 0:4 disk controller is Hard disk 5. (Hard disk 5 = /dev/mapper/log_vg-log)

 10. Use the command below to extend the newly added disk space.
       vpxd_servicecfg storage lvm autogrow
       
       If successful, result will show VC_CFG_RESULT=0

 11. Use the command below to check the disk space.
      df -h

Example: /dev/mapper/log_vg-log successful increase to 15GB.

#SCCM 2012R2 - Determine SCCM 2012 CU version

1. Launch registry, navigate HKLM\Software\Microsoft\SMS\Setup
2. On right panel, check on CULevel.

or Power Shell 

• Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\SMS\Setup -Name "CULevel"

CULevel value is (0). Mean no CU installed.

#SCCM 2012R2 - Software Update Point unable to connect WSUS

Error: System.Net.WebException: The request failed with HTTP status 404: Not Found.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)

Event ID: 6703

1. Verify the WsusPool is Started. (Under Application Pools)

2. Verify WSUS port number correct. 

Default port for WSUS Windows 2012, 8530

Default port for WSUS Windows 2008, 80

  

#SCCM 2012R2 - Software Update Manager unable to update

Event Error: 6703

Configuration Manager Trace Log:

Sync failed: WSUS update source not found on site XX. Please refer to WCM.log for configuration error details.

Solution:

1. Verify WSUS Server Connection Account with correct credential.

2. To verify, open Configuration Manager, Administration > Servers and Site System Roles, select the site server with SUP role, right click on SUP role, select properties.

3. Launch Widows Server Update Services, under options select WSUS Server Configuration Wizard.

4. Reconfigure and start connecting as below. This may take few minutes to hours. Be patient. If this screen stop for long time, you may restart the server and re-launch the WSUS Wizard again.  

#Exchange 2013 - Exchange server exist in AD schema

Error: The Exchange Server is in an inconsistent state. Only disaster recovery mode is available. Please use Setup /,:RecoveryServer to recover this Exchange server.

Solution:

1. Log in to AD. Open ADSI Edit, connect AD with configuration.

2. Navigate to Configuration[Domain name] --> CN=Configuration,DC=Domain name,DC=Domain name --> CN=services --> CN=Microsoft Exchange --> CN=Domain name --> CN=Administrative Groups --> CN=Exchange Administrative Group --> CN=Servers.

3. Delete the exchange server with the error above. (example: CN=DO-EXCH)

#Web application proxy - ADFS Proxy unable to connect second ADFS Proxy server

Enter credential adfs proxy fail.

Ensure that remote management is enabled on the selected server, and then enter the name and password of an account that has administrator rights on that server. For example, user@example.contoso.com or domain\user name.  

Solution:

1. Add 2nd proxy server to 1st proxy server in server manager.

Follow here