33 C
Dubai
Monday, May 5, 2025
Home Blog Page 84

Exchange Management Shell error – The WinRM Shell client cannot process the request–Exchange 2013

While Opening Exchange 2013 – It Errors out as below

image

Error —

New-PSSession : [Mail.careexchange.in] Processing data from remote server Mail.careexchange.in failed with the following  error message:

The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not valid.

The shell handle is valid only when WSManCreateShell function completes successfully.

Change the request including a valid shell handle and try again.

For more information, see the about_Remote_Troubleshooting Help topic. At line:1 char:1
+ New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Exch

 

Fix –

Exchange Back end Virtual Directory – SSL Certificate wasn’t assigned

 

Open – IIS –

Right click on Exchange Back End

Click on Edit Bindings

image

Click on Edit

image

Select the Valid SSL Cert

image

Do IISreset

Reopen Exchange Management shell

How to Add LUN to a Windows Server 2012 R2 Machine using EMC VNX5300

Start – Search – iSCSI Initiator

image

Open It – Discovery

Click on Discover Portal

image

Add the IP of your Storage – Leave the Default Port

image

Now Connect to the pairs like a4/b4 and a5/b5 – whichever is assigned

image

While you Connect make sure you give a Check on “Enable Multi-path”

image

Now iSCSI connector is ready on the Windows Server 2012 R2.

 

Now login to VNX

Click on Hosts –  Initiators

image

Search for the initiators machine name from where you connected

image

Now Choose one of the initiators and click on register

Choose Initiator Type – CLARiiON/VNX

Enter the new host name and IP address

Click on ok

Now do the Same process of registering the initiator record for all the other ones.

image

Now host should be listing in the host list . if its not listing refresh the host list  . You can logout and login to refresh it in worst case

 

 

Creating LUN –

 

Now Click on Hosts – LUNS

 

image

Click on Create – In the bottom

Enter the User capacity you required – am just adding a witness storage for hyper v cluster so making it a 2 GB drive

Click on Name – Type the LUN Name

image

Click on the advanced TAB

Choose default owner –SPB – (Its my case )

image

Click on Apply now LUN is ready

 

Creating Storage Group

Hosts – Storage Groups

image

Click on Create Storage Group – Enter a friendly name

image

Now Choose Yes

image

Now Choose the LUN we created now ADD the LUN

image

 

Click on the Hosts Tab –

Add the appropriate machine from the Available Hosts

image

Now Click  on Ok

——–

iSCSI connector is configured / LUN is created / Created Storage Group Add the LUN and hosts to be connected it

——-

Now Make Sure you Install the  Multipath I/O Feature on the server

image

Start – Search – MPIO

Add appropriate Vendors – Click OK

image

 

Now the Disk should have showed up on the your disk manager

Start – Run – Diskmgmt.msc

Right click on the disk – Click on Online

image

Now right click again – Initialize the disk – Choose GPT

Make it GPT – Cause MBR cannot be extended more than 1TB (Up to you)

image

Now right click on the Disk again – Convert it to a Dynamic Disk

image

Right click again Click on “New Simple Volume”

image

Make it NTFS

image

Now Drive has been added from iSCSI Storage VNX 5300

image

Blackberry Enterprise Server 12 will be released soon – What’s new ?

image

I had to write this article for users who are thinking to migrate their servers to newer versions .

As Bes10 released last year , Admins had to run BES 5 Server for Supporting older Blackberry devices and Run BES 10 Server to support BES 10 devices and MDM (Mobile Device management) for Android and iOS devices.

Now they came up with a plan of Releasing BES 12 Server later this year. which unifies BES10 and BES5 to one platform

So it will be supporting –

Older Blackberry Devices

Bes10 Devices

Android Devices

iOS devices

Windows Phone 8 – (will Included in Bes 12)

—-

Currently they have introduced a EZ PASS program. Which allows users to migrate to BES 10 with Free Technical Support until January 31, 2015

image

http://el.blackberry.com/ezpass

 

Now choice is yours . Wait for BES 12 or Migrate to BES 10 for free and jump to BES 12 again .

Enjoy the Blackberry Journey.

Does your email delivers late to your Outlook ?

I was wondering why my smart phones receive email before my Outlook does , Every time it gets a beep sound and after a while I see the same email delivers to my Outlook.

I was searching for an option to receive the email on the same time.

After a quick search , I found there is a option in your Outlook where you can define your interval timings for checking new email.

By Default Outlook 2013 does this check every 30 minutes.

Open your Outlook . Click on your SEND/RECEIVE tab

image

Click on the Send/Receive Groups

You will see a option “Schedule an automatic Send/Receive”

image

You can choose a minimum of 1 minute . and Enjoy Faster email.

If you Server is slow . Please spend 5 minutes to kick your IT admin . ha ha .

Note : This articles applies when Outlook  is Configured in Cache mode . We recommend to have the Outlook to be in cache mode . So that you can access your emails offline. Also it allows the servers to run with better performance

To Check which mode you are currently using

Click on File – Account settings

image

Double Click on your Profile you can see you are in Cache mode or in Online mode

image

 

Hope this article was informative

What is loose Truncation in Exchange 2013 Sp1 DAG (Database Availability Group)?

image

Whats is Called Loose Truncation ? in Exchange 2013 Sp1

Lets make this simple ,

Normally if one Database copy goes offline in one of the DAG Members, Logs are not Truncated in all the databases copies , Which waits for the other failed copy to come back , so that other copies can help the failed copy to re sync the logs

But this situation doesn’t help admins all the time , Lets say I have a four node DAG , if I have one failed copy – logs stops truncating  . Disks get filled up , Which stresses the admins to remove the copy and reseed later

Exchange 2013 Sp1 introduces a new feature called loose truncation  – To avoid this situation

Loose Truncation is an optional feature in Exchange 2013 DAG – if loose truncation  is enabled ,  Where database copies will check their own disk space , if disk space gets low , All the databases copies will truncate logs independently

Now when the failed copies comes back – It cannot re sync as logs have been deleted , Two options to overcome or fix the failed copy  – Enable Auto reseed or Update the database manually

How To Enable Loose Truncation

 

You need to add the below registries on Every DAG member

There are three registry values you can configure

 

Step1 –

Start – Run – Regedit

HKLM\Software\Microsoft\ExchangeServer\v15\

Create a DWORD value

BackupInformation

 

Step2-

Below BackupInformation – Create Below DWORD values

 

LooseTruncation_MinCopiesToProtect – (Value 0 Is default – Disable Loose Truncation)

This key is used to enable loose truncation. It represents the number of passive copies to protect from loose truncation on the active copy of a database

 

LooseTruncation_MinDiskFreeSpaceThresholdInMB (200GB Is default – Free disk space Goes below default value – Loose Truncation is initated)

Available disk space (in MB) threshold for triggering loose truncation

 

LooseTruncation_MinLogsToProtect – (Default Values – 100,000 for passive database copies and 10,000 for active database copies)

The minimum number of log files to retain on healthy copies whose logs are being truncated

Exchange 2013 SP1 – Released for Download – 5 Important things you should know

image

Yes , Exchange 2013 Service pack 1 is released

Download Exchange 2013 Sp1 from the below link

http://www.microsoft.com/en-us/download/details.aspx?id=41994

 

5 Important things Exchange Admins should know about Exchange 2013 Service Pack SP1

 

1. Exchange 2013 Sp1 now can be installed on Windows Server 2012 R2

2. Exchange 2013 Sp1 comes with Edge Transport server role

3. New Communication Method has been introduced where Outlook Will connect using (MAPI) over HTTP

Messaging Application Programming Interface (MAPI) over HTTP will Support Clients with explicit pause and resume functionality when their machines goes to hibernate or change networks. It will be stress relief for admin from various Outlook issues (E.g You will create a internal url like https://mail.careexchange.in/mapi)

Supported Clients for ( MAPI over HTTP) – Outlook 2013 SP1

4.It leverages DAG with no AAP (Administrative Access Points)

For Example –

You can create DAG with No static IP address

Which wont create cluster name object (CNO) in Active Directory anymore

No IP address and DNS entry for the Cluster resources

Also it will allow dynamic voting system in the cluster . Which is super cool . When one nodes goes down it recalculates and keep the existing nodes alive. When nodes comes back it rejoins the cluster with no hassle

Note – This type of cluster cannot be managed using Failover Cluster Manager , It can be managed only using PowerShell (It’s a optional feature in Exchange 2013 Sp1)

5.SSL offloading is supported,

Incoming SSL Connections can be terminated on your frontend CAS servers and move the SSL workload to a load balancer device

 

× How can I help you?