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

After installing Windows 2000 (Datacenter Server or Advanced Server) or Windows 2003, system properties shows that only around 3.37 GB of physical memory (RAM) is available for application and system use, although 4 GB or more RAM modules have been installed, and BIOS can correctly identifies the full installed size of physical memory, which means that the motherboard and x86 or x64 CPU processor can support more than 4 GB of physical memory.

32-bit Windows operating system depends on PAE (Physical Address Extension) feature to use more than 4 GB of physical memory. On most Windows 2000 and Windows Server 2003 system, especially those run in NUMA mode on a NUMA-capable computer. PAE is disabled by default. PAE is enabled by default only if DEP (Data Protection Execution) is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB.

Thus, if PAE is not enabled in Windows 2000 and Windows Server 2003 (for example, if DEP is turned off by administrator), the system may not able to detect, identify and see more than 4GB memory, and will have to allocate slightly more than 3GB of memory for system and application only as some memory address space has to be reserved and mapped for system devices and peripherals.

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:

Code:

[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:

Code:

[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 : Windows 2000 Advanced Server
Maximum memory support with PAE : 8 GB of physical RAM

Operating system : Windows 2000 Datacenter Server
Maximum memory support with PAE : 32 GB of physical RAM

Operating system : Windows XP (all versions)
Maximum memory support with PAE : 4 GB of physical RAM*

Operating system : Windows Server 2003 (and SP1), Standard Edition
Maximum memory support with PAE : 4 GB of physical RAM*

Operating system : Windows Server 2003, Enterprise Edition
Maximum memory support with PAE : 32 GB of physical RAM

Operating system : Windows Server 2003, Datacenter Edition
Maximum memory support with PAE : 64 GB of physical RAM

Operating system : Windows Server 2003 SP1, Enterprise Edition
Maximum memory support with PAE : 64 GB of physical RAM

Operating system : Windows Server 2003 SP1, Datacenter Edition
Maximum memory support with PAE : 128 GB of physical RAM

how to add /PAE in windows 2008/win 7 ?

1. Click Start- All Programs-Accesories-Commando Prompt - "Right Click-Run as administrator"
2. "Bcdedit /set PAE forceenable"
3. Restart Server


cheers!!!
Gaurang Patel

free spam filter

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

How to Disable SMB 2.0 on Windows 7/2008

How to Disable SMB 2.0 on Windows 7/2008

Server Message Blocks Protocol (SMB) is the file sharing protocol used by default on Windows-based computers. SMB 1.0 was designed for early Windows network operating systems such as Microsoft LAN Manager and Windows for Workgroups, but until Windows Server 2008 and Vista, all Microsoft-based operating systems continued to use it more or less in its original format.

SMB 2.0 was introduced in Windows Vista and Windows Server 2008. SMB 2.0 is designed for the needs of the next generation of file servers. Windows Server 2008 and Windows Vista support both SMB 1.0 and SMB 2.0 in order to preserve backward compatibility.

Some of the enhancements in SMB 2.0, include:

• Sending multiple SMB commands in the same packet which reduces the number of packets sent between a client and server
• Larger buffer sizes
• Increased scalability, including an increase in the number of concurrent open file handles on the server and the number of shares that a server can share out
• Support for Durable Handles that can withstand short network problems
• Support of Symbolic Links

Testing done with copying large files between Windows Vista and Windows Server 2008, and then Vista to Windows 2003, have shown that by using SMB 2.0 the file copying was, in averege, 2 times faster than with older operating systems.

However, while SMB 2.0 seems to do a good job if BOTH client and server OSs support it, in some cases it will slow things down. The reson for this is that the version of SMB used for file sharing is determined during the SMB session negotiation. If both the client and server support SMB 2.0, then SMB 2.0 is selected during the initial negotiation. However, if they don't both support it, SMB 1.0 will be used to in order to preserve backwards compatibility.

The SMB protocol version to be used for file operations is decided during the negotiation phase. During the negotiation phase, a Windows Vista client advertises to the server that it can understand the new SMB 2.0 protocol. If the server (Windows Server 2008 or otherwise) understands SMB 2.0, then SMB 2.0 is chosen for subsequent communication. Otherwise the client and server use SMB 1.0.

When using the terms "client" and "server" in case of file and print sharing, it does not necessarily mean that a client-type OS such as Vista "always" connects to a server-type Os such as Windows Server 2008. Sometimes, a Vista computer will connect to another Vista computer, and in that case, the computer that is "serving" the shares is considered to be the "server".

Here's how SMB is used when related to SMB versions:

• When a Windows Server 2008/Vista "client" connects to a Windows Server 2008/Vista "server", SMB 2.0 is used.
• When a Windows Server 2008/Vista "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.
• When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/Vista "server", SMB 1.0 is used.
• When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.

So, for troubleshooting purposes, mostly in an environment that has mixes operating systems, you might want to consider disabling SMB 2.0. You need to do so on both the "client" and the "server" operating systems. To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems run the following commands:

sc config lanmanworkstation depend= browser/mrxsmb10/nsi

sc config mrxsmb20 start= disabled

Note there's an extra " " (space) after the "=" sign.

To enable back SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the “client” systems run the following commands:

sc config lanmanworkstation depend= browser/mrxsmb10/mrxsmb20/nsi

sc config mrxsmb20 start= auto

Again, note there's an extra " " (space) after the "=" sign.

In order to disable SMB 2.0 on the server-side computer, follow these steps:

Warning!

This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, do not attempt these instructions. Instead, seek the help of a trained computer specialist.

1. Run "regedit" on Windows Server 2008 based computer.
2. Expand and locate the sub tree as follows.

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters

3. Add a new REG_DWORD key with the name of "Smb2" (without quotation mark)

Value name: Smb2

Value type: REG_DWORD

0 = disabled

1 = enabled

free spam filter

SQL Server 2008 installation will fail if the setup account does not have certain user rights

The following error has occurred while installing Microsoft SQL server 2008 R2.

ERROR :

Updating permission setting for folder 'C:\Program Files\Microsoft SQL Server\100\DTS\' failed. The folder permission setting were supposed to be set to 'D:(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;0x1200a9;;;BU)'.

Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

CAUSE :

above problem occured just because of your local / Domain Security policy Restrictions.

This behavior is by design. In addition to adding the user account that is running the setup as a local administrator as documented in How to: Install SQL Server 2008 (Setup), the setup user account requires the following default user rights for the setup to complete successfully.

Local Policy Object Display Name	User Right
Backup files and directories	SeBackupPrivilege
Debug Programs	SeDebugPrivilege
Manage auditing and security log	SeSecurityPrivilege

RESOLUTION :

To add the rights to the local administrator account follow these steps:

1. Log on to the computer as a user who has administrative credentials.
2. Click Start, click Run, type Control admintools , and then click OK.
3. Double-click Local Security Policy.
4. In the Local Security Settings dialog box, click Local Policies, double-click User Rights Assignment, and then double-click Backup Files and Directories.
5. In the Backup Files and Directories Properties dialog box, click Add User or Group.
6. In the Select User or Groups dialog box,type the user account being used for setup, and then click OK two times.
7. Repeat the procedure for the other two policies mentioned in the Cause section
8. On the File menu, click Exit to close the Local Security Settings dialog box. 

For more information please refer microsoft Knowledge base article : http://support.microsoft.com/kb/2000257


Cheers!!!!

Gaurang Patel

free spam filter

ERROR : reporting services catalog database file existence while installing SQL server 2008 R2

SQL Server 2008 R2 Setup shows the following error messages after running a set of rules to determine if the installation process wizard Pre-requisites check.

•  "Reporting Services Catalog Database File Existence" failed
• "Reporting Services Catalog Temporary Database File Existence" failed.

Error message when you install a SQL Server 2008 Reporting Services instance by using an instance name that you previously uninstalled: "The catalog database file exists"

CAUSE :

This issue occurs because the databases for the SQL Server 2008 Reporting Services instance that you want to install already exist on the computer with following path.

C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA


RESOLUTION :

Solution 1:

Use a different SQL instance name.

Solution 2:

Manually Remove .MDF and .LDF files from below path and Re-run Setup.
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA



Cheers!!!

Gaurang Patel

free spam filterexchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

Certain Folders are not Visible in Windows Explorer

Hellow Friends,

Last day i had a Problem with Windows Explorer due to this problem Some Folders are not visible in Windows Explorer.

My File server was 2008 R2 SP1 and accessing shared files from Windows 7 , XP and all other flavours of OS, but i was not able to access that folders.
After trouble shooting of this problem i found interesting thing, when i access folders with Full path in explorer than it was accessible, but the same folder was not accessible via Command Prompt.

I have changed Folder Option to show hidden files and Folder but the problem was still remains then after i decided to start server in safe mode and full scan with fully updated Antivirus software but problem was not resolved.

Finally i got the problem resolution with cause.

Cause :

This problem may arise due to Some system file corruption or Malicious software / Virus issues which change some system settings.

Resolution :

1) Open Command Prompt.
2) Go to your Folder Drive
3) Type Command " attrib -h -r -s /D /S < Folder Name >" or " attrib -h -r -s /D /S < *.*>"
4) hit Enter
5) Bang!!!!! now Files and Folders will appears with existing File and Folder permissions.

i also found some work around for this particular Problem.

1) http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/947489ae-dc86-45f0-ad5e-463a62e1d59f

2) http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/09bd78bf-06c3-4c85-91f7-41bc12c647bb

3) http://social.technet.microsoft.com/Forums/en-US/winserverPN/thread/f29363c6-c75b-44d0-91ce-e159063671d1

Cheers !!!

Gaurang Patel

free spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

How to change Share Point 2010 Product Key

How to Change Share Point 2010 Product Key after installation?

Hear i am going to demonstrate how to change product key of Share Point after installation.

1) Login to Central Administration Farm Portal
2) Select " Upgrade and Migration" on left pane.
3) Select Convert Farm License Type
4) Type Product Key.
5) Apply.

Note : you can upgrade server license with higher version, by using this practice server version can not be degrad.
For Example : Trial to License ( any version )
                       Standard to Enterprise.


Regards,

Gaurang Patel

free spam filter