Archive for the ‘Windows 2003’ category

« Older Entries

How to Enable PAE in x86 32-bit Windows Server 2003 and 2000 to Use Large 4GB or More RAM Memory

March 5th, 2010

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

No comments »

Posted in Windows 2000, Windows 2003

Tags:

How to migrate Horde (Plesk) address, calendar and perferences.

June 18th, 2009

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*

No comments »

Posted in Plesk, Windows 2003, horde

Tags:

The color depth of my remote desktop session has become low (256 colors/8 bit). How can I fix this?

June 4th, 2009

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.

No comments »

Posted in Remote Desktop, Windows 2003, Windows 2008 Server

Tags:

Use Task Scheduler to restart IIS (windows 2000/2003)

December 31st, 2008

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.

No comments »

Posted in Internet Information Server 6, Windows 2003

Tags:

Installing Zend Optimzer onto a linux server

December 30th, 2008

New Page 1

To install Zend onto a Linux server, its not as complex as it may seem and

its actually pretty easy. To do so, you will first need to SSH onto the linux

server. Once you do this, simply type the following to access the root

directory;

cd /root

Now that you are in the root directly, if you type the following, it will

pull the Zend files over to the servers. This is an install hosted on this blog;

wget

http://keithdmitchell.com/downloads/zend/ZendOptimizer-3.3.3-linux-glibc23-i386.tar.gz

Now that you have this, you are ready to install Zend.

Since the file is in the root directly, you will need to type the following

to start;

tar xvfx ZendOptimizer-3.3.3-linux-glibc23-i386.tar.gz

Once that is done, you will need to goto the directly that the files are now

located, so type;

cd  ZendOptimizer-3.3.3-linux-glibc23-i386

Once you have changed directory, Make sure the install.sh file has been

created. To do this type this command:

ls -la

If you see the files, you are now ready to follow-up on the install. To start

the install process, type  the following;

./install.sh

This will start the install process and prompt you using a setup wizard. Make

you sure read and accept the license agreement (otherwise you will not be able

to install zend).

By default, zend will install to /usr/local/zend or

/usr/local/zend/etc. When it asks you if you are using a webserver,

enter yes, as you are using apache web server.

It will ask for your location of the php.ini file on your server. Depending
on

your OS and if you are running a control panel, it will end up being a different

location.

.

If you aren’t sure, then quit the install and type;

locate php.ini

This will attempt to locate the php.ini file for you. Zend will

attempt to locate it on the install process, but if it can’t, then you will need

to find the file.

Next it will ask if you are using Apache web server. Answer yes

as you are.

It will then ask for the apache control utility directory, Zend will locate
this for you.

Zend will then install, verify the install and then ask to restart the
webserver,

which you will need it to do.

Once this is done, the Zend optimizer is installed.

Congrats! You have now installed  Zend Optimizer v3.3.3.  If

you have a php test page, this will also now show;

Zend Optimizer v3.3.3, Copyright (c) 1998-2007, by Zend Technologies

No comments »

Posted in Linux, PHP, Qmail, Windows 2003, Zend Optimzer

Tags: