In BAS 5, select user.
In Messaging configuration section, click Default configuration.
Click Edit user.
Change Redirect to BlackBerry device from Yes to No.
Click Continue to user information edit.
Click Save all.
In BAS 5, select user.
In Messaging configuration section, click Default configuration.
Click Edit user.
Change Redirect to BlackBerry device from Yes to No.
Click Continue to user information edit.
Click Save all.
Normally it should not be necessary to manually delete a service. Uninstalling an application should remove its associated service (if any).
However, should it be necessary to manually remove a service:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services
or
From CMD
Note:
To install the Microsoft Exchange Server Messaging Application Programming Interface (MAPI) Client and Collaboration Data Object (CDO) 1.2.1 without Microsoft Exchange System Manager or the Microsoft Exchange Server MAPI Client and CDO previously installed, complete the following steps:
Important: Restarting certain BlackBerry Enterprise Server services delays email message delivery to BlackBerry smartphones. For more information, see KB04789.
To update to the Microsoft Exchange Server MAPI Client and CDO 1.2.1 from a MAPI client pack or Microsoft Exchange System Manager, complete the following steps:
Important: Restarting certain BlackBerry Enterprise Server services delays email message delivery to BlackBerry smartphones. For more information, see KB04789.
Note: The Microsoft Exchange 2000 or Microsoft Exchange 2003 CD-ROM might be required in order to uninstall Microsoft Exchange System Manager. If the end user license agreement does not appear during installation of the Microsoft Exchange Server MAPI Client and CDO 1.2.1, or the MAPI32.DLL file is 600 KB or more, the Microsoft Exchange Server MAPI Client and CDO 1.2.1 did not install correctly. The installation appears to have completed successfully, but the Program Files\ExchangeMAPI directory is not installed and the MAPI client is not updated. This occurs if all of the MAPI files were not renamed with the .old file extension before installation.
To verify the successful installation of the Microsoft Exchange Server MAPI Client and CDO 1.2.1, complete the following steps:
Note: The file directories listed in the logs contain the version of the files, and the currently available version may be newer than what is listed above.
From http://www.blackberry.com/btsc/viewContent.do?externalId=KB15779&sliceId=1
AIM
1. Menu->Settings->Buddy List
2. Check box for “Hide the taskbar icon when I close the Buddy List”
MediaMonkey
1. Tools->Options->General
2. Uncheck “Always show tray icon”
3. Select Minimize to MicroPlayer
Skype
1. Navigate to C:\Program Files\Skype\Phone
2. On the Compatibility tab Check box for “Run this program in compatibility mode for”
3. Select Windows Vista (Service Pack 2)
Winamp
1. Options->Preferences->General Preferences
2. Uncheck Show Winamp in Taskbar
3. Check Show Winamp in System Tray
Windows Live
1. Navigate to C:\Program Files \Windows Live\Messenger
2. Right click msnmsgr.exe and select properties
3. On the Compatibility tab Check box for “Run this program in compatibility mode for”
4. Select Windows Vista (Service Pack 2)
Yahoo
1. Messenger->General
2. Check box for “Remove the taskbar button when I minimize the main window”
The following table shows examples of searches you might find useful. The search query syntax, available when the Instant Search (Instant Search: A Search feature that provides search results quickly with word highlighting as you type. The Instant Search pane is always available in Mail, Calendar, Contacts, Tasks, Notes, Folder List, and Journal.) feature is enabled, follows this basic form: keyword:your search criteria value.
For example, from:bobby
You can also use logical operators AND, NOT, OR, <, >, =, and so forth to refine your search, and these are noted in the table. Logical operators must be typed in uppercase letters.
Note The search query syntax is created automatically and displayed in the Instant Search box when you use the Query Builder described in the previous section.
| Type this | To find this |
| bobby | Items containing bobby, BOBBY, BoBby, or any other combination of uppercase and lowercase letters. Instant Search is not case sensitive. |
| bobby moore | Items containing both bobby and moore, but not necessarily in that order. |
| bobby AND moore | Items containing both bobby and moore, but not necessarily in that order. Note that logical operators such as AND, NOT, and OR must be in uppercase letters. |
| bobby NOT moore | Items containing bobby, but not moore. |
| bobby OR moore | Items containing bobby, moore, or both. |
| "bobby moore" | Items containing the exact phrase bobby moore. Note the use of double quotes so that the search results match the exact phrase within the quotes. |
| from:"bobby moore" | Items sent from bobby moore. Note the use of double quotes so that the search results match the exact phrase within the quotes. |
| from:"bobby moore" about:”status report” | Items sent from bobby moore where status report appears in the subject line, body, and attachment contents. Note the use of double quotes so that the search results match the exact phrase within the quotes. |
| hasattachment:yes | Items that have attachments. You can also use hasattachment:true to get the same results. |
| attachments:presentation.pptx | Items that have attachments named presentation.pptx or if the attachment contains presentation.pptx within its contents. |
| subject:"bobby moore" | Items whose subject contains the phrase bobby moore. |
| subject:bobby moore | Items with bobby in the subject line and with moore anywhere else in the document. |
| cc:"bobby more" | Items in which the display name bobby moore is on the Cc line. |
| cc:bobbymoore@contoso.com | Items in which the e-mail address bobbymoore@contoso.com is on the Cc line. |
| bcc:bobby | Items in which bobby is on the Bcc line. |
| messagesize:<10 KB | Items whose size is less than 10 kilobytes. Note the use of the "less than" comparison operator (<). |
| messagesize:>5 MB | Items whose size is larger than 5 megabytes. Note the use of the "greater than" comparison operator (>). |
| received:=1/1/2006 | Items that arrived on 1/1/2006. Note the use of the "equals" comparison operator (=). |
| received:yesterday | Items that arrived yesterday. Instant Search also recognizes the follow date values: |
| Relative dates: For example, today, tomorrow, yesterday | |
| Multi-word relative dates: For example, this week, next month, last week, past month, coming year | |
| Days: Sunday, Monday ... Saturday | |
| Months: January, February ... December | |
| received:last week | Items that arrived last week. Note that if you run this query again a month from now you will obtain different results because it is a time relative query. |
| due:last week | Items that are flagged for follow up a due date. |
| messagesize:tiny | Items whose size is less than 10 kilobytes |
| messagesize:small | Items whose size is between 10 and 25 kilobytes |
| messagesize:medium | Items whose size is between 25 and 100 kilobytes |
| messagesize:large | Items whose size is between 100 and 500 kilobytes |
| messagesize:verylarge | Items whose size is between 500 kilobytes and 1 megabyte |
| followupflag:follow up | Items that are flagged for follow up. |
| messagesize:enormous | Items whose size is larger than 5 megabytes |
| hasflag:true | Items that are flagged for follow up. |
| from:bobby (received:1/7/05 OR received:1/8/05) | Items from bobby that arrived on either 1/7/05 or 1/8/05. Note the use of parentheses to group the dates. |
| received:>=10/1/06 AND received:<=10/5/06 | Items that arrived between 10/1/06 and 10/5/06. |
| received:>10/1/06 AND received:<10/5/06 | Items that arrived after 10/1/06 but before 10/5/06. |
| sent: yesterday | Items that you sent yesterday. |
| to:bobby | Items that you sent to bobby when you are searching in the Sent Items folder. |
| read:no | Items that have not been read. You can also use read:false to get the same results. |
| subject:status received:May | Items received from anyone during the month of May (any year) where the subject contains status. |
| startdate:next week subject:status | Calendar items next week where the subject contains status. |
| is:recurring | Calendar items that are recurring. |
| organizer:bobby | Calendar items where bobby is the organizer. |
| category:business | Items that are categorized as business. |
| firstname:bobby | Contacts that contain bobby in the First Name field. |
| lastname:moore | Contacts that contain moore in the Last Name field. |
| nickname:bobby | Contacts that contain bobby in the Nickname field. |
| jobtitle:physician | Contacts that contain physician in the Job Title field. |
| pager:555-0100 | Contacts that contain 555-0100 in the Pager field. |
| businessphone:555-0100 | Contacts that contain 555-0100 in the Business Phone field. |
| homephone:555-0100 | Contacts that contain 555-0100 in the Home Phone field. |
| mobilephone:555-0100 | Contacts that contain 555-0100 in the Mobile Phone field. |
| carphone:555-0100 | Contacts that contain 555-0100 in the Car Phone field. |
| businessfax:555-0100 | Contacts that contain 555-0100 in the Business Fax field. |
| homefax:555-0100 | Contacts that contain 555-0100 in the Home Fax field. |
| businessaddress:(4567 Main St., Buffalo, NY 98052) | Contacts that contain 4567 Main St., Buffalo, NY 98052 in the Business Address field. Note the use of parentheses to enclose the address. |
| homeaddress:(4567 Main St., Buffalo, NY 98052) | Contacts that contain 4567 Main St., Buffalo, NY 98052 in the Home Address field. Note the use of parentheses to enclose the address. |
| businesscity:buffalo | Contacts that contain buffalo in the Business City field. |
| businesspostalcode:98052 | Contacts that contain 98052 in the Business Postal Code field. |
| street:(4567 Main St) | Contacts that contain 4567 Main St in the Business Address Street field. Note the use of parentheses to enclose the address. |
| homestreet:(4567 Main St) | Contacts that contain 4567 Main St in the Home Address Street field. Note the use of parentheses to enclose the address. |
| birthday:6/4/1960 | Contacts that contain 6/4/1960 in the Birthday field. |
| webpage:www.contoso.com | Contacts that contain the URL www.contoso.com in the Web Page Address field. |
From:
Before implementing client version blocking it’s a good idea to know versions are in use. With this information you can tell which clients need to be upgraded to a newer version before blocking is implemented, or simply which clients will no longer be able to connect after it is implemented. In Exchange 2007 client version information is retrieved using the Get-LogonStatistics cmdlet.
Get-LogonStatistics accepts a mailbox, a mailbox database, or a server name as input and returns statistics including user name, logon time, last access time, client name, and client version.
For example, to list the client versions used to access a single mailbox, the command is:
Get-LogonStatistics JSmith | ft UserName,ClientVersion,LogonTime
To list the client versions for all clients connecting to a specific server:
Get-LogonStatistics –Server SERVER01 | ft UserName,ClientVersion,LogonTime
To list the client versions for all clients on all mailbox servers, and export the results to a CSV file:
Get-MailboxServer | Get-LogonStatistics | `
Select UserName,ClientName,ClientVersion,LogonTime | `
Export-Csv -Path ExchangeClientVersions.csv
Once you have identified the clients in use in your organisation and taken any remedial action necessary you can move on to blocking any further access by unwanted clients.
Determining Which Client Versions to Block
The client version is determined by the version of Emsmdb32.dll on the client. This is not necessarily the same as the Outlook version, or the version of any other DLL or executable files. This table shows the version of Emsmdb32.dll for major releases or updates of Outlook since the release of Office XP.
Release
Emsmdb32.dll Version
Office XP RTM
10.0.2627.1
Office XP SP1
10.0.3416.0
Office XP SP2
10.0.4115.0
Office XP SP3
10.0.6515.0
Office 2003 RTM
11.0.5604.0
Office 2003 SP1
11.0.6352.0
Office 2003 SP2
11.0.6555.0
Office 2003 SP3
11.0.8161.0
Office 2007 RTM
12.0.4518.1014
Office 2007 SP1
12.0.6211.1000
Office 2007 SP2
12.0.6423.1000
Table 1 - Emsmdb32.dll version by Office release
There are some important points to note:
The MAPI client version numbers listed in Table 1, and those in the results of the Get-LogonStatistics cmdlet, are in the format x.0.y.z. When specifying MAPI versions to be blocked you must use the format x.y.z. For example, the version number for Outlook 2003 RTM becomes 11.5604.0.
When setting per-server restrictions it is very important to avoid restricting clients with version numbers 6.y.z as Exchange Server makes use of MAPI for server-side component connections and uses MAPI versions within the 6.y.z range (with the version number potentially varying by Exchange component and patch level). This does not apply to per-mailbox restrictions.
Microsoft recommends that at a minimum you block all MAPI clients with version numbers equal to or earlier than 5.3164.0.0.
Single versions are blocked by specifying the version in the format <version>, an open-ended range is blocked by using the format -<version1> or <version2>-, and a specific inclusive range is blocked by using the format <version3>-<version4>. Multiple sets of client versions can be disabled using a comma or semi-colon separated list.
Range Type
Example
Effect
<version>
11.5604.0
Block the specified MAPI version.
-<version>
-11.0.0
Block the specified version number, and all previous versions.
<version>-
11.0.0-
Block the specified version number, and all newer versions.
<version>-<version>
11.0.0-11.9.9
Block the specified version numbers, and all clients between the specified versions.
Table 2 - Example client version blocking syntax
Some example blocking settings to use:
Blocking Setting
Effect
11.5604.0
Block Outlook 2003 RTM
-5.9.9;7.0.0-11.9.9
Block all clients older than Outlook 2007
12.0.0-
Block all versions of Outlook starting with Outlook 2007 and including all future versions
-5.3164.0
Block Microsoft recommended Outlook versions
-5.99;7.0.0-
Block all MAPI clients, except for Exchange Server components
Table 3 - Example client version blocking settings
As mentioned earlier, restrictions can be implemented per-server or per-mailbox. Per-server restrictions are implemented via a registry change, and per-mailbox restrictions are implemented via the Exchange Management Shell – it is not possible to use the Exchange Management Console.
If both server and mailbox restrictions are used the most restrictive combination of both settings applies, additionally a server restriction cannot be overridden by a mailbox setting.
For example:
Server Restriction
Mailbox Restriction
Net Effect
-5.3164.0
-11.9.9
Mailbox can only be accessed using Outlook 2007
-5.9.9;7.0.0-
11.0.0-11.9.9
Mailbox cannot be accessed by any MAPI client (which is not executing on the Exchange server)
Table 4 – Cumulative effect of restrictions
Note – Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.
You need to be a local administrator on the Exchange server in order to edit the registry.
Start the registry editor on your Exchange 2007 Mailbox server
Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem registry key.
Right-click ParametersSystem, select New, and then select String value.
Name the new string value “Disable MAPI Clients”.
Right-click Disable MAPI Clients, and then click Modify.
Enter the restriction setting, for example -5.9.9;7.0.0-11.9.9
Close the registry editor
The change will be effective within 15 minutes, or to make it effective immediately you can restart the Microsoft Exchange Information Store service. Once the change takes effect any existing client connections which do not meet the version requirements will be terminated.
The Set-CASMailbox cmdlet is used to implement per-mailbox restrictions. To use the Set-CASMailbox cmdlet you must be delegated the Exchange Recipient Administrator role.
To prevent a mailbox from using Outlook clients prior to Outlook 2007 the command is:
Set-CASMailbox JSmith -MAPIBlockOutlookVersions "-11.9.9"
To remove a restriction for a mailbox:
Set-CASMailbox JSmith -MAPIBlockOutlookVersions $null
To prevent all mailboxes in a particular database from using clients other than Outlook 2007 RTM:
Get-Mailbox -Database "SERVER01\SG1\Database 1" | `
Set-CASMailbox -MAPIBlockOutlookVersions "-12.4518.1013;12.4518.1015-"
When an Outlook 2003 or Outlook 2007 user tries to connect with a restricted client version they will receive the message “Your Exchange Server administrator has blocked the version of Outlook that you are using. Contact your administrator for assistance.”
Users of older clients will receive the message “Cannot start Microsoft Outlook. The attempt to log on to the Microsoft Exchange Server computer has failed.”
More information on Get-LogonStatistics and Set-CASMailbox can be found in TechNet:
Source: http://www.simple-talk.com/sysadmin/exchange/restricting-outlook-client-versions-in-exchange-2007/
Run these two scripts to have permissions on the database level.
Get-MailboxDatabase | Add-ADPermission -User "changename" -AccessRights ExtendedRight -ExtendedRights Receive-As, ms-Exch-Store-Admin
Get-MailboxDatabase | Add-ADPermission -User "changename" -AccessRights ExtendedRight -ExtendedRights Send-As, ms-Exch-Store-Admin
Restart Blackberry services on the BES in this order
These should cover the following deployment:- Remote BlackBerry Administration Service- BlackBerry Enterprise Server (Core Components only)- High Availability configuration for BES components- Pooling configuration for BAS componentsFor the BES components, the BlackBerry Alert, BlackBerry Policy Service, and BlackBerry Synchronization Service services are set to Manual. In an HA configuration, if these services are started on another node, then they will not startup when the Controller service is started. If they are not detected as started on another node, or if there is no HA configuration, then they will start when the Controller service is started. This is why all three services are not present in the startup script (in an HA configuration, this would cause an error or three).
BlackBerry Enterprise Server:
Start Services:
net start "BlackBerry Router"
net start "BlackBerry Attachment Service"
net start "BlackBerry Dispatcher"
net start "BlackBerry MDS Connection Service"
net start "BlackBerry Alert"
net start "BlackBerry Controller"
Stop Services:
net stop "BlackBerry MailStore Service"
net stop "BlackBerry MDS Connection Service"
net stop "BlackBerry Dispatcher"
net stop "BlackBerry Attachment Service"
net stop "BlackBerry Controller"
net stop "BlackBerry Router"
net stop "BlackBerry Policy Service"
net stop "BlackBerry Synchronization Service"
net stop "BlackBerry Alert"
BlackBerry Administration Service
Start Services:
net start "BlackBerry Administration Service - Application Server"
net start "BlackBerry Administration Service - Native Code Container"
Stop Services:
net stop "BlackBerry Administration Service - Native Code Container" /Y
net stop "BlackBerry Administration Service - Application Server"
net stop "BlackBerry Administration Service - Native Code Container"
From
8.8.8.8 Google
8.8.4.4 Google
4.2.2.1 GTE
4.2.2.2 GTE
208.67.222.222 opendns
208.67.220.220 opendns
Home users can either do this on your router on the computer's NIC.
For business on Active Directory, try this
On your Active Directory server, navigate to DNS Manager
1. Right click the server name and select properties
2. Forwarders tab
3. Click Edit button
4. Add IP Address from above
5. Click OK
6. Click OK
Log onto your sonicwall. Once logged on, change the URL from http://x.x.x.x/main.html to http://x.x.x.x/diag.html
Click Internal Settings button.
Scroll to bottom and click Flush Connections button.
This happened to me after a client's Sonicwall reached the maximum number of connections. On the System->Status page the Current Connections was 65536. The maximum connections that this Sonicwall with this firmware can have when using GAV/IPS is 65536.
You can find out maximum connection information by navigating to System->Diagnostics. In the Tech Support Report section check all four boxes and click Download Report. Save the report to desktop. Open report and search for “Max Connections when using GAV/IPS”. Compare that number with the number Status page.
When the maximum connections have been made, the logs should have an entry stating:
The cache is full; 65536 open connection; some will be dropped.
The above was listed for me on the Status page in the Latest Alerts section.
Blackberry Enterprise Server (BES) 5.0 installs and links to Java 1.5.0_15. If you update to the latest version of Java and remove Java 1.5.0_15 then the admin console will not work. In Internet Explorer you will get an “Internet Explorer cannot display the webpage.
If you check your Services, you may notices the following services stopped:
BlackBerry Administration Service - Application Server
BlackBerry Administration Service - Native Code Container
If you attempt to start or restart the service you get a message "BlackBerry Administration Service - Application Server service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service." or
"BlackBerry Administration Service - Native Code Container service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."
Checking Event View Application errors you may have:
Source: BAS-NCC Event: 4, 4096, 4097, 4098
The description for Event ID ( 4 ) in Source ( BAS-NCC ) cannot be found.
The description for Event ID ( 4096 ) in Source ( BAS-NCC ) cannot be found.
The description for Event ID ( 4097 ) in Source ( BAS-NCC ) cannot be found.
The description for Event ID ( 4098 ) in Source ( BAS-NCC ) cannot be found.
or
Source: BAS-AS Event: 4, 4096, 4097, 4098
The description for Event ID ( 4 ) in Source ( BAS-AS ) cannot be found.
The description for Event ID ( 4096 ) in Source ( BAS-AS ) cannot be found.
The description for Event ID ( 4097 ) in Source ( BAS-AS ) cannot be found.
The description for Event ID ( 4098 ) in Source ( BAS-AS ) cannot be found.
The fix is to update two registry entries point to the most current Java. For my example my current version of Java is 1.6.0_07. Change
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BAS-AS\Parameters\JVM Library
C:\Program Files\Java\jre1.5.0_15\bin\client\jvm.dll
to
C:\Program Files\Java\jre1.6.0_07\bin\client\jvm.dll
and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BAS-NCC\Parameters\JVM Library
C:\Program Files\Java\jre1.5.0_15\bin\client\jvm.dll
to
C:\Program Files\Java\jre1.6.0_07\bin\client\jvm.dll
NOTE that you may also need to update:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\BAS-AS\Parameters\JVM Library
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\BAS-NCC\Parameters\JVM Library
Start/Restart Blackberry services if necessary after changes.
You can also re-install Java 1.5.0_15 by navigating to the extracted BES 5 folder
\BlackBerry Enterprise Server 5.0.0\tools\Java 2 Runtime Environment, SE v1.5.0_15.msi
More can be found on Blackberry KB14697
ADP iPayStatments may not be viewable in Internet Explorer and you receive a red X instead of your statement in PDF form. In the above example, I am using XP sp3, Internet Explorer 8, and Acrobat 9. I have also come across this issue with Adobe Reader 9 regardless of patch version.
First, verify you have these two proper settings:
If you have the above settings and still have the problem the continue reading.
The root of the issue is that a previous versions of Adobe Reader/Acrobat did not fully remove all registry entries when it was uninstalled. Sites like ADP are calling some function of Adobe Reader/Acrobat but the registry entry is pointing to a previous version of Adobe Reader/Acrobat and therefore you get the red X.
ADP support was not much help. Their response was that XP sp3 and Adobe Reader/Acrobat 9 was not supported even though XP sp3 has been available since May 2008. Adobe Reader/Acrobat 9 has been available since July 2008. ADP support solution was downgrade Adobe Reader/Acrobat 9 to 8. This was not an acceptable solution for several reasons. Adobe Reader/Acrobat 9 is the current offering and has the most current security and Adobe recommends 9 over 8. Also, the client that I’m helping has a license for 9, not 8.
The fix is to delete the following folder in the registry:
[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\8.0]
for others they may have [HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\6.0] or[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\7.0]
You can copy the following into a txt file and give change the extension from .txt to .reg. Double click the .bat file and it will automatically delete the folder for you.
Windows Registry Editor Version 5.00
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\8.0]
Here is an alternative fix that takes a little longer and may require restarts. You also have to have admin rights on the computer.
Here is the big .reg file I used to remove all previous versions of Adobe Acrobat and Adobe Reader prior to version 9:
Windows Registry Editor Version 5.00
# Adobe 6 Removal
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Distiller\6.0]
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Elements\6.0]
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\6.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\6.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Reader\6.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Synchronizer\6.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Distiller\6.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Elements\6.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\6.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\6.0]
[-HKEY_LOCAL_MACHINE\Software\Adobe\Repair\Adobe Reader\6.0]
[-HKEY_LOCAL_MACHINE\Software\Adobe\Repair\Adobe Acrobat\6.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\6.0]
[-HKEY_USERS\S-1-5-18\Software\Adobe\Acrobat Reader\6.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Acrobat Reader\6.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Adobe Acrobat\6.0]
[-HKEY_USERS\S-1-5-18\Software\Adobe\Adobe Acrobat\6.0]
[-HKEY_USERS\S-1-5-21-1547161642-2077806209-682003330-1219\Software\Adobe\Adobe Acrobat\6.0]
# Adobe 7 Removal
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Distiller\7.0]
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Elements\7.0]
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\7.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\7.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Reader\7.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Synchronizer\7.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Distiller\7.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Elements\7.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\7.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\7.0]
[-HKEY_LOCAL_MACHINE\Software\Adobe\Repair\Adobe Reader\7.0]
[-HKEY_LOCAL_MACHINE\Software\Adobe\Repair\Adobe Acrobat\7.0]
[-HKEY_LOCAL_MACHINE\Software\Adobe Systems\Common Install\Shared Service\B2E57000]
[-HKEY_CLASSES_ROOT\Installer\Features\68AB67CA3301B7447A50000000000020]
[-HKEY_CLASSES_ROOT\Installer\Products\68AB67CA3301B7447A50000000000020]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\7.0]
[-HKEY_USERS\S-1-5-18\Software\Adobe\Acrobat Reader\7.0]
[-HKEY_USERS\S-1-5-18\Software\Adobe\Adobe Acrobat\7.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Acrobat Reader\7.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Adobe Acrobat\7.0]
[-HKEY_USERS\S-1-5-21-1547161642-2077806209-682003330-1219\Software\Adobe\Adobe Acrobat\7.0]
# Adobe 8 Removal
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Distiller\8.0]
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Elements\8.0]
[-HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\8.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\8.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Reader\8.0]
[-HKEY_CURRENT_USER\Software\Adobe\Adobe Synchronizer\8.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Distiller\8.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Elements\8.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\8.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\8.0]
[-HKEY_LOCAL_MACHINE\Software\Adobe\Repair\Adobe Reader\8.0]
[-HKEY_LOCAL_MACHINE\Software\Adobe\Repair\Adobe Acrobat\8.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\8.0]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\68AB67CA7DA73301B7448A0000000020]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-A80000000002}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\68AB67CA7DA73301B7448A0000000020]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Features\68AB67CA7DA73301B7448A0000000020]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Low Rights\ElevationPolicy\{358E6F10-DE8A-4602-8424-179CA217F8EE}]
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Low Rights\ElevationPolicy\{9C6A861C-B233-4994-AFB1-C158EE4FC578}]
[-HKEY_USERS\S-1-5-18\Software\Adobe\Adobe Acrobat\8.0]
[-HKEY_USERS\S-1-5-18\Software\Adobe\Acrobat Reader\8.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Acrobat Reader\8.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Adobe Acrobat\8.0]
[HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\ShellNoRoam\MUICache]
"C:\\WINDOWS\\TEMP\\Adobe Reader 8\\setup.exe"=-
[HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\ShellNoRoam\MUICache]
"C:\\WINDOWS\\TEMP\\Adobe Reader 8\\setup.exe"=-
[-HKEY_USERS\S-1-5-21-1547161642-2077806209-682003330-1219\Software\Adobe\Adobe Acrobat\8.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Backup\Preferences\brr1\Software\Adobe\Acrobat Reader\8.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Backup\Preferences\brr2\Software\Adobe\Acrobat Reader\8.0]
[-HKEY_USERS\.DEFAULT\Software\Adobe\Backup\Preferences\brr3\Software\Adobe\Acrobat Reader\8.0]
The fix to the issue was discovered using Active Registry Monitor and these:
UPDATE 8/21/2009
I just read this Adobe KB article. Even though I got mine working from doing the above, you can try these additional steps:
In the registry delete the HKEY_CLASSES_ROOT\AcroExch.Document and HKEY_CLASSES_ROOT\AcroExch.Document.7.
When I launched Acrobat it launched the installer and repaired the registry keys and prompted to restart the computer. If you still have problems perform a repair by going to Add Remove Programs and highlighting Adobe Acrobat/Reader and clicking Change/Repair.
How To Backup Blackberry Enterprise Server (BES)
Know your BES database name by navigating to
Start->Programs->BlackBerry Enterprise Server->BlackBerry Server Configuration
Make note of the database on the Database Connectivity.
On the BES, navigate to Start->Run
Type CMD
In the command window type
osql –E
backup database
Example:
backup database besmgmt to disk = “C:\BESDbackup\backup
Type go
From http://forums.crackberry.com/f3/how-remove-sent-my-blackberry-4980/
Step 1
Login to you BIS site depending on your carrier. The most popular carriers are listed below.
Verizon
Alltel
AT&T
Nextel / Sprint
Rogers
Telus
T-Mobile (U.K)
T-Mobile (U.S)
Other Carriers are listed here
Step 2
Click edit next to the email account you want to remove the signature from.
Step 3
In the field titled "Signature" erase all the text for no signature or edit it to display something in place of "Sent from my BlackBerry."
In a command console, here is how you change directories (cd) to an unmapped network path.
Use pushd instead of cd to change the current directory to a share accessed via a UNC path (e.g.: >pushd \\myserver\myshare).
When done, use popd to get back to prompt.
Windows XP Pro & Vista Business/Ultimate/Enterprise
Windows 2000/XP HOME: (2000 & XP Pro do not require you to boot into safe mode)
Windows Vista Home Premium
Windows 2000:
Disable the splash screen
This site maintains a list of free downloads from Microsoft. If you have any problems with the links go to bhandler.spaces.live.com and navigate your way from there.
To re-create the Show desktop icon yourself, follow these steps:
[Shell]
Command=2
IconFile=explorer.exe,3
[Taskbar]
Command=ToggleDesktop
The Quick Launch toolbar uses the files in the following folder:
%userprofile%\Application Data\Microsoft\Internet Explorer\Quick Launch
The Show Desktop icon file should be available now
More can be read here
http://support.microsoft.com/kb/190355