Edit the following files :
- cpqhmmd.ini

[HMMDConfiguration]
AnonymousAccess=True
LocalSecurityAccess=true
SleepModeCheck=false

- cpqhmmdx.ini
[HMMDConfiguration]
LocalAccessEnabled=true
LocalAccessType=Administrator

Then restart the services of HP from the Services mmc console of windows (particularly the HP Insight Foundation Agent service)

Then try to open the manage homepage again. You should be able to access the site. Your browser will use the ADMINISTRATOR access by default.

Just dont forget that as soon as you are logged in change the password and revert the changes that you have made to the mentioned files. And restart the services again to ensure that youll restore the security settings.

Hope this helps.

“d” is the drive where vista is installed.

Once there, type: “bcdedit.exe” or you can just type “bcdedit“. Do not include the quotation marks ” “.

It will generate a screen like this:

———————————————————————————————————

Windows Boot Manager
——————–
identifier              {bootmgr}
device                  partition=C:
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
resumeobject            {fe04aef5-e49c-11db-9f2f-cdf57e93812b}
displayorder            {ntldr}
                        {default}
toolsdisplayorder       {memdiag}
timeout                 10

Windows Legacy OS Loader
————————
identifier              {ntldr}
device                  partition=C:
path                    \ntldr
description             Windows 2003 Server Enterprise

Windows Boot Loader
——————-
identifier              {default}
device                  partition=D:
path                    \Windows\system32\winload.exe
description             Microsoft Windows Vista
locale                  en-US
inherit                 {bootloadersettings}
osdevice                partition=D:
systemroot              \Windows
resumeobject            {fe04aef5-e49c-11db-9f2f-cdf57e93812b}
nx                      OptIn

——————————————————————————————————

now check your result against the above, make sure that all the parameters above are the same (except for your drive letter, which might be different from mine).

Now look at the “windows bootloader” section and note what you see in your report/DOS screen:

You may notice that instead of displaying “osdevice partition=D:” it may display “osdevice unknown“. The same applies with “device“. I have highlighted what I am referring to as bold in the report above.

If these settings are not showing the drive on which your vista is installed, you must change it. Since mine is drive “D” for vista, this is the command you must type:

D:\Windows\System32>bcdedit /set {default} osdevice “partition=D:

Also, if the “device” is showing as unknown, type this command: 

D:\Windows\System32>bcdedit /set {default} device “partition=D:

If the path is  \Windows\system32\winload.exe, then that’s fine. Remember “D” above is the name of the drive on which your vista is installed. If your vista in on “F”, use “F”, etc. “default” in the blue text command above is the identifier for the os boot-up that you are trying to fix, in this case, vista. Sometimes, for the identifier you might have some long random numbers (GUID), just copy it and use it if is not the “default” that is shown.

Exit the DOS screen, restart your system, and you should be ok. If you have any problems please let me know.

Note Skip this method if the operating system is Windows 2000.

To clear the temporary file and restart the hotfix installation or the service pack installation, follow these steps:

1. Delete all the tmp*.cat files in the following folders:

   %systemroot%\system32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}

   %systemroot%\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}

2. Delete all the kb*.cat files in the following folders:
   %systemroot%\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
   %systemroot%\System32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE}
3. Delete all the oem*.* files from the %systemroot%\inf folder.
4. At the command prompt, type the following commands. Press ENTER after each command.
   net stop cryptsvc
   ren %systemroot%\System32\Catroot2 oldcatroot2
   net start cryptsvc
   exit
5. Restart the failed hotfix installation or service pack installation.

            Click on Help > Detect and Repair

1. Select “Repair My Shortcuts While Repairing” and (if available) “Discard my customized settings and restore default settings”
2. Click OK

Even when least expensive or same-site target selection is enabled,
clients might still access high-cost or out-of-site targets. Also, when
default target selection is enabled, a client computer might access a target
server outside of its own site, even though a same-site target exists. These
problems are typically caused by one of the following situations:

.. The same-site target is temporarily unavailable (due to server or network
issues), and the client fails over to the next target, which could be
outside of the client’s site.

.. DFS uses the IP address-to-site mappings in Active Directory to determine
the site of a target. If a target’s IP address is not mapped to its current
site, DFS cannot properly order that target in a referral. Incorrect site
mappings can occur when subnets are not configured correctly or when a
server or domain controller is moved to another site in the Active Directory
Sites and Services snap-in, but the server’s or domain controller’s IP
address still maps to the subnet of the previous site. Incorrect site
mappings often occur when domain controllers are not moved to the site that
corresponds to their IP address or when domain controllers are left in the
default first site or the site where they originally belonged.

.. If no same-site targets exist and a client unexpectedly chooses a
high-cost target, it might be caused by an incorrect site cost setting.

.. The client’s IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the client.

.. The target’s IP address is not in a subnet that is defined in Active
Directory and so DFS cannot obtain site information about the target.

.. DNS lookup issues on the DFS root server are causing DNS name-to-IP
address mappings to fail. The problem might be caused by DNS issues or when
a server has multiple IP addresses but not all of those addresses are mapped
to sites in Active Directory.

.. The client is using a cached referral that has become outdated due to
target change,, site changes, or both. For example, a target was added or
removed from a link or root, or a target was moved from one site to another.
The client will obtain an updated referral and after the referral expires,
the client’s cache is cleared (using the Dfsutil.exe /pktflush command), or
the client is rebooted.

.. Site information has changed, but the old site information is still cached
on the root server or domain controller in the target site cache, client
site cache, or site cost cache.

.. The DFS object is not up-to-date when the root server polls a domain
controller. This can be caused by Active Directory replication latency or
failure.

.. The Bridge all site links option is disabled. (This option is available in
the Active Directory Sites and Services snap-in) Turning off Bridge all site
links can affect the ability of DFS to refer client computers to target
computers that have the least expensive connection cost. An Intersite
Topology Generator that is running Windows Server 2003 relies on the Bridge
all site links option being enabled to generate the intersite cost matrix
that DFS requires for its site-costing functionality. If you turn off this
option, you must create site links between the Active Directory sites for
which you want DFS to calculate accurate site costs. Any sites that are not
connected by site links will have the maximum possible cost. For more
information about site link bridging, see Active Directory Replication
Topology Technical Reference.

.. Site awareness is not working correctly because the restrictanonymous
registry entry located at
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa is set to two on
Windows 2000 domain controllers. If this registry entry is set to two, DFS
root servers that are not domain controllers (and are running either Windows
2000 Server or Windows Server 2003) randomly sort the targets in a referral,
regardless of the namespace type (stand-alone or domain-based), target
selection method, or client operating system.

.. Domain controllers do not consistently provide site-costed SYSVOL
referrals because the SiteCostedReferrals registry entry was not set on all
domain controllers.

http://support.microsoft.com/kb/905846

Digging on the web, I found only more and more articles either repeating the steps from the Microsoft article or stating similar problems, with no solutions, to mine.

Firstly, let me declare the obvious: port 123 (SNTP) was forwarded to my domain controllers IP, both TCP and UDP, on my ADSL router. (NAT)

I tried my silver-bullet: unregister w32time and start again. I created the following batch script:

net stop w32time

w32tm /unregister
w32tm /register

w32tm /config /manualpeerlist:192.43.244.18 /syncfromflags:MANUAL /reliable:YES

net start w32time

w32tm /config /update

w32tm /resync /rediscover

The first line stops the NT service. You then unregister it and re-register it, recreating all the registry keys with default values, giving you a standard starting point. After that, I configure it, specifying an NTP server’s ip address as a peer (this IP is time.nist.gov) and that it should synch from the manual peer list. I also mark this server as a reliable time server. I then start the service again, tell it to update its configuration, just in case, and then resync.

Extra Steps :-

You have to be very sure you followed the instructions for using an external time source correctly. I’ve used these instructions on many a 2K3 server without issue, so to recap:

1. Change Windows to use the NTP protocol for time synchronization:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
Value: Type
Data: NTP

2. Configure the AnnounceFlags value:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
Value: AnnounceFlags
Data: 5

3. Enable the NTP server value:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
Value: Enabled
Data: 1

4. Specify the NTP server to use:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer
Value: NtpServer
Data: time.nist.gov,0×1

5. Select the NTP polling interval:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval
Value: SpecialPollInterval
Data: 900

6. Configure the time correction settings:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection
Value: MaxPosPhaseCorrection
Radix: Decimal
Data: 3600

Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection
Value: MaxNegPhaseCorrection
Radix: Decimal
Data: 3600

After this, stopping and restarting the NTP service should get you working. If it does not, check the value configured in step 4 – this being misconfigured is the only time I’ve seen errors in the Windows Time service like the ones you’ve posted, so it’s possible this is incorrect in your registry. I would also suggest using a time server OTHER than time.nist.gov, as it is a VERY busy time server and you are likely to miss one or two time syncs to it before you get a good one. I would suggest using another time server, preferrably a stratum-2 NTP server closer to you. You can find these listed here:
http://www.eecis.udel.edu/~mills/ntp/clock2a.html