While avoiding terminology such as “pirated” and “counterfeit,” WGA Notifications will provide end users running Windows XP copies detected as non-genuine with the necessary information and assistance for them to get valid licenses for the operating system.

“Windows Genuine Advantage Notifications notifies you if a copy of Microsoft Windows XP is not genuine. The notification messages only appear on computers that have failed the Windows Genuine Advantage validation process and that are running a copy of Windows XP that is not genuine. If you are running a validated, genuine copy of Windows XP, you will not receive notification messages,” reads an excerpt from the tools description.

Microsoft has failed to reveal the changes, if any, implemented in the WGA Notifications update, but the WindowsXP-KB905474-ENU-x86.exe file has gone live on the Download Center on August 25, and in this context it is different from the WindowsXP-KB905474-ENU-x86-Standalone.exe release dating back to early 2007. The only visible difference is in terms of the supported operating systems where Windows XP SP2 is featured alongside XP SP3.

With the release of Service Pack 3 for Windows XP, Microsoft has adapted the installation process and activation mechanism of the platform to match that of Windows Vista. Not only are XP SP3 users installing the client no longer required to enter the product key during the deployment phase, but the product now benefits from a 30-day activation-free trial period.

Windows Genuine Advantage Notifications is available for download here.

Related posts

• Black Screen of Death for XP SP3 and Vista SP1 (2)
• XP SP3, Some Problems Emerge (1)
• XP SP3 Can Kill All Update Installations (0)
• Windows XP SP3 RTM Multilingual User Interface (MUI) Pack (3)
• Windows XP SP3 Release Candidate RC2 (0)
• Windows SteadyState for Vista and XP (1)
• Windows PowerShell 1.0 for XP SP3 (0)
• How to remove Windows is not genuine notification (0)
• How Does Windows Product Activation Work (1)
• XP virtual computing avoids dual-boot complexity (0)
• Windows XP SP3 RTM Symbols Package (1)
• Windows XP Service Pack 3 FINAL (2)
• Windows Vista: An FAQ for Nonprofits (0)
• Windows Search 4.0 (0)
• Windows PowerShell V2 CTP2 (0)
• Windows Malicious Software Removal Tool (0)
• Will SP3 Save Windows XP? (1)
• WGA Phones Home When Canceled (0)
• Vista SP1 Solution Accelerator (1)
• Troubleshoot Failed Installations of XP SP3 RTM Build 5512 (0)
• The First Update for XP SP3 RTM (0)
• Make Room for Windows XP SP3 (0)
• Free Vista SP1 and XP SP3 Support (0)
• Download Windows XP SP3 RTM Build 5512 (1)
• Download Windows Vista Recovery Disc (1)

Related posts

• February 2008 Popular Tips for PcTipsBox - TOP10 (0)
• Windows PowerShell 1.0 for XP SP3 (0)
• April 2008 Popular Tips for PcTipsBox - TOP10 (0)
• Windows Vista: An FAQ for Nonprofits (0)
• Windows PowerShell V2 CTP2 (0)
• Windows Malicious Software Removal Tool (0)
• Download Windows Firewall with Advanced Security (4)
• Windows XP SP3 RTM Multilingual User Interface (MUI) Pack (3)
• Windows XP SP3 Release Candidate RC2 (0)
• Windows Vista and Malware Immunity (0)
• Vista SP1 Solution Accelerator (1)
• Uninstalling Internet Explorer 8 (0)
• Tweak Vista with Some Usefull Rundll32 Commands For Windows vista (0)
• Troubleshoot Failed Installations of XP SP3 RTM Build 5512 (0)
• TOP10 - June 2008 Popular Tips (1)
• The Vista Built-in Super Administrator Account Has Survived in Vista SP1 (1)
• Speed Up Windows Vista Network Performance with TCP Windows Tuning (2)
• SP3 Automatic Distribution for Office 2003 (1)
• See all Computers from your Workgroup without Windows Freezing (0)
• Microsoft Offers TCP/IP Fundamentals for Windows (0)
• March 2008 TOP10 Tips from Pctipsbox (0)
• Make your computer dual-boot Vista and XP (6)
• How to Perform Disk Defragment Windows Vista from the Command Line (0)
• How to Make XP Last You a Long Time (1)
• Dual-booting XP deletes Vista restore points (1)

The WPA Process

When you enter the product key three identifiers are generated and collected:

* Hardware ID: A unique identifier that’s generated from information gathered about the computer’s hardware.

* Product ID: A 25-character unique key supplied when you purchase Windows Vista.

* Installation ID: An identifier Windows Vista creates from the hardware ID and product ID.

During the WPA process the product and hardware IDs are sent to Microsoft and the computer is “activated”.

If you make significant hardware changes (like replacing the motherboard and graphics card at the same time) you’ll have to re-activate your copy of Windows Vista.

Note: You don’t have to activate Windows Vista during the first 30 days of use.

If you’re installing Windows Vista I highly suggest not choosing to automatically activate Windows Vista during the installation. You should wait the full 30 days to make sure all of the hardware is properly working before activating.

Related posts

• XP virtual computing avoids dual-boot complexity (0)
• Windows Vista: An FAQ for Nonprofits (0)
• Verify you have signed drivers (2)
• Uninstalling Vista Product Keys Activates the Platform’s Kill Switch (0)
• Make Room for Windows XP SP3 (0)
• How to dual boot Vista with Ubuntu (1)
• Windows Vista Reduced Functionality Mode Triggers (1)
• Windows Vista Hardware Compatibility List (0)
• Windows Vista Hardware Assessment Network Tool (0)
• Windows Vista Hardware Assessment (0)
• Windows Vista Hack: Run Vista legally for a year without activation (0)
• Windows Vista Does Not Play Well with Networks (0)
• Windows Vista and Malware Immunity (0)
• Windows Malicious Software Removal Tool (0)
• Windows logs off automatically while login (0)
• Vista SP1 Performance Analysis Tools (1)
• Vista Presents Erroneous Scores for Hardware Configurations (0)
• Vista Machines with More than 4 GB of RAM Have Limited Shut-Down (2)
• Vista iPod Patch Released (0)
• Use Any USB Drive With Windows Vista Readyboost (2)
• Top Reasons to Stick with Vista (1)
• Six Caveats – 64-bit Windows Vista (1)
• Seven Tips to Manage Your Files Better (1)
• Remove spyware from your computer (0)
• Remove Old Files After Vista SP1 Installation (0)

SP1 may have stopped a couple of the hacks being used to get around activation, but that hasn’t stopped the hackers. Vista Loader apparently works on Vista SP1.

Post from: ITsVISTA

Vista Loader 2.1.3 Windows Vista Activator 2008 Support SP1 with No Boot String Free Download » My Digital Life

Related posts

• Windows Vista SP1 RC Refresh Available to Public
• KB937769
• Fixing Windows Vista, one machine at a timeE
• An investigation of GUI changes found in Windows Vista SP1
• Vista upgrade is mostly behind-the-scenes fixes

Post from: ITsVISTA

ITsVISTA Web Links: April 11th

Related posts

• ITsVISTA Web Links: October 1st, 2007
• ITsVISTA Web Links: July 5th, 2007
• KB941020
• Dell’s Windows Vista vs XP differences video
• KB950167

Post from: ITsVISTA

ITsVISTA Web Links: April 4th

Related posts

• ITsVISTA Web Links: March 4th
• KB935427
• ITsVISTA Web Links: May 18th, 2007
• ITsVISTA Web Links: June 18th, 2007
• ITsVISTA Web Links: July 31st, 2007

Post from: ITsVISTA

ITsVISTA Web Links: March 3rd

Related posts

• Improve Vista’s Disk Performance by 15% without SP1
• Living with Vista press coverage @ CES
• ITsVISTA Web Links: February 24th
• ITsVISTA Web Links: October 23rd, 2007
• KB944155

How to extend the Windows Server 2008 evaluation period
http://support.microsoft.com/kb/948472

This is quoted from the article:

SUMMARY

This article describes how to extend, or re-arm, the Windows Server 2008 evaluation period. The evaluation period is also known as the "activation grace" period. These instructions apply to any edition of Windows Server 2008. This includes evaluation copies.

INTRODUCTION

Evaluating Windows Server 2008 software does not require product activation. Any edition of Windows Server 2008 may be installed without activation, and it may be evaluated for 60 days. Additionally, the 60-day evaluation period may be reset (re-armed) three times. This action extends the original 60-day evaluation period by up to 180 days for a total possible evaluation time of 240 days.
Note Although you can reset the 60-day evaluation period, you cannot extend it beyond 60 days at any time. When you reset the current 60-day evaluation period, you lose whatever time is left on the previous 60-day evaluation period. Therefore, to maximize the total evaluation time, wait until close to the end of the current 60-day evaluation period before you reset the evaluation period.

MORE INFORMATION

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.

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.

<?xml version="1.0" encoding="UTF-16"?><Task version="1.2" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">  <RegistrationInfo>    <Date>2007-09-17T14:26:04.433</Date>    <Author>Microsoft Corporation</Author>  </RegistrationInfo>  <Triggers>    <TimeTrigger id="18c4a453-d7aa-4647-916b-af0c3ea16a6b">      <Repetition>        <Interval>P59D</Interval>        <StopAtDurationEnd>false</StopAtDurationEnd>      </Repetition>      <StartBoundary>2007-10-05T02:23:24</StartBoundary>      <EndBoundary>2008-09-17T14:23:24.777</EndBoundary>      <Enabled>true</Enabled>    </TimeTrigger>  </Triggers>  <Principals>    <Principal id="Author">      <UserId>domain\alias</UserId>      <LogonType>Password</LogonType>      <RunLevel>HighestAvailable</RunLevel>    </Principal>  </Principals>  <Settings>    <IdleSettings>      <Duration>PT10M</Duration>      <WaitTimeout>PT1H</WaitTimeout>      <StopOnIdleEnd>true</StopOnIdleEnd>      <RestartOnIdle>false</RestartOnIdle>    </IdleSettings>    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>    <AllowHardTerminate>true</AllowHardTerminate>    <StartWhenAvailable>false</StartWhenAvailable>    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>    <AllowStartOnDemand>true</AllowStartOnDemand>    <Enabled>true</Enabled>    <Hidden>false</Hidden>    <RunOnlyIfIdle>false</RunOnlyIfIdle>    <WakeToRun>true</WakeToRun>    <ExecutionTimeLimit>P3D</ExecutionTimeLimit>    <DeleteExpiredTaskAfter>PT0S</DeleteExpiredTaskAfter>    <Priority>7</Priority>    <RestartOnFailure>      <Interval>PT1M</Interval>      <Count>3</Count>    </RestartOnFailure>  </Settings>  <Actions Context="Author">    <Exec>      <Command>C:\Windows\System32\slmgr.vbs</Command>      <Arguments>-rearm</Arguments>    </Exec>    <Exec>      <Command>C:\Windows\System32\shutdown.exe</Command>      <Arguments>/r</Arguments>    </Exec>  </Actions></Task>

3. In the sample task, change the value of the following “UserID” tag to contain your domain and your alias:

<UserId>domain\alias</UserId>

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.

-

“Activation, also known as Microsoft Product Activation or Windows Product Activation, is an anti-piracy technology designed to verify that Microsoft software products are legitimately licensed. Activation works by verifying that the product key the 25-character code located on your Certificate of Authenticity (usually affixed to your computer) or proof of license label (usually affixed to the installation disc case) is authentic and is not in use on more personal computers than are permitted by the software license”, reads a fragment of the Windows Vista Activation FAQ. (more…)