You can still use P9.

If it's not too inconvenient, I would hardwire (Cat5/6) the laptop to the router for this; Cat cable gives more bandwidth and more reliable connection than wireless. But wireless would suffice.

The render slave (aka remote) machine does not need a runtime installed; when the master's queue sends the remote a job, it includes the geometries and texture image maps, etc. In your case, since both machines will have Poser11Pro installed, either machine could function as master, with the other serving as remote. So you will indeed want to copy your runtime from the desktop to the laptop. Your strategy is wise, in that the desktop has much greater cooling capacity than a laptop, so I'd definitely use the desktop for rendering while using the laptop for scene setup and sending queue jobs as master. If you can scrounge more computers up, install only Queue Manager on them by running DLM and inserting the Queue serial key instead of the Poser 11 Pro key.

My machines are Win7, so there may be specific pointers for Win10 that someone else will need to inject. Let's assume that you have P11Pro installed on both machines, and both machines are connected to (the same) router/switch.

The two most common causes of failure seem to be [1] Firewall permissions - Queue, FFRender64, and Poser must all have firewall permissions, both in and out, on all machines in your network. If you don't get a firewall query popup the first time you launch Queue, you may need to open your firewall apllication rules and manually change the settings for Queue, FFRender64, and Poser. [2] Build numbers must match - In order for the master's Queue and the remote's Queue to acknowledge each other, all machines on your network must have the same build number. So, if you updated your master's P11Pro (Queue gets updated along with it), then you must update Queue on all of your remotes also.

So, time to try it out. On each remote, launch Queue Manager. On your master, open a scene in Poser 11 Pro. Open the master's Queue, and set the master's Queue to not process jobs locally. At the bottom of the master's Queue UI window, you should see available message from 192.168.1.119 or similar from each remote on your network. That tells you that the Master's Queue sees the remote's Queue. Conversely, at the bottom of each remote's Queue UI window, you should see discovery query from 192.168.1.101 which confirms that the remote's Queue sees the master's Queue.

Set the scene render settings, bearing in mind that it will be using the CPU only, and send the render to queue. There may be several seconds before you see anything happen; P11Pro has handed off to Queue, which saves a PZ3 of that particular scene frame (or animation). Then, you'll see a burst of file transfer notices in the Queue window. If you look at the remote's Queue, you should incoming file transfer notices, and a job assignment appears in the Queue window.

Poser 12, in feet.  

OSes:  Win7Prox64, Win7Ultx64

Silo Pro 2.5.6 64bit, Vue Infinite 2014.7, Genetica 4.0 Studio, UV Mapper Pro, UV Layout Pro, PhotoImpact X3, GIF Animator 5