Tag Archives: System Administration
Domain controller as server for hosting your company Active Directory (AD) is very important part of your network infrastructure. In case of its failure logging users on AD is impossible. Because of that one of the main things in planning your network infrastructure is make plan for implementing redundant domain controller in network infrastructure. In case you have it, failure of one of them does not mean that user will be unable to log on the system. Since failed domain controller is up again, backup controller will be in function of users authentication or other functions which it can have (DNS server etc.). On this way your network can stay functional, reliable and more resistible to failures.
This is the 2nd Part of the article. You can read 1st part here. Just to let you be aligned with us, we considered
- The name of the central server is ldap1.yourcompany.com with IP 192.168.100.201
- To test the configuration we have another server internal.yourcompany.com with IP 192.168.100.10
- sifatpeter is the name of the user we will use for testing the solution
which was defined in the 1st part of the article. We ensured that the ldap service was configured and the service was up and running. Be informed that the ldap daemon named is slapd, for openldap suit.
Using same password to login multiple systems was an ambition for System Administrators from long time back. Network Information System (NIS) was one of the early implementation to achieve that goal. But NIS had few drawbacks which required strong alternative to support the requirement. We know, LDAP (Lightweight Directory Access Protocol) was originally developed to provide directory services based on the X.500 standard. Microsoft used LDAP Active Directory Service and Novell used for Novell Directory Services (NDS) products. LDAP’s inherent features makes it a strong alternative for NIS to be used for central authentication.In this article we will try to show you how you can achieve central authentication system using Linux and LDAP for SSH login.
This is the continuation of article on Linux performance. In Part 1 we have discussed on performance related to Memory and Log files. Here we will continue the same for CPU. We hope our Part 3, and final part, will be about Disk and Network.
Hope we are not running out of CPU
Generally performance bottleneck that we have discussed in Part 1 or for any reason, CPU is the respondent to the user. When CPU is not free we say we are having performance problem. Even for Memory shortage, CPU had to do a lot of other extra tasks to perform the computing requests of running processes to mitigate Memory shortage and as a consequence we get busy CPU. That we have discussed how to know if the problem comes from Memory Shortage. Now we will discuss how we will know that our system has enough Memory but it’s a pure CPU shortage.
This is the Part 2 of our previous article about Active Directory Federation Service. You can visit Part 1 here.
When you have Federation Services installed as server roles on both sides of federation (account and resource) you have to properly configure servers to establish trust between them. Configuration includes configuring trust policy on both servers, create and configure group claim and AD account store and establish trust by importing policy from one federation server to another, on partner side. In this article I will describe process of AD FS server configuration. Configuration of both federation servers (account and resource) will be described.
When you install a fresh Linux box, may be for web server or mail server or for other services, you see the server performance is very good at the beginning. But performance of the server degrades gradually day by day and you are frustrated. But most of the time, just practicing good System Admin deeds you can keep your system’s performance in optimum level. In his article, we will show you what are the easy secrets you should always remember to keep your system’s performance up to the mark. Remember we are not touching any performance issue that may cause by application itself.
Active directory federation service is Windows component which enables authentication of users on sites beyond its administrative domain. Example for this type of authentication is when users from one site have to access resources on some external site such as resources in partner network (e.g. Partner web sites etc.) When resource on remote site needs authentication for accessing, but “local” credentials should to be used, that is point where Active Directory Federation Service (AD FS) takes place.
Active Directory Federation Services enable using your AD (Active Directory) service to authenticate its users when they access resources belonging to other domains and placed on remote locations. To enable service which allows this type of authentication Active Directory federation should de established between two remote sites. There should be Active Directory Federation servers placed on both locations.
HTTP Server is a web server developed and maintained by The Apache Software Foundation. The stated objective of Apache is to create an open source HTTP server that will run on any modern operating system and hardware. In addition to it’s wide platform support, Apache is also infinitely configurable. LDAP, Lightweight Directory Access Protocol, is an Internet protocol that email and other programs use to look up information from a server. With Apache+LDAP authentication Apache users are stored in LDAP directory is very useful in single sign-on (SSO) authentication on various Apache servers and LDAP directory. In this article we will show how you can configure Apache to authentication users from LDAP directory.
- Working Apache 2.1 or later
- OpenLDAP server, client and other libraries and utilities.
Below yum commands may help you to install them if you don’t have them ready. If you don’t have yum you can use similar commands (e.g. apt-get) to install them.
Many organizations and companies have implemented Microsoft Active directory service as central database of their information system objects. You can think about Active Directory (AD) as database of all objects used in your company information system. Those objects are computers as main part of your IT systems, then users, group of users, printers, scanners, applications and many other objects used in production computer network and IT system. Active directory is used for centralization control of all objects placed in it.
Active Directory has logical and physical structure. Logical structure of AD is database of objects in your infrastructure. But all data from AD should be placed on physical servers. These server which host data from AD are domain controllers. There can be one or more domain controllers on which AD structure are placed. Because of complexity of its structure planning and organizing it before implementation, it is not easy task and needs big effort to achieve efficient and useful implementation of your AD company infrastructure.
is very known to best suited open source Database system when it comes about web application. But still it shows bad performance which causes bad times for web site owners. Most of the time its not MySQL’s capability, rather database design or SQL code causes MySQL act badly. In this article we will discuss about some common issues related MySQL performance and give you some direction to fixing this problem.
Generally there are 4 kinds of problem that may hit MySQL performance:
- Inefficient schema design
- Poor indexing or no indexing
- Bad SQL Code writing
- Server Variable not tuned properly