http://www.emailcashpro.com

Getting Error Events from Multiple Event Logs

source link

Get-EventLog can read events only from one event log at a time. If you want to find events in multiple event logs, you can append array information, though:
$events = @(Get-EventLog -LogName System -EntryType Error)
$events += Get-EventLog -LogName Application -EntryType Error
$events
In these cases, it might be easier to use WMI in the first place - which can query any number of event logs at the same time.
This will get you the first 100 error events from the application and system log (cumulated, so if the first 100 errors are in the application log, no system log errors will be reported, of course):

Get-WmiObject -Class Win32_NTLogEvent -Filter 'Type="Error" and (LogFile="System" or LogFile="Application")' |
  Select-Object -First 100 -Property TimeGenerated, LogFile, EventCode, Message

When you replace Get-WmiObject with Get-CimInstance (which is new in PowerShell 3.0), then the cryptic WMI datetime format is automatically converted to normal date and times:

Get-CimInstance -Class Win32_NTLogEvent -Filter 'Type="Error" and (LogFile="System" or LogFile="Application")' |
  Select-Object -First 100 -Property TimeGenerated, LogFile, EventCode, Message

How to tell if you have Exchange 2003 Enterprise or Standard

source link
source link

1) Application Log - Use the event viewer on the Exchange server and analyze the Application Log.  If event id 1216 is reported when the Information Store comes online then you have Standard.  If 1217 is reported then you have enterprise.

2) System Manager - In Exchange System Manager, tree down to the “Servers” folder  and click the folder itself so your servers appear in the right pane.  This view should show 2 columns including an “Edition” column

Server Types & Versions

It has always been easy to indentify the service pack and build numbers of Exchange servers by examining the 'Servers' view in Exchange System Manager.
The Exchange System Manager supplied with Exchange 2003 now includes two more useful columns in this view:
Type - this column will show Basic, Front-end or Clustered.
Edition - this column will show Standard, Standard/Evaluation, Enterprise or Enterprise/Evaluation.
A sample screen shot is shown below. Here you'll see an Exchange 2003 server running the evaluation edition of Exchange 2003 Enterprise coexisting with an Exchange 5.5 server. It's worthwhile to note that Exchange 5.5 servers will always show as Standard even if they are running the Enterprise version of Exchange 5.5. The good news is that the columns are correctly filled in for Exchange 2000 servers.

How to find all users with Forwarding Address is set

Source Link

Exchange 2003:
In native Exchange 2003 you can do a custom search in Active Directory Users & Computers to find all users with forwarding address is set with some internal or external address.
(objectClass=*)(altrecipient=*)
Example: I have set a forwarding address for User 32 to forward all mails to User 31.

Now find it with Custom Search.
Active Directory Users & Computers -> Find -> Select Custom Search -> Enter (objectClass=*)(altrecipient=*) in LDAP Query Text Box -> Click Find Now.



Exchange 2007:
If Exchange 2007 is in native mode or co-existence with Exchange 2003 then you can use PowerShell to find the same thing.
Get-Mailbox | Where {$_.ForwardingAddress -ne $null} | Select Name, ForwardingAddress, DeliverToMailboxAndForward
Example: I have set a forwarding address for User 22 to forward all mails to User 21.



Now find it with PowerShell.

Note: PowerShell gives all users who are on Exchange 2007 as well as Exchange 2003. You can see the Exchange Version in below screen.



Fix the “App can’t be opened because it is from an unidentified developer” Error in Mac OS X

source

Since OS X Mountain Lion, the Mac defaults to preventing applications from unidentified developers or sources from being launched. You’ll discover the message in OS X 10.8 when you try to launch a Mac app that didn’t come from a verified source or from the Mac App Store, and you’ll get an alert dialog that says “[App name] can’t be opened because it is from an unidentified developer”.


This new security feature is called GateKeeper, and it doesn’t mean you can’t run those unverified apps on the Mac, you just have to either temporarily skirt the security blanket of GateKeeper, or turn off the app limitations entirely.

Temporarily Get Around “App Can’t Be Opened” Gatekeeper Alert Message

This is probably the best option for most users, since it maintains some security:
  1. Right-click (or control-click) the application in question and choose “Open”
  2. Click the “Open” button at the next dialog warning to launch the app anyway
You can do this with any third party app that gives you this warning dialog and open it anyway.


If you get tired of constantly right-clicking apps to open them, return to pre-Mountain Lion levels of app security by turning off Gatekeepers app verification completely.

Disable GateKeeper’s Unidentified App Developer Prevention Completely

This is generally best for advanced users who know what apps to trust and not to trust:
  1. Launch System Preferences from the Apple  menu
  2. Choose “Security & Privacy” and then click the “General” tab, followed by clicking the lock icon in the corner to unlock the settings
  3. Look for “Allow applications downloaded from:” and choose “Anywhere”
  4. Accept the security warning and allow
  5. You can now launch any app from any location or developer

Multiple "Desktop" Address Book databases on the BlackBerry smartphone

source link

Environment
  • BlackBerry Desktop Software
  • BlackBerry Enterprise Server
  • BlackBerry smartphones
  • Mac OS
  • Windows
Overview
On the BlackBerry smartphone there are two different Desktop address books. They are visible from Contacts > Options. Some contacts exist only on the BlackBerry smartphone and will not synchronize to the mailbox.

Cause
The primary Address Book is empty and blocks the synchronization process.

Resolution
To resolve this issue for Blackberry Desktop Software on a Windows computer, complete the following steps:
  1. Perform a full backup of the BlackBerry smartphone using BlackBerry Desktop Software.
  2. Wipe the BlackBerry smartphone data by following these steps:
    1. On BlackBerry smartphones running BlackBerry Device Software 4.0 through 5.0 go to Options > Security Options > General Settings, press the Menu key and select Wipe Handheld, and on BlackBerry smartphones running BlackBerry Device Software 6.0 through 7.1 go to Options > Security > General Settings.
    2. Type BlackBerry where prompted.
    3. Select Wipe Handheld or Wipe Data.
  3. Ensure the radio is not enabled. By default, the radio is disabled after performing a security wipe.
  4. Connect the BlackBerry smartphone to BlackBerry Desktop Software.
  5. When prompted, choose the the mail profile, which is linked to the Exchange mailbox of the BlackBerry smartphone user.
  6. Go to Backup and Restore > Advanced.
  7. Load the backup file that was created in step 1 by going to Options > Open.
  8. From the left side, select the Address Book - All database, and then click the arrow pointing to the right and allow the request.
  9. Close the Backup and Restore window and click Synchronize.
  10. Make sure Synchronize organizer data is selected.
  11. In the Synchronization Configuration window, choose to synchronize only the address book.
  12. Setup synchronization with the Exchange mailbox used to receive email.
    Note: Some entries may be duplicated. Duplicates should be deleted manually.
  13. Perform a wired synchronization process.
  14. When the synchronization process is complete, disconnect the BlackBerry smartphone.
  15. Wipe the device (see step 2).
  16. Set the Enterprise Activation password for the BlackBerry smartphone user.
  17. On BlackBerry smartphones running BlackBerry Device Software 4.0 through 5.0 go to Options > Advance Options > Enterprise Activation and on BlackBerry smartphones running BlackBerry Device Software 6.0 through 7.1 go to Options > Device > Advance System Settings > Enterprise Activation.
  18. Type the corresponding email address and the password.
  19. Let the BlackBerry smartphone activate.
  20. If necessary, restore any missing information from the full backup.
    Note: Restore only the missing databases, do not use full restore.
The wireless synchronization should proceed as expected and there should only be one Desktop contact list in Contacts > Options.
Note: If theBlackBerry Internet Service is used to receive personal emails, go to Options > Device Advance System Settings > Default Services and ensure that Desktop is set as default service for email, calendar and contact list.
To resolve this issue for Blackberry Desktop Software on a Mac computer, complete the following steps:
  1. Perform a full backup of the BlackBerry smartphone using BlackBerry Desktop Software.
  2. Wipe the BlackBerry smartphone data by following these steps:
    1. On BlackBerry smartphones running BlackBerry Device Software 4.0 through 5.0 go to Options > Security Options > General Settings, press the Menu key and select Wipe Handheld, and on BlackBerry smartphones running BlackBerry Device Software 6.0 through 7.1 go to Options > Security > General Settings.
    2. Type BlackBerry where prompted.
    3. Select Wipe Handheld or Wipe Data.
  3. Ensure the radio is not enabled. By default, the radio is disabled after performing a security wipe.
  4. Connect the BlackBerry smartphone to BlackBerry Desktop Software.
  5. Go to Restore.
  6. Select the backup file that was created in Step 1.
  7. Click Restore Selected data.
  8. Scroll down and select Address Book - All.
  9. Click Restore.
  10. Close the Backup and Restore window.
  11. Make sure that only the Address Book is selected for sync.
  12. Perform a wired synchronization process.
  13. When the synchronization process is complete, disconnect the BlackBerry smartphone.
  14. Wipe the device (see step 2).
  15. On BlackBerry smartphones running BlackBerry Device Software 4.0 through 5.0 go to Options > Advance Options > Enterprise Activation and on BlackBerry smartphones running BlackBerry Device Software 6.0 through 7.1 go to Options > Device > Advance System Settings > Enterprise Activation.
  16. Type the corresponding email address and the password.
  17. Let the BlackBerry smartphone activate.
  18. If necessary, restore any missing information from the full backup.
    Note: Restore only the missing databases, do not use full restore.
The wireless synchronization should proceed as expected and there should only be one Desktop contact list in Contacts > Options.
Note: If the BlackBerry Internet Service is used to receive personal emails, go to Options > Device Advance System Settings > Default Services and ensure that Desktop is set as default service for email, calendar and contact list.

"Operation could not be completed (error 0x00000709)" error when you use a CNAME record for a print server in Windows Server 2008 R2

Source Link

Symptoms
When you try to connect to a printer by using an alias (CNAME) resource record for a print server that is running Windows Server 2008 R2 or for a client computer that is running Windows 7 and that hosts a printer, you receive the following error message:
Windows couldn't connect to the printer. Check the printer name and try again. If this is a network printer, make sure that the printer is turned on, and that the printer address is correct.
Additionally, the following will be seen in a Network Monitor trace:
[client request] 34 4.421875  {MSRPC:9, SMB2:8, TCP:2, IPv4:1} IP addressIP address Winspool Winspool:RpcOpenPrinterEx Request, Printer = \\printsvr\Microsoft XPS Document Writer [server response] 37 4.843750  {MSRPC:9, SMB2:8, TCP:2, IPv4:1} IP addressIP address Winspool Winspool:RpcOpenPrinterEx Response, Status = ERROR_INVALID_PRINTER_NAME
Cause
This issue can occur because of optimization changes to the spooler code for non-clustered computers. When the operating system loads, the Print Spooler service loads the local name of the computer and the other local names that are in the DNS cache. The Print Spooler service uses the local names to service requests. Therefore, the service must gain access to the network and then query for names such as an alias (CNAME) resource record. This behavior decreases the performance of the service.
Workaround
To work around this issue, use the following command to add a registry key on the print server that is running Windows 2008 Server R2 and that is being accessed by an alias (CNAME) resource record:
reg add HKLM\SYSTEM\CurrentControlSet\Control\Print /v DnsOnWire /t REG_DWORD /d 1
Note This registry key decreases performance. Therefore, we recommend that you add this registry key on only the print servers that must be accessed by an alias (CNAME) resource record.

After modifying the registry entry, please restart the Print Spooler service for the entry to take effect.

More information
Load balancing printers by using a Network Load Balancing (NLB) technology or the Domain Name System (DNS) round robin feature is not supported. The workaround that is mentioned in this article is only for the scenario where one print server that is running Windows Server 2008 R2 is accessed by an alias (CNAME) resource record that refers to only that one server.

When the Mailbox Merge Program Tries to Open the Message Store, the Operation Is Unsuccessful

source link

Symptoms

If you use the Microsoft Exchange Mailbox Merge Program (Exmerge.exe) to export mailboxes to a personal folder (.pst) file or import mailboxes from a .pst file, the operation is unsuccessful, and the following error message appears in the Exmerge.log file:
Error opening message store (MSEMS). Verify that the Microsoft Exchange Information Store service is running and that you have the correct permissions to log on. (0x8004011d)

Resolution

To troubleshoot this issue, follow these steps:
  1. Verify that the user account under which you run the Exchange Mailbox Merge program has the Receive As and Send As security permissions set to Allow for the Mailbox Store. To do this, follow these steps:
    1. Start Exchange System Manager. To do this, click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
    2. Expand Servers, expand the server that you want, expand the storage group that you want (for example, expand First Storage Group), and then expand Mailbox Store.
    3. Right-click Mailbox Store, and then click Properties.
    4. Click the Security tab, and then click the user account whose permissions you want to verify.
    5. In the Permissions list, click to select the Receive As check box in the Allow column, click to select the Send As check box in the Allow column, and then click OK.
    6. If the user account is a member of a group (domain administrators or enterprise administrators), this group must also have send as and receive as rights to the mailbox store.
  2. Verify that the user account under which you run the Exchange Mailbox Merge program has delegation authority at the Organization level in Exchange System Manager. To do this, follow these steps:
    1. In Exchange System Manager, right-click the organization (for example, right-click First Organization (Exchange)), and then click Delegate control. The Exchange Administration Delegation Wizard starts.
    2. Click Next.
    3. If the user account under which you run the Exchange Mailbox Merge program is not listed in the Users and groups box, and if it does not have the role of Exchange Full Administrator, click Next, add this user account with the role of Exchange Full Administrator, and then click OK.
    4. Click Next, and then click Finish.
  3. Quit Exchange System Manager.
  4. Restart the Microsoft Internet Information Service (IIS) Admin Service. To do this, follow these steps.

    NOTE: This restarts the Exchange Information Store service.
    1. Click Start, click Run, type services.msc in the Open box, and then click OK.
    2. In the Name list, right-click IIS Admin Service, and then click Restart.
    3. Click Yes to confirm the restarting of the services.
    4. Quit the Services snap-in.