Suse / timezone turkey +03

servername:~ # date
Sat Mar 18 01:40:53 EET 2017

servername:/tmp/time # zypper install timezone-2016g-0.60.1.x86_64.rpm
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following package is going to be upgraded:
  timezone

The following package is not supported by its vendor:
  timezone

1 package to upgrade.
Overall download size: 354.4 KiB. Already cached: 0 B. After the operation,
additional 1.3 KiB will be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package timezone-2016g-0.60.1.x86_64                        (1/1), 354.4 KiB (  1.2 MiB unpacked)
Checking for file conflicts: .........................................................................[done]
(1/1) Installing: timezone-2016g-0.60.1.x86_64 .......................................................[done]
servername:/tmp/time # date
Sat Mar 18 02:42:30 +03 2017
servername:/tmp/time #

Get-DhcpServerv4Scope

$dateEnd = get-date

$filename = get-date $dateEnd -Format yyyyMMdd-hhmm


Get-DhcpServerv4Scope -ComputerName servername1 | Get-DhcpServerv4Reservation -ComputerName servername1 > C:\DHCPLOG\dhcp_reservation_"$filename".csv

Get-DhcpServerv4Scope -ComputerName servername2 | Get-DhcpServerv4Reservation -ComputerName servername2 >> C:\DHCPLOG\dhcp_reservation_"$filename".csv

Install failover cluster feature using powershell

PS C:\> Install-WindowsFeature -Name Failover-Clustering –IncludeManagementTools

Success Restart Needed Exit Code      Feature Result

------- -------------- ---------      --------------

True    Yes            SuccessRest... {Failover Clustering, Failover Clustering ...

WARNING: You must restart this server to finish the installation process.

PS C:\>

Deploying agent using PsExec utility

Deploying agent using PsExec utility

Steps to install the agent using psexec utility:

Create a network share (eg. \\MyServer\MyShare).

Download the agent and save it in the created network share.
Download the PsTools and install it in one of the Windows machine.
Open a command prompt and navigate to the directory where the PsTools is installed
Create a text file and enter name of device line by line in the file.
Execute the below command to install the agent on each computer listed in the file.

psexec.exe @<file name> -u <domain name\user name> -p <password> msiexec /i <msi file name>

For eg: psexec.exe @ComputersList.txt -u WORKGROUP\administrator -p password msiexec /i "\\assetexplorer\msi\ManageEngineAssetExplorerAgent.msi"

Unregister vSphere Replication from vCenter Server if the Appliance Was Deleted

Unregister vSphere Replication from vCenter Server if the Appliance Was Deleted

If the vSphere Replication appliance virtual machine does not exist because it was deleted, you cannot use the virtual appliance management interface (VAMI) to unregister vSphere Replication from vCenter Server. Instead, you can use the Managed Object Browser (MOB) to delete the vSphere Replication extension.

Prerequisites

Log in to https://<vCenter_Server_address>/mob/?moid=ExtensionManager with vCenter Server credentials.

Procedure

1. In the extensionList property, click the corresponding link for the com.vmware.vcHms extension key to check the key details.
2. Verify that the displayed data is for a vSphere Replication appliance that is already lost.
3. In ExtensionManager, click unregisterExtension.
4. Type com.vmware.vcHms for the extension key value, and click Invoke Method.
5. Verify that the result displays void and not an error message.

An error message might appear if the specified extension is not registered, or if an unexpected runtime error occurs.

     

     6.Close the window.

   
     7. Refresh the ExtensionManager page and verify that the extensionList entry does not include com.vmware.vcHms.

https://pubs.vmware.com/srm-55/index.jsp#com.vmware.srm.install_config.doc/GUID-8110B494-53FC-4B82-8953-1C3E57933909.html