Microsoft’s Error Reporting in windows sometimes is disturbing, most of us don’t want to send that error report because it’s of no use. Even I am fed up of this stupid error pop up every time. There’s a easy way to disable Microsoft error report in windows.

Disable Microsoft Error report in Windows XP:

1- Open Control Panel (Start > Control Panel)

2- Open the Problem Reports & Solutions applet Under advanced options and disable error reporting.

Disable Microsoft Error report in Windows Vista:

1- Right click on my computer (Desktop) and click properties

2- Click the Advanced Tab

3- You’ll see a “Error reporting” button at the bottom, click it

4- Select Disable Error Reporting

And you’re done.

Supporting auto completion, multi document, multi view, full drag and drop, it is an editor of million of users. If the currently opened file is modified or deleted outside Notepad++, it automatically notifies of the changes and asks to update the document (reload the file or remove the file). Did I also told you it also supports zoom and zoom of the document. You can also use bookmarks, and macro recording and playback.

Here’s what new:

1. Fix the crash issue under Chinese/Korean/Japanese Windows environment.
2. Fix go to line command line bug.
3. Enhance Find in files and Find in all opened files features’ performance.
4. Fix dialog off screen problem under multi-monitor environment.
5. Make smart highlight work only with mouse double clicked in order to improve the its performance.
6. Fix all doc tab blink bug when Notepad++ is re-activated.
7. Fix “replace with space” in GUI not be remembered bug.
8. Fix HTML syntax highlighting is not applied in php, asp file bug.
9. Add the smart highlight file size limit - 2 MB in order to improve the performance.

[Download Notepad++ v5 Beta]

You'll find that GPOs themselves are much easier to create and edit using Microsoft's Group Policy Management Console (GPMC), a drop-in replacement for the more limited Group Policy Object Editor that you might know from previous versions of Windows Server. Native Group Policy Object Editor, the tool has limitations: the biggest by far being the lack of ability to see the exact scope of a GPO's application, making troubleshooting very difficult. The GPMC fixes this and also offers a cleaner interface, scripting functionality, and enhancements to troubleshooting and modeling features.

To navigate around in the GPMC, you need to expand the forest you want to manage in the left pane. Then you can select specific domains and sites within that forest, and OUs within individual domains. When you expand, for example, a particular domain, links to the GPOs that exist are listed within their respective OUs. They also are listed under the Group Policy Objects folder. Clicking on a GPO brings up a four-tabbed screen in the right pane.

The first tab is the Scope tab, which examines how far-reaching the effects of this GPO are. Sites, domains, and OUs that are linked to the GPO you've selected are listed at the top of the window. You can change the listing of pertinent links using the drop-down box, where you can choose to list links at the current domain, the entire forest, or all sites. At the bottom of the window, any security filtering done by ACLs is listed. Clicking the Add button brings up the standard permissions window, as you would expect from the Group Policy Object Editor.

At the very bottom, you can see any WMI filters to which this GPO is linked. You can choose to open the WMI filter for editing by clicking the Open button. You can associate only one WMI filter with any particular GPO, and WMI filters work only with Windows XP, Windows Vista, Windows Server 2003, and Windows Server 2008. We'll get to these in a bit—for now, let's move on.

The next tab, Details, simply shows the domain in which the current GPO is located, the owner of the GPO, when the GPO was created and modified, the version numbers for the user and computer portions, the GUID of the object, and whether the GPO is fully enabled or fully disabled or whether just the computer or user configuration portions are enabled.

The Settings tab is one of the most useful tabs in the GPMC. The GPMC will generate HTML-based reports of all the settings in a particular GPO, and you can condense and expand portions of the report easily for uncluttered viewing. You can print the report for further reference, or save the report for posting to an internal web site for your IT administrators. It's a much, much easier way to discern which settings a GPO modifies than the Group Policy Object Editor. To edit the GPO that is displayed in the report, simply right-click it and select Edit. To print the HTML report, right-click it and select Print; to save the report, right-click it and select Save Report.

Finally, the Delegation tab lists in a tabular format the users and groups that have specific permissions for the selected GPO, what those permissions are, and whether they're inherited from a parent object. Clicking Add brings up the common Select User, Computer, or Group dialog box that you are familiar with from reading this chapter. You can remove a delegated permission by clicking the appropriate user or group in the list and then clicking the Remove button. The Properties button will bring up the standard Active Directory Users and Computers view of the selected user and group.

Like NTFS permissions, GPs are cumulative and inherited—cumulative in that the settings modified by a policy can build upon other policies and "amass" configuration changes, and inherited in that objects below other objects in Active Directory can have any GPs that are applied to their parent object be applied to themselves automatically.

GPOs are associated with, or linked, to any number of objects, either within a directory or local to a specific machine. To implement a GP on a specific type of object, follow these guidelines.

Local computer

Use the Local Security Policy snap-in inside Control Panel à Administrative Tools. Or, for a more complete look, use Start à Run à gpedit.msc.

A specific computer

Load the MMC, and then select Add Snap-in from the File menu. Browse in the list and add the Group Policy Object Editor to the console. On the Select Group Policy Object screen, peruse the list to find the specific object you want.

Entire domain

Install and launch the Group Policy Management Console, and then right-click on the domain and create or edit a policy from there.

OU within Active Directory

Install and launch the Group Policy Management Console, right-click on the OU, and create or edit a policy from there.

Active Directory site

Launch Active Directory Sites and Services, right-click the site's name, and select Properties from the context menu. Navigate to the Group Policy tab, and create or edit a policy from there.

Windows applies GPs in the following order, which you can remember with the acronym of "LSDOU":

Local GPOs

Site-specific GPOs, in an order which the site administrator configures

Domain-specific GPOs, in an order which the domain administrator configures

OU-specific GPOs, from the parent OU down through the ranks to the child OU

The only exception to this rule occurs when you're using NT 4.0 system policies that are created and set with the NT System Policy Editor. Recall from NT administration days that the system policies are called NTCONFIG.POL, so if Windows finds that file present, it applies these policies before the local GPO. Of course, these policies can be overwritten by policies that come farther down in the application chain.

Normally when you want to access the Disk Cleanup tool, you usually have to either find it through the start menu, or open up the drive properties window. Instead of going through all that, we can use a simple registry hack to add a menu item to the drive right-click menu.

Using the Hack

After installation, you can simply right-click on a drive and choose “Disk Cleanup” from the menu:

If you are using Windows Vista, you’ll be asked whether you want to clean up your files or all files…

And then disk cleanup will begin:

Manual Registry Hack

Open up regedit through the start menu search or run box, and then browse down to the following key:

HKEY_CLASSES_ROOT\Drive\shell

Create a new key called “diskcleanup” and set the default value to “Disk Cleanup”. Then create another key underneath it called “command” and set the value to the following:

cleanmgr.exe /d %1

The change should be immediate, just right-click on the drive and you should see the new menu item.

Downloadable Registry Hack

Simply download, extract, and double-click on DiskCleanupDriveMenu.reg to enter the information into the registry. You can use the included RemoveDiskCleanupDriveMenu.reg file to reverse the changes.

Download DiskCleanupDriveMenu Registry Hack

The next video in our Server Core series is going to cover making our demo server into a RODC or Read-Only Domain Controller.  One pre-requisite for a RODC is an existing Windows 2008 based DC in the domain.  You also need to run adprep /rodcprep before you can add the RODC.  Other than that it is pretty straight-forward but without the DCPromo wizard can cause a challenge.  Let's see how it is done!

Note: Double-click on the video to go full screen.

 

If you want to give these demos a try yourself be sure to grab the lab build guide and demo scripts here!