Sorry for delay.

Does this setting on the Proxy make it's way into the Boot Disks?  That's 
how we have to provision at the moment.  We're finding the central 
unattended_url and foreman_url settings are used when creating the ISO 
images.  We can't use DHCP/PXE provisioning at all.  Some network zones 
don't even have DNS, so we have to use IP addresses to point at 
Satellite/Proxy.

On Thursday, 1 September 2016 12:46:18 UTC+1, Dave Mc wrote:
>
> Hi,
>
> I believe I have a similar setup to you that I have just got working.
>
> On the remote smart proxy I have :-
>
> /etc/foreman-proxy/settings.d/templates.yml
> :enabled: true
> :template_url: http://smartproxy1.remote.local:8000
>
> /etc/foreman-proxy/settings.yml
> :http_port: 8000
>
> Now I can generate a New Host associated with either Smart Proxy and 
> verify that the /var/lib/tftpboot/pxelinux.cfg/[mac-address] file has a ks 
> argument pointing to the local Smart Proxy
>
> Dave
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to