Home > Intel Communities > Open Port IT Community > Intel® vPro™ Expert Center > Blog > Tags > ider

Intel vPro Expert Center Blog

5 Posts tagged with the ider tag
1

Serial over LAN, or SOL for short, is a great tool for diagnostics. Combined with IDE redirection, or IDER, there’s a tremendous amount of things you can do remotely to manage clients. One of the areas where SOL can be helpful is for delivering status updates for IDER boot images that use a graphical interface. Instead of asking someone to read what’s on the screen to you, you can have a clear picture of what’s going on.

The key to this is to include the SOL driver in your live CD boot image. The actual process of including this driver will vary depending on the live CD tools you are using. I won’t go into specific details on the steps needed to include the driver in this post. The popular live CD tools, such as the Windows AIK, have a lot of information available on how to include drivers.

Once you have the SOL driver included in your live CD you can begin to take advantage of the SOL interface by sending text output to the SOL serial port. In most cases the port is COM3, but it may be on another COM port. You will need to do some testing to see which COM port your hardware platforms use for SOL.

Here’s one common scenario where this can be very handy. Let’s say you have a live CD that includes an in-band remote access tool, like PC Anywhere or a VNC server. You can include a startup script that echo’s out the computer’s hostname and IP address information to COM3. That way, you will know when the live CD has booted and the information it may have registered with DNS/DHCP. If you are using a Windows based live CD all you need to do is include commands like this:

echo %computername% >com3

ipconfig >com3

You can even incorporate some ANSI control codes to control formatting. For instance, if you want to have the remote SOL terminal clear it’s screen, you can send the Esc+[2J. The trick is generating the “Esc+” part. In order to do this in Windows, you need to hold down the Alt key, press 0027 on the ten key pad (make sure you include the two zeros) and then let the Alt key go. Unfortunately, Notepad does not seem to support this functionality. As an alternative, I recommend using Notepad++. Once you are done, you should have something like this:

echo ^[[2J >com3

Note: The escape character may appear as "^[" or something else altogether, like a little arrow or block character.  It depends on your OS and application.

Here’s an example of the output I get from a Live CD I built using Bart’s PE Builder.

Live CD Feedback over SOL.jpg

1 Comments Permalink
2

Did you know that vPro has the capability to give you remote GUI access out-of-band (OOB) using the serial-over-LAN (SoL) interface? It's true.

 

Normally we think of SoL as a solution for remotely accessing BIOS or as a tool for running text based remote diagnostic utilities as part of an IDE redirection (IDR-R) session. SoL is capable of doing more than console redirection. If you look in the device manager on a vPro client and expand the Ports (COM & LPT) you will see an entry for the SoL interface:

 

 

 

 

 

This port allows the local operating system to interact with AMT's out-of-band connection to a management console. You can try this yourself with the following steps:

 

 

  1. Open up a SoL session to your vPro client using your management console. (you can use the Manageability DTK if you do not currently have access to a management console)

  2. Open up a command prompt on the vPro client you are connected to via SoL.

  3. Enter the following command:

    1. echo hello>com3

    2. Note: the actual COM port number for your SoL interface may be different, check device manager to see what it is.

  4. Look at your SoL session on your management console. You should see the word "hello" appear in your console window.

 

So what does this all mean? It means that if you have some software monitoring the SoL port that you can send and receive data to your OS OOB.

 

A great example of how to leverage the SoL interface can be found in the Manageability DTK. The DTK gives you the ability to redirect TCP traffic over the SoL interface by utilizing an agent, the Manageability Outpost, on the vPro client. There is corresponding functionality available in the Manageability Commander tool and Manageability Director tools. This allows you to map a TCP port on your vPro client back to a TCP port on your management console and tunnel TCP traffic between your management console and vPro clients over the SoL connection.

 

If you combine TCP redirection with remote control software, like Remote Desktop, VNC and similar tools, you can enable OOB access to a full GUI on a remote machine.

 

I've put together a video that demonstrates how you can use this ability to remotely manage a client with a full GUI, including the ability to transfer files, using vPro's OOB management capabilities.

 

 


 

2 Comments Permalink
3

My name is Brad Lund; I work in the Enterprise End User Integration Lab (EIL) as a Senior Systems Engineer. This article is the first in a series of blogs I plan to deliver describing how, with the aid of some very useful tools, we can use IDE Redirection (IDE-R) and Serial over LAN (SOL) to provide the console operator with a more user friendly approach to remotely diagnosing and repairing client systems.

 

SOL is a great technology that has been around for a number of years. It is generally used in data centers for taking control of a computer in order to make changes to its BIOS. Since output from BIOS is by nature "pure text", SOL, whose interface is based on VT-100 terminal emulation, works fine. But what if the problem requires the console operator to interact with the client in a manner that dictates a graphic interface be present to load and run diagnostic applications?

 

Since the Enterprise Integration Lab are End User focused, we have had several customers ask us how they could leverage this Usage Scenario to take control of an AMT client while providing the operator with a more intuitive and useful interface. Additionally, every one of the End Users we interact with has a set of tools they use to perform diagnostics and repair. But if the client system is out-of-band, meaning no O/S present, it is NOT a BIOS related issue and the diagnostic tools require the operator to have a graphic view of the client system, how can we deliver on this request?

 

This series of blogs will attempt to show various ways to address these questions and more. I will start this blog series with the client residing inside the Enterprise using AMT to contact the console operator and utilizing very basic tools - take control. Upcoming blogs will show how to do this for clients residing outside the Enterprise (in the internet cloud) using Client Initiated Remote Access (CIRA) to contact the console via of a Management Presence Server in the DMZ and more robust tools - very cool!

 

So let's get on with it shall we?

 

The Tool Set

For this first installment I am using AMT Commander from the AMT DTK to initiate a client connection and perform console redirection (IDE-R). The client platform is Montevina (AMT v4.0). I will also push a Pre-installation Environment (PE) down the wire to boot the client into a graphic environment; either WinPE 2.0 or BartPE can be used. Whichever the choice, the greatest thing about a PE is its ability to be customized. You can build a PE to include not only the necessary drivers to bring a system up, but also all the required software for a technician to truly diagnose and practically correct any problem. A full explanation of PE's is beyond the scope of this blog but easily searchable via your favorite search engine. Lastly, to complete the process I will use UltraVNC, a publicly available application that gives the console operator the ability to view the remote client screen; graphically!

 

The Scenario

In this setting we have a client system where the O/S fails to boot-up (see Figure 1 - left image). This could happen if the client did something to their system which caused the registry to become unreadable by the O/S. Or perhaps the owner of the system accidentally deleted a critical file(s) required by the O/S to boot properly. In any case, the client calls their support center and is walked thru the required steps to perform BIOS initiated AMT. Once initiated, the console operator can then connect to the client; Figure 1 - right image.

 

Figure 1: Remote client screen on left - Console operator screen on right

 

 

 

 

 

 

 

 

After connecting to the client, the console operator opens the SOL/IDE-R mapping interface and assigns the appropriate .iso images for Floppy and CD-R redirection (see Figure 2 - left image). Note: You must assign both a Floppy and a CD image for SOL/IDE-R to operate properly. Also, while you can use IDE devices physically attached to the console system, working with .iso images are faster and more flexible.

 

 

Figure 2: Point device mapping to .iso images, start SOL/IDE-R, take control of client system.

 

 

 

 

 

 

 

 

The next step after starting redirection is to take control of the remote client as shown in Figure 2 - right image and indicate which image to boot from. In this case since we have our PE stored as a CD-R .iso image we tell it to "Remote Reboot to Redirected CD" Figure 3.

 

 

 

Figure 3: Remote reboot to CD-R image

 

 

 

 

 

 

 

 

At this point the client system has started a reboot and loading the PE image from the console. However, because we are using SOL the console operator can only see the "text" generated information. Notice the screen in the foreground of Figure 3 titled "PuTTY", this is the SOL interface and portrays only the "please wait" line from the boot loader; not very intuitive or useful. As a result the console operator will have to ask the client to inform them when the PE has finished loading on their system (see Figure 4).

 

 

Figure 4: Client system completed boot to PE and ready for remote control

 

 

 

 

 

 

 

 

Here is where the fun begins. After the PE loads onto the client system, the console operator starts UltraVNC; pointing it to the client, Figure 5 - left image. Part of the PE build includes the necessary network drivers to give this system an IP stack so it can be accessed via UltraVNC Once UltraVNC connects it opens a graphic window where we can actually see and control the client as though we are sitting at their machine, Figure 5 - right image. Again, we are using the SOL interface to show us text information and the TCP/IP protocol to allow UltraVNC to connect an OOB client - pretty cool huh?

 

 

Figure 5: UltraVNC to display client screen on console operator system

 

 

 

 

 

 

 

 

From here we can invoke a whole series of commands and view the results in real-time. In the example shown in Figure 5 - right image, I am running regedit - OK I realize it is showing the PE registry but with the right tools we can load and analyze the client registry or any other application and/or device.

 

Remember I said the beauty of PE's lie in their ability to be customized? If your shop use specific diagnostic tools you can include them into the PE at build time and use them here by simply clicking on the orange "GO" button (different PE's have different ways to access applications).

 

What I have shown here is the ability to use some very rudimentary protocols along with widely available tools to perform very powerful diagnostic and repair functions on a broken client. Keep in mind however this is only one of many ways to achieve this capability. In fact, this particular example can take a fair amount of time to load depending on network traffic and size of .iso image. But it is much better than the down time required to bring the remote system into the support center.

 

EIL are constantly finding solutions to answer the hard questions for our End Users. In upcoming blogs I plan to show similar capabilities using different techniques to minimize load times while maximizing efficiency. I hope you found this blog useful if you have any questions please feel free to ask. See you soon...

3 Comments Permalink
1

 

If you have not read parts 1 and 2, please read these before reading this part as this is a continuation of the story begun previously.

 

 

 

 

 

http://juice.altiris.com/book/4687/altiris-and-intel-vpro-use-cases

 

 

 

 

 

From the OS level vPro has tools to help quarantine and remediate compromised systems as demonstrated in part 2. This section explores the capabilities at the hardware layer, completely below the OS and any related dependencies. Can the IT staff continue to respond well to threats and avoid outages and threats to the businesses wellbeing? When the gloves come off sometimes even the most secure networks are vulnerable to threats.

 

 

 

Mighty Modern Marketing HQ - Boston, Massachusetts

"This is Jessica, how can I help you?"

 

The voice that spoke through the headset caused her to flinch, and she moved the earpiece two inches away from her ear.

 

 

"This can't be happening now!" the voice exclaimed loudly.

 

 

"What's the problem?" she responded calmly, hoping the user would match her volume.

 

 

He didn't. "The timing is the worst possible, since the end of quarter is only two days away! I need my computer up and running two hours ago!"

 

 

"Let me see... I'm speaking to Mitch Cavanaugh, correct?"

 

 

"Yes," he responded, his voice dropping a trifle. "My computer isn't booting, and I have sales to approve and record. If I don't get this up quick, we may not be able to add this revenue this quarter!"

 

 

"I understand," she said as she used the Altiris Console under the All Computers Collection to find his computer. She double-clicked on it, bring up Resource Manager.

 

 

"I see you're using an HP 7800..." she began.

 

 

"I need this problem fixed pronto," he interrupted.

 

 

"Of course," she said, clicking on the ‘Real-Time' tab. "Give me just a moment."

 

 

She smiled, feeling a warmth from the fact that she'd made sure those with the most business critical functions got the vPro systems first. The Real-time tab loaded, revealing the function tree in the left-hand pane. She noted immediately that only the AMT functions loaded, and that the system's powerstate was on.

 

 

"I can see," she said when she heard a sound of irritation on the other line, "that while there is power to your computer, the operating system is not loading."

 

 

A pause followed her comment. "Really?" Mitch responded, the edge on his voice disappearing. "You can tell me that already? Usually I have to tell you IT people everything... that's great. So do you know what's going on?"

 

 

"Give me another moment," she said in her most pleasant voice. She clicked on the Hardware Management node in the left tree. After the page loaded, she choose the reboot radial under the Remote power management section. Under Redirection options she check the box, "Display task progress and remotely control computer". Next she clicked "Run Task Now". When the page began to refresh a new window popped up, showing her the boot of the computer.

 

 

"Wait, my computer just rebooted..." Mitch said, sounding suspicious.

 

 

"Yes, I just initiated a reboot," she responded. "I'm going to watch the boot from here."

 

 

"You can do that? I thought I had to be in Windows for that to work."

 

 

When the boot verified devices on the system she noticed that no hard drive was detected. The message "No boot device" appeared.

 

 

"Okay Mitch, the computer isn't recognizing the hard drive for some reason. Give me a moment to check a few more things."

 

 

"Is that fixable?" Mitch inquired.

 

 

"I don't know yet. Give me a moment."

 

 

She rebooted again, but also added the "Enter BIOS on startup" option by checking the box. The remote window reappeared, this time entering the BIOS. She looked under the IDE channels, but no hard drive was listed.

 

 

"Okay Mitch, I've determined that your hard drive isn't being detected at all by the computer. Since you have critical work to perform, we'll immediately image and restore your data to a backup system using Deployment Server and Symantec's Backup Exec. It should take about 30 minutes. Tevita Tatafu will bring it by then. It's about lunchtime. Can you take a short break?"

 

 

"Well... it is a little early for lunch, but that should work."

 

 

"Alright Mitch. Anything else?"

 

 

"No... I just hope the backup had all my files on it."

 

 

"It should."

 

 

"Thanks."

 

 

She leaned back as she hung her headset by the phone. "Tevita?"

 

 

He swung out of his cube, a huge smile on his face. "Mr. Cavanaugh having problems?"

 

 

"Yeah," she responded.

 

 

"He's such a joy. Did you know he was the one who got impatient waiting in line at the vending machine so he ran to the nearest Dunkin Donuts, opening the door fast enough to knock Edgar flat on his back?"

 

 

"You be nice," scolded Jessica with a stern look. "He may have anxiety issues, but he's a spot on accountant."

 

 

Tevita laughed richly. "Spot on, eh? And what do you know about Accounting?"

 

 

"I got a Masters from University of Chicago's Graduate School of Business, in Accounting."

 

 

"You did?"

 

 

"Yes. Now don't make me a liar and get that machine to Mitch ‘pronto'."

 

 

Tevita laughed, but got up and headed to the equipment room. Jessica sorted through her email. She wanted to clear out her inbox but only halfway through the process Tevita returned, no longer smiling. His mouth bent down in a frown she rarely saw, and usually only when he was about to explode with anger. His eyes didn't seethe, but looked down at a computer in his hands. He sat down and rolled his chair over towards her cube.

 

 

"It really is missing the hard drive," he said, expertly using the buttons on the side to open the case. He pointed to an empty bay. "It should be in here, but... well... the IDE cable was cut, right here. Seems stupid, since they had to unscrew the drive, but..."

 

 

She stared at the empty bay. "Someone stole his hard drive?"

 

 

Tevita nodded. "It looks that way. Mitch said he only left to take a restroom break, and when he came back the system was off and wouldn't boot."

 

 

"This isn't good..." Jessica started to say.

 

 

"Guys!" Bobby said loudly, his voice piercing through the area like a gunshot. They both stood up, staring at the gangly developer loping towards them from the door to the server room.

 

 

"The sky must be falling," Tevita said, but despite the amusement in his voice his mouth only twitched once in an upward smile.

 

 

"What's wrong?" Jessica asked.

 

 

Bobby took a deep breath. "It's a ninja. I swear by my grandma's heirloom earrings that a ninja just showed up in the server room!"

 

 

"A ninja!!?" Jessica exclaimed.

 

 

Tevita looked down a the computer he held. "Bobby, that's not funny..."

 

 

Bobby threw his hands up. "You know I don't have an imagination, or much of a sense of humor. Didn't you used to call me Cardboard Boy?"

 

 

"Yeah, but I stopped after you randomly locked out my user account at the worst possible moments..."

 

 

"I'm not kidding."

 

 

Jessica, feeling like she'd just stepped off a rollercoaster, reached out and put a hand on the wall. "Bobby, you mean to tell me there's a ninja loose in the building?"

 

 

"Well.. no. He's lying unconscious in the server room."

 

 

Tevita gave her a quick look, then bee-lined towards the door to the server room. Jessica wanted to run the other way, but Bobby gave her a helpful shove on the back towards the room. She glanced behind at him, and he blushed.

 

 

"Sorry, but the more witnesses the better."

 

 

The figure sprawled out on the floor clutched a hard drive in his back-gloved hands. He didn't look like a real ninja, but a black ski mask that looked similar to a ninja wrap covered his face. A goose-egg on his forehead the size of a golf ball, halfway hidden by the mask, seemed to say loudly why he wasn't conscious. Jessica found herself staring, her mouth hanging open and her hand moving up to cover it.

 

 

"Oh my gosh," she said, her voice embarrassingly high-pitched. Her heart hammered in her chest as if she'd just jumped off a cliff

 

 

Tevita gave Bobby a searching look. "Do you know martial arts or something?" he asked.

 

 

"No. I thought I heard something while I was bringing back the two new demo laptops, so I went to check it out. When I saw him, I just reacted."

 

 

"What did you do?"

 

 

"Well... I had a MacBook Air in my left hand, and a Panasonic Toughbook in the right. The MacBook might be thin enough to decapitate a ninja, but more likely it would have bounced off his skull without slowing him down, so I threw the Toughbook."

 

 

Tevita reached out with his toe and nudged the intruder.

 

 

"We should leave and call the police," Jessica said, edging towards the door.

 

 

"He's out cold," Tevita said, reaching down to pick up the Toughbook. The screen gleamed beautifully, no sign of damage despite being used as a blunt weapon. "Too bad these aren't vPro yet," he said.

 

 

"I called the police," Bobby said. "They should be here soon."

 

 

The next half-hour moved as if in a dream. Jessica felt like she'd stepped out of the real world and into some crazy movie. Slowly the facts of the intruder came to light, and like wiping away the mist on a foggy window things didn't seem as ridiculous as they first seemed.

 

 

The man had been hired to steal a specific hard drive. He was fully cooperative with police, apologetic for getting caught and worrying everyone. He indicated he wore the mask not as an intimidation method, but to remain incognito to security cameras. The policy cuffed him and off he went, leaving everyone standing there in disbelief.

 

 

"Is that Mitch's hard drive?" she finally asked Tevita, who had retrieved the hard drive the "ninja" held.

 

 

Tevita pointed to connector of a cut IDE cable sticking out the back. "It looks like it..."

 

 

Bobby took the drive, hefting it, his small eyes squinting. "No, this is a RAID drive. He ‘raided' a server..."

 

 

Jessica stared at him as he chuckled. Tevita stared for a moment, and broke into a wide grin.

 

 

"And you say you have no sense of humor," he said with a laugh.

 

 

"My Dad told me puns don't count," Bobby responded.

 

 

"What about the data on Mitch's hard drive?" Jessica inquired. "I know he had confidential, sensitive information on it."

 

 

Bobby shrugged. "Nothing we can do about it unless we can find it. It wouldn't be the first time."

 

 

She shook her head. "Too bad vPro doesn't have disk encryption yet. I know they're working on it."

 

 

Bobby's head perked up. "vPro with disk encryption? Nice."

 

 

The receptionist motioned to Jessica, and she walked over.

 

 

"Mr. Johnson has called a meeting in the executive briefing room," she explained, a phone held between her ear and her raised shoulder. "He says it's urgent, but not to worry."

 

 

"Not to worry," she echoed, feeling a surreal sense of amusement at the statement. "Right."

 

 

She rounded up Tevita and Bobby and they headed upstairs. The executive briefing room flooded with light, with the impeccable CEO standing by the floor to ceiling window showing the bottom half of the skyline to downtown Boston. He smiled casually, his hands clasped behind his back. When they'd all entered and sat down, he turned around, his smiling increasing.

 

 

"The mighty defenders arrive," he said. "I had a call from Mitch Cavanaugh concerning your ability to quickly resolve the theft of his hard drive. I commend you on a lightning-fast response. I can tell by your expressions that you're a bit shaken."

 

 

He paused, the smile abating. "Let me assure you that we are permanently stepping up our security. I blame myself for not taking steps against blatant thievery. I guess I'd hoped my former colleague had gotten past that type of criminality."

 

 

Bobby raised his hand, and Mr. Johnson gestured at him. He cleared his throat, folding his skinny arms.

 

 

"So don't we have enough evident now to get the police involved?"

 

 

Mr. Johnson shook his head. "No, and even with the thief in hand I doubt they'll be able to link this to New Nifty Networks. For all we know this isn't related to them, though our situation and the probability point in that direction. No, we won't be making any effort to link the thief with Nifty. Your job is to continue tightening our security.

 

 

"First, let me commend you, Tevita, for your mastery of providing mirror systems to people when theft occurs. Second, I commend you, Bobby, for always delivering when issues arrive. Lastly, I commend you, Jessica, for your insistence on vPro. I know Edgar and others have given you are hard time about it, but it seems you prove it's worth daily."

 

 

"Thank you," she said.

 

 

"Our next step is to find out if any other systems have had their hard drives stolen. I'll leave this task in your capable hands. If you have any questions or concerns, please come see me in my office."

 

 

As quickly as the meeting started, it ended.

 

 

When they reached their cube area, Tevita didn't sit down at his, but followed her into hers. He stared at the Altiris Console idling on her screen, his arms folded and his expression pinched in thought. She sat down, eyeing him, as she reached for her keyboard.

"Let me guess," Tevita said, "you already have a plan?"

 

 

She let her hands fall into her lap. "Well... yeah. It shouldn't difficult to find out which systems no longer have HDDs even if the systems have been off for a while. I just..."

 

 

Her voice faded away. She stared at Tevita, trying to sort through her emotions.

 

 

"You're freaked," Tevita offered.

 

 

"No... well... yeah. I kind of am. Cyber attacks are one thing, but Bobby's ninja..."

 

 

Tevita retrieved his chair from his cube, sitting down and leaning back at the entrance of her cube. "With computers thieves usually only break into places for the hardware. Some of the servers Bobby runs cost more than a new BMW. Stealing the hard drives means they're after data. It's really no different, except we're using software to block software attacks, and we use guards, locks, and other such things for the hardware attacks. You heard Johnson. I don't think you have to worry."

 

 

She sighed. "We should get occupational hazard pay. I'll get over it, though I may bring pepper spray tomorrow."

 

 

"That'll work."

 

 

She cracked her knuckles by clasping her fingers and pushing her arms out. "Let's get into this. First off, we can't rely on Inventory Solution to know if the hard drive is there or not, since the OS obviously has to be up and running to get an updated Inventory. We might be able to use the Altiris Agent's last check-in time to note those systems that are no longer reporting, but that won't tell us if those machines are simply off or something similar."

 

 

Tevita nodded. "Fun. Without the hard drive we have no manageability capability."

 

 

"Except for the one thing that runs outside of the hard drive."

 

 

"Intel vPro."

 

 

"Exactly. All capabilities are still available even when the hard drive's been yanked."

 

 

"So we can use RTSM to remote into those systems not responding in Altiris using Serial-Over-LAN to see if the hard drive is there, like you did for Mitch."

 

 

Jessica nodded, smiling. "That would work, but I have a faster, much easier way."

 

 

Tevita rolled closer as she put her hand on the mouse and started using the Altiris Console, his eyes focused on the screen. "I like easy," he said.

 

 

She browsed under Manage and clicked on Jobs. When the left-pane tree loaded, she browsed under Tasks and Jobs, Server Tasks, Real-Time Console Infrastructure, and clicked on ‘Get Intel® AMT Inventory'. She clicked the Run Now button.

 

 

On the resulting window that popped up she gave the Run name: Ninja stolen hard drive, and clicked on the ‘Select computers' link. Within the ‘Select Computers' dialog in the left-most pane, she browsed in the tree from Collections, Out of Band Management, Provisioning, and double-clicked on ‘Provisioned Intel® AMT Computers. The middle pane showed a list of all vPro capable systems in the environment, and the right-most pane showed the Provisioned collection she'd selected. She clicked OK. She then clicked the Run Now button.

 

 

"That's it," she said, leaning back. "In the next minute or two we should have inventory from all vPro capable systems."

 

 

The Tongan shook his head. "You're going to outsmart us all out of a job," he said.

 

 

She raised an eyebrow at him. "Are you kidding? We might, just might, get to all the stuff on our plates we normally leave forever on the backburner."

 

 

She browsed in the Altiris Console under View, Reports, Incident Management, Real-Time Console Infrastructure, and selected Intel® AMT Hardware Inventory. When the report home page loaded, she clicked the Run this report link. For the parameters she left ‘System' to Any, and changed ‘Hardware Type' to ‘Media'. She clicked the ‘Refresh' button to load the report.

 

 

"Okay, this shows us all systems that have a hard drive reported with AMT Inventory. We could manually compare the list, but why not create a new report that shows us systems that do not have anything in the Media table?"

 

 

She right-clicked on the ‘Real-Time Console Infrastructure' folder and choose New, Report. She gave it the name: Intel vPro Computers Without a Hard Drive. She choose ‘Enter SQL Directly' and then rolled back from her desk.

 

 

"Alright SQL guru, I'll give you what I need and you can figure out the query."

 

 

He scooted around her, reaching for the keyboard. "Alright. Shoot."

 

 

"Okay, we need to have a list of all computers that either do not have an entry within the table Inv_AMT_Media_Device. That's it."

 

 

"That's it? That's easy enough..."

 

 

Tevita entered in the SQL, and saved the report. When they ran it, only two systems showed up.

 

 

Jessica looked at the names of the computers. "These are both from accounting, but Joe is in New York doing his accounting work on his laptop, and this other... he's here, but hasn't reported anything yet.

 

 

Tevita stood, dragging his chair back to his cube. "I'll take care of these two. Why don't you go home?"

 

 

"And leave you here..."

 

 

He laughed. "I'll be fine. It's almost five, and you probably want to take a nice relaxing evening trying not to think about thieves and ninjas."

 

 

"Thanks for that," she commented dryly, but with no conviction. "Only if you're sure..."

 

 

"I'm sure. I'll see you tomorrow."

 

 

"Thanks. Have a good evening."

 

 

 

End Part III

Recognizing the need for better physical security, and using vPro to minimize the effects of theft, the IT team continue to rise to meet the challenges facing them.

1 Comments Permalink
0

 

Years before I started working on Intel AMT, designers where creating a list of usages that would be enabled by Intel AMT. The list included, I presume, usages around 3PDS, remote reboot to BIOS, disk redirection, etc. Many of the Intel AMT usages that are promoted on the Intel web site. When I started work on the DTK, a personal challenge had always been to find new ways of using existing features to do different and sometimes unexpected things. Create new usages for Intel AMT that it was never originally designed to do. I now present my top 5 abuses of existing features.

 

TCP-over-Serial-over-LAN. The Intel AMT serial port I am told, was originally designed as an easy way to remotely take control of the BIOS and recovery OS remotely. Designers needed a way for BIOS to be able to send test display data to a remote console. A virtual serial port was a great solution. It so happens that in the original design, this serial port was always enabled and usable, even when the normal OS was running. This allows a serial agent to talk to a console while bypassing the OS’s network stack. This is interesting on its own and I started work on a serial agent of my own. Things took a weird twist when I started sending binary data and sending files over this serial port, making it very valuable. It’s only a few weeks later that I realized I could also send TCP traffic over this serial link, making it possible to contact TCP services on the Intel AMT computer even if the network stack was disabled. A few days later, I showcased the first demonstration of VNC-over-SOL, and turning this abuse of the serial port into an instant hit. To this day, VNC-over-SOL is still, one of the most impressive demonstrations of Intel AMT.

 

Reverse Watchdog. When Intel sales people demonstrate Intel AMT to customers, they often get asked if you can shutdown gracefully an Intel AMT computer using Intel AMT. The simple answer was no, Intel AMT will perform a brutal shutdown or reset upon request. To perform operations like a clean shutdown or reset, sleep or hibernation requires the involvement of the OS. You could tell a serial agent like Intel AMT Outpost to perform the shutdown, but that required opening the serial connection and could be a problem if you had to shutdown many computers. I needed a way to pass a small amount of information to a running Intel AMT agent on the PC, do it using SOAP/WSMAN only and if possible get confirmation of reception. We could store the command into 3PDS and have the agent read it periodically, but 3PDS required setup and that little amount of data would have required allocation of a 4K flash page. The solution came when looking at the agent presence feature. When a console creates a new agent, the agent can now register this agent locally. The agent also get the timeout of the agent in seconds (from 1 to 65535), this would be the key. By constantly trying to register a known GUID, Intel AMT Outpost could see if the agent existed or not. If suddenly the registration works, the timeout value would indicate that type of shutdown operation to perform. Better yet, the simple fact that registration occurred changes the state of the agent to “Running”, confirming to the console that the message was indeed received. Today the Intel AMT Terminal has “Agent Commands” in the remote control that allows a user to perform soft operations when the agent is running, even if the OS network stack is not working.

 

Mouse over serial. A few months back I started work on a smaller version of Intel AMT Outpost called Intel AMT Guardpost. The idea was that if a serial agent was going to be useful, it was going to need to run on a recovery OS, run in the background with no dependencies and with as little footprint as possible (Is it not annoying to have all there background processes running?). The C/C++ version of Intel AMT Outpost was on its way. One feature I always wanted to work on was a remote Windows command prompt; it took over a week to finally pull this off. I could now remotely shell to DOS and perform basic command line operations. I could also enter the command like editor with the “Edit” command at which point, the temptation to support the mouse-over-serial-over-LAN was a must have. Using the binary serial protocol, I added the support to the terminal in a few hours. To this day, it’s still a fun and amazing demonstration of outstanding remote manageability.

 

IDE-R within the OS. A few days after first enabling IDE-R within Intel AMT Commander, I stumbled upon something I had not noticed before. If an administrator where to start IDE redirection and the OS was to re-scan its plug & play devices, the additional floppy and CDROM drive would show up in Microsoft Windows. This was immediately interesting since transferring files over the serial port was limited to 115kb/sec a very slow speed in today’s world. With IDE-R, you can copy files at around CDROM 4x speed on a local network. All I needed was a way for Intel AMT Outpost to cause the OS to rescan its plug & play devices. A few hours later the “HWRESCAN” command was built and for the first time, an administrator could mount a CDROM remotely and install a patch as high speed without ever using the OS’s network stack. This feature also turned out to be an excellent compliment to VNC-over-SOL.

 

 

Fast data path using IDE-R. This is not an idea I never built into the DTK, but I wanted to add it to this list since it would also be an interesting was to use existing features in new ways. The serial-over-LAN feature turned out to be extremely valuable, but it is also slow. Serial ports are very inefficient. One way someone could speed things up is to use IDE-R as a fast by-pass to the OS. An administrator would mount a virtual floppy disk drive containing a single file. This file, would not really exist, it would contain different data each time it was read, making it possible to send data to an OS agent thru Intel AMT at much higher speeds. Also, since the floppy is a read/write device, the agent could write into the virtual file data that it wants to send to the console. It would be quite a bit of work to pull this off, but it certainly seems possible. Someone would just have to know the internal format of an .img file.

 

That’s my top 5. I realize this is probably a rather advanced blog article, but this is proof that you can have a lot of fun to any technologies.

 

 

 

Ylian (Intel AMT Blog)

 

 

0 Comments 8 References Permalink