How to Enable Users for Lync 2013

Login to the Lync URL

https://Lync.abc.com/Cscp/

Single sign on will work for this

clip_image002[4]

Click on Enable Users for Lync Server.

clip_image003[4]

Click Add to add the user for enabling it.

clip_image004[4]

Type the user logon name in search field and click find, select the required user and click ok.

clip_image005[4]

Select pool server from the drop down from Pool list.

clip_image006[4]

Select Enterprise Voice from the Telephony drop down list.

clip_image007[4]

Click on the Enable to enable the user for lync.

Configure Outlook 2007 to work over HTTP using RPC protocol

To setup RPC over HTTP on windows XP using Outlook 2007 click on Start and then click on Control Panel then click on the Mail applet in control panel.

The mail setup window should show up:

clip_image002

Click on E-mail Accounts..Then click on Account Settings, click on New:

clip_image004

  1. The new E-mail Account Setup should come up. Select Microsoft Exchange, POP3, IMAP, or HTTP and click Next

clip_image006

Click on “Manually configure server settings or additional server type. then click Next:

Select Microsoft Exchange on the next screen. Click Next. On the next screen, enter the name of the exchange server, and the Username:

clip_image008

After you have entered the info, click on More Settings. Click on the Connection tab on the Microsoft Exchange window:

clip_image010

Check the dial box to connect to Microsoft Exchange using HTTP and then click on Exchange Proxy Settings.

The Microsoft Exchange Proxy Settings windows should come up:

clip_image012

Check Connect Using SSL only if your organization exchange server is configured for SSL socket using the 443 port. Otherwise uncheck it. Enter the information about your exchange server as the screen shot below:

clip_image014

After you have entered all the information, close out of all the windows, and restart Outlook 2007. Your Outlook 2007 should work from anywhere now.

How to setup a Blackberry Support user account

1. Login to BES console.

2. Expand Administrator users

3. Click Create an administrator user

4. Fill in the required fields: only use ADM accounts for Admin logins.

5. For Role: Select Senior helpdesk Administrator. Do not create an Enterprise admin account.

6. clip_image002

7. Enter your password in the Administrators password field.

8. Click > Create an administrator user.

9. Done.

How to Count Number of Mailboxes in Exchange 2010 Using Powershell

Command to count all type of mailboxes in Exchange Management Shell

Get-Mailbox -ResultSize Unlimited | measure-object

Command to count Specific type of mailboxes in Exchange Management Shell

Get-Mailbox -ResultSize Unlimited | where {$_.ResourceType -eq “Equipment”} | measure-object

Command to count mailboxes on a specific server in Exchange Management Shell

Get-Mailbox -ResultSize Unlimited | where {$_.ServerName -eq “SERVERNAME”} | measure-object

How to Add Email Address or Domain Name to Mailbox Trusted Sender in MS exchange 2010 using powershell

For All Exchange Mailboxes in an Organisation

get-Mailbox | Set-MailboxJunkEmailConfiguration -TrustedSendersAndDomains @{Add=’Email Address to be white listed’, ‘Domain to be whitelisted’}

For a Single Mailbox

Set-MailboxJunkEmailConfiguration -Identity “User Email” -TrustedSendersAndDomains @{Add=’Email Address to be white listed’, ‘Domain to be whitelisted’}

Non Delivery Report (NDR) Error Codes For MS Exchange Server 2007

 

Below are the NDR codes for MS Exchange 2007. Knowledge of Non Delivery Report (NDR) Codes and their relative meanings help to resolve the Email Delivery Issues very fast and accurately.

NDR Codes

Explanation of Codes in Exchange Server 2007
4.2.2 The recipient has exceeded their mailbox limit. It could also be that the delivery directory on the Virtual server has exceeded its limit.
4.3.1 Insufficient system resources.  This normally means not enough disk space on the delivery server. Microsoft say this Exchange NDR may be reported as out-of-memory error.
4.3.2 A classic temporary problem.  Most likely, the Administrator has frozen the queue.
4.4.1 Intermittent network connection.  The server has not yet responded.  Classic time-out problem.  If it persists, you will also get a 5.4.x status code error.
4.4.2 The server started to deliver the message but then the connection was dropped.  The sending server is configured to retry automatically.
4.4.6 Too many hops.  Most likely, the message is looping.
4.4.7 Problem with a protocol timeout, for example a message header limit.  Check receiving server connectors.
4.4.9 A DNS problem.  Check your smart host setting on the SMTP connector.  For example, check correct SMTP format. Also, use square brackets in the IP address [197.89.1.4]  You can get this same NDR error if you have been deleting routing groups.
4.6.5 Multi-language situation.  Your server does not have the correct language code page installed.
5.0.0 SMTP 500 reply code means an unrecognized address.  You get this NDR when you make a typing mistake when you manually try to send email via telnet. The most likely cause is a routing error.  One solution maybe to add an * in the address space. A separate cause for NDR 5.0.0 is a DNS problem.
5.1.x Exchange 2007 NDR problems with email address.
5.1.0 Sender denied.  Often seen with contacts. Verify the recipient address. Mismatched Network Card duplex setting.
5.1.1 Bad destination mailbox address.  5.1.1 is the most common Exchange 2007 NDR; there is a problem with the recipient address. Maybe the recipient does not exist. Possibly the user was moved to another server in Active Directory. Check mailbox delegation. Maybe an Outlook client replied to a message while offline. Check connector configuration.
5.1.2 SMTP; 550 Host unknown.  An error is triggered when the host name can’t be found.  For example, when trying to send an email to bob@ nonexistantdomain.com. [Example kindly sent in by Paul T.]
5.1.3 Invalid recipient address.  Another problem often seen with contacts.  Address field maybe empty.  Check the address information.  Or there could be a syntax error.
5.1.4 Destination mailbox address ambiguous.  Two objects have the same address, which confuses the Exchange 2007 Categorizer.
5.1.5 Destination mailbox address invalid.
5.1.6 Problem with homeMDB or msExchHomeServerName – check how many users are affected.  Sometimes running RUS (Recipient Update Service) cures this problem.  Mailbox may have moved.
5.1.7 Invalid address.  Problem with senders mail attribute, check properties sheet in ADUC.
5.1.8 Something the matter with sender’s address
5.2.x NDR caused by the large size of the email.
5.2.1 Mailbox cannot be accessed.
5.2.2 The recipient has exceeded their mailbox storage quota.
5.2.3 Recipient cannot receive messages this big.
5.2.4 Most likely, a distribution list or group is trying to send an email.
5.3.0 Problem with MTA, maybe someone has been editing the registry to disable the MTA.
5.3.1 Mail Server system full.
5.3.2 System not accepting outside network messages.
5.3.3 Remote server has insufficient disk space to hold email.
5.3.4 Message too big.
5.3.5 System incorrectly configured.  Multiple Virtual Servers are using the same IP address and port.
5.4.0 DNS Problem.
5.4.1 No answer from host.
5.4.2 Bad connection.
5.4.3 Routing server failure.  No available route.
5.4.4 Cannot find the next hop, check the Routing Group Connector.
5.4.6 Tricky looping problem, a contact has the same email address as an Active Directory user.
5.4.7 Delivery time-out.  Message is taking too long to be delivered.
5.4.8 Microsoft advises, check your recipient policy. SMTP address should be yourdom.com. NOT server.yourdom.com.
5.5.0 Underlying SMTP 500 error.  Our server tried ehlo, the recipient’s server did not understand and returned a 550 or 500 error.
5.5.1 Invalid command.  (Rare Exchange NDR)
5.5.2 Possibly the disk holding the operating system is full.
5.5.3 Too many recipients.  More than 5,000 recipients.
5.5.4 Invalid domain name.
5.5.5 Wrong protocol version.
5.5.6 Invalid message content.
5.6.0 Corrupt message content.  Try sending without attachment.
5.6.1 Media not supported.
5.6.3 More than 250 attachments.
5.7.1 A very common Exchange 2007 NDR, the cause is a permissions problem.  For some reason the sender is not allowed to email this account. Perhaps an anonymous user is trying to send mail to a distribution list. Alternatively, a user may have a manually created email address that does not match a System Policy. Check SMTP Virtual Server Access Tab.  Try checking this box: Allow computers which successfully authenticate to relay. Check the outgoing SMTP logs. Check: Mailbox – <Mailboxname> – Properties – Mail Flow Settings – Message delivery restrictions. Try disabling Windows-Integrated-Security.  Instead allow only standard authorization on the SMTP receiver on the Exchange 2007 server. Check Attachment filtering on the Edge server.
5.7.2 Distribution list cannot expand and so is unable to deliver its messages.
5.7.3 Not Authorized, security problem.  It could be that the sender cannot send to the alternative address. On another tack, check external IP address of ISA server. Make sure it matches the SMTP publishing rule.
5.7.4 Extra security features not supported.  Check delivery server settings
5.7.5 Cryptographic failure.  Try a plain message with encryption.
5.7.6 Certificate problem, encryption level maybe to high.
5.7.7 Message integrity problem.

Want to control the properties of e-mail messages sent to a specific domain in MS Exchange powershell

Create a new remote domain by using the New-RemoteDomain cmdlet.

Type:

New-RemoteDomain -Name “Contoso.com Configuration” -DomainName contoso.com

Then modify the properties that you want for this remote domain by using the Set-RemoteDomain cmdlet:

Set-RemoteDomain “Contoso.com Configuration” -AutoReplyEnabled $True -AutoForwardEnabled $True