- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've got a newly-built Intel D965GF-based PC, no OS installed, and I'm trying to coax some response out of AMT by BIOS-twiddling alone, so far with no success at all. Configured the ME to be always on, set up AMT in small-business mode, DHCP enabled, changed the computer name from the default "iDBO", set a test domain-name. I've created a minimal network - a Netgear router acting as DHCP server and gateway, a laptop to monitor the router state, and the '965 PC.
AMT does nothing at all - doesn't even show up as connected to the router! Also tried setting a static IP address in the AMT configuration, but still can't get a response (using AMT Commander discovery, or PING, or using the browser to connect to
I've scanned through numerous documents, both from the Intel website and elsewhere, but none of them have made clear whether I need to install Windoze and some AMT/ME drivers on the test PC - I thought this was one of the main points of AMT, to administer a PC with a non-bootable OS?
All suggestions gratefully received...
Thanks, Mike
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks anyway, Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Setting a ME password of "Password_1" is allowed by the BIOS, but the ME engine doesn't like it. Changing the password to "Password1!" fixed the problem. Only took two days to find that - thanks Intel!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm not sure I understand how your Bios was accepting the "Password_1" but the ME wasn't. When I tried to change my ME password to that, it rejected it right away. Maybe you are adding an additional password for your Bios? If that's the case then the Bios simply uses a different level of password strength, I suppose. But your comment was interesting so I did some digging around and there are a couple places in the SDK docs (Network Interface Guide, for example) that do spell out what the rules are for the ME password. I blogged it - if your are interested check it out. What I found out was that there are many interpretations for howstrong password is constructed. The blog below details what our NIG states. And Microsoft says that space characters do not count toward the characters that give the password it's strength (I'm figuring that the underscore may be considered a space character.)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page