Intel Communities: Message List - DHCP and DNS registrations with AMT

Re: DHCP and DNS registrations with AMT

merlyn.cooper@communitybancshares.com — Tue, 23 Mar 2010 20:05:51 GMT

I'm not as fluent in DHCP/DNS as the other posters, but we have never had issue with workstations pulling into DHCP and registering their workstation name. The newest hardware, HP dc7800, are pulling in with HPSystem, not their computer name. We've used the same process for all of our workstations, but this new hardware... that's something else!

There doesn't seem to be a resolution posted. That may mean that over the last two years, nothing has been found to edit the system's info to correct this issue.

The computer name pulls into Novell Zenworks to register the workstation object, but doesn't get read into DNS/DHCP. Was there EVER a resolution?

Thank you ~ Merlyn

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Mon, 27 Oct 2008 14:01:09 GMT

I haven't yet gotten to the bottom of my DNS / DHCP issue yet, I'm still working on some pre-deployment requirements in our environment. Most of our workstations were named with an underscore "_" as part of the computer name and AMT will not function with this character in place so we're working on a method to rename all our systems first. In addition there appears to be an issue with 3.2.1 machines that were upgraded to 3.2.1 from an earlier BIOS. We're in the process of setting up a WS-TRAN server to work this issue. Once we get these issues solved, we'll move on to hopefully provisioning and investigating the DNS / DHCP issue!

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Mon, 27 Oct 2008 13:24:15 GMT

Did you ever get an acceptable solution for dealing with your issue? Curious if any methods you could share for others that may be expereincing this problem.

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Tue, 12 Aug 2008 18:45:30 GMT

Man, I can't find the 'insert attachment' capability in a new post.....where would I find the option?

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Tue, 12 Aug 2008 18:41:51 GMT

There are so many places where the error occurs I'd rather just send the log.......lazy. I'll create a brand new post just for the log file.

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Tue, 12 Aug 2008 18:37:21 GMT

Well, when you creating a new post, you can attach a file... Can you just copy and paste the full ApplyControlToken error you are seeing?

--Matt Royer

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Tue, 12 Aug 2008 18:02:00 GMT

I'm seeing some ApplyControlToken hex errors but the numbers are not as exact as you mention. I'd love to add my amtopmgr.log file...how does one do that?

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Tue, 12 Aug 2008 17:54:24 GMT

In terms of your provisioning issue,

Are you seeing the following error in the amtopmgr.log...

During SCCM Management Controller Discovery
Error 0x80090308 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x6fcb970 returned by ApplyControlToken
During SCCM attempt to Provision
Error 0x80090308 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x261b948 returned by ApplyControlToken

If not, can you attach a full copy of your amtopmgr.log (from the start of provisioning to the failure)?

--Matt Royer

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Tue, 12 Aug 2008 17:53:48 GMT

Matt,

I've been working with a system that I've assigned a static IP and forced not to look at DHCP at all to see how that works out. I'm still not able to provision the system however I'm not having DNS / DHCP problems either. It almost seems like the communication between the client and the SCCM server goes about half way and initiates the DHCP processes but then it stops due to authentication problems and then the DHCP / DNS records are left in limbo until the next IPCONFIG / REGISTERDNS or similar command.

I went to the HP site and downloaded the Intel LMS and SOL to see if that made any difference but alas no change except some new and different failures in the SCCM amtopmgr.log.

I tried adding a machine using the OOB wizard by manually entering the machine hash and the wizard ran through but nothing seems to have happened. I've still got only one OOB option in my SCCM console.

I'm scratching my head at this point.

Re: DHCP and DNS registrations with AMT

webadmin@intel.com — Tue, 12 Aug 2008 17:43:42 GMT

Sandy,

In terms of the DHCP / DNS scenario you saw. The root of what’s happening is that by default, HP puts HPSystem as the default ME hostname when the client is in an unprovisioned state. When the vPro Client loads, the Management Engine (ME) is the first thing to come up (happens shortly after post). When the ME loads, it will request an IP address and will register the IP address in DNS. Since HP has “HPSystem” as the default hostname in an unprovisioned state, ME will register the HPSystem in DNS with the associated IP address. When the vPro Client boots up the Operating systems, the OS will grab the same IP address the ME picked up and will register it’s hostname in DNS (essentially overwriting the HPSystem DNS registration with the OS hostname). During SCCM (our any other ISV for that matter) provisioning process, SCCM will set the ME hostname to what was either A) Enter in the Out Of Band Import Wizard or B) Pulled from the SCCM Client Agent during agent based initiation. Once provisioned, the ME hostname will match the Operating System and any DNS update (from the OS or ME) will update to the same record.

Although I have not been able to reproduce it consistently, it appears that the initiation of the provisioning process sometimes initiates the ME send a DNS update request. With the ME hostname still being HPSystem, it overwrote the DNS record the OS registered. If you were to do an ipconfig /renew on the OS or reboot the computer, the OS Hostname should be re-stamped back in DNS. This does not appear to be an issue with other OEMs that leave the ME hostname blank in an unprovisioned state.

Once the provisioning process is complete and the ME hostname is synched with OS, you should not see this problem anymore.

--Matt Royer