Member Avatar for rockmania

How to make PXES thin client OS boot directly using RDP?
PXES thin client OS is what i have.what i want is...
i want to enter into RDP without going to the basic screen where it shows the Options.also i want my RDP settings set...

i tried modifying the isolinux.cfg file in boot\isolinux folder like this

DEFAULT rdp
PROMPT 0
TIMEOUT 5

LABEL rdp
KERNEL vmlinuz
APPEND ramdisk_size=15604 ro initrd=pxes.img root=/dev/ram console=null SESSION_DEFAULT=rdp RDP_SERVER_NAME= X_VIDEO_MODES="1024x768" RDP_COLOR_DEPTH=16 MOUSE_WHEEL_ENABLED=1 RDP_ASK_ENABLED=0


but nothing happens.the IP no is my localhost IP.

can somebody help in making the PXES boot directly using the RDP into the OS thus showing the remote desktop?

  • 2 Contributors
  • 1 Reply
  • 667 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by dtmilano

Dani AI

Generated

A few points that explain why your change didn’t take effect and how to fix it quickly.

If the client is PXE/network-booting, editing the ISO’s isolinux.cfg won’t change what the network-served bootloader uses: PXE clients use PXELINUX and read pxelinux.cfg/default (ISOLINUX is for CD/ISO boots). PXES itself then fetches and executes the TFTP-served config scripts under /pxes/config (a global default.conf and a per-host file). That means you must apply your auto‑RDP settings on the files the PXE client actually downloads, not only inside the ISO. (jfearn.fedorapeople.org)

Two practical ways to make the client go straight to RDP:

  • Put the RDP/session options on the kernel command line served by PXELINUX (the APPEND line) or
  • Export the same options from the TFTP pxes/config/default.conf (or the per‑host config the client runs after network comes up).
    Do not include an http:// prefix — the boot scripts expect a hostname or IP (optionally with a port), not an HTTP URL. After you change the TFTP files, reboot a client and watch the client console / tftpd log: PXES’s init (rcS) fetches and executes default.conf and then the host-specific conf, so you’ll immediately see whether your settings are read. (sourceforge.net)

Troubleshooting checklist: ensure DHCP option 67/your PXE filename points to the pxelinux binary and the pxelinux.cfg/default you edited; confirm the TFTP paths (and that you rebuilt the ISO only if you really boot from CD); check for any default values baked into pxes.img that might override kernel cmdline; and test with a visible change (so you know which config was applied). If editing PXES proves painful, consider modern alternatives (Thinstation or the CULT-style images mentioned by ) which include ready examples for auto-connecting to RDP. (sourceforge.net)

Member Avatar for dtmilano

How to make PXES thin client OS boot directly using RDP?
PXES thin client OS is what i have.what i want is...
i want to enter into RDP without going to the basic screen where it shows the Options.also i want my RDP settings set...

i tried modifying the isolinux.cfg file in boot\isolinux folder like this

DEFAULT rdp
PROMPT 0
TIMEOUT 5

LABEL rdp
KERNEL vmlinuz
APPEND ramdisk_size=15604 ro initrd=pxes.img root=/dev/ram console=null SESSION_DEFAULT=rdp RDP_SERVER_NAME= X_VIDEO_MODES="1024x768" RDP_COLOR_DEPTH=16 MOUSE_WHEEL_ENABLED=1 RDP_ASK_ENABLED=0


but nothing happens.the IP no is my localhost IP.

can somebody help in making the PXES boot directly using the RDP into the OS thus showing the remote desktop?

You should use cult thinclient, which is the newest (and fastest) Open Source thin client Operating System.
Take a look at cult-thinclient.sf.net for downloads and general info and you will find the answer to your question on how to boot directly into RDP here (http://codtech.com/wiki/index.php/CULT_classic_custom:_usage) and here ().
There's also a cult mailing list at SF.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.