Showing posts with label 2003. Show all posts
Showing posts with label 2003. Show all posts

Wednesday, June 20, 2012

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

Wednesday, May 2, 2012

Windows Deployment Service Fail to start in 2003 and 2008 with SCCM

Windows Deployment Service Fail to start in 2003 and 2008 with SCCM.

I have a Windows 2008 Server that has WDS + SCCM 2007 R3 installed.  The Windows
Deployment Services Server Service isn't started and when I try to
Start  it I got a message that says:

Windows could not Start the Widows Deployment Services Server on Local
Computer.  For more information, review the System Event Log.  If this
is a non-Microsoft service, contact the service vendor, and refer to

server-specific error code 2310.
Event viewer lists Event ID 257 and this:
An error occurred while trying to Start the Windows Deployment Services
server.
 Error Information: 0x906
  
Hear is the Problem Analysis and Resolution of below errors.

CAUSE :

This problem occurs because the location of the computer object that is running WDS has changed in the Active Directory directory service.

A Windows Deployment Services (WDS) server is running Microsoft Windows Server 2003 with Service Pack 1 (SP1) or Microsoft Windows Server 2003 with Service Pack 2 (SP2). If you move the WDS server to a different organizational unit, the WDS server may not start. Additionally, one of the following error messages may be logged in the System log on the WDS server:

Error Messages :

Error message 1
Type: Error
Event ID: 7024 Source: Service Control Manager
Description: The Windows Deployment Services Server service terminated with service-specific error 9 (0x 3).
exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter Error message 2
Type: Error
Event ID: 7024 Source: Service Control Manager
Description: The Windows Deployment Services Server service terminated with service-specific error 19 (0x13)
One of the following groups of error messages may also be logged in the Application log:

Error message group 1

Type: Error
Event ID: 261
Source: WDSPXE
Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x 3

Type: Error
Event ID: 1800 Source: BINLSVC
Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x 3

Type: Error
Event ID: 1803
Source: BINLSVC
Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2
Error message group 2

Event Type: Error
Event Source: BINLSVC
Event ID: 1803 Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2

Event Type: Error
Event Source: BINLSVC
Event ID: 1800 Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x13

Event Type: Error
Event Source: WDSPXE
Event ID: 261 Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSPXE
Event ID: 265 Description: An error occurred while trying to initialize provider BINLSVC. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSServer
Event ID: 513 Description: An error occurred while trying to initialize provider WDSPXE from C:\WINDOWS\system32\wdspxe.dll. Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSServer
Event ID: 522
Description: An error occurred while trying to shutdown provider WDSPXE. Error Information: 0x6

RESOLUTION :

To resolve this problem, reinitialize the WDS server after you move the WDS server to a different organizational unit. To do this, follow these steps:
  1. Click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type wdsutil /uninitialize-server, and then press ENTER.
  3. Move the WDS account to Active Directory in the new organizational unit.
  4. To reinitialize the WDS service, type wdsutil /initialize-server /reminst:{RemoteInstallFolder} at a command prompt, and then press ENTER.

Enjoy!!!!