How to disable TCP/IP Properties button

Sometimes we need to set prohibit for administrative access to prevent users for changing IP address. In this case, if all the computers are not a connected to domain see the solution. This policy is working who have access whatever or IP address is setting by static or dynamic.

1. Start - Run - gpedit.msc - Enter.

2. Group Policy – User configuration – Administrative Templates – Network – Network Connections – “Prohibit access to properties of a LAN connection”

 

 

 

3. Open  “Prohibit access to properties of a LAN connection” – select “Enable” – click Apply. 

How to: OpManager 8 Free Edition installation on RHEL 5

I. OpManager Installation

1. Download OpManager 8 http://www.manageengine.com/products/opmanager/download.html .

[root@localhost]# ls
ManageEngine_OpManager.bin

[root@localhost]# chmod u+x *
[root@localhost]# ls –l
-rwxr-xr-x root root 5723539 Dec 7 4:24 ManageEngine_OpManager.bin
[root@localhost]# ./ManageEngine_OpManager.bin

InstallShield Wizard
Initializing InstallShield Wizard…
Searching for Java(tm) Virtual Machine….
Preparing Java(tm) Virtual Machine…
………………………….
……………………………..
2. The InstallShield Wizard will install “ManageEngine Opmanager 8” windows open on your computer. To continue, then click next.
3. Choose “I accept the terms of the license agreement.”
4. Choose the Opmanager Edition (Free Edition).
5. Select your language. (By default English)
6. Click Next to install “ManageEngine Opmanager 8” in this directory.
Default directory name: /opt/AdventNet/ME/Opmanager
7. Select the Web Server Port Number. Default web server port number is 80.
8. Details of Installation and click Next.
9. Wait for installing ManageEngine Opmanager.
10. Cleck “NO” for a newer keytool file.
11. Extracing Files. Wait for a minutes.
12. Select the Server Name.
13. Information Box for confirm.
14. The InstallShield Wizard has successfully installed ManageEngine Opmanager.

II. OpManager 8 configuration

How to Fix: Event Log Error, Event ID: 10016

(System Log/ Event Log) Error Message:

ERROR: DCOM, Event ID: 10016 NT AUTHORITY\SYSTEM Description: The application-specific permission settings do not grant local launch permission for the COM Server application with CLSID {24FF4FDC-1D9F-4195-8C79-0DA39248FF48} to the user NT AUTHORITY\SYSTEM SID (s-1-5-18). This security permission can be modified using the Component Services administrative tool.

According to http://support.microsoft.com/kb/899965 link, I searched the registry for the CLSID {24FF4FDC-1D9F-4195-8C79-0DA39248FF48} and it turned out to be Quarantine Private SHA Binding class with an AppID of {B292921D-AF50-400c-9B75-0C57A7F29BA1} which I have been able to match up with the Network Access Protection Agent (“NAP Agent Service”).

Consequent:

May your computer:

-          can not connect to remote desktop

-          somehow stopped periodically ping

-          RDP session terminates and is not renewed

-          Locally connected to the “fallen” PC

-          You saw a message stating that “not enough system memory to complete operation”

-          Slow booting

-          Blue screen

Cause:

This error can occur on any operation system. Error occurs when the administration Agent is trying to use Network Access Protection. By default, the user is not SYSTEM DCOM-the rights to run the Network Access Protocol Agent. Or if you use Novell Client software on your company network it may to cause of this problem.

For our system this error can occur following items:

1. Users with Novell Client old version
2. Somehow related to the Anti-Virus program installed on clients.

Fix:

1. Upgrade Novell client software to last one.
2. Download natfix.zip file from this link http://support.kaspersky.ru/downloads/utils/napfix.zip. And to disable Network Access Protection Agent must specify a file disablenap.exe. Run disablenap.exe file.

How-to-Setup-your-own-primary-and-secondary-name-servers

Simple Steps in creating your own name servers on redhat-release box.

STEP 1

Requirements:

Server with additional free virtual IP address.

Make sure that you have your domain and the associated name servers registered through your registrar such as enom, networksolutions, etc. Also make sure that the name servers reolves to your server.

First we need to get the following bind packages, Which can be installed using "yum install " command or using the command "up2date -i ".

After the install process is complete, you can check if the packages are installed using the command below. The below command shows that the packages are installed on the severs.

# rpm -qa|grep bind
bind-devel-9.2.1-16
bind-utils-9.2.1-16
bind-9.2.1-16
redhat-config-bind-1.9.0-13

STEP 2

After the above packages are installed we need to open/edit the file /etc/named.conf and then create a entry for our primary and secondary name servers.