sync both BB and email accounts

messages icon> black app>  scroll to options>genral ,inbox ,email reconsicalltion.

Delete on answer>

How to enable system protection:

How to enable system protection:
1.start>control panel>
2.system security
3.system protection
4.Local disk (); click configure

How to create network backup-

How to create network backup-

1.cpntprl panel>system Security>backup
2.Deselct admin libraries
3.deselect include system image drive c:
4.select next.

How to create a system repair disk:

How to create a system repair disk:
1. contorl panel
2.backup and retore
3.create a system reapir disk
4.Create disc

App locker

AppLocker policies are located in the Computer Configuration\Windows Settings\ Security Settings\Application Control Policies node of a standard Windows 7 or Windows Server 2008 R2 GPO.

The Application Compatibility Toolkit (windows7)

The Application Compatibility Toolkit

The Application Compatibility Toolkit (ACT) is a collection of tools that allows you to resolve application compatibility issues. You can use the ACT to determine whether existing applications are compatible with Windows 7 before deploying the new operating system.

The ACT contains the following components:

• Application Compatibility Manager
• Compatibility Administrator
• Internet Explorer Compatibility Test Tool
• Setup Analysis Tool
• Standard User Analyzer

You learn more about each of these tools in the rest of this lesson.

Note

MORE INFO: ACT You can obtain the ACT by going to http://download.microsoft.com and searching for the toolkit by name.

To change a dynamic disk back to a basic disk using the Diskpart utility

To change a dynamic disk back to a basic disk using the Diskpart utility, perform the following procedure:

1. Back up all volumes on the disk you want to convert.
2. Open an elevated command prompt and enter diskpart.
3. At the DISKPART> prompt, enter list disk. Note the number of the disk you want to convert.
4. At the DISKPART> prompt, enter select disk <disknumber>
5. At the DISKPART> prompt, enter detail disk <disknumber>
6. For each volume on the disk, at the DISKPART> prompt, enter select volume= <volumenumber> and then enter delete volume.
7. At the DISKPART> prompt, enter select disk <disknumber>
8. At the DISKPART> prompt, enter convert basic.

Convert a MBR to GPT

To use the Diskpart command-line utility to change a disk from MBR to GPT partition style, perform the following procedure:

1. Back up the data on the basic MBR disk that you want to convert.
2. Open an elevated command prompt and enter diskpart.
3. At the DISKPART> prompt, enter list volume. Note all the volume numbers.
4. For each volume listed, at the DISKPART> prompt, enter select volume <volumenumber>
5. For each volume, at the DISKPART> prompt, enter delete volume.
6. At the DISKPART> prompt, enter list disk. Note the disk number of the disk that you want to convert.
7. At the DISKPART> prompt, enter select disk <disknumber>.
8. At the DISKPART> prompt, enter convert gpt.

You can also use both Disk Manager and the Diskpart utility to

Configuring Computer Policy to Allow Non-Administrators to Install Specific Device Setup Classes

EXERCISE 1: Configuring Computer Policy to Allow Non-Administrators to Install Specific Device Setup Classes

This exercise permits a non-administrative user to install any imaging device (such as a webcam) that has a signed driver on the Canberra computer. You first determine the GUID of the Imaging Devices setup class and then configure computer policy to permit non-administrators to install this class of device. The exercise requires that at least one device of that setup class is installed on your computer. If not, use another setup class. You need to know the procedure—the actual device setup class you choose is not important. To permit non-administrators to install a specific type of hardware device, perform the following procedure:

1. Log on to the Canberra computer with the Kim_Akers account.
2. If the Don Hall non-administrator (ordinary user) account does not already exist, create it.
3. Open Device Manager.
4. Expand Imaging Devices in the Device Manager tree. Select a device (such as a webcam).
5. Right-click the device and choose Properties.
6. On the Details tab, in the Property list, click Device Class Guid, as shown in Figure 4-23.
   
   Figure 4-23: Determining a device class GUID
7. The GUID is displayed, as shown in Figure 4-24. Right-click the GUID and choose Copy. Paste the GUID into Microsoft Notepad so you do not lose it.
   
   Figure 4-24: Monitor device type GUID
8. Click Start. Enter mmc gpedit.msc in the Start Search box and press Enter. This starts Local Group Policy Object Editor.
9. In Local Group Policy Object Editor, under Local Computer Policy, double-click Computer Configuration, double-click Administrative Templates, double-click System, and select Driver Installation.
10. In the details pane, double-click Allow Non-Administrators To Install Drivers For These Device Setup Classes, as shown in Figure 4-25.
    
    Figure 4-25: Accessing the Allow Non-Administrators To Install Drivers For These Device Setup Classes policy
11. In the Allow Non-Administrators To Install Drivers For These Device Setup Classes dialog box, shown in Figure 4-26, select Enabled.
    
    Figure 4-26: Enabling the Allow Non-Administrators To Install Drivers For These Device Setup Classes policy
12. Click Show.
13. In the Show Contents dialog box, select the text box under Value to highlight it, double-click the text box, and paste the GUID you copied earlier (including the curly braces). The Show Contents box should be similar to Figure 4-27.
    
    Figure 4-27: Pasting the GUID into the Show Contents dialog box
14. Click OK to close the Show Contents dialog box.
15. Click OK to close the Allow Non-Administrators To Install Drivers For These Device Setup Classes dialog box. Local Group Policy Editor shows the policy is Enabled.
16. If you want, stage the driver for a reputable third-party imaging device. Then log on to the Canberra computer as Don Hall and install the device. Staging a driver is described in Exercise 2.