Requirements for windows 2008 server

By -


Windows Server 2008 System Requirements


This software is intended for evaluation and deployment planning purposes only. If you plan to install the software on your primary computer, it is recommended that you back up your existing data prior to installation.


To use Windows Server 2008, you need*:
ComponentRequirement
Processor
• Minimum: 1 GHz (x86 processor) or 1.4 GHz (x64 processor)
• Recommended: 2 GHz or faster
Note: An Intel Itanium 2 processor is required for Windows Server 2008 for Itanium-Based Systems.
Memory• Minimum: 512 MB RAM
• Recommended: 2 GB RAM or greater
• Maximum (32-bit systems): 4 GB (Standard) or 64 GB (Enterprise and Datacenter)
• Maximum (64-bit systems): 32 GB (Standard) or 1 TB (Enterprise and Datacenter) or 2 TB (Itanium-Based Systems)
Available Disk Space
• Minimum: 10 GB
• Recommended: 40 GB or greater
Note: Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.
DriveDVD-ROM drive
Display and Peripherals• Super VGA (800 x 600) or higher-resolution monitor
• Keyboard
• Microsoft Mouse or compatible pointing device

Comments

Post a Comment

Popular posts from this blog

Boot configuration Data Store --BCDEdit /set

By -
The  BCDEdit /set  command sets a boot entry option value in the Windows boot configuration data store (BCD). Use the  BCDEdit /set  command to configure specific boot entry elements, such as kernel debugger settings, data execution protection (DEP) and processor address extension (PAE) options, and to load alternate hardware abstraction layer (HAL) and kernel files. You can use these boot entry options when you are testing and debugging your driver for Windows Vista, Windows 7, and later versions of Windows. bcdedit /set [{ID}] datatype value Parameters [ { ID }] The  { ID }  is the GUID that is associated with the boot entry. If you do not specify an  { ID } , the command modifies the current operating system boot entry. If a boot entry is specified, the GUID associated with the boot entry must be enclosed in braces  { } . To view the GUID identifiers for all of the active boot entries, use the  bcdedit...
Read more

ADSI Edit

By -
Image
ADSI Edit (adsiedit.msc) Updated: March 19, 2010 Applies To: Windows SBS 2008, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2 Active Directory® Service Interfaces Editor (ADSI Edit) is a Lightweight Directory Access Protocol (LDAP) editor that you can use to manage objects and attributes in Active Directory. ADSI Edit (adsiedit.msc) provides a view of every object and attribute in an Active Directory forest. You can use ADSI Edit to query, view, and edit attributes that are not exposed through other Active Directory Microsoft Management Console (MMC) snap-ins: Active Directory Users and Computers, Active Directory Sites and Services, Active Directory Domains and Trusts, and Active Directory Schema. This topic includes the following sections: Installing ADSI Edit ...
Read more

How to analyze SFC /scannow logs

By -
Sfc /scannow will inspect all of the important Windows files on your computer, including Windows DLL files. If System File Checker finds an issue with any of these protected files, it will replace it. You can find the sfc logs inside CBS.log under C:\Windows\logs\CBS\ folder. There will be a lot of entries in cbs logs. You can filter out the log for SFC by running the below command.  findstr /c:"[SR]" cbs.log > sfcdetails.txt The above command will search for the string [SR] and if it found , then it copies the corresponding entry in to the sfcdetails.txt Below is sample text extracted from CBS log by using the above command ----------------------------------------------------------------------------------------------------------- 2013-06-24 12:55:44, Info                  CSI    00000210 [SR] Verify complete 2013-06-24 12:55:44, Info      ...
Read more