I believed most of the Windows System Admin will noticed that server time on the new fresh installed Windows is not correct.
As a Windows System Admin, first thing you should do is change the server time zone and sync the server time to internet time server.
Recently, i get complain from customer reported that the server time is incorrect. Even we advise them to sync the server time to internet time server, but they still do not understand to do that.
As for information, Microsoft does not enable NTP time sync by default. You can very easily manually enable it using the Windows Time Service, which supports time synchronisation from an NTP time server.
Here i going to share some of the simple command to sync NTP in Windows Server 2012.
A) Manual Sync NTP server
w32tm /config /manualpeerlist:IP Address or NTP Server /syncfromflags:manual /reliable:yes /update
B) Start Windows Time Service
net start w32time
C) Stop Windows Time Service
net stop w32time
D) Resync Time
Step1: Run Command Prompt as Administrator or Run Windows PowerShell. In this example, i going to use Windows PowerShell Continue reading
In some situation, you may experience your mailbox will get full of used or unused email. To remove email in inbox, it will take long time to do it in Zimbra GUI. Refer to example to below screenshot, i have more than 68000 email in my inbox.
To empty the inbox email, it can be done it via CLI. Below is the command to remove all the inbox message for the particular email account
[root@mail ~]# su – zimbra
[zimbra@mail ~]$ zmmailbox -z -m firstname.lastname@example.org emptyFolder /Inbox
Once above command been execute, it took less than 1 minute to remove 68000 email from the inbox
Error Message “Existing lock /var/run/yum.pid: another copy is running as pid xxxx.” is a very common error which you might come across in Red Hat Linux distro while trying to run yum command.
As you see the error from above screenshot, it mentioned that yum command is locked by another application. Meaning that someone already run the yum command and the process is running.
To find out which process and user holding the yum lock, just enter following command:-
From the above screenshot, PID 11290 is currently run by root user and holding the yum lock.
It is very easy to solve this issue, first wait the process finished. Second is kill the process ID. Below is the command to kill the PID
kill -9 11290
Now you should able to use yum command.