Memory Limits in Windows OS

Memory and Address Space Limits

The following table specifies the limits on memory and address space for supported releases of Windows.

Memory type	Limit in 32-bit Windows	Limit in 64-bit Windows
User-mode virtual address space for each 32-bit process	2 GB Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT	2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default) 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set
User-mode virtual address space for each 64-bit process	Not applicable	With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default): x64:  8 TB Intel IPF:  7 TB 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared
Kernel-mode virtual address space	2 GB From 1 GB to a maximum of 2 GB with 4GT	8 TB
Paged pool	Limited by available kernel-mode virtual address space or the PagedPoolLimit registry key value. Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value. Windows Home Server and Windows Server 2003:  530 MB Windows XP:  490 MB Windows 2000:  350 MB	128 GB Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM. Windows 2000:  Not applicable
Nonpaged pool	Limited by available kernel-mode virtual address space, the NonPagedPoolLimit registry key value, or physical memory. Windows Vista:  Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value. Windows Home Server, Windows Server 2003, and Windows XP/2000:  256 MB, or 128 MB with 4GT.	75% of RAM up to a maximum of 128 GB Windows Vista:  40% of RAM up to a maximum of 128 GB. Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM. Windows 2000:  Not applicable
System cache virtual address space (physical size limited only by physical memory)	Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value. Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value. Windows Home Server, Windows Server 2003, and Windows XP/2000:  860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.	Always 1 TB regardless of physical RAM Windows Server 2003 and Windows XP:  Up to 1 TB depending on configuration and RAM. Windows 2000:  Not applicable

 

Physical Memory Limits: Windows 7

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

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
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	2 GB

 

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 in 64-bit Windows
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 in 32-bit Windows	Limit in 64-bit Windows
Windows Server 2008 Datacenter	64 GB	2 TB
Windows Server 2008 Enterprise	64 GB	2 TB
Windows Server 2008 HPC Edition	Not applicable	128 GB
Windows Server 2008 Standard	4 GB	32 GB
Windows Server 2008 for Itanium-Based Systems	Not applicable	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 in 32-bit Windows	Limit in 64-bit Windows
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	Not applicable

 

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

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 in 32-bit Windows	Limit in 64-bit Windows
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition	128 GB 64 GB with 4GT	2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition	64 GB	2 TB
Windows Storage Server 2003, Enterprise Edition	8 GB	Not applicable
Windows Storage Server 2003	4 GB	Not applicable
Windows Server 2003 R2 Datacenter Edition Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition	128 GB 16 GB with 4GT	1 TB
Windows Server 2003 R2 Enterprise Edition Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition	64 GB 16 GB with 4GT	1 TB
Windows Server 2003 R2 Standard Edition Windows Server 2003, Standard Edition SP1 Windows Server 2003, Standard Edition SP2	4 GB	32 GB
Windows Server 2003, Datacenter Edition	128 GB 16 GB with 4GT	512 GB
Windows Server 2003, Enterprise Edition	32 GB 16 GB with 4GT	64 GB
Windows Server 2003, Standard Edition	4 GB	16 GB
Windows Server 2003, Web Edition	2 GB	Not applicable
Windows Small Business Server 2003	4 GB	Not applicable
Windows Compute Cluster Server 2003	Not applicable	32 GB

 

Physical Memory Limits: Windows XP

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

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
Windows XP	4 GB	128 GB
Windows XP Starter Edition	512 MB	Not applicable

 

Physical Memory Limits: Windows 2000

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

Version	Limit in 32-bit Windows
Windows 2000 Professional	4 GB
Windows 2000 Server	4 GB
Windows 2000 Advanced Server	8 GB
Windows 2000 Datacenter Server	32 GB

 

Memory Limits in Windows OS

Memory and Address Space Limits

The following table specifies the limits on memory and address space for supported releases of Windows.

Memory type	Limit in 32-bit Windows	Limit in 64-bit Windows
User-mode virtual address space for each 32-bit process	2 GB Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE and 4GT	2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default) 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set
User-mode virtual address space for each 64-bit process	Not applicable	With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default): x64:  8 TB Intel IPF:  7 TB 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared
Kernel-mode virtual address space	2 GB From 1 GB to a maximum of 2 GB with 4GT	8 TB
Paged pool	Limited by available kernel-mode virtual address space or the PagedPoolLimit registry key value. Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value. Windows Home Server and Windows Server 2003:  530 MB Windows XP:  490 MB Windows 2000:  350 MB	128 GB Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM. Windows 2000:  Not applicable
Nonpaged pool	Limited by available kernel-mode virtual address space, the NonPagedPoolLimit registry key value, or physical memory. Windows Vista:  Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value. Windows Home Server, Windows Server 2003, and Windows XP/2000:  256 MB, or 128 MB with 4GT.	75% of RAM up to a maximum of 128 GB Windows Vista:  40% of RAM up to a maximum of 128 GB. Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM. Windows 2000:  Not applicable
System cache virtual address space (physical size limited only by physical memory)	Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value. Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value. Windows Home Server, Windows Server 2003, and Windows XP/2000:  860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.	Always 1 TB regardless of physical RAM Windows Server 2003 and Windows XP:  Up to 1 TB depending on configuration and RAM. Windows 2000:  Not applicable

 

Physical Memory Limits: Windows 7

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

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
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	2 GB

 

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 in 64-bit Windows
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 in 32-bit Windows	Limit in 64-bit Windows
Windows Server 2008 Datacenter	64 GB	2 TB
Windows Server 2008 Enterprise	64 GB	2 TB
Windows Server 2008 HPC Edition	Not applicable	128 GB
Windows Server 2008 Standard	4 GB	32 GB
Windows Server 2008 for Itanium-Based Systems	Not applicable	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 in 32-bit Windows	Limit in 64-bit Windows
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	Not applicable

 

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

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 in 32-bit Windows	Limit in 64-bit Windows
Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition	128 GB 64 GB with 4GT	2 TB
Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition	64 GB	2 TB
Windows Storage Server 2003, Enterprise Edition	8 GB	Not applicable
Windows Storage Server 2003	4 GB	Not applicable
Windows Server 2003 R2 Datacenter Edition Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition	128 GB 16 GB with 4GT	1 TB
Windows Server 2003 R2 Enterprise Edition Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition	64 GB 16 GB with 4GT	1 TB
Windows Server 2003 R2 Standard Edition Windows Server 2003, Standard Edition SP1 Windows Server 2003, Standard Edition SP2	4 GB	32 GB
Windows Server 2003, Datacenter Edition	128 GB 16 GB with 4GT	512 GB
Windows Server 2003, Enterprise Edition	32 GB 16 GB with 4GT	64 GB
Windows Server 2003, Standard Edition	4 GB	16 GB
Windows Server 2003, Web Edition	2 GB	Not applicable
Windows Small Business Server 2003	4 GB	Not applicable
Windows Compute Cluster Server 2003	Not applicable	32 GB

 

Physical Memory Limits: Windows XP

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

Version	Limit in 32-bit Windows	Limit in 64-bit Windows
Windows XP	4 GB	128 GB
Windows XP Starter Edition	512 MB	Not applicable

 

Physical Memory Limits: Windows 2000

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

Version	Limit in 32-bit Windows
Windows 2000 Professional	4 GB
Windows 2000 Server	4 GB
Windows 2000 Advanced Server	8 GB
Windows 2000 Datacenter Server	32 GB

 

Thanks to Ajay for recollecting this – Virus Clean with the help of Super DAT File

How to scan for viruses in DOS

 

Step 1 - Download and Extract the current SuperDAT Files

1. Click on the following link or type the URL into an Internet browser address bar:
   http://www.mcafee.com/apps/downloads/security_updates/superdat.asp?region=us&segment=enterprise
2. Click the I Agree button (if needed) to verify you have a current support agreement with McAfee.
3. English users, please click the link named sdatxxxx.exe (where 'xxxx' replaces the current SDAT version number) and save the file to your C:\ Drive.
4. All others please select the appropriate localized language from the drop-down list, click the link named sdatxxxx.exe (where 'xxxx' replaces the current SDAT version number) and save it to your C:\ Drive.
5. From the Taskbar, select Start and then Run.
6. In the Open field, type command and click OK. A DOS command window will open.
7. Type CD\ and press Enter. You should now be at a C:\ prompt.
8. Type SDATXXXX.EXE /E C:\SDAT and press Enter. (Note: The 'x's should be replaced with the appropriate numbers of the file that was downloaded above.) This will create an SDAT folder on the C:\ drive, and extract the SDAT files to this folder.
   Note: Windows XP Users with Service Pack 2 installed will be presented with a security warning when attempting to extract the file. Please click Run to continue the extraction process.
   
9. Once the C:\ prompt is displayed again, please type exit and press Enter.

Step 2 - Disable Windows System Restore

Windows XP utilize a restore utility that backs up and protects selected files automatically to the C:\_Restore folder. This means that an infected file could be stored there as a backup and VirusScan would be unable to delete these files. The System Restore utility must be disabled to remove any infected files from the C:\_Restore folder.

 

Windows XP

1. Right-click the My Computer icon on the Desktop and click Properties.
2. Click on the System Restore tab.
3. Put a check mark in the box next to Turn off System Restore.
4. Click the OK button.
5. You may be prompted to restart the computer. Click Yes to restart.
   Note: To re-enable the System Restore utility, repeat the steps above and in step 3 remove the check mark from the box next to Turn off System Restore.

Step 3 - Boot the Computer to DOS

1. If the computer is on: From the Taskbar, click Start, then Shutdown and choose Restart.
2. If the computer is off, turn the computer on.
3. When the opening splash screen appears, begin tapping the F8 key every second.
   Note: On some computers, if you press F8 too soon you will get a keyboard error. If this happens, press the F1 key to continue.
4. The Windows 2000 (or XP) Advanced Options Menu will appear. Use the arrow keys to choose Safe Mode with Command Prompt.
5. Login to your computer (if necessary).
6. When the computer is finished booting, the c:\> prompt will appear on the screen.
   Note: If there is anything typed after c:\>, type cd\ and press Enter.
7. Continue with the scan instructions below.

Step 4 - Scan the Computer

1. At the c:\> prompt, type cd sdat and press Enter.

2. Type scan.exe /adl /clean /all /sub /program /unzip /analyze /rptall /report report.txt and press Enter.

This will perform a virus scan, which will clean and delete any viruses you may have on your computer.

Explanation of DOS scan switches:

• /all - Scans all files
• /adl - Scans all local drives
• /sub - Scans within subdirectories
• /program - Enables Potentially Unwanted Program scanning
• /unzip - Enables archive scanning
• /analyze - Enables heuristics
• /clean - Sets the automatic action for the scanner to Clean anything detected
• /rptall - Enables verbose logging
• /report=C:\scan.txt - Saves the verbose logging as a text file in the root of C: called scan.txt

Multiple Infections

After the scan has run, a summary report of the scan will be created in the sdat folder on the C:\ drive. If this summary reports that your computer had multiple infections, it is recommended that you run the scan again to make sure the computer has been completely cleaned.
To determine if an additional scan is needed, please complete the following steps:

Step 5 - Review the Scan Report

1. Restart the computer into Normal Mode.
2. Double-click the My Computer icon.
3. Double-click the C:\ drive.
4. Double click the sdat folder.
5. Locate the file named report.txt and double-click to open.
6. The report contains several lines that look similar to this:
   
   If the top line named Possibly Infected has a number greater that 5, it is recommended that you run the scan in DOS again.
7. If you need to run the scan again, repeat the above instructions for Boot the Computer to DOS and Scan the Computer.

Additional Information

• How to perform a DOS virus scan in Windows Vista

Thanks to Ajay for recollecting this – Virus Clean with the help of Super DAT File

How to scan for viruses in DOS

 

Step 1 - Download and Extract the current SuperDAT Files

1. Click on the following link or type the URL into an Internet browser address bar:
   http://www.mcafee.com/apps/downloads/security_updates/superdat.asp?region=us&segment=enterprise
2. Click the I Agree button (if needed) to verify you have a current support agreement with McAfee.
3. English users, please click the link named sdatxxxx.exe (where 'xxxx' replaces the current SDAT version number) and save the file to your C:\ Drive.
4. All others please select the appropriate localized language from the drop-down list, click the link named sdatxxxx.exe (where 'xxxx' replaces the current SDAT version number) and save it to your C:\ Drive.
5. From the Taskbar, select Start and then Run.
6. In the Open field, type command and click OK. A DOS command window will open.
7. Type CD\ and press Enter. You should now be at a C:\ prompt.
8. Type SDATXXXX.EXE /E C:\SDAT and press Enter. (Note: The 'x's should be replaced with the appropriate numbers of the file that was downloaded above.) This will create an SDAT folder on the C:\ drive, and extract the SDAT files to this folder.
   Note: Windows XP Users with Service Pack 2 installed will be presented with a security warning when attempting to extract the file. Please click Run to continue the extraction process.
   
9. Once the C:\ prompt is displayed again, please type exit and press Enter.

Step 2 - Disable Windows System Restore

Windows XP utilize a restore utility that backs up and protects selected files automatically to the C:\_Restore folder. This means that an infected file could be stored there as a backup and VirusScan would be unable to delete these files. The System Restore utility must be disabled to remove any infected files from the C:\_Restore folder.

 

Windows XP

1. Right-click the My Computer icon on the Desktop and click Properties.
2. Click on the System Restore tab.
3. Put a check mark in the box next to Turn off System Restore.
4. Click the OK button.
5. You may be prompted to restart the computer. Click Yes to restart.
   Note: To re-enable the System Restore utility, repeat the steps above and in step 3 remove the check mark from the box next to Turn off System Restore.

Step 3 - Boot the Computer to DOS

1. If the computer is on: From the Taskbar, click Start, then Shutdown and choose Restart.
2. If the computer is off, turn the computer on.
3. When the opening splash screen appears, begin tapping the F8 key every second.
   Note: On some computers, if you press F8 too soon you will get a keyboard error. If this happens, press the F1 key to continue.
4. The Windows 2000 (or XP) Advanced Options Menu will appear. Use the arrow keys to choose Safe Mode with Command Prompt.
5. Login to your computer (if necessary).
6. When the computer is finished booting, the c:\> prompt will appear on the screen.
   Note: If there is anything typed after c:\>, type cd\ and press Enter.
7. Continue with the scan instructions below.

Step 4 - Scan the Computer

1. At the c:\> prompt, type cd sdat and press Enter.

2. Type scan.exe /adl /clean /all /sub /program /unzip /analyze /rptall /report report.txt and press Enter.

This will perform a virus scan, which will clean and delete any viruses you may have on your computer.

Explanation of DOS scan switches:

• /all - Scans all files
• /adl - Scans all local drives
• /sub - Scans within subdirectories
• /program - Enables Potentially Unwanted Program scanning
• /unzip - Enables archive scanning
• /analyze - Enables heuristics
• /clean - Sets the automatic action for the scanner to Clean anything detected
• /rptall - Enables verbose logging
• /report=C:\scan.txt - Saves the verbose logging as a text file in the root of C: called scan.txt

Multiple Infections

After the scan has run, a summary report of the scan will be created in the sdat folder on the C:\ drive. If this summary reports that your computer had multiple infections, it is recommended that you run the scan again to make sure the computer has been completely cleaned.
To determine if an additional scan is needed, please complete the following steps:

Step 5 - Review the Scan Report

1. Restart the computer into Normal Mode.
2. Double-click the My Computer icon.
3. Double-click the C:\ drive.
4. Double click the sdat folder.
5. Locate the file named report.txt and double-click to open.
6. The report contains several lines that look similar to this:
   
   If the top line named Possibly Infected has a number greater that 5, it is recommended that you run the scan in DOS again.
7. If you need to run the scan again, repeat the above instructions for Boot the Computer to DOS and Scan the Computer.

Additional Information

• How to perform a DOS virus scan in Windows Vista

Miscellaneous notes for “Dummy”s

Never select a PXE Distribution Point when deploying packages.

This may stop that PXE point from functioning. Use the list of DP Groups or select the specific DPs required.

When setting up Advertisements to execute at specific times use:-

UTC if you want the installation to start at the same time the world over regardless of local time. For example, if you want the installation to commence on all PCs regardless of location at 3:30AM Dallas time, select UTC on the Advertisement window.

Local Time if you want the installation to commence at a specific local time, ie at 2:00PM UK time and 2:00PM Canada time.

The “All Packages” canned report now shows all packages and not all packages at all distribution points.

If you wish to view all packages at a specific DP, please select the “All Packages for Distribution Point“ report.

Site WAN throttling

If a site with an SCCM DP Server has issues around bandwidth utilization and it seems that when SCCM deploys a new version of the Package (12GB) that users are impacted. The SCCM team can then throttle the SCCM utilization of the bandwidth during business Hours (6AM-6PM) so it only uses 50% or 20% of available bandwidth. Note that the less bandwidth the longer packages will take to reach the site.

Clean out obsolete client records

When a PC is being built from a PXE boot task sequence, an option exists for the immediate installation of other applications, This will only work if the flag is set on the packages program as per the below screen shot – “Allow the program to be installed from the Install Software Task Sequence without being advertised. If this flag is not set, the package will install approximately 2 hours after the task sequence is complete.

When the you notices packages without a source, they you can deleted those.

Miscellaneous notes for “Dummy”s

Never select a PXE Distribution Point when deploying packages.

This may stop that PXE point from functioning. Use the list of DP Groups or select the specific DPs required.

When setting up Advertisements to execute at specific times use:-

UTC if you want the installation to start at the same time the world over regardless of local time. For example, if you want the installation to commence on all PCs regardless of location at 3:30AM Dallas time, select UTC on the Advertisement window.

Local Time if you want the installation to commence at a specific local time, ie at 2:00PM UK time and 2:00PM Canada time.

The “All Packages” canned report now shows all packages and not all packages at all distribution points.

If you wish to view all packages at a specific DP, please select the “All Packages for Distribution Point“ report.

Site WAN throttling

If a site with an SCCM DP Server has issues around bandwidth utilization and it seems that when SCCM deploys a new version of the Package (12GB) that users are impacted. The SCCM team can then throttle the SCCM utilization of the bandwidth during business Hours (6AM-6PM) so it only uses 50% or 20% of available bandwidth. Note that the less bandwidth the longer packages will take to reach the site.

Clean out obsolete client records

When a PC is being built from a PXE boot task sequence, an option exists for the immediate installation of other applications, This will only work if the flag is set on the packages program as per the below screen shot – “Allow the program to be installed from the Install Software Task Sequence without being advertised. If this flag is not set, the package will install approximately 2 hours after the task sequence is complete.

When the you notices packages without a source, they you can deleted those.

CREATE All Non Client Systems collection

 

The below is the query for creating All Non Client Systems:-

 

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Client = 0

CREATE All Non Client Systems collection

 

The below is the query for creating All Non Client Systems:-

 

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Client = 0

Updates Performance Monitor counter : LODCTR

Updates Performance Monitor counter

 

LODCTR
    Updates Performance Monitor counter names and explain text for an extensible
counter

Usage:
    LODCTR [\\computername] filename
        computername is the name of the remote computer.
            Local machine is used if computername is not specified.
        filename is the name of the initialization file that contains
            the counter name definitions and explain text for an extensible
            counter DLL.

    LODCTR /S:<FileName>
        save current perf registry strings and info to <FileName>

    LODCTR /R:<FileName>
        restore perf registry strings and info using <FileName>

Note: any arguments with spaces in the names must be enclosed within
Double Quotation marks.

Updates Performance Monitor counter : LODCTR

Updates Performance Monitor counter

 

LODCTR
    Updates Performance Monitor counter names and explain text for an extensible
counter

Usage:
    LODCTR [\\computername] filename
        computername is the name of the remote computer.
            Local machine is used if computername is not specified.
        filename is the name of the initialization file that contains
            the counter name definitions and explain text for an extensible
            counter DLL.

    LODCTR /S:<FileName>
        save current perf registry strings and info to <FileName>

    LODCTR /R:<FileName>
        restore perf registry strings and info using <FileName>

Note: any arguments with spaces in the names must be enclosed within
Double Quotation marks.

Seven Habits of Highly Effective People

1. HABIT ONE: BE PROACTIVE
2. HABIT TWO: BEGIN WITH THE END IN MIND
3. HABIT THREE: PUT FIRST THINGS FIRST
4. HABIT FOUR: THINK WIN – WIN
5. HABIT FIVE: SEEK FIRST TO UNDERSTAND THEN TO BE UNDERSTOOD
6. HABIT SIX – SYNERGISE
7. HABIT SEVEN: SHARPEN THE SAW

Seven Habits of Highly Effective People

1. HABIT ONE: BE PROACTIVE
2. HABIT TWO: BEGIN WITH THE END IN MIND
3. HABIT THREE: PUT FIRST THINGS FIRST
4. HABIT FOUR: THINK WIN – WIN
5. HABIT FIVE: SEEK FIRST TO UNDERSTAND THEN TO BE UNDERSTOOD
6. HABIT SIX – SYNERGISE
7. HABIT SEVEN: SHARPEN THE SAW