Monthly Archives: April 2020

Exchange HTTP Error 503. The Service is Unavailable

Posted on by
Reply

issue happen while renewing Degicert SSL certification , due to some unknown reason exchange took self-sign certificate which results , ECP,OWA, Exchange shell was not able to access and email follow was also interrupted

To resolved the issue below were the action taken :-

  1. To Open “ISS Manager”, Type “inetmgr” in “RUN” and select Default Web site and Open “Edit Binding option”
  2. Now Select Port “443”.

1

3. Check the SSL Certificate setting and assigned “Correct Exchange Certificate”      which you have imported with the help of degicert tool

2_2.JPG

4. Similarly, check for Port “444” Under Exchange Back End Change and View Settings.

444 is for the backed

2_3

5. After checking the Configuration of APP pools mentioned in the first restart the IIS services or restart the exchange server.

Thanks 

 

 

 

 

How to install Docker Community Edition on CentOS 8.1

Posted on by
Reply

Docker Engine Supports CentOS 8.1 to run the container on it . Docker is available in two version which is Community (CE) and Enterprise Edition

Installtion Steps :- 

Enable Docker CE Repository

Docker Package are not avilable on CentOS package Respositories , run the dnf command to enable docker CE package repository

[root@localhost admin]# dnf config-manager --add-repo=https://download.docker.com/linux/centos/docker-ce.repo

Install Docker CE using dnf Command 

[root@localhost admin]# dnf list docker-ce

CentOS-8 – AppStream                                                                                     1.1 MB/s | 6.8 MB     00:06

CentOS-8 – Base                                                                                          1.2 MB/s | 6.0 MB     00:04

CentOS-8 – Extras                                                                                        3.4 kB/s | 5.5 kB     00:01

Docker CE Stable – x86_64                                                                                 13 kB/s |  22 kB     00:01

Available Packages

docker-ce.x86_64                                             3:19.03.8-3.el7                                             docker-ce-stable

Remove podman Manpage to avoid conflicts with file from Docker Package

click here

[root@localhost admin]# sudo yum remove -y podman-manpages

Run DNF command to install latest version of docker

[root@localhost admin]# dnf install docker-ce --nobest -y

once the installtion is completed start and enable service

[root@localhost admin]#systemctl start docker
[root@localhost admin]#systemctl enable docker

verfily and test docker CE Engine

[root@docker-ce ~]# docker run hello-world

Command Output 
Unable to find image ‘hello-world:latest’ locally
latest: Pulling from library/hello-world
0e03bdcc26d7: Pull complete
Digest: sha256:8e3114318a995a1ee497790535e7b88365222a21771ae7e53687ad76563e8e76
Status: Downloaded newer image for hello-world:latest

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the “hello-world” image from the Docker Hub.
(amd64)
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/

For more examples and ideas, visit:
https://docs.docker.com/get-started/

visit also

https://www.linuxtechi.com/install-docker-ce-centos-8-rhel-8/ 

https://nishantpanchal.wordpress.com/2020/04/16/docker-conflicts-with-file-from-package-podman-manpages-on-centos-linux-release-8-1-1911-core/ 

Many Thanks for your support !

What is Joud Cloud & Services

Posted on by
Reply

What is Joud Cloud :- 

Cloud computing is the delivery of computing services – compute power, storage, applications and other IT Resources –(“Cloud Services”)on demand over the internet (“The Cloud”). Companies offering Cloud Services are called Cloud Service Providers and they charge for these services based on usage, similar to how you are billed for electricity and water at home.

Cloud Computing continues to disrupt the traditional work of IT and transform the way companies of all verticals and sizes are doing business. Moving to the cloud provides companies with more agility, elasticity, cost saving and the ability to expand their business footprint and to develop a global reach towards their customers.

 What Services Joud Cloud Offers :-

JOUD Cloud Services is a secure cloud services platform with a broad set of services such as computing power, storage, business continuity and information security to help businesses scale and grow, all delivered as a utility: on-demand, available in minutes, with a pay-as-you-go pricing model.

With JOUD Cloud Services, you don’t need to make large upfront investments in hardware and software licensing, to run your business applications neither go through the hustle of spending a lot of time on managing them, instead, you can provision and access exactly the right type and size of computing resources you need, almost instantly, and only pay for what you use

Information Managment :- 

  • Compute and Storage
  • Backup and Recovery
  • Disaster Recovery
  • Enterprise File Sharing

Information Security :- 

  • Firewall
  • End Point Protection
  • Email Security
  • WAF
  • Advanced Threat Protection
  • SIEM

Partner with:-

  • Fortinet
  • Nutanix
  • veeam
  • Rubrik
  • Carbonite

 

To know more :-

https://joud.cloud/

sales@joud.cloud

 

Thanks

Docker Conflicts with File from Package podman-manpages on CentOS Linux release 8.1.1911 (Core)

Posted on by
1

Docker installation on the Centos is very simple and quick , As part of docker installation steps on the centos you might face following error after running dnf command to install latest version of docker,

# “dnf install docker-ce –nobest -y”

Errror: Transaction check error:
file /usr/share/man/man1/docker-attach.1.gz from install of docker-ce-cli-1:19.03.8-3.el7.x86_64 conflicts with file from package podman-manpages-1.4.2-5.module_el8.1.0+237+63e26edc.noarch
file /usr/share/man/man1/docker-build.1.gz from install of docker-ce-cli-1:19.03.8-3.el7.x86_64 conflicts with file from package podman-manpages-1.4.2-5.module_el8.1.0+237+63e26edc.noarch
file /usr/share/man/man1/docker-commit.1.gz from install of docker-ce-cli-1:19.03.8-3.el7.x86_64 conflicts with file from package podman-manpages-1.4.2-5.module_el8.1.0+237+63e26edc.noarch
file /usr/share/man/man1/docker-container-prune.1.gz from install of docker-ce-cli-1:19.03.8-3.el7.x86_64 conflicts with file from package podman-manpages-1.4.2-5.module_el8.1.0+237+63e26edc.noarch
file /usr/share/man/man1/docker-container.1.gz from install of docker-ce-cli-1:19.03.8-3.el7.x86_64 conflicts with file from package podman-manpages-1.4.2-5.module_el8.1.0+237+63e26edc.noarch

So in these case podman mainpages are conflicts with the Docker ,so to fix these i just remove the manpage from podman, but keep podman. Run following command to remove podman-manpages

# sudo yum remove -y podman-manpages

Thanks

 

How to Run Enterprise Vault Throttling Policy on Exchange Server

Posted on by
Reply

Exchange Server 2013 and 2010 have a default throttling policy which restricts user accounts to no more than 20 open connections to the server. This restriction on the Vault Service account would cause failures of the Enterprise Vault tasks that run under the account. To prevent these failures, you must remove the restriction from the Vault Service account when you archive from Exchange Server 2013 and 2010.

Enterprise Vault includes a PowerShell script called SetEVThrottlingPolicy.ps1 which creates a new policy and assigns it to the Vault Service account to remove the restriction. You must run SetEVThrottlingPolicy.ps1 against an Exchange 2013 or 2010 mailbox. If your Vault Service account already has a mailbox on Exchange Server
2007 or earlier, you must first move the mailbox to Exchange 2013 or 2010.

However, in certain circumstances it may be problematic to create and assign this policy via the powershell script provided. In those situations the below commands can be manually run to create and assign the policy to the Vault Service Account mailbox.

Example:

.\SetEVThrottlingPolicy.ps1 -user domainname\vsa -server EX2013-CAS.EV.Local

— After running the command if it is asking for user name & password
Please use exchange server credentials, using that currently you are logged in.
Example : domainname\exchangeadmin and password = *******

in my case i had issue with archving where the task was unable to archive item with the error Lie Mode Lock

https://www.veritas.com/support/en_US/article.100013533