<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vnc on Anything About IT</title><link>https://www.verboon.info/tags/vnc/</link><description>Recent content in Vnc on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 26 Dec 2009 15:36:37 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/vnc/index.xml" rel="self" type="application/rss+xml"/><item><title>Remote Management of AMT/vPro machine with WinPE and VNC</title><link>https://www.verboon.info/2009/12/remote-management-of-amtvpro-machine-with-winpe-and-vnc/</link><pubDate>Sat, 26 Dec 2009 15:36:37 +0000</pubDate><guid>https://www.verboon.info/2009/12/remote-management-of-amtvpro-machine-with-winpe-and-vnc/</guid><description>&lt;p&gt;Intel vPro/AMT enabled systems allow you to remotely reboot a system from a redirected CD-ROM aka as IDE-R.  So if one of your users devices doesn&amp;rsquo;t boot its OS properly anymore, you can remotely boot that system with a diagnostics CD that you have stored on your local disk drive.&lt;/p&gt;
&lt;p&gt;As long as that recovery CD has a text based interface such as the &lt;a href="http://www.sysresccd.org/Main_Page"&gt;SystemRescueCD&lt;/a&gt; the system can be remotely managed through the remote VT100 terminal, but unfortunately that doesn’t work for graphical interfaces such as WinPE. So we need an alternative method to remotely manage that device. Since Microsoft’s own remote desktop (RDP) does not work under Windows PE, we are going to use VNC which is small and FREE.&lt;/p&gt;</description></item></channel></rss>