NTFS Partition
Click the Start button, point to Settings, click Control Panel, and then double-click Services.
Select the EventLog service and click Startup. Change the Startup Type to Disabled, and then click OK. If you are unable to log on to the computer but can access the registry remotely, you can change the Startup value in the following registry key to 0x4:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog
Restart Windows.
NOTE: When the system starts up, several services may fail; a message informing the user to use Event Viewer to review errors may appear.
Rename or move the corrupt *.evt file from the following location:
%SystemRoot%\System32\Config
In Control Panel Services tool, re-enable the EventLog service by setting it back to the default of Automatic startup, or change the registry Startup value back to 0x2.
Back to the top
FAT partition (Alternative method)
Boot to a MS-DOS prompt using a DOS bootable disk.
Rename or move the corrupt *.evt file from the following location:
%SystemRoot%\System32\Config
Remove the disk and restart Windows.
When Windows is restarted, the Event Log file will be recreated.
Thursday, March 25, 2010
Wednesday, March 24, 2010
Hack to Activate Office 2010 RC (RTM Escrow) With Free Product Key
Before you are installing office 2010 RC,We need to follow the below steps or else we can install office 2007 and we can upgrade it to office 2010 Rc(key not required for this procedure)
nullMicrosoft does not invite many people to join the official MS Office 2010 RC (Release Candidate) beta testing program in Connect website. For people who downloads and installs Office Professional 2010 RC (RTM Escrow) build 14.0.4734.1000 for volume licensing distribution channel, it’s possible to install the Office 2010 without any product key. For user who wants to activate the installed Office 2010, which may become the final RTM version (the RTM version is now rumored to be build 14.0.4740.1000), here’s the trick or hack on how to activate Office 2010 RC.null
The workaround to crack Office 2010 activation as detailed below works by replacing the unactivated tokens.dat and pkeyconfig-office.xrm-ms, with activated version, which provided for free by Microsoft for Office 2010 Beta program. The free product key for Office 2010 Beta is a MAK type (Multiple Activation Key), which is now required to activate volume licensing version of Office 2010 products.
One benefit of using MAK to activate a Microsoft product is that, the system does not required to update or refresh its activation status, internally or externally against any activation servers. The convenience is provided from computers, such as laptops or notebooks, which does not connected to the corporate network persistently or consistently. Reactivation is only required when there is a hardware change. Best of all, if for any reason the software product which has received a MAK product key loses activation or fails validation, its functionality is not limited or restricted. Only nagging notifications will appear, which will disappear when the product is activated again.
Furthermore, the time bomb, which renders the pre-release Office 2010 useless after an expiry date does not exist in the leaked volume or Select versions of Office 2010. So, the activated Office 2010 RC (RTM Escrow) will likely to stay activated forever, even if it’s been activated with license files from the beta.
1.If there is any existing Office 2010 been installed, uninstall it, then reboot the system.
2.Download and install official Microsoft Office 2010 Beta (the version of Office 2010 suites to install is Office Professional 2010 Beta build 14.0.4536.1000, and must be the same system architecture of x86 or x64 that intends to be installed at RC, i.e. 32-bit Office 2010 Beta activation files will activate 32-bit Office 2010 RC/RTM while 64-bit Office 2010 Beta activation files will activate 64-bit Office 2010 RC/RTM).
While at the Office 2010 Beta page, register and request for a free product key (which is a MAK – Multiple Activation Key) for Office 2010 to activate the installed Office Professional 2010 Beta over Internet against Microsoft’s activation key.
3.Once Office Professional 2010 Beta has been installed and activated, copy the pkeyconfig-office.xrm-ms file from the following folder to another folder location for safekeeping:
%ProgramFiles%\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\
Tip: User who installs 32-bit Office 2010 in 64-bit OS should find the file at %ProgramFiles(x86)%\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\ folder.
4.Also copy and save the tokens.dat file in the following folder to another but same folder location as above for safekeeping (for Windows Vista, Windows 7 and Windows Server):
%ProgramData%\Microsoft\OfficeSoftwareProtectionPlatform\
In Windows XP, it’s located here:
%AllUsersProfile%\Microsoft\OfficeSoftwareProtectionPlatform\
5.After copying above two files, uninstall the installed Office 2010 Beta product.
6.Download and install Office 2010 RC (RTM Escrow) for corporate volume licensing distribution channel.
7.Download ActivateOffice2010beta.7z script by SoLoR from MDL forum.
8.Extract the activate.cmd script from the archive and place the file inside the same folder with the two saved tokens.dat and pkeyconfig-office.xrm-ms files in steps above.
9.Edit the activate.cmd file with any text editor, and the modify the following line to include the Office 2010 MAK product key used to activate the beta version:
cscript “%PROGRAMFILES%\Microsoft Office\Office14\ospp.vbs” /inpkey:GVFBT-K6Q6T-HTX3P-C4K7G-7V2FR
Replace the GVFBT-K6Q6T-HTX3P-C4K7G-7V2FR in the line above to own personalized Office 2010 MAK product key.
10.Run a console command prompt as administrator.
11.Change directory to the folder with three files mentioned above – activate.cmd, tokens.dat and pkeyconfig-office.xrm-ms.
12.Execute the activate.cmd.
The script will automate the process to take ownership and grant full access permissions on tokens.dat and pkeyconfig-office.xrm-ms, and then replace the files with activated copy. It then calls the ospp.vbs via cscript engine to re-input the product key for Office 2010 and activate the full version product:
cscript “%PROGRAMFILES%\Microsoft Office\Office14\ospp.vbs” /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript “%PROGRAMFILES%\Microsoft Office\Office14\ospp.vbs” /act
13.The Office 2010 should be activated. To check activation status of Office 2010, run the following command:
cscript “%PROGRAMFILES%\Microsoft Office\Office14\ospp.vbs” / dstatus
How to Activate Microsoft Visio 2010 and Project 2010
Visio 2010 and Project 2010 are using the same tokens.dat for activation status. As such, just install the Viso 2010 Beta and Project 2010 Beta and activate them before performing steps above.
Tip: For user who has problem activating Office 2010 RC or RTM Escrow after following steps above, try to delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform registry key after uninstalling Office 2010 Beta.
Tip: The data inside tokens.dat file is generated based on the hardware configuration, so it will be different on each PC. If you intend to activate Office 2010 with crack method above, backup the tokens.dat from each PCs you intend to do so.
The MS Office 2010 activation crack is likely able to crack and activate Office 2010 RTM build. As the method has been revealed, it’s likely that Microsoft will fix the loophole before releasing the final RTM version of Office 2010. Thus, the RTM build version of Office 2010 is unlikely to stay at 14.0.4734.1000, especially when the target RTM data to be around April.
Have a Great Day!!!!!!!
Satish.P
nullMicrosoft does not invite many people to join the official MS Office 2010 RC (Release Candidate) beta testing program in Connect website. For people who downloads and installs Office Professional 2010 RC (RTM Escrow) build 14.0.4734.1000 for volume licensing distribution channel, it’s possible to install the Office 2010 without any product key. For user who wants to activate the installed Office 2010, which may become the final RTM version (the RTM version is now rumored to be build 14.0.4740.1000), here’s the trick or hack on how to activate Office 2010 RC.null
The workaround to crack Office 2010 activation as detailed below works by replacing the unactivated tokens.dat and pkeyconfig-office.xrm-ms, with activated version, which provided for free by Microsoft for Office 2010 Beta program. The free product key for Office 2010 Beta is a MAK type (Multiple Activation Key), which is now required to activate volume licensing version of Office 2010 products.
One benefit of using MAK to activate a Microsoft product is that, the system does not required to update or refresh its activation status, internally or externally against any activation servers. The convenience is provided from computers, such as laptops or notebooks, which does not connected to the corporate network persistently or consistently. Reactivation is only required when there is a hardware change. Best of all, if for any reason the software product which has received a MAK product key loses activation or fails validation, its functionality is not limited or restricted. Only nagging notifications will appear, which will disappear when the product is activated again.
Furthermore, the time bomb, which renders the pre-release Office 2010 useless after an expiry date does not exist in the leaked volume or Select versions of Office 2010. So, the activated Office 2010 RC (RTM Escrow) will likely to stay activated forever, even if it’s been activated with license files from the beta.
1.If there is any existing Office 2010 been installed, uninstall it, then reboot the system.
2.Download and install official Microsoft Office 2010 Beta (the version of Office 2010 suites to install is Office Professional 2010 Beta build 14.0.4536.1000, and must be the same system architecture of x86 or x64 that intends to be installed at RC, i.e. 32-bit Office 2010 Beta activation files will activate 32-bit Office 2010 RC/RTM while 64-bit Office 2010 Beta activation files will activate 64-bit Office 2010 RC/RTM).
While at the Office 2010 Beta page, register and request for a free product key (which is a MAK – Multiple Activation Key) for Office 2010 to activate the installed Office Professional 2010 Beta over Internet against Microsoft’s activation key.
3.Once Office Professional 2010 Beta has been installed and activated, copy the pkeyconfig-office.xrm-ms file from the following folder to another folder location for safekeeping:
%ProgramFiles%\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\
Tip: User who installs 32-bit Office 2010 in 64-bit OS should find the file at %ProgramFiles(x86)%\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\ folder.
4.Also copy and save the tokens.dat file in the following folder to another but same folder location as above for safekeeping (for Windows Vista, Windows 7 and Windows Server):
%ProgramData%\Microsoft\OfficeSoftwareProtectionPlatform\
In Windows XP, it’s located here:
%AllUsersProfile%\Microsoft\OfficeSoftwareProtectionPlatform\
5.After copying above two files, uninstall the installed Office 2010 Beta product.
6.Download and install Office 2010 RC (RTM Escrow) for corporate volume licensing distribution channel.
7.Download ActivateOffice2010beta.7z script by SoLoR from MDL forum.
8.Extract the activate.cmd script from the archive and place the file inside the same folder with the two saved tokens.dat and pkeyconfig-office.xrm-ms files in steps above.
9.Edit the activate.cmd file with any text editor, and the modify the following line to include the Office 2010 MAK product key used to activate the beta version:
cscript “%PROGRAMFILES%\Microsoft Office\Office14\ospp.vbs” /inpkey:GVFBT-K6Q6T-HTX3P-C4K7G-7V2FR
Replace the GVFBT-K6Q6T-HTX3P-C4K7G-7V2FR in the line above to own personalized Office 2010 MAK product key.
10.Run a console command prompt as administrator.
11.Change directory to the folder with three files mentioned above – activate.cmd, tokens.dat and pkeyconfig-office.xrm-ms.
12.Execute the activate.cmd.
The script will automate the process to take ownership and grant full access permissions on tokens.dat and pkeyconfig-office.xrm-ms, and then replace the files with activated copy. It then calls the ospp.vbs via cscript engine to re-input the product key for Office 2010 and activate the full version product:
cscript “%PROGRAMFILES%\Microsoft Office\Office14\ospp.vbs” /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
cscript “%PROGRAMFILES%\Microsoft Office\Office14\ospp.vbs” /act
13.The Office 2010 should be activated. To check activation status of Office 2010, run the following command:
cscript “%PROGRAMFILES%\Microsoft Office\Office14\ospp.vbs” / dstatus
How to Activate Microsoft Visio 2010 and Project 2010
Visio 2010 and Project 2010 are using the same tokens.dat for activation status. As such, just install the Viso 2010 Beta and Project 2010 Beta and activate them before performing steps above.
Tip: For user who has problem activating Office 2010 RC or RTM Escrow after following steps above, try to delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform registry key after uninstalling Office 2010 Beta.
Tip: The data inside tokens.dat file is generated based on the hardware configuration, so it will be different on each PC. If you intend to activate Office 2010 with crack method above, backup the tokens.dat from each PCs you intend to do so.
The MS Office 2010 activation crack is likely able to crack and activate Office 2010 RTM build. As the method has been revealed, it’s likely that Microsoft will fix the loophole before releasing the final RTM version of Office 2010. Thus, the RTM build version of Office 2010 is unlikely to stay at 14.0.4734.1000, especially when the target RTM data to be around April.
Have a Great Day!!!!!!!
Satish.P
Tuesday, March 23, 2010
Sharepoint & Visual Studio 2010
Today, we officially announced that May 12th, 2010, is the launch date for SharePoint 2010 & Office 2010. In addition, we announced our intent to RTM (Release to Manufacturing) this April 12 2010.
It’s an exciting time for us! We hope you can virtually join us on May 12th at 11am EST to listen to Stephen Elop, President of the Microsoft Business Division, announce the launch. You can register for the event @ http://sharepoint.microsoft.com/businessproductivity/proof/pages/2010-launch-events.aspx
It’s an exciting time for us! We hope you can virtually join us on May 12th at 11am EST to listen to Stephen Elop, President of the Microsoft Business Division, announce the launch. You can register for the event @ http://sharepoint.microsoft.com/businessproductivity/proof/pages/2010-launch-events.aspx
MS OFFICE ERRORS
null
I understand that when you tried to open Outlook 2010 beta on the Windows 7 computer, you encountered the following error:
null
"Either there is not default mail client of the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client."
You tried to repair Office, but the problem persists.
Before we go further, I would like to confirm if you tried Ben’s suggestions to start Outlook in the safe mode. If we can start Outlook in the safe mode, the issue is caused by some third party add-ins in the Outlook program. We can try to disable them.
However, if the problem persists when trying to start Outlook in the safe mode, let’s continue.
First, let’s try to manually set Outlook 2010 as the default e-mail client on Windows 7:
Click Start.
Type "default programs" in the Start Search box.
Click Default Programs under Programs in the search results.
Now click Set your default programs.
Highlight Microsoft Office Outlook or Microsoft Outlook on the left.
Click Set this program as default.
Click OK.
Check the issue again. If the problem persists, this issue may occur when the Outlook registry is corrupted. Let’s try to remove the related registry and try to repair Office again.
===============
Click Start, in the Search box, type regedit, and then press ENTER.
In Registry Editor, locate the following subkey in the registry: HKEY_LOCAL_MACHINE\Software\Clients\Mail\Microsoft Outlook
Select the subkey, and then press DELETE.
Click Yes.
Quit Registry Editor.
Click Start, then click Control Panel.
Click Programs and Features.
Click the Office 2010 program that you want to repair, then click Change.
Click Repair, then click Continue. You might need to restart your computer after the repair is complete.
Can we open Outlook after this? If the problem persists, we might need to reinstall the Office program to resolve the issue.
PROCEDURE 2
An administrator can monitor the performance of their Outlook application by shutting down all other applications and then running the performance monitoring tool from the Task Manager which will show the CPU utilization and memory usage on the Performance tab. If the Task Manager is not available to an end user then get an administrator to follow these steps:
1.Press the Ctrl-Alt-Delete key sequence simultaneously.
2.Choose Task Manager.
3.Select the Performance tab.
You can also select the Processes tab to view all CPU and memory usages per process running on the system. Selecting the CPU or Memory headings from within the Process tab will allow an administrator to monitor the usages from high to low or from low to high based on the needs of the administrator.
An administrator might want to try opening Outlook in safe mode by using the following command with the forward slash safe argument:
C:Program FilesMicrosoft OfficeOFFICE11Outlook.exe / safe
In safe mode the add-ins are not running which is at least a workaround to allow your users to run their email application while preventing the potential issue of memory leaks. One way of determining if the add-ins are causing trouble is to start Outlook normally and then disable the add-ins one-by-one. An administrator can start Outlook, disable an add-in, restart Outlook and then monitor the memory for memory leaks. If no leaks are occurring then repeat the same procedure until an add-in has been identified. Once identified then remove that add-in permanently, install the previous add-ins and then report the problem to the respective author of the add-in.
Another diagnostic procedure to take would be to run all spyware applications and check for something out of the ordinary. This is why routine and regular maintenance of all software applications on the client is strongly recommended to prevent problems before they happen.
A less desirable approach is to completely uninstall Outlook and then re-install it so that they are operating with a clean application.
If your client is running an earlier version of Outlook such as Outlook 2000 then there was a patch (service pack 3 – SP3) which existed that fixed this memory leak problem. You can check the Microsoft Knowledge database for the following article: http://support.microsoft.com/?kbid=811167.
I understand that when you tried to open Outlook 2010 beta on the Windows 7 computer, you encountered the following error:null
"Either there is not default mail client of the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client."
You tried to repair Office, but the problem persists.
Before we go further, I would like to confirm if you tried Ben’s suggestions to start Outlook in the safe mode. If we can start Outlook in the safe mode, the issue is caused by some third party add-ins in the Outlook program. We can try to disable them.
However, if the problem persists when trying to start Outlook in the safe mode, let’s continue.
First, let’s try to manually set Outlook 2010 as the default e-mail client on Windows 7:
Click Start.
Type "default programs" in the Start Search box.
Click Default Programs under Programs in the search results.
Now click Set your default programs.
Highlight Microsoft Office Outlook or Microsoft Outlook on the left.
Click Set this program as default.
Click OK.
Check the issue again. If the problem persists, this issue may occur when the Outlook registry is corrupted. Let’s try to remove the related registry and try to repair Office again.
===============
Click Start, in the Search box, type regedit, and then press ENTER.
In Registry Editor, locate the following subkey in the registry: HKEY_LOCAL_MACHINE\Software\Clients\Mail\Microsoft Outlook
Select the subkey, and then press DELETE.
Click Yes.
Quit Registry Editor.
Click Start, then click Control Panel.
Click Programs and Features.
Click the Office 2010 program that you want to repair, then click Change.
Click Repair, then click Continue. You might need to restart your computer after the repair is complete.
Can we open Outlook after this? If the problem persists, we might need to reinstall the Office program to resolve the issue.
PROCEDURE 2
An administrator can monitor the performance of their Outlook application by shutting down all other applications and then running the performance monitoring tool from the Task Manager which will show the CPU utilization and memory usage on the Performance tab. If the Task Manager is not available to an end user then get an administrator to follow these steps:
1.Press the Ctrl-Alt-Delete key sequence simultaneously.
2.Choose Task Manager.
3.Select the Performance tab.
You can also select the Processes tab to view all CPU and memory usages per process running on the system. Selecting the CPU or Memory headings from within the Process tab will allow an administrator to monitor the usages from high to low or from low to high based on the needs of the administrator.
An administrator might want to try opening Outlook in safe mode by using the following command with the forward slash safe argument:
C:Program FilesMicrosoft OfficeOFFICE11Outlook.exe / safe
In safe mode the add-ins are not running which is at least a workaround to allow your users to run their email application while preventing the potential issue of memory leaks. One way of determining if the add-ins are causing trouble is to start Outlook normally and then disable the add-ins one-by-one. An administrator can start Outlook, disable an add-in, restart Outlook and then monitor the memory for memory leaks. If no leaks are occurring then repeat the same procedure until an add-in has been identified. Once identified then remove that add-in permanently, install the previous add-ins and then report the problem to the respective author of the add-in.
Another diagnostic procedure to take would be to run all spyware applications and check for something out of the ordinary. This is why routine and regular maintenance of all software applications on the client is strongly recommended to prevent problems before they happen.
A less desirable approach is to completely uninstall Outlook and then re-install it so that they are operating with a clean application.
If your client is running an earlier version of Outlook such as Outlook 2000 then there was a patch (service pack 3 – SP3) which existed that fixed this memory leak problem. You can check the Microsoft Knowledge database for the following article: http://support.microsoft.com/?kbid=811167.
Difference between Core i3, Core i5 and Core i7
Intel will stop selling Core 2 Duo and Core 2 Quad in 2010. Core is the new range of Intel processors.
Core i3:
* Entry level processor.
* 2-4 Cores
* 4 Threads
* Hyper-Threading (efficient use of processor resources)
* 3-4 MB Catche
* 32 nm Silicon (less heat and energy)
null
Core i5:
* Mid range processor.
* 2-4 Cores
* 4 Threads
* Turbo Mode (turn off core if not used)
* Hyper-Threading (efficient use of processor resources)
* 3-8 MB Catche
* 32-45 nm Silicon (less heat and energy)null
Core i7:
* High end processor.
* 4 Cores
* 8 Threads
* Turbo Mode (turn off core if not used)
* Hyper-Threading (efficient use of processor resources)
* 4-8 MB Catche
* 32-45 nm Silicon (less heat and energy)
Core i3:
* Entry level processor.
* 2-4 Cores
* 4 Threads
* Hyper-Threading (efficient use of processor resources)
* 3-4 MB Catche
* 32 nm Silicon (less heat and energy)
null
Core i5:
* Mid range processor.
* 2-4 Cores
* 4 Threads
* Turbo Mode (turn off core if not used)
* Hyper-Threading (efficient use of processor resources)
* 3-8 MB Catche
* 32-45 nm Silicon (less heat and energy)null
Core i7:
* High end processor.
* 4 Cores
* 8 Threads
* Turbo Mode (turn off core if not used)
* Hyper-Threading (efficient use of processor resources)
* 4-8 MB Catche
* 32-45 nm Silicon (less heat and energy)
Saturday, March 13, 2010
Windows Server Commands
netdom query fsmo ( for checking fsmo roles )
dcdiag ( checks the entire system services)
netsh dhcp
The DHCP service has detected that it is running on a DC and has no
credentials configured for use with Dynamic DNS registrations initiated by the
DHCP service. This is not a recommended security configuration. Credentials for
Dynamic DNS registrations may be configured using the command line "netsh dhcp server set dnscredentials" or via the DHCP Administrative tool.
Usage: netsh [-a AliasFile] [-c Context] [-r RemoteMachine] [-u [DomainName\]Use
rName] [-p Password | *]
[Command | -f ScriptFile]
The following commands are available:
Commands in this context:
? - Displays a list of commands.
add - Adds a configuration entry to a list of entries.
advfirewall - Changes to the `netsh advfirewall' context.
bridge - Changes to the `netsh bridge' context.
delete - Deletes a configuration entry from a list of entries.
dhcp - Changes to the `netsh dhcp' context.
dhcpclient - Changes to the `netsh dhcpclient' context.
dump - Displays a configuration script.
exec - Runs a script file.
firewall - Changes to the `netsh firewall' context.
help - Displays a list of commands.
http - Changes to the `netsh http' context.
interface - Changes to the `netsh interface' context.
ipsec - Changes to the `netsh ipsec' context.
lan - Changes to the `netsh lan' context.
nap - Changes to the `netsh nap' context.
netio - Changes to the `netsh netio' context.
ras - Changes to the `netsh ras' context.
rpc - Changes to the `netsh rpc' context.
set - Updates configuration settings.
show - Displays information.
winhttp - Changes to the `netsh winhttp' context.
wins - Changes to the `netsh wins' context.
winsock - Changes to the `netsh winsock' context.
The following sub-contexts are available:
advfirewall bridge dhcp dhcpclient firewall http interface ipsec lan nap netio
ras rpc winhttp wins winsock
Subscribe to:
Posts (Atom)