If I have a computer that has previously been provisioned for out of band management and it must now be reimaged and given the same computer name, what is the proper procedure? Do you need to unprovision the computer first and remove the out of band management controller account from AD? Then reimage and re provision? Or can you keep it provisioned and the oob account in tact, and just reimage the system and let SCCM re discover the controller? Anyone using oob that has experience with this?
OK so if I take a provisioned machine and reimage it, retaining the same name it originally had and leaving the oob mgmt controller account in tact in AD, SCCM sees the AMT status for the client as 'Unknown.' Trying to discover oob mgmt controllers through the sccm console results in an error, and on the client the oobmgmt.log indicates "!! Device is already provisioned."
So what happens now? I would hate to think that in a situation as common as reimaging a client machine, that the techs need to go out and yank CMOS batteries each time in order to get the client to re-provision properly.
If you are rebuilding the system and plan on using the same name again, you do not need to unprovision it first.
If you are going to rename the computer as part of the rebuild process you will first want to unprovision the system. Ideally, you will want to do this in SCCM so that it can delete the AD object for you. Once the new OS install is complete let SCCM provision the system again and you will be all set. You could also unprovision AMT from the MEBx and then manually delete the AMT entry from your SCCM AMT OU.
If you change the name of the OS without unprovisioning AMT first you will end up with a situation where the hostname on the TLS certificate in AMT does not match the hostname of the OS that gets registered in DNS, which will prevent SCCM from being able to comminicate with AMT over the network.
Hey Dan but thats just it -- im not renaming the computer.
The machine is reimaged and the same computer name as it originally had is chosen. so there isnt any host name mismatch. After the machine is up and running, SCCM sees the AMT status as unknown, fails to discover the oob mgmt controller, and forcing the out of band discovery on the client results in the oobmgmt.log saying the system is already provisioned.
if i reset cmos and run sccm oob discovery, everything provisions properly.
So what is going wrong here?
Are you deleting the computer's record in SCCM or leaving it in place?
If you delete the record of a provisioned system in SCCM, it will also delete the AMT remote admin password, which can cause problems like you are describing.
Can you explain how this should work in SCCM then? If there is no hostname mismatch (the system is reimaged with the same name it previously had when the AMT was provisioned), why is SCCM failing to discover the AMT status? The system knows it is still provisioned (based on the info in the oobmgmt.log, but SCCM shows the system as status "unknown"
Thats funny you mention this... I was starting to think that was my problem and am in process of testing the reimage without deleting the old account first
i think that will fix everything
I am a bit confused on the renaming an AMT device and successfuly having the host name change as well. Here are the steps we take, and this seems not to work.
Renaming AMT Enabled Computer
Step 1: Unprovision AMT computer in SCCM
** Verify or Delete the the AMT computer account in Active Directory (I delete the account right after step (4).
Step 2: Delete SCCM client record from SCCM database
Step 3: Rename computer
In a email exchange between you and I back in Feb 2010, you had mentioned that we need to perform a "partial unprovision" and then "re-provision" the system
"so, if you need to rename a system you will need to do a partial unprovision and re-provision the system."
Can you verify these steps for me? I think they are as follows...
1. In AMT Bios, manually change the "HOSTNAME" to new computer name
2. Partial unprovision (in SMB mode)
Will SCCM now detect and provision device?
Is this done in the MEbX