Sponsored Content
Special Forums Windows & DOS: Issues & Discussions Analogues applications between Windows Application to Linux Post 302924133 by gandolf989 on Thursday 6th of November 2014 12:38:23 PM
Old 11-06-2014
Quote:
Originally Posted by andresguillen
Hi Guys
I have a network where exist differences windows applications like
Active Directory (to management the profile of each person)
DNS

Well, as you know for these applications the company must be, every year, buy licenses.
I want know what option exist I could test / evaluate with the aim of remove the AD and the DNS

I appreciate your comments / suggestion

Best Regards
I don't think that you need to choose between managing Linux and Windows servers. For example, you can use Active Directory to manage the usernames and passwords in Linux. I have used system with AD managing connections but I did not install or set that up. So I am not sure how to install it.

The thing you might want to focus on is maintaining a single sign on across all servers and workstations and making sure that everyone has access to the applications that they need and that they work.

Having said that, for me anytime I can kill something that only runs on Windows and convert to something that runs on Linux I would do just that. But you have to find the business need to migrate from one application to another.
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

executing applications/commands on a unix server from a windows PC

i have a network drive (samba) mounted on to my PC and also i have SSH client on my machine. however i need to run applications/commands on a unix server from the middle of a different executable(windows compatable one). so i need to connect to the unix server from SSH through the... (1 Reply)
Discussion started by: megastar
1 Replies

2. UNIX for Dummies Questions & Answers

What kind of security applications UNIX and Windows have in common?

Hi guys, may I know what kind of security applications do UNIX and Windows have in common? This is related to a project that is approaching its deadline, so would you all please be kind enough to help me? Thank You. (0 Replies)
Discussion started by: austintham
0 Replies

3. Windows & DOS: Issues & Discussions

Porting Applications Using Windows SFU

I am trying to port a UNIX POSIX compliant application to Windows using Windows Services For UNIX version 3.5. The application is written in C and therefore I need to compile it using the cc command. I am running into many problems, but the one that specifically has me stuck right now is this.... (0 Replies)
Discussion started by: sidinsd
0 Replies

4. AIX

How can invoke applications on Windows machine from AIX server

Hi folks, Before I start explaning my problem let me tell you I am new to Unix environment. I am working on a application. It was developed in java (on Windows machine). But application for production will be deployed on AIX machine. One of my requirement is I need to invoke QTP scripts and... (3 Replies)
Discussion started by: sachinrt
3 Replies

5. UNIX for Dummies Questions & Answers

startX windows application during boot.....putty connection takes the windows

Dear all i am new to linux/debian i run my application on the computer...during startup in bashrc i wrk wid dis script to invoke startx..i do this above command and it works perfectly... if && ; then startx -- -br 1>/dev/null exit 0 fi i use winscp for file transfer and putty for... (1 Reply)
Discussion started by: venkat_330
1 Replies

6. UNIX for Dummies Questions & Answers

How can I rebuild applications that developed in UNIX? I need to use it in windows os with cygwin

I need to rebuild an application that developed in unix environment and run in windows OS with cygwin. so How can I rebuild from the source code? is there any one who said something on this regard? (2 Replies)
Discussion started by: bejirond
2 Replies
REALMD.CONF(5)							   File Formats 						    REALMD.CONF(5)

NAME
realmd.conf - Tweak behavior of realmd CONFIGURATION FILE
realmd can be tweaked by network administrators to act in specific ways. This is done by placing settings in a /etc/realmd.conf. This file does not exist by default. The syntax of this file is the same as an INI file or Desktop Entry file. In general, settings in this file only apply at the point of joining a domain or realm. Once the realm has been setup the settings have no effect. You may choose to configure SSSD[1] or Winbind[2] directly. Only specify the settings you wish to override in the /etc/realmd.conf file. Settings not specified will be loaded from their packaged defaults. Only override the settings below. You may find other settings if you look through the realmd source code. However these are not guaranteed to remain stable. There are various sections in the config file. Some sections are global topic sections, and are listed below. Other sections are specific to a given realm. These realm specific sections should always contain the domain name in lower case as their section header. Examples of each setting is found below, including the header of the section it should be placed in. However in the resulting file only include each section once, and combine the various section setting together as lines underneath the section. For example [users] default-home = /home/%U default-shell = /bin/bash ACTIVE-DIRECTORY These options should go in an [active-directory] section of the /etc/realmd.conf file. Only specify the settings you wish to override. default-client Specify the default-client setting in order to control which client software is the preferred default for use with Active Directory. [active-directory] default-client = sssd # default-client = winbind The default setting for this is sssd which uses SSSD[1] as the Active Directory client. You can also specify winbind to use Samba Winbind[2]. Some callers of realmd such as the realm command line tool allow specifying which client software should be used. Others, such as GNOME Control Center, simplify choose the default. You can verify the preferred default client softawre by running the following command. The realm with the preferred client software will be listed first. $ realm discover domain.example.com domain.example.com configured: no server-software: active-directory client-software: sssd type: kerberos realm-name: AD.THEWALTER.LAN domain-name: ad.thewalter.lan domain.example.com configured: no server-software: active-directory client-software: winbind type: kerberos realm-name: AD.THEWALTER.LAN domain-name: ad.thewalter.lan os-name (see below) os-version Specify the os-name and/or os-version settings to control the values that are placed in the computer account operatingSystem and operatingSystemVersion attributes. This is an Active Directory specific option. [active-directory] os-name = Gentoo Linux os-version = 9.9.9.9.9 SERVICE
These options should go in an [service] section of the /etc/realmd.conf file. Only specify the settings you wish to override. automatic-install Set this to no to disable automatic installation of packages via package-kit. [service] automatic-install = no # automatic-install = yes USERS
These options should go in an [users] section of the /etc/realmd.conf file. Only specify the settings you wish to override. default-home Specify the default-home setting in order to control how to set the home directory for accounts that have no home directory explicitly set. [users] default-home = /home/%D/%U # default-home = /nfs/home/%D-%U The default setting for this is /home/%D/%U. The %D format is replaced by the domain name. The %U format is replaced by the user name. You can verify the home directory for a user by running the following command. $ getent passwd 'DOMAIN/User' DOMAINuser:*:13445:13446:Name:/home/DOMAIN/user:/bin/bash Note that in the case of IPA domains, most users already have a home directory configured in the domain. Therefore this configuration setting may rarely show through. default-shell Specify the default-shell setting in order to control how to set the Unix shell for accounts that have no shell explicitly set. [users] default-shell = /bin/bash # default-shell = /bin/sh The default setting for this is /bin/bash shell. The shell should be a valid shell if you expect the domain users be able to log in. For example it should exist in the /etc/shells file. You can verify the shell for a user by running the following command. $ getent passwd 'DOMAIN/User' DOMAINuser:*:13445:13446:Name:/home/DOMAIN/user:/bin/bash Note that in the case of IPA domains, most users already have a shell configured in the domain. Therefore this configuration setting may rarely show through. REALM SPECIFIC SETTINGS
These options should go in an section with the same name as the realm in the /etc/realmd.conf file. For example for the domain.example.com domain the section would be called [domain.example.com]. To figure out the canonical name for a realm use the realm command: $ realm discover --name DOMAIN.example.com domain.example.com ... Only specify the settings you wish to override. computer-ou Specify this option to create directory computer accounts in a location other than the default. This currently only works with Active Directory domains. [domain.example.com] computer-ou = OU=Linux Computers,DC=domain,DC=example,DC=com # computer-ou = OU=Linux Computers, Specify the OU as an LDAP DN. It can be relative to the Root DSE, or a complete LDAP DN. Obviously the OU must exist in the directory. It is also possible to use the --computer-ou argument of the realm command to create a computer account at a specific OU. user-prinicpal Set the user-prinicpal to yes to create userPrincipalName attributes for the computer account in the realm, in the form host/computer@REALM [domain.example.com] user-principal = yes automatic-id-mapping This option is on by default for Active Directory realms. Turn it off to use UID and GID information stored in the directory (as-per RFC2307) rather than automatically generating UID and GID numbers. This option only makes sense for Active Directory realms. [domain.example.com] automatic-id-mapping = no # automatic-id-mapping = yes manage-system This option is on by default. Normally joining a realm affects many aspects of the configuration and management of the system. Turning this off limits the interaction with the realm or domain to authentication and identity. [domain.example.com] manage-system = no # manage-system = yes When this option is turned on realmd defaults to using domain policy to control who can log into this machine. Further adjustments to login policy can be made with the realm permit command. fully-qualified-names This option is on by default. If turned off then realm user and group names are not qualified their name. This may cause them to conflict with local user and group names. [domain.example.com] fully-qualified-names = no # fully-qualified-names = yes AUTHOR
Stef Walter <stef@thewalter.net> Maintainer NOTES
1. SSSD https://fedorahosted.org/sssd/ 2. Winbind http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/winbind.html realmd 06/10/2014 REALMD.CONF(5)
All times are GMT -4. The time now is 03:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy