I have been setting up RHEL6.8 VNC Desktop VM's at work for certain teams, I have created an Ansible playbook to fully configure VNC on a new server.
One thing that I really cant get to work is user network settings.
my /etc/network-scripts/ifcfg-eth0 is fully setup and is done in the script we use for provisioning servers, yet after connecting via VNC to a user desktop there is never any network or proxy settings there.
Where are the files for these individual user settings kept, I can't seem to find this anywhere on the internet and would just like to add these to my Ansible playbook so I don't have to manually log into every single user and set these up through the GUI.

Thanks in advance

Shouldn't that be /etc/sysconfig/network-scripts rather than /etc/network-scripts?

Anyways, I can't see what it is that you are looking for? Are you looking for the ip details or something else? I wouldn't rely on checking a file for ip details and instead would recommend checking such details with the ip command.

If this isn't what you are after, a bit more clarification may help.

Hi yes, missed out that in the post.

The issue is that my network properties on the server using ssh are completely correct, 'ip addr show/ip a' both show the correct properties, but when setting up GUI desktop users going into their individual network settings as you would usually on a GUI desktop there is no settings there, you have to manually add a wired device and configure the settings.
I dont use GUI linux desktops often and assumed each new user would be using the settings from ifcfg-eth0

This is my ifcfg file, the network on the server functions correctly and you can access satellite and repositories etc.
With a GUI desktop you need browser functionality and when going into the network connections in the GUI there is no device there

DEVICE="eth0"
BOOTPROTO="static"
HWADDR="###########"
IPADDR="##########"
NETMASK="255.255.254.0"
GATEWAY="###########"
DNS1="##########"
DNS2="#########"
IPV6INIT="no"
MTU="1500"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"

(##### = redacted info)

I have all my IP details, I can still configure the dektops settings manually as I know the IP, Gateway and DNS etc. but I would like to be able to have it so when setting up a new user desktop it configures the network automatically

I've attached a screen of the GUI

Attached Thumbnails

 

Don't really use GUIs on RHEL/CentOS that much, but I believe most the GUI tools will be using network manager for managing system IP details. As you'll note from your own configuration, you aren't using NetworkManager (NM_CONTROLLED="no") and so I suspect that is why the GUI appears empty.

When you GUI in, kick open a terminal and see if the "ip addr show" commands work using the CLI tools, if so then this maybe the case.

1 members found this post helpful.

[root@####### ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether ############ brd ff:ff:ff:ff:ff:ff
inet ###########/23 brd ######### scope global eth0
[root@####### ~]#


surprisingly it does come back with the right IP, good shout on the network managed part though, I will look into that, you wouldn't happen to know where NM keeps its config would you? thanks for the help so far.
hopefully someone else has set this up before.

Update: Thank you r3sistance you're a life saver. Turns out I don't need to find the config location of network manager.

Setting the nm_controlled option to 'yes' in ifcfg file and then rebooting the server made it so when I connect to a desktop it already has the wired device setup. Having never used network manager or GUI based desktops for RedHat I wasn't aware of this and our script sets it to 'no' by default

No problem, Network Manager can sometimes cause confusing behavior and so people have defaulted it off for a while but in CentOS 6 and 7 it is becoming more reliable/less troublesome than use to be. If I remember correctly, Network Manager was originally designed for laptops moving between various wireless networks and was not so good on servers.