Windows and Linux Real time scenarios and answers that Works

On the Windows Taskbar, click Start > Programs > Administrative Tools > Group Policy Management . The version of Windows that you use may display All Programs instead of Programs in the Start menu. In the Group Policy Management window, in the console tree, expand the domain, expand Computer Configuration , expand Software Settings , right-click Software Installation , and then click Properties . On the Advanced tab, check Uninstall this application when it falls out of the scope of management , and then click OK . In the right pane, right-click the software package, and then click Remove . In the Remove Software dialog box, check Immediately uninstall the software from users and computers , and then click OK . Close the Group Policy Object Editor window, and then close the Group Policy Management window. The software uninstalls when the client computers are restarted.

 Issue With Microsoft Windows Server 2003, you get the following events and the server performance may be degraded: Type: Error Date: Date Time: Time Event ID: 333 Source: Application Popup User: N/A Computer: MachineName Description: An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry. Additional symptoms that you might see with this event are the following: Performance issues with the SQL databases. Issues with cluster resources going offline. File/Print server performance issues. Login issues where you get insufficient memory errors and profile load issues. Complete server hang. SQL server error logs may report I/O related errors. Solution The Event ID 333s are written to the system event log if the Microsoft Windows operating system is not able to flush and write to the registry hive. Even

0x8007046A When Copying a Large File Warning : This post deals with editing the registry. If you don’t know what that is stop right here & ask someone else to help you. Using the registry editor incorrectly can cause serious problems that may require you to reinstall Windows. Use the registry editor at your own risk. When copying a large file from Windows Server 2003 to Windows Server 2008 R2 you may receive an error that says, “Error 0x8007046A: Not enough server storage is available to process this command.” If you try to copy the same file to a USB hard drive on the Windows Server 2003 box you get a similar error that says, “Cannot copy filename : Insufficient system resources exist to complete the requested service.” To resolve this create the following registery entry on the Windows Server 2003 box & reboot the server. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters] “IRPStackSize”=dword:00000015 If you

If you have an application that you want to run on Windows Server 2012  that requires the .NET Framework 3.5, you will most likely run in to a problem when trying to install it. If you are trying to install .NET Framework 3.5 from the  Server Manager  GUI, you will see this when installing the feature: “Do you want to specify an alternate source path? One or more installation selections are missing source files…” To solve this, you can either: 1. Go to a command prompt and enter this: dism /online /enable-feature /featurename:NetFX3 /all /Source:d:\sources\sxs /LimitAccess Note: Source should be the Windows installation disc. In my case, this was located on D: 2. Go down to “Specify an alternate source path” and enter “d:\sources\sxs” as the path. Now you should see this under your Features list:

Install Telnet Client on Windows Server 2008 R2 or Windows Server 2008 On Windows Server 2008, you can use the Role Management tool to install optional components. To install Telnet Client on Windows Server 2008 R2 or Windows Server 2008 Start Server Manager. Click Start , right-click Computer , and then click Manage . If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue . In the Features Summary section, click Add features . In the Add Features Wizard , select Telnet Client , and then click Next . On the Confirm Installation Options page, click Install . When installation finishes, on the Installation Results page, click Close .

Requirement: Minimum: Single processor with 1.4 GHz (x64 processor) or 1.3GHz (Dual Core) Minimum: 512 MB RAM Minimum: 32 GB or greater The first step is to assign a ip to the server that you going to deploy the AD. Its nessary to install it as DNS server too. So its better to have fixed ip it doesn't mean you cannot install AD without fixed ip address but it will solve lot of issues if you used fixed ip. In here the server ip is 10.0.0.14. Since we going to make it as DNS server too you should use the same ip as the preferred DNS server. Next step is to install the Active directory roles. Unlikely the older version of windows servers Microsoft highly recommend to use server manager option to install roles before you run dcpromo. Click on start menu and select the Server Manager Select the roles from the right hand panel and click on add roles option. From the roles list select the "Active Directory Domain Services" role and Click &qu

A Red Hat Certified System Administrator (RHCSA) is able to perform the following tasks: Understand and use essential tools for handling files, directories, command-line environments, and documentation Operate running systems, including booting into different run levels, identifying processes, starting and stopping virtual machines, and controlling services Configure local storage using partitions and logical volumes Create and configure file systems and file system attributes, such as permissions, encryption, access control lists, and network file systems Deploy, configure, and maintain systems, including software installation, update, and core services Manage users and groups, including use of a centralized directory for authentication Manage security, including basic firewall and SELinux configuration Configure a FTP server which is anonymous download to all user in your network and allow the user with

Resize Logical Partition (LVM) In Linux A Red Hat Certified System Administrator (RHCSA) is able to perform the following tasks: Understand and use essential tools for handling files, directories, command-line environments, and documentation Operate running systems, including booting into different run levels, identifying processes, starting and stopping virtual machines, and controlling services Configure local storage using partitions and logical volumes Create and configure file systems and file system attributes, such as permissions, encryption, access control lists, and network file systems Deploy, configure, and maintain systems, including software installation, update, and core services Manage users and groups, including use of a centralized directory for authentication Manage security, including basic firewall and SELinux configuration. Resize y

There are different ways to solve this issue , Few of them are mentioned below .A permanent fix for this issue is yet to find. Solution : 1 Remove "Windows Live Messenger" from their terminal server resolved logout issues. Solution : 2 Start "Remote Desktop Services Manager" Identify the user ID in the Users tab In the Processes tab sort by ID Go down to the user ID and end the winlogon.exe process the user session will be logged off Solution : 3 From: mikefrobbins.com by graham ross From a command prompt on my PC or another computer on the domain I ran this to find out the PID of the svchost.exe associated with SENS sc \servername queryex SENS Note down the PID of that process and kill that process using PID. taskkill /S servername /PID xxxx /F Solution: 4 From : Windows Sever Forum The COM+ Event System timed out attempting to fire the Logoff method on event class {D5978650-5B9F-11D1-8DD2-00AA004ABD5E} for publisher and subscriber . The subscriber failed

By default a Windows Server 2012 Hyper-V virtual machine is configured to automatically save the state of the virtual machines when the physical computer is turned off without shutting down the guest operating systems. With this configuration, if the corresponding service was running during the shutting down of the physical computer, the virtual machines automatically boot up from the saved state after the physical computer powers on again. With this kind of default configuration, the overall boot time of the physical Windows Server 2012 becomes quite slow. In order to use the virtual machines efficiently, you can configure the Hyper-V VMs to automatically shut down before the physical computer is finally shut down. Here is how you can configure the Windows Server 2012 Hyper-V virtual machine settings in order to get the optimum results: Using the appropriate account that has the required privileges, log on to the Windows Server 2012 computer on which the Hyper-V r

An authentication error has occurred. The Local Security Authority cannot be contacted" issue Workaround : Login into the server Right click on computer--> Properties --> Remote settings Uncheck the following option  Allow Connections only from computer  Running Remote Desktop with Network Level Authentication.

OpenSSL CVE-2014-0160 Heartbleed bug and Red Hat Enterprise Linux Issue Does CVE-2014-0160 affect Red Hat Enterprise Linux? Need fix for openssl heartbleed bug What versions of Red Hat Enterprise Linux are affected by openssl heartbleed vulnerability? Do we have a list of packages/services we ship with RHEL that need a restart after OpenSSL has been updated? Environment Red Hat Enterprise Linux 7 Release Candidate (RC) not affected Red Hat Enterprise Linux 7 Beta affected Red Hat Enterprise Linux 6 affected Red Hat Enterprise Linu

Press the power button on your system, and after few moments you see the Linux login prompt. Have you ever wondered what happens behind the scenes from the time you press the power button until the Linux login prompt appears? The following are the 6 high level stages of a typical Linux boot process. 1. BIOS BIOS stands for Basic Input/Output System Performs some system integrity checks Searches, loads, and executes the boot loader program. It looks for boot loader in floppy, cd-rom, or hard drive. You can press a key (typically F12 of F2, but it depends on your system) during the BIOS startup to change the boot sequence. Once the boot loader program is detected and loaded into the memory, BIOS gives the control to it. So, in simple terms BIOS loads and executes the MBR boot loader. 2. MBR MBR stands for Master Boot Record. It is located in the 1st sector of the bootable disk. Typically /dev/hda, or /dev/sda MBR is less than 512 bytes in size. This has three

pam_tally2 module is used to lock user accounts after certain number of failed ssh login attempts made to the system. This module keeps the count of attempted accesses and too many failed attempts. pam_tally2 module comes in two parts, one is pam_tally2.so and another is pam_tally2 . It is based on PAM module and can be used to examine and manipulate the counter file. It can display user login attempts counts, set counts on individual basis, unlock all user counts. By default, pam_tally2 module is already installed on the most of the Linux distributions and it is controlled by PAM package itself. This article demonstrates on how to lock and unlock SSH accounts after reaching a certain failed number of login attempts. How to Lock and Unlock User Accounts Use ‘ /etc/pam.d/password-auth ‘ configuration file to configure login attempts accesses. Open this file and add the following AUTH configuration line to it at beginning of the ‘ auth ‘ section.   auth

Hello All, The following are the troubleshooting steps that you need to perform if you receive the error message as NTLDR IS MISSING in Windows 2003 server. Pre-requisites : For this you need one Floppy Drive, one Floppy and Windows 2003 server bootable CD respected to its installed versions. Steps to be performed. 1) Reboot the server and check error is still persisting 2) Download the Raid drivers for the Raid controller if you have configured Raid on the server. 3) Write the downloaded Raid drivers to a floppy disk. 4) Connect the Floppy Disk drive to the server and insert the 2003 server bootable CD into the CD drive and reboot the server and then boot with the CD. 5) Press F6 to load the SATA / SCSI Raid Driver 6) when it prompts press S to load the Driver. 7) Follow the onscreen instructions to load the Raid Drivers. 8) Press R to repair the Windows 9) Enter the Administrator password when it prompts. 10) copy E:\i386\ntldr C:\ Note : a) For the ser

Red Hat Linux Static Routing Configuration I've two network interface connected to two different routers as follows:   [a] eth0 LAN network 10.0.0.0/8 - gateway IP - 10.8.2.65 [b] eth1 ISP assigned network 202.54.22.128/28 - gateway IP - 202.54.22.129 I can only ping to public server but not to another servers inside LAN? I'm not able to route traffic via 10.8.2.65. How do I configure static routing under Red Hat Enterprise Linux 5.x or CentOS Linux 5.2? A. Under Red Hat you need to define static routing using route command. The configuration is stored under /etc/sysconfig/network-scripts/route-eth0 for eth0 interface. Update route using route command Type the following command: # route add -net 10.0.0.0 netmask 255.0.0.0 gw 10.8.2.65 eth0 # route -n Create static routing file The drawback of abive 'route' command is that, when RHEL reboots it will forget static routes. So store them in configuration file: echo '10.0.0.0/8 via

Configuring rsyslog on the Centralized Logging Server The steps in this procedure must be followed on the system that you intend to use as your centralized logging sever. All steps in this procedure must be run while logged in as the root user. Configure SELinux to allow rsyslog traffic. # semanage -a -t syslogd_port_t -p udp 514 Configure the iptables firewall to allow rsyslog traffic. Open the /etc/sysconfig/iptables file in a text editor. Add an INPUT rule allowing UDP traffic on port 514 to the file. The new rule must appear before any INPUT rules that REJECT traffic. -A INPUT -m state --state NEW -m udp -p udp --dport 514 -j ACCEPT Save the changes to the /etc/sysconfig/iptables file. Restart the iptables service for the firewall changes to take effect. # service iptables restart Open the /etc/rsyslog.conf file in a text editor. Add this line to the file, defining the location logs will be saved