Search in uioop.blogspot.com

Wednesday, August 20, 2008

How to Automatically Rearm and Extend Activation Grace Period in Windows Vista and Server 2008

Windows Vista and Windows Server 2008 has free activation grace period which allows user to install and use the operating system for 120 days and 240 days without product key or product activation completed. The initial grace period given is 30 days and 60 days respectively for Windows Vista and Server 2008, and user has to “rearm” the system when the expiration of grace period is nearly ending in order to reset and extend the trial evaluation period, and hence activation grace period again.

Neither Windows Vista nor Windows Server 2008 display prominently when is the activation-free evaluation grace period ends (even though it’s actively reminding user to activate Windows with information on how many days left to activate, which usually ignored by users). Surely you don’t want a warning dialog message box pops up suddenly to notify that you may be victim of counterfeiting or to activate the system now, especially if your notebook/laptop computer is used for business presentation. System administrators also certainly don’t want to face with uncertainty or instability possibly brought by expiry of activation grace period, especially if the server is running critical processes, applications or databases.

Instead of remembering the activation grace period expiry or ending date to manually rearm and reset activation grace period in Windows Vista and Windows Server 2008, Microsoft provides the following script which can be used with Task Scheduler to schedule automatic extension of the evaluation period and activation-bypass grace period of Windows Server 2008 every 60 days, which should be able to used in Windows Vista too which requires to be triggered every 30 days.

How to Automate the Rearm and Extension of the Activation Grace Period in Windows Server 2008 and Vista

On the Windows Vista or Windows Server 2008 system, copy and paste the following Task code to text editor such as Notepad. In the Task, change the value of the following UserID tag (as in domain\alias line) to contain domain name and user name alias (for user on domain Active Directory), or local host name and user ID (for standalone Windows Vista user). Then save it as a .xml file. For example, ReArm.xml or 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 (My Digital Life)</Author>
</RegistrationInfo>
<Triggers>
<TimeTrigger id="18c4a453-d7aa-4647-916b-af0c3ea16a6b">
<Repetition>
<Interval>P31D</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>

Or, download a copy of ReArm.xml directly (you still need to change the “UserID”.

  1. Click Start, point to Administrative Tools (in Windows Vista, go to Control Panel -> System and Maintenance), and then click Task Scheduler.
  2. In the Task Scheduler, click Import Task on the “Action” menu.
  3. Select the task .xml file saved from above above. For example, click Extend.xml or ReArm.xml.
  4. Click Import.
  5. A “Create Task” window will appear. Click the Triggers tab.

    Schedule Automatic Rearm Activation Grace Period

  6. Click the One Time trigger, and then click Edit.
  7. Change the start date of the task to a date just before the end of current evaluation period (activation grace period expiry date).

    User can also customize the schedule so that the Task Scheduler automates the rearm of system license status every 30 days (for Windows Vista) or 60 days (for Windows Server 2008) for 3 times. For example, change to Daily with recurring every 30 or 60 days, and then set an Expire date for the task after 120 days or 240 days.

  8. Click OK, and then exit the Task Scheduler.

The Task Scheduler will now run the evaluation reset and rearm operation on the date that been specified automatically to extend the free usage of Windows operating system.

Extend Vista or Windows Server 2008 Activation-free Evaluation Period

http://www.mydigitallife.info/2008/06/08/how-to-install-and-use-windows-server-2008-240-days-for-free/

http://support.microsoft.com/kb/948472

How to manually extend the activation grade period on expiring

When the 60-day activation grace period is about to expire and end, run the slmgr.vbs script to reset and extend the evaluation period for another new 60-day trial evaluation period, with everything including programs installed and data intact.

  1. Open an elevated privilege command prompt.
  2. Type the slmgr.vbs -rearm, and then press Enter to reset the activation grace period to 60 days.
  3. Restart the computer.

To check the status or time that is left on current activation grace period or evaluation period, run slmgr.vbs -dli command to display the number of days that are left in the current 60-day evaluation period.

DisableNum Lock Auto On once XP Login

HKEY_USERS\Default\Control Panel\Keyboard\

* HKEY_CURRENT_USER\Control Panel\Keyboard\

Within the Keyboard key there should be a string called InitialKeyboardIndicators. The possible values for this string are:

* 0 = Num Lock is turned off once you login
* 1 = Disable Num Lock
* 2 = Num Lock is turned on once you login

Wednesday, August 6, 2008

PC able to power on but no display

PC able to power it on. CD rom is working, HDD is working but Monitor no display.
-tried to re-seat RAMs,
-graphic card is on board and had tried insert a PCI graphic card on the board.
-swapped power supply.
-took out cmos battery.
But problem still remain.

-Let the PC rest 20min later, and able to have display but after restart the system problem occurring again.
-suspect on board graphic card faulty.
-after changing the motherboard everything is fine.

Tuesday, July 22, 2008

NTLDR is Missing Error Resolution

http://pcsupport.about.com/od/findbyerrormessage/a/ntldrmissingxp.htm

Fixes for NTLDR Errors

  1. Restart the PC. The NTLDR error could be a fluke.

  2. Check your floppy and optical (CD/DVD) drives for media. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk or CD/DVD.

    Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive is listed first.

  3. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors. There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.

  4. Restore the NTLDR and ntdetect.com files from the Windows XP CD. Restoring these two important system files from the original Windows XP CD may do the trick.

  5. Repair or replace the boot.ini file. This will prevent the NTLDR error if the cause of the problem is a boot.ini file that is not configured properly for your Windows XP installation.

  6. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the "NTLDR is Missing" error.

  7. Repair the Windows XP master boot record. NTLDR error messages may also appear if the master boot record is corrupt.

  8. Open your computer's case and ensure that the cable that connects the hard drive to the motherboard is firmly in place. If this does not resolve the issue, try replacing the cable. NTLDR error messages could be caused by loose or malfunctioning IDE cables.

  9. Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.

  10. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.

  11. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch. While this will almost certainly resolve any NTLDR errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.

    If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.

  12. Finally, if all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive. Replace the hard drive and then perform a new installation of Windows XP.

AVG Internet Security 2013

Total Pageviews

Contributors