All posts by Barry Mercer
2003 P to V 100% CPU
I been ahving issues with a P to V recently where the CPU is pegged at 100% shortly after boot, making it impossible to login or do anything. I gave it more RAM and somehow managed to log in and fire up task manager before the madness started. I killed the offending tasks and had a look through the services to see which one was no longer running. It turns out that “HP Insight Foundataion Agent” was the culprit. I’ve disabled this along with al the other HP Agents and things seem fine. It was a pretty old version we were running, and it might be fixed in a newer one. However they serve no purpose now it’s a VM so disabling them is probably a good thing either way.
6570b bitlocker tpm enable
I was having a lot of trouble enabling the TPM in my task sequence in SCCM for the 6570b. Using the biosconfigutility part of SP52095 I discovered that HP have for some inexplicable reason, changed the command to enable the TPM.
OLD:
Activate Embedded Security On Next Boot
Disable
*Enable
NEW
Activate TPM On Next Boot
Disable
*Enable
To be safe, I’d do a /getconfig and makesure that everything else is right. They’ve changed a few other “Embedded security” tags to be simply “TPM” instead.
manage-bde device is not ready
Bitlocker was prompting me fro the recovery each time I booted. The solution to this is the following:
manage-bde -protectors c: -disable
manage-bde -protectors c: -ENABLE
However I was then told that the device was not ready when enabling it. The solution is to fire up disk management, assign a drive letter to the hidden partition and then give it a go. This worked for me and I was able to enable it fine. I then removed the drive letter.
Netapp Oncommand login “Null”
Have been having a random problem with oncaommand. Despite saving my username and passowrd, after a while ity will stop saving it and show my logon name as being “NULL”. It appears this stems from an encryption key that oncommand uses. From what I gather this is corrupt in someway or oncommand can’t use it. It’s stored (on my win7 machine) in c:\users\%username%\netapp\systemmanager. Delete the three files that are in there (the key, the config and a backup) and you should be good to go next time you open it.