How to check the version of PHP ?

To verify the update is working create a simple testphp.php in your www directory with the following source code:

and open it in a web browser. The new PHP version should be reflected at the top of the page.


ssh into the server or run the follwing command in terminal

php -v

How can I downgrade my version of PHP ?

Iphp 5.3 on Fedora 17 or Redhat using atomic repo.

You will need to remove php and httpd first (not compulsory)

yum remove php
yum remove httpd

Add the following at the end of /etc/yum.conf(if required)


Install php from atomic repo

wget -q -O - | sh
yum install php

More details at

How do I restart Parallels Plesk Panel

This can be done using the following commands when logged in as root via SSH on the Parallels Plesk Panel (PP) server:

Parallels Plesk Panel for Linux:

~# /etc/init.d/psa stop
~# /etc/init.d/psa start

Parallels Plesk Panel installed on FreeBSD server in versions prior to 8.1:

~# /usr/local/psa/rc.d/psa stop
~# /usr/local/psa/rc.d/psa start

Parallels Plesk Panel on FreeBSD since version 8.1:

~# /usr/local/etc/rc.d/ stop
~# /usr/local/etc/rc.d/ start

How to correctly uninstall DrWeb antivirus

Uninstall DrWeb from my Parallels Plesk Panel server because we do not use it.


Log in to the server under root and do the following:

Remove DrWeb antivirus packages:

# rpm -e drweb-updater drweb-common drweb-bases drweb-base drweb-daemon psa-drweb-configurator

Go to Server > Server Components (or Tools & Settings > Server Components on Plesk 10.x and newer) and update list of server components to detect that Dr.Web has been removed.

After that, run forced update of mail server configuration:

# /usr/local/psa/admin/sbin/mchk --without-spam

Remove the cron entry remaining after the uninstallation:

# rm -rf /var/spool/cron/drweb
# rm -rf /etc/cron.daily/drweb-update

Discontinue monitoring of the service by Watchdog:

/usr/local/psa/admin/bin/modules/watchdog/wd --unmonit-service=drweb

Local Group Policy deployment for non domain computers

How to create a local policy and deploy it to non-domain computers

1. Create local group policy
a. run mmc
b. add group policy object editor snap in with the local computer as policy object
c. add necessary administrative templates
d. define settings
e. close the policy object editor as to create, save and apply the policy to the local computer

2. Copy local policy
the created local group policy is to be found under:
%windir%\system32\group policy\
(this is by default a hidden folder)

copy the group policy folder with all subfolders and files in it

paste it into the same place on the computer you want to have these settings applied to

the policy will take effect on next restart

keep in mind that the local policy is the first to be applied so it is overwritten by any other policies that may be defined for this machine

3. Remove policy
if the policy is no longer necessary it is not enough to remove or delete the Group Policy folder as the settings are retained in the windows registry

if you know what the settings are then you can edit them into whatever value is required

otherwise run the local group policy object editor again (as in step 1) and reset all settings back to NOT CONFIGURED

restart the workstation and check to see if the settings are returned to their defaults

How to Export Local Group Policy Settings Made In gpedit.msc.

To export group policy you made in on a machine with the Local Group Policy Editor (gpedit.msc) to other machines follow following steps.

1.) Open %systemroot%\system32\grouppolicy\

Within this folder, there are two folders – “machine” and “user”. Copy these to folders to the “%systemroot%\system32\grouppolicy – folder on the target machine. All it needs now is a reboot or a “gpupdate /force”.

Note: If you cannot see the “grouppolicy” folder on either the source or the target machine, be sure to have your explorer folder options set to “Show hidden files and folders”…

For security settings:

1.) Open MMC and add the Snapin “Security Templates”.

2.) Create your own customized template and save it as an “*inf” file.

3.) Copy the file to the target machine and import it via command line tool “secedit”:

secedit /configure /db %temp%\temp.sdb /cfg yourcreated.inf