To enable PAE in Windows Server 2003 and Windows 2000 (and Windows XP), append the /PAE switch to the end of the line of operating system in the Boot.ini file. To disable PAE, use the /NOPAE switch. The Boot.ini normally located in the root folder (i.e. C:\) with Read-Only and Hidden attributes, which are required to be removed before the file can be edited.

For example,

Original Boot.ini:

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT=”Microsoft Windows 2000 Advanced Server”
/fastdetect

Change the Boot.ini to become:

[boot loader]
timeout=0
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT=”Microsoft Windows 2000 Advanced Server”
/fastdetect /PAE

For Bootcfg command, use:

bootcfg /raw "/pae" /A /ID 1

Restart the computer after modification to make the change effective.

Note that even with PAE enabled, there is still memory limit imposed by the operating system itself. The table below list the maximum memory support with PAE enabled for Windows 2000, Windows Server 2003 and Windows XP. Most 32-bit client based Windows operating system, such as Windows XP and Windows Vista (see way to use large memory of more than 4GB in 32-bit Windows Vista), has OS level limit that restricts the maximum amount of memory able to be used to 4GB.

Operating system Maximum memory support with PAE
Windows 2000 Advanced Server 8 GB of physical RAM
Windows 2000 Datacenter Server 32 GB of physical RAM
Windows XP (all versions) 4 GB of physical RAM*
Windows Server 2003 (and SP1), Standard Edition 4 GB of physical RAM*
Windows Server 2003, Enterprise Edition 32 GB of physical RAM
Windows Server 2003, Datacenter Edition 64 GB of physical RAM
Windows Server 2003 SP1, Enterprise Edition 64 GB of physical RAM
Windows Server 2003 SP1, Datacenter Edition 128 GB of physical RAM
none

<!– /* Font Definitions */ @font-face {font-family:”Cambria Math”; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:”"; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:”Calibri”,”sans-serif”; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:”Times New Roman”; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:”Times New Roman”; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} –>

To improve the security of a Linux server, especially a web server, which is exposed to the Internet and possible worldwide hackers, it’s best to enable the server to automatically send a notification email to predefined email address anytime someone logs in as root to the host. To configure the automatic email alert notification to a default email address on each incident of root log on on the server, use the following guide.

1. Login to the server via SSH using as root ID.
2. Ensure that you’re at home directory of root. Then open up the .bash_profile for editing using pico or vi by typing one of the following commands at command shell line:

Using Pico#  pico .bash_profile
Using Nano#  nano .bash_profile
Using Vi#    vi .bash_profile

3. Scroll down to the end of the file and add the following line:

“echo ‘ALERT - echo ‘ALERT - Root Shell Access (YourserverName) :’ `date` `who` | mail -s “Alert: Root Access from `who | cut -d”(” -f2 | cut -d”)” -f1`” user@example.com” (Without the quotes)

4. Replace user@email.com with the actual email account address that you want to the root access alert notification been sent to. Note that you can change the text contains in the email alert  too. You will want to change the (YourserverName) to your actual server name or hostname.

Now logout and login again as root, you should receive an email alert at your inbox. This works on most popular flavor of Linux such as RedHat, CentOS, Ubuntu, FreeBSD , etc.

none

Sadly, migrating settings that are saved in Horde is not supported by Plesk 8 as of 8.6, and likely not in Plesk 9. However there is a way to migrate the data, however it will need to be done manually. To do so, you will need to goto the server where the information that you need to migrate is. Once there, you need to login via shell / SSH. Once logged in, we need to backup 3 things;

kronolith_events

kronolith_storage

Horde Mysql database

To do this, we need to backup the tables as such;

~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --tables kronolith_events > kronolith_events.dump
~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --tables kronolith_storage > kronolith_storage.dump

Then we need to backup the Horde database;

~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde > horde.old.dump
Now that we have the files, you will need to move them to the new server, either by ftp, wget, scp or however you move your files between your servers.
Now on the new server, make sure you make a backup of these files incase this fails;
~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde > horde.new.dump
~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --tables kronolith_events > kronolith_events.dump
~# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` horde --tables kronolith_storage > kronolith_storage.dump
Put these files in a different directory to make sure you do not get confused.
Now we can start to restore the old data by doing the following;
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` horde < kronolith_events.dump
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` horde < kronolith_storage.dump
Before you restore the Horde database, you will want to remove the existing one first and then recreate it;
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e"drop database horde"
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` -e"create database horde"
Then restore the original Horde database;
~# mysql -uadmin -p`cat /etc/psa/.psa.shadow` horde < horde.old.dump
Once you do this and restart Horde/Exim, you will have all of your contacts and settings migrated and ready to use on the new server.
*MAKE SURE YOU MAKE BACKUPS BEFORE YOU DO THIS*
none

This seems to be related to a known problem with Windows Server 2003 Service Pack 2: “The color depth is unexpectedly changed to 8-bit when a high screen-resolution setting is used in a terminal-server session that is connected to a Windows Server 2003-based computer”

Applying the hotfix from http://support.microsoft.com/kb/942610 fixes the problem.

If applying the hotfix and restarting the server still does not fix the problem, confirm if the following registry key exists on your server:

Registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
\Terminal Server
Registry entry: AllowHigherColorDepth
Type: REG_DWORD
Value: 1

If it does not exist, add it and restart the server.

none

This step-by-step article describes how to use Iisreset.exe and Task Scheduler to schedule Internet Information Services (IIS) 5.0 and 6.0 to restart.

To schedule IIS to restart on the local computer, follow these steps:

1. Click Start, point to Settings, and then click Control Panel.

2. Double-click Scheduled Tasks.

3. Double-click Add Scheduled Task, and then click Next.

4. Click Browse, navigate to the %SystemRoot%\System32 folder, click Iisreset.exe, and then click Open.

5. Either accept the default name that is displayed in the Type a name for this task box or type the name that you want to use.

6. Under Perform this task, click the interval that you want to use for this task, and then click Next.
7. If you chose to schedule a daily task, a weekly task, a monthly task, or a task that runs only one time in step 6, specify the time and the day when you want the task to run, and then click Next.

8. Type the user name and the password of a user account in which you want to run the task, and then click Next.

This account must be a member of the Administrators group. You must type the user name by using the following format, where domain is the domain name and username is the user account in which you want to schedule the task:

domain\username

9. Click to select the Open advanced properties for this task when I click Finish check box, and then click Finish.

10. Click the Task tab.

11. At the end of the command line that is displayed in the Run box, insert a space, type /restart, and then click OK.

For example, to stop and restart IIS services on the local computer, the command line that is displayed in the Run box should look similar to the following command line, where drive is the drive on which Windows is installed:

drive:\winnt\system32\iisreset.exe /restart

NOTE: You can use other Iisreset.exe parameters in combination with /restart. For example, to restart the computer if an error occurs less than one minute after the Internet services attempt to start, use the /rebootonerror parameter and the /timeout:value parameter. In this scenario, the command line that is displayed in the Run box looks similar to the following command line:
drive:\winnt\system32\iisreset.exe /restart /rebootonerror /timeout:60

Alternatively, if you want to schedule the computer to restart, use the /reboot parameter. In this scenario, the command line that is displayed in the Run box looks similar to the following command line:
drive:\winnt\system32\iisreset.exe /reboot

12. Verify that the new task is displayed in the Scheduled Tasks window, and then close the Scheduled Tasks window.

none