Skip to main content

Posts

Showing posts with the label Linux

Modify The Tombstone Lifetime

I would include a few PowerShell scripts here that can be used to modify the tombstone lifetime along with the deleted object lifetime. Remember that the default for both of these is going to be 180 days and will show up as Null if you use LDP to view the attributes. PowerShell Script to change the tombstone lifetime of my domain (AdminPrep.Local) to 250 days: Set-ADObject -Identity “CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=AdminPrep,DC=Local” –Partition “CN=Configuration,DC=AdminPrep,DC=Local” –Replace:@{“tombstoneLifetime” = 250} PowerShell Script to change the deleted object lifetime: Set-ADObject -Identity “CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=AdminPrep,DC=Local” –Partition “CN=Configuration,DC=AdminPrep,DC=Local” –Replace:@{“msDS-DeletedObjectLifetime” = 250} Courtesy : LazySysAdmin

Configure NIS Services in a Linux server

What is NIS? Network Information Service (NIS) is used for keeping a centralized repository of users, hostnames and other useful information in a computer network. In single server UNIX environments, the list of users and groups is usually kept in a file such as  /etc/passwd . Using NIS adds a "global" directory which is used for authenticating users from any host on the network. Install the Packages: Install the  yp-tools, ypbind and  ypserv  rpm packages on the server. [root@nissrv1 /]# rpm -qa |grep ypbind ypbind-1.12-5.21.6 [root@ nissrv1 /]# rpm -qa |grep ypserv ypserv-2.8-7 [root@ nissrv1 /]# rpm -qa |grep yp-tools yp-tools-2.8-6 Defining the NIS Domain Name: Edit the  /etc/sysconfig/network  file  We need to add the NIS domain name we wish to use in the /etc/sysconfig/network file.  For this example, we will call the domain "LINUX-NIS".  #/etc/sysconfig/network NISDOMAIN="LINUX-NIS"   Note : Use Non-FQDN Names.Edit /etc/hosts file as well t

Setup a Kickstart Server

1. Install and configure the DHCPD server 02. Install tftp server and enable TFTP service a. yum install tftp-server b. Enable TFTP server. vi /etc/xinetd.d/tftp and change disable to 'no' c. service xinetd restart 03. Install syslinux if not already installed a. yum install syslinux 04. Copy needed files from syslinux to the tftpboot directory cp /usr/lib/syslinux/pxelinux.0 /tftpboot cp /usr/lib/syslinux/menu.c32 /tftpboot cp /usr/lib/syslinux/memdisk /tftpboot cp /usr/lib/syslinux/mboot.c32 /tftpboot cp /usr/lib/syslinux/chain.c32 /tftpboot 04. Create the directory for your PXE menus mkdir /tftpboot/pxelinux.cfg 05. For each "Release" and "ARCH" Copy vmlinuz and initrd.img from /images/pxeboot/ directory on "disc 1" of that $Release/$ARCH to /tftpboot/images/RHEL/$ARCH/$RELEASE mkdir -p /tftpboot/images/RHEL/i386/4.3 mkdir -p /tftpboot/images/RHEL/i386/5.5 mkdir -p /tftpboot/images/RHEL/x86_64/4.3 mkd

Starting a Kickstart Installation

Firstboot  does not run after a system is installed from a Kickstart file unless a desktop and the X Window System were included in the installation and graphical login was enabled. Either specify a user with the  user  option in the Kickstart file before installing additional systems from it (refer toSection 32.4, “Kickstart Options” for details) or log into the installed system with a virtual console as root and add users with the  adduser  command. To begin a kickstart installation, you must boot the system from boot media you have made or the  Red  Hat  Enterprise  Linux DVD, and enter a special boot command at the boot prompt. The installation program looks for a kickstart file if the  ks  command line argument is passed to the kernel. DVD and local storage The  linux ks=  command also works if the  ks.cfg  file is located on a vfat or ext2  file  system  on local storage and you boot from the Red Hat Enterprise  Linux  DVD. With Driver Disk If you need to use a driver disk w