Hardware Support and Software Pre-Requisites Data protector 6.2

HP Data Protector software

Introduction

HP Data Protector software simplifies application protection in virtual and physical environments through unified recovery and advanced automation. Global, one-touch backup configuration and a wide range of disk-based recovery options across HP and non-HP arrays, including fully-automated application recovery, help you meet any SLA for up to 70% less total cost of ownership than competitive backup software solutions.

More than 41,000 customers around the world, and nearly half of the Global 500, rely on HP Data Protector software to protect their critical applications and data. Data Protector is a key component of the HP Information Management solution portfolio, which dramatically simplifies the management and governance of information for today's modern enterprise organization.

What's New

Extending the Power of HP - down-to-the-second recovery of application for HP P4000 arrays.

Only HP Data Protector software can recover virtual server applications and data to any point in time - down-to-the-second - from a centralized console without scripting. Data Protector 6.2 extends this functionality to the P4000. Together, Data Protector and P4000 achieve a highly cost-effective enterprise recovery solution ideal for virtual server deployments of applications such as Microsoft SharePoint, Microsoft Exchange and SQL Server.

Data Protector allows backup administrators to select the point in time to which they'd like to recover into the Data Protector console. Data Protector accesses the application transaction log (where all of the application's transactions are recorded before they're processes and/or written to data files) and fills in the data gaps between snapshots. Data Protector then synchronizes the application with the data and restarts the application. This functionality is possible with any Data Protector recovery solution whether from snapshot, disk or tape.

Extending simplified snapshot functionality to non-HP arrays such as EMC CLARiiON and Network Appliance

Data Protector Zero Downtime Backup snapshot support has been extended to non-HP arrays through VSS integration. Global one-touch protection ensures snapshot configurations - as well as all backup methods - are automatically extended to new virtual machines, Microsoft databases, and Oracle databases as they're brought online. One click in the Data Protector console and Data Protector will automatically apply the chosen backup method to new VMs and databases. This level of automation extends to physical environments as well.

Reducing the burden of single item recovery on the backup administrator.

Data Protector Granular Recovery Extension empowers SharePoint and VMware vSphere administrators to recover single items directly from the application administrator's console, without asking for assistance from the backup administrator.

Data Protector allows application administrators to recover single items from Data Protector disk or tape backups - they don't need to know or use Data Protector, nor do they need to contact the backup administrator. For SharePoint environments, GRE allows application administrators to recover single items from ANY 3rd party snapshots.

NEW Data Protector Reporter software - sophisticated operational analysis, SLA compliance reporting across multi-site distributed geographies.

Data Protector software includes robust reporting capabilities, including a notification function which allows customers to forward events to HP or 3rd-party reporting or management tools such as HP Storage Essentials and IBM Tivoli. For customers who require the most advanced reporting capabilities, HP provides Data Protector Reporter software - which delivers enterprise reporting, designed specifically for Data Protector customers. HP Data Protector Reporter software is customer-installable software which delivers centralized, automated reporting to optimize operations and infrastructure - and realize up to 30% savings. It features a powerful reporting engine that drives global, multi-site backup and restore analysis. Data Protector Reporter features 35+ out-of-the-box reports including SLA and performance reporting. The optional current licensed module provides enhanced powerful customized ad-hoc query and analysis flexible reporting. For more information, please download the Data Protector Reporter QuickSpecs on hp.com/go/dataprotector.

Enhanced single-pass disaster recovery functionality - for no additional cost.

Data Protector 6.2 introduces new disaster recovery functionality which is included in the cost of Data Protector. Unlike some backup software solutions that require you to keep a separate image backup from which to initiate recovery, Data Protector provides "single-pass DR" - which enables customers to create a disaster recovery image from any existing full backup. You can restore from physical-to-virtual and virtual-to-physical servers across dissimilar hardware. In addition, once the backup administrator initiates the disaster recovery process, Data Protector automatically re-builds the system and the partitioning. Data Protector 6.2 supports both Linux and Windows operating systems - for specific support please check the compatibility matrix on hp.com/go/dataprotector.

In addition, Data Protector DR functionality is especially useful in remote and branch office environments. Data Protector is fully replication aware, and provides a single management console from which to oversee deduplication-enabled replication between local or geographically distributed sites. When Data Protector performs a backup in the remote office, the backup with the DR image can be replicated to the central data center, In the event of an outage, the DR image can be prepared and delivered to the ROBO site via FTP site or by shipping a USB drive for fast recovery.

IPv6 and NDMP

Data Protector 6.2 is fully IPv6 compliant. Data Protector IPv6 support is backward compatible for IPv4 environments. In addition, Data Protector 6.2 also provides NDMP snapmirror to tape support, which provides efficient backup of large files.

Hardware Support and Software Pre-Requisites Hardware Support Broad coverage of HP-UX, Windows, Solaris, Tru64, OpenVMS, NetWare, Linux, AIX, and other operating environments HP XP/EVA, and EMC Symmetrix disk array support for ZDB/IR Backup to disk supports any storage that the server's operating system supports HP Tape libraries, StorageTek, ADIC, IBM etc. For detailed information on HP Data Protector support matrices please visit: http://www.hp.com/go/dataprotector Software Pre-Requisites Cell Manager Requirements The Data Protector Session Manager does not support the IDB on a file system that is mounted as NFS type. On Systems Running HP-UX (PA-RISC) - 11.11, 11.23, 11.31 and HP-UX (IA64) - 11.23, 11.31 The Cell Manager must meet the following minimum requirements: The Soft File Limit per Process on the Cell Manager should be at least 1024. 256 MB RAM (512 MB recommended) For each parallel backup session 40 MB of RAM are required and 5 - 8 MB per data segment size. For example, if you want to run 60 parallel backup sessions 3 GB of RAM plus 512 MB for data segments are needed. 240 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB). It is recommended to modify the kernel parameters as follows: Set maxdsiz (Max Data Segment Size) or maxdsiz_64 (for 64-bit systems) to at least 134217728 bytes (128 MB). Set semmnu (Number of Semaphore Undo Structures) to at least 256. After committing these changes, recompile the kernel and reboot the machine. On Systems Running Solaris 8/9/10 The Cell Manager must meet the following minimum requirements: 256 MB of RAM (512 MB recommended) For each parallel backup session 40 MB of RAM are required and 5-8 MB per data segment size. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM plus 512 MB of data segments are needed. 300 - 425 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) The following values of kernel parameters are recommended: SEMMNI (maximum number of semaphore sets in the entire system) = 100 and SEMMNS (maximum semaphores on the system) = 256. A system restart is necessary for kernel changes to take effect. The requirements for viewing online Help on the Data Protector Cell Manager are the same as on Data Protector clients. For Java GUI Client, Java Runtime Environment (JRE) 1.5.0_06 or newer (for example, 1.5.0_07) is required. On Systems Running Windows XP The Cell Manager must meet the following minimum requirements: 256 MB RAM (512 MB recommended). For each parallel backup session 40 MB of RAM are required. For example, if you want to run 60 parallel backup sessions 3 GB of RAM are needed. Windows 2000, Service Pack 3 or later Windows XP Professional, Service Pack 1 must be installed 190 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) 2 + 5MB of disk space needed on system drive For viewing online help on the Data Protector Cell Manager, Microsoft Internet Explorer 6.0 or newer is required. For Java GUI Client, Java Runtime Environment (JRE) 1.5.0. or newer (for example, 1.5.0_07) is required. On Systems Running Windows Server 2003 (32-bit) and Windows 2003/2008 & 2008-R2 (64-bit x86_64) The Cell Manager must meet the following minimum requirements: 256 MB RAM (512 MB recommended). Each parallel backup session requires 40 MB of RAM. For example, 60 parallel backup sessions requires 3 GB of RAM. 190 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB) 2 + 5MB of disk space needed on system drive On Windows Server 2008 systems, the firewall must also be configured to accept "Remote Service Administration" (NP) connections (port 445). On Windows Server 2008 systems, administrative privileges are required to install Data Protector A.06.2. For viewing online Help on the Data Protector Cell Manager, Microsoft Internet Explorer 6.0 or newer version is required. For the Java GUI Client on Windows Server 2003 systems, Java Runtime Environment (JRE) 1.5.0_06 or newer update (for example, 1.5.0_07) is required. For the Java GUI Client on Windows Server 2008 systems, BEAJRockit 5.0 1.5.0_06 or newer update (for example, 1.5.0_07) is required. On Linux Systems The Cell Manager must meet the following minimum requirements: 256 MB RAM (512 MB recommended). For each parallel backup session 40 MB of RAM are required and 5 - 8 MB per data segment size. This means that, for example, if you want to run 60 parallel backup sessions 3 GB of RAM plus 512 MB for data segments are needed. 300 - 425 MB of disk space + approximately 2% of planned data to be backed up (for use by the IDB). If the version of libstdc++ on the system is not 5 (for example libstdc++.so.6 instead of libstdc++.so.5) you need to install the compatibility package compat-2004 or compat-libstdc++. To install the Java GUI Server on Red Hat Enterprise Linux 4.0, the libstdc++-4.0.2-8.fc4.x86_64.rpm package is required. If yours system does not already contain a 64-bit version of libstdc++. so. 5 then you must install it with libstdc++-3.3.3-7.x86_64.rpm. To run the Java GUI Server on SuSE Linux Enterprise Server 9 (64-bit), the package compat-libstdc++-lsb-4 .0.2_20050901-0.4. x86_64 . rpm is required. Requirements for viewing online Help on the Data Protector Cell Manager are the same as on Data Protector clients. For Java GUI Client, Java Runtime Environment (JRE) 1.5.0_06 or newer (for example, 1.5.0_07) is required. Operating Systems supported by HP AutoPass The following Windows operating systems are supported by HP AutoPass: Windows 2000 Windows XP Windows Server 2003 (32-bit) Windows Vista (32-bit) Windows Server 2008 (32-bit) The following HP-UX operating systems are supported by HP AutoPass: HP-UX 11.00, HP-UX 11.11 (PA-RISC) HP-UX 11.23, HP-UX 11.31 (PA-RISC, Itanium) Solaris and Linux operating systems are not supported.

Error 1935.An error occurred during the installation

Error 1935.An error occurred during the installation of assembly 'Microsoft.VC80.ATL,



If you receive a 1935 error when you try to install software, the Windows file system transaction log has become corrupted. The transaction log is used by the Windows file system to recover when a file error occurs. It can also happen if there is an error with the installation of .netframework.
Step 1: To correct this install error, you need to clear the log.

a. Open an Administrator command prompt: Right-click Start > All Programs > Accessories > Command Prompt and select "Run as Administrator" and click "Allow" for the elevation prompt
b. In the command prompt, type the command below:
fsutil resource setautoreset true C:\
c. This assumes that C: is the drive in which Vista is installed. If it is installed on another drive like D:, please change the drive letter appropriately.
d. Reboot the system.
e. Install the software and check.
Step 2: Check if you are able to install in clean boot.
“How to perform Clean Boot” http://support.microsoft.com/kb/929135

Note: Please ensure that the computer is set to start as usual by following the step 7 from the article.
Step 3: Repair .net framework and check.
Repair the Microsoft .NET Framework installation
To do this, follow these steps:
a. Click Start, click Control Panel, and then click Add or Remove Programs.
b. In the Currently installed programs list, click Microsoft .NET Framework, and then click Change/Remove.
c. Click Repair, and then click Next.
Diana
Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think.

Configure IP address on RHEL 5 (GUI & Text mode)

Configure IP address on RHEL 5

 First Method – GUI

Issue the command below to bring up the GUI interface.

#system-config-network

Click on the desire NIC card profile and click on edit button at the top.

 

Select the "Statically set IP address" and key in your desire IP address.

 

Click on the "Activate" button

 

Click on the "Yes" button

Click  the "OK" button

Once done, issue the command below to for changes to take  immediate effect.

#service network restart

Or

#/etc/init.d/network restart

Second Method – Text Based GUI

Issue the command below to bring up the Text-Based-GUI.

#system-config-network-tui

Choose which NIC card you want to edit and hit the "Enter" key

 

Key in all the desire details and once you are done, hit the OK button.

 

Always restart the network service for changes to take immediate effect. Issue the command below to restart the network service.

#service network restart

Third Method – Editing Script File

The location of the script file is at

#/etc/sysconfig/network-script/ifcfg-eth0

Issue the command below to edit the script file.

#vi /etc/sysconfig/network-script/ifcfg-eth0

After you had edit the file, issue the command below to save the file

:wq!

Restart the network services for changes to take immediate effect

#service network restart

How to add/modify IP Address in Redhat Enterprise Linux

Adding the IP Address in Redhat Enterprise Linux can be done by using the netconfig tool or by editing the network-scripts or by using the ifconfig command. While this procedure is tested on Redhat Enterprise Linux, I'm sure it should work on CentOS, Fedora and older Redhat versions.

Set IP Address using Netconfig

Netconfig is a utility in Redhat Enterprise Linux which allows you to add/modify the IP Address the system, the Netmask, default gateways and the Name Servers.

Launch Netconfig,

rhel5# /usr/bin/netconfig

This launches a window as follows:

For static IP uncheck the "Use Dynamic IP configuration(BOOTP/DHCP)"

Now, enter the IP Address, netmask, Default Gateway & Primary Name Server.

Once done, restart the networking service

rhel5# service network restart

or to just reread the interface config files

rhel5# service network reload

This should set the IP Address.

Manually edit Interface configuration files

You can also manually edit the interface configuration files and add/modify the IP Address.

The Network interface configuration files are found in the directory

/etc/sysconfig/network-scripts/

Let's say there are 2 interfaces eth0 & eth1. The files to edit will be

ifcfg-eth0 – For interface eth0

ifcfg-eth1 – For interface eth1

To add the IP Address for interface eth0, edit ifcfg-eth0

rhel5# cd /etc/sysconfig/network-scripts

rhel5# vi ifcfg-eth0

Enter the following Parameters

DEVICE=eth0
BOOTPROTO=static
BROADCAST=192.168.1.255
HWADDR=00:0F:1F:2F:3F:4F
IPADDR=192.168.1.10
NETMASK=255.255.255.0
NETWORK=192.168.1.0
ONBOOT=yes
TYPE=Ethernet

Where

DEVICE indicates the interface
BOOTPROTO indicates if it is static IP or uses DHCP/BOOTP

The above sets the IP Address, Broadcast address, Network, Netmask etc.

Once done, save the file and restart the network service for the changes to take effect.

rhel5# service network restart

or to just reread the interface config files

rhel5# service network reload

Using ifconfig

This is dynamic and the change take effect instantly.

rhel5# ifconfig eth0 192.168.1.10 netmask 255.255.255.0 gw 192.168.1.1 up

This sets the IP Address, Netmask and the default gateway on the interface

Difference between: Full, Differential, and Incremental Backup

Submitted by Laxman (chinnilax@gmail.com)

Type	Definition	Benefits	Drawbacks
Full Backup:	A complete backup of everything you want to backup.	Restoration is fast, since you only need one set of backup data.	The backing up process is slow. High storage requirements.
Differential Backup:	The backup software looks at which files have changed since you last did a full backup. Then creates copies of all the files that are different from the ones in the full backup. If you do a differential backup more than once, it will copy all the files, or parts of files that have changed since the last full backup, even if you already have identical copies of those files in a previous differential backup. For restoring all the data, you will only need the the last full backup, and the last differential backup.	Faster to create than a full backup. Restoration is faster than using incremental backup. Not as much storage needed as in a full backup.	Restoration is slower than using a full backup. Creating a differential backup is slower than creating an incremental backup.
Incremental Backup:	The backup software creates copies of all the files, or parts of files that have changed since previous backups of any type (full, differential or incremental). For example if you did a full backup on Sunday. An incremental backup made on Monday, would only contain files changed since Sunday, and an incremental backup on Tuesday, would only contain files changed since Monday, and so on.	This method is the fastest when creating a backup. The least storage space is needed.	Restoring from incremental backups is the slowest because it may require several sets of data to fully restore all the data. For example if you had a full backup and six incremental backups. To restore the data would require you to process the full backup and all six incremental backups.

How to install Turbo C++ on Windows 7

We are providing detailed procedure how to install Turbo C++ on Windows 7.

Users having Win 7 Proand Win 7 Ultimate should use the virtual Windows XP Mode to install Turbo C++.
Installing Turbo C++ on Windows 7

1. Extract the zip files to: e.g. C:\TurboC



Extract zip files
2. Run the install: C:\TurboC\INSTALL.EXE



Run the install
3. Press Enter to continue



Press Enter to continue
4. Enter the Source drive: e.g.C and press Enter to continue



Enter the Source drive

5. Enter the Source path: \TURBOC and press Enter to continue



Enter the Source path
6. In directories specify where Turbo C files are copied. E.g. C:\TC . When done go to start instalation and press Enter



Specify where Turbo C++ files are copied
7. Succesfull instalation



Succesfull instalation

8. First launch from your destination e.g. C:\TC\BIN\TC.EXE

How to install Turbo C++ on Windows 7 64bit

Providing step-by-step procedure how to install Turbo C++ on 64 bit Windows 7.

1. Install the software DOSBox ver 0.73 : download here

2. Create a folder,for example „Turbo“ (c:\Turbo\)

3. Download and extract TC into the Turbo folder (c:\Turbo\): download here

4. Run the DOSBox 0.73 from the icon located on the desktop:



5. Type the following commands at the command prompt [Z]: mount d c:\Turbo\ [The folder TC is present inside the folder Turbo]

Now you should get a message which says: Drive D is mounted as a local directory c:\Turbo\



6. Type d: to shift to d:



7. Next follow the commands below:

cd tc
cd bin
tc or tc.exe [This starts you the Turbo C++ 3.0]


8. In the Turbo C++ goto Options>Directories> Change the source of TC to the source directory [D] ( i.e. virtual D: refers to original c:\Turbo\ . So make the path change to something like D:\TC\include and D:\TC\lib respectively )

How to start TurboC++ in the DOSBox automatically:

You can save yourself some time by having DOSBox automatically mount your folders and start TurboC++:

For DOSBox versions older then 0.73 browse into program installation folder and open the dosbox.conf file in any text editor. For version 0.73 go to Start Menu and click on “Configuration” and then “Edit Configuration“. Then scroll down to the very end, and add the lines which you want to automatically execute when DOSBox starts.

Automatically mount and start Turbo C++3.0 in DOSBox ver 0.73:



Scroll down to the very end, and add the lines:



Those commands will be executed automatically when DOSBox starts!

Please note:

Full screen: Alt and Enter

When you exit from the DosBox [precisely when u unmount the virtual drive where Turbo C++ 3.0 has been mounted] all the files you have saved or made changes in Turbo C++ 3.0 will be copied into the source directory(The directory which contains TC folder)

Don’t use shortcut keys to perform operations in TC because they might be a shortcut key for DOSBOX also . Eg : Ctrl+F9 will exit DOSBOX rather running the code .

VIDEO tutorial (there is another setup – original path to Turbo C++ is h:\tc\ and drive H is mounted as drive C:)

Windows Server 2008 R2 Evaluation Virtual Hard Drive Images for Hyper-V (180 Days)

Files in this download

The links in this section correspond to files available for this download. Download the files appropriate for you.

Windows Server 2008 R2 Enterprise Evaluation (Full Edition).exe
1.0 GB DOWNLOAD

Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part01.exe
500.0 MB DOWNLOAD

Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part02.rar
500.0 MB DOWNLOAD

Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part03.rar
500.0 MB DOWNLOAD

Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part04.rar
500.0 MB DOWNLOAD

Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part05.rar
37.0 MB DOWNLOAD

Windows Server 2008 R2 Enterprise Evaluation (Server Core).exe 

706.0 MB DOWNLOAD

Overview

The Microsoft VHD format is the common virtualization file format for Hyper-V that provides a uniform product support system, and provides more seamless manageability, security, reliability and cost-efficiency for customers.

This VHD release is available in English only and is for evaluation and testing purposes. Evaluating any version of Windows Server 2008 R2 software does not require entering a product key, however will require activation within 10 days. Failing to activate the evaluation will cause the licensing service to shut the machine down every hour (The 10 day activation period can be reset four (4) times by using the rearm command. See below for further information on activation rearm). Once activated, the evaluation will run for 180 days. After this time, you will need to uninstall the evaluation software and reinstall a fully-licensed version of Windows Server 2008 R2.

As this installation requires Hyper-V, you will need to have a base install of Windows Server 2008 (64-bit edition) or Windows Server 2008 R2, running Hyper-V. For more information on obtaining and installing the latest version of Hyper-V, please visit the Hyper-V Homepage.

Both virtual machines available here are running Windows Server 2008 R2 Enterprise Edition Evaluation. One is the default full installation, and the other has been configured as a default Core installation. For more information on the difference between full and core installation please see the Windows Server 2008 Editions Overview pages. For download options please see the IMAGE SELECTION section in the instructions below.

As both virtual machines do not have anti-virus installed, they should not be connected to any network until it has anti-virus installed.

System requirements

Supported Operating Systems: Windows Server 2008 R2

Required Software: Windows Sever 2008 or Windows Server 2008 R2 installed with Hyper-V*
Processor: 2.0 GHz or faster (x64) Hardware Assisted Virtulization Required
Disk Space: At least 10.0 GB of free disk space
RAM: 2.5 GB of available physical RAM**

*The VM images themselves are 64bit images and as such you will need to determine 32bit application compatibility for the applications you may wish to install.

* *The amount of physical RAM depends on what applications are running on the Server. You can use the Task Manager to identify how much physical RAM is available on your machine. Running applications other than Hyper-V will consume available physical RAM.

Instructions

Using the Windows Server 2008 R2 VHD with Hyper-V

1. On your computer, install Windows Server 2008 or Windows Server 2008 R2 and Microsoft Hyper-V. Detailed instructions on how to install the latest version of Microsoft Hyper-V can be found here: http://www.microsoft.com/windowsserver2008/virtualization/install.mspx
2. Download the files required. There are 2 different images (Windows Server 200 R2 Enterprise Full Installation and Windows Server R2 Enterprise Server Core Installation), and 2 ways to download them based on your current internet connection – see IMAGE SELECTION section below for further information.
3. When you have installed Hyper-V and extracted the VHD files, copy the VHD file to a pre-selected location (recommended default location C:\Users\Public\Documents\Microsoft Hyper-V\Virtual Hard Disks)
4. Open Hyper-V Manager. Click Start, point to Administrative Tools, and then click Hyper-V Manager.
5. From the Action pane, click New, and then click Virtual Machine.
6. From the New Virtual Machine Wizard, click Next.
7. On the Specify Name and Location page, specify what you want to name the virtual machine and where you want to store it. (you can keep this as default location for ease).
8. On the Memory page, specify enough memory to run the guest operating system you want to use on the virtual machine (Recommendation at least 2Gb).
9. On the Networking page, connect the network adapter to an existing virtual network if you want to establish network connectivity at this point.
10. On the Connect Virtual Hard Disk page, select “Use and existing virtual hard disk”, and browse to the location you copied the VHD file to in step 3 above.
11. Select finish (you can also start the VHD at this time, however we recommend you create a snapshot before you start the VHD for the first time).
12. To logon to the machine, use the following credentials:
• Username: administrator, password: Pass@word1 (Administrator account)

IMAGE SELECTION

To make is easier to download the VHD images, we have created 2 different ways to download the files. You have the choice of downloading the entire compressed files as one image, or as a multi-part archive (All images are self-extracting archives). Below is the session legend (you can also download these files by right-clicking on them and saving them to your system).

Windows Server 2008 R2 Enterprise Evaluation (Full Edition)

Single Image

1. Windows Server 2008 R2 RC Enterprise Evaluation (Full Edition)

Multi-part Image

1. Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part01.exe
2. Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part02.rar
3. Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part03.rar
4. Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part04.rar
5. Windows Server 2008 R2 Enterprise Evaluation (Full Edition).part05.rar

Windows Server 2008 R2 Enterprise Evaluation (Server Core)

Single Image Only

1. Windows Server 2008 R2 Enterprise Evaluation (Server Core).exe

Additional information

Please refer to the documents below for further information

Installing Windows Server 2008 R2

Windows Server 2008 R2 Release Notes

How to manually rearm the 10 day activation grace period
When the initial 10-day activation period nears its end, you can run the Slmgr.vbs script to reset it back to 10 days. To do this, follow these steps:

1. Click Start, and then click Command Prompt.

2. Type slmgr.vbs -dli, and then press ENTER to check the current status of your activation period.

3. To reset the activation period, type slmgr.vbs –rearm, and then press ENTER.

4. Restart the computer.

This resets the activation period to 10 days, and can be used up to four times. After this you will need to either activate or reinstall 

How to install Windows Server 2008 without activating it and extend the evaluation period

How to install Windows Server 2008 without activating it

1. Run the Windows Server 2008 Setup program.
2. When you are prompted to enter a product key for activation, do not enter a key. Click No when Setup asks you to confirm your selection.
3. You may be prompted to select the edition of Windows Server 2008 that you want to evaluate. Select the edition that you want to install.
   
   Note After Windows Server 2008 is installed, the edition cannot be changed without reinstalling it.
4. When you are prompted, read the evaluation terms in the Microsoft Software License Terms, and then accept the terms.
5. When the Windows Server 2008 Setup program is finished, your initial 60-day evaluation period starts. To check the time that is left on your current evaluation period, run the Slmgr.vbs script that is in the System32 folder. Use the -dli switch to run this script. The slmgr.vbs -dli command displays the number of days that are left in the current 60-day evaluation period.

How to manually extend the evaluation period

When the initial 60-day evaluation period nears its end, you can run the Slmgr.vbs script to reset the evaluation period. To do this, follow these steps:

1. Click Start, and then click Command Prompt.
2. Type slmgr.vbs -dli, and then press ENTER to check the current status of your evaluation period.
3. To reset the evaluation period, type slmgr.vbs –rearm, and then press ENTER.
4. Restart the computer.

This resets the evaluation period to 60 days.

Back to the top

How to automate the extension of the evaluation period

You may want to set up a process that automatically resets the evaluation period every 60 days. One way to automate this process is by using the Task Scheduler. You can configure the Task Scheduler to run the Slmgr.vbs script and to restart the server at a particular time. To do this, follow these steps:

1. Click Start, point to Administrative Tools, and then click Task Scheduler.
2. Copy the following sample task to the server, and then save it as an .xml file. For example, you can save the file as Extend.xml.

   
   
     
       2007-09-17T14:26:04.433
       Microsoft Corporation
     
     
       
         
           P31D
           false
         
         2007-10-05T02:23:24
         2008-09-17T14:23:24.777
         true
       
     
     
       
         domain\alias
         Password
         HighestAvailable
       
     
     
       
         PT10M
         PT1H
         true
         false
       
       IgnoreNew
       true
       true
       true
       false
       false
       true
       true
       false
       false
       true
       P3D
       PT0S
       7
       
         PT1M
         3
       
     
     
       
         C:\Windows\System32\slmgr.vbs
         -rearm
       
       
         C:\Windows\System32\shutdown.exe
         /r
       
     
   
   
   

3. In the sample task, change the value of the following “UserID” tag to contain your domain and your alias:
   domain\alias
4. In the Task Scheduler, click Import Task on the Action menu.
5. Click the sample task .xml file. For example, click Extend.xml.
6. Click Import.
7. Click the Triggers tab.
8. Click the One Time trigger, and then click Edit.
9. Change the start date of the task to a date just before the end of your current evaluation period.
10. Click OK, and then exit the Task Scheduler.

The Task Scheduler will now run the evaluation reset operation on the date that you specified.

How to make bootable pen drive with iso image

1. Download and install UltraISO trial.

2. Plug in your pen drive.

3. Open UltraISO as Administrator (right-click shortcut, "Run as Administrator")

4. Open the CD/DVD image file you want to write to pendrive in this instance of UltraISO (File>Open).

5. Under the Bootable menu, select Write Disk Image.

6. A new dialog should open up, listing your pen drive(s).

7. Select the pendrive you want to write your image to.

8. Set the Write Method to USB-HDD (or USB-HDD+ if your BIOS supports it).

9. Click the Write button, and then click Yes/OK in the warning dialog (All data on this drive will be destroyed ....... do you want to continue) that pops up.

8. relax and enjoy the Tip.


Download Link For UltraISO

Windows Server 2003 MCSE training videos have been developed by a few of the best Microsoft trainers

Video Contents:-

01) Windows Server 2003 - Active Directory Installation
02) Windows Server 2003 - Active Directory Users and Computer Management
03) Windows Server 2003 - DHCP Client Configuration
04) Windows Server 2003 - DHCP Server Address Leases
05) Windows Server 2003 - DHCP Server Configuration
06) Windows Server 2003 - DNS Server Configuration
07) Windows Server 2003 - DNS Server Forwarder Configuration
08) Windows Server 2003 - File Server & Shadow Copy
09) Windows Server 2003 - IIS Server Configuration
10) Windows Server 2003 - IIS Server Installation
11) Windows Server 2003 - Logging into an Windows Server 2003 Domain
12) Windows Server 2003 - Mail Server Installation
13) Windows Server 2003 - Mail Server Test
14) Windows Server 2003 - Print Server Configuration
15) Windows Server 2003 - RAS Server Configuration
16) Windows Server 2003 - Streaming Media Server Installation
17) Windows Server 2003 - Streaming Media Server Configuration I
18) Windows Server 2003 - Streaming Media Server Configuration II
19) Windows Server 2003 - Terminal Server Installation
20) Windows Server 2003 - Terminal Server Usage
21) Windows Server 2003 - WINS Server