Memory Limits for Windows Releases

 

Physical Memory Limits: Windows 8

The following table specifies the limits on physical memory for Windows 8.

Version Limit on X86 Limit on X64
Windows 8 Enterprise 4 GB 512 GB
Windows 8 Professional 4 GB 512 GB
Windows 8 4 GB 128 GB

 

Physical Memory Limits: Windows Server 2012

The following table specifies the limits on physical memory for Windows Server 2012. Windows Server 2012 is available only in X64 editions.

Version Limit on X64
Windows Server 2012 Datacenter 4 TB
Windows Server 2012 Standard 4 TB
Windows Server 2012 Essentials 64 GB
Windows Server 2012 Foundation 32 GB
Windows Storage Server 2012 Workgroup 32 GB
Windows Storage Server 2012 Standard 4 TB
Hyper-V Server 2012 4 TB

 

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.

Version Limit on X86 Limit on X64
Windows 7 Ultimate 4 GB 192 GB
Windows 7 Enterprise 4 GB 192 GB
Windows 7 Professional 4 GB 192 GB
Windows 7 Home Premium 4 GB 16 GB
Windows 7 Home Basic 4 GB 8 GB
Windows 7 Starter 2 GB N/A

 

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.

Version Limit on X64 Limit on IA64
Windows Server 2008 R2 Datacenter 2 TB
Windows Server 2008 R2 Enterprise 2 TB
Windows Server 2008 R2 for Itanium-Based Systems 2 TB
Windows Server 2008 R2 Foundation 8 GB
Windows Server 2008 R2 Standard 32 GB
Windows HPC Server 2008 R2 128 GB
Windows Web Server 2008 R2 32 GB

 

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on X64 Limit on IA64
Windows Server 2008 Datacenter 64 GB 1 TB
Windows Server 2008 Enterprise 64 GB 1 TB
Windows Server 2008 HPC Edition 128 GB
Windows Server 2008 Standard 4 GB 32 GB
Windows Server 2008 for Itanium-Based Systems 2 TB
Windows Small Business Server 2008 4 GB 32 GB
Windows Web Server 2008 4 GB 32 GB

 

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.

Version Limit on X86 Limit on X64
Windows Vista Ultimate 4 GB 128 GB
Windows Vista Enterprise 4 GB 128 GB
Windows Vista Business 4 GB 128 GB
Windows Vista Home Premium 4 GB 16 GB
Windows Vista Home Basic 4 GB 8 GB
Windows Vista Starter 1 GB

 

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003 R2

The following table specifies the limits on physical memory for Windows Server 2003 R2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on X64
Windows Server 2003 R2 Datacenter Edition 64 GB

(16 GB with 4GT)

1 TB
Windows Server 2003 R2 Enterprise Edition 64 GB

(16 GB with 4GT)

1 TB
Windows Server 2003 R2 Standard Edition 4 GB 32 GB

 

Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 2 (SP2). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on X64 Limit on IA64
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition 64 GB

(16 GB with 4GT)

1 TB 2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition 64 GB

(16 GB with 4GT)

1 TB 2 TB
Windows Server 2003 with Service Pack 2 (SP2), Standard Edition 4 GB 32 GB

 

Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 1 (SP1). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on X64 Limit on IA64
Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition 64 GB

(16 GB with 4GT)

X64 1 TB 1 TB
Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition 64 GB

(16 GB with 4GT)

X64 1 TB 1 TB
Windows Server 2003 with Service Pack 1 (SP1), Standard Edition 4 GB 32 GB

 

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on IA64
Windows Server 2003, Datacenter Edition 64 GB

(16 GB with 4GT)

512 GB
Windows Server 2003, Enterprise Edition 64 GB

(16 GB with 4GT)

512 GB
Windows Server 2003, Standard Edition 4 GB
Windows Server 2003, Web Edition 2 GB
Windows Small Business Server 2003 4 GB
Windows Compute Cluster Server 2003 32 GB
Windows Storage Server 2003, Enterprise Edition 8 GB
Windows Storage Server 2003 4 GB

 

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.

Version Limit on X86 Limit on X64 Limit on IA64
Windows XP 4 GB 128 GB 128 GB (not supported)
Windows XP Starter Edition 512 MB N/A N/A

 

Physical Memory Limits: Windows Embedded

The following table specifies the limits on physical memory for Windows Embedded.

Version Limit on X86 Limit on X64
Windows XP Embedded 4 GB
Windows Embedded Standard 2009 4 GB
Windows Embedded Standard 7 4 GB 192 GB
Advertisements

Downgrading VM hardware version 8 to version 7

Make sure you have a good backup of the VM
Power off the VM
Make sure the VM doesn’t have any snapshots before proceeding
From the ESX console or from a Putty session, edit the VMs VMX file, using your favorite editor
vi /vmfs/volume/Datastore/srv-1/srv-1.vmx

Change the virtual hardware version from:
virtualHW.version = “8”
to
virtualHW.version = “7”

Change the virtual hardware version from:
ddb.virtualHWVersion = “8”
to
ddb.virtualHWVersion = “7”

You should now be able to power on the VM as virtual hardware version 7.

Outlook continually prompting for username and password — Exchange Autodiscover

Autodiscover allows you to automatically configure Outlook 2007 clients, but, there is a lot more behind the Autodiscover functionality. When you have issues with the Out-of-Office or Free/Busy information in Outlook 2007 in combination with Exchange Server 2010 (or Outlook 2010 and Exchange Server 2010) it is likely that it is caused by a misconfiguration in the Autodiscover configuration.

Autodiscover information is stored in a so called SCP or Service Connection Point. You can view this SCP using Active Directory Sites and Services after you have enabled the “View Services Node” option:

When installing the Client Access Server (Autodiscover is part of this Server Role) the SCP is automatically created in Active Directory and configured with the default values. If you have multiple CAS Servers there will be multiple SCP’s as well.

When Outlook 2007 is installed on a domain joined workstation then the Outlook client will query Active Directory for the Autodiscover information. Active Directory will return a list of SCP’s and the Outlook client will automatically select the first SCP in this list. Using the information found in the SCP the Outlook client will contact the Client Access Server for its configuration information and the Outlook client will be configured automatically.

Non-domain clients are a bit trickier to configure since they will not query the Active Directory. Because of this non-domain clients try to retrieve information using the Autodiscover website. The FQDN that the Outlook client will use is based on the SMTP address that is used when starting the Outlook 2010 client the first time. So, when an e-mail address vvadher@Avtargroup.co.in is entered, the Outlook client will start trying to connect to the Client Access Server using HTTPS. There are several URL’s that Oulook will use, but the most important is https://autodiscover.avtargroup.co.in.

Most people are missing is the autodiscover.domainname.com (where domainname.com) is the part after the @ in your e-mail address. Newer versions of outlook will look for this for OAB download, free/busy information, Out of Office etc etc. If it’s not there then outlook will continually give user prompts. To accompany this you must have an SSL Certificate that contains the autodiscover.domainname.com URL (whilst you can configure ways around this, it really isn’t worth all the hastle). So purchasing an SAN/UCC Certificate with the following names in is a must for Exchange 2007 and Exchange 2010:

  • autodiscover.domainname.com
  • owa.domainname.com (the URL used for Outlook Web Access)
  • servername.domainname.local (the internal FQDN of your Exchange Server)
  • SERVERNAME (NETBIOS Name of your Server)

 

If you have all the above configured and you are still experiencing problems then the following procedure will more than likely fix it for you. It has been working a lot for me lately and also for people asking questions on Experts Exchange.

In Internet Information Services (IIS) Manager locate the Exchange virtual directories, if you are using Small Business Server 2008 these will be under the SBS Web Applications website, if your not using SBS then they will be under the Default Website.

The virtual Directories you are looking for are:

  1. Autodiscover
  2. EWS
  3. RPC
  4. OAB

In turn highlight each of these virtual directories and double click the Authentication icon on the right hand side. Right click on Windows Authentication and select Advanced Settings. Place a check box in the box for Enable kernel-mode authentication. Do this for each virtual directory listed above.

More Reference :-

http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/exchange-autodiscover.html

http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/exchange-autodiscover-part2.html

 

The User Profile Service service failed the logon

The User Profile Service service failed the logon. User Profile cannot be loaded.

I got this problem when I try to login with a new user account on Windows 7 PC which is added to the domain.

I think the problem caused by some secuirty permission changes to the default user account in the path C:\Users.

The solution, unhide Default user by doing (Computer -> Tools -> Folder options -> ) ,

The right click over the Default user -> Properties -> Security  then change the permission as bellow so it fixes the issue. Basically you are replacing all child object permissions for Default user.

Now you should be able to login.

Manually Generating Offline Address Book on Exchange 2010

An Exchange offline address book (OAB) is an Address Book that contains one or more address lists. It is availalble to Exchange Client software (e.g Outlook 2007) when users are not connected to Exchange Server and are offline.

OABs are not generated frequently in  a day because OAB generation process consumes much system resources if they contain hundreds of email addresses. Instead they are normally generated once or twice in a day depending upon the size of the OAB and need of the organization owning that OAB.

Sometimes its necessary to immediately generate the OAB when a new email address is added to Exchange System, so that the new email address is immediately available to outlook (or) other clients through downloading the latest OAB.

For immediate OAB generation and distribution (both PF, and web based distribution through CAS) I do following steps:

1Run Update-OfflineAddressbook “offline address book”  in Exchange Management Shell. e.g

Update-OfflineAddressbook “Default offline address book”

2. Restart System Attendant Service on the OAB Generation Server (Mailbox Server). This service is responsible for generating the OAB by communicating with Active Directory infrastructure.

3. Either run following command in EMS

Update-FileDistributionService “CASServerName”

or just restart File Distribution Service on CAS Server.

File distribution service copies the OAB from the Mailbox Server, where System Attendant Service puts OAB in a shared folder “C:\Program Files\Microsoft\Exchange Server\ExchangeOAB”. Outlook clients then download the OAB from CAS published OAB Virtual Directory.