Thanks for the response. I understand what you are trying
to do. But looks like the WMS Administrator snap-in
requires you to be an Administrator, or else it cannot
quite figure out how to connect to the server when you
specify the hostname. It figures things out when Localhost
is used to add the server.

Unfortunately, the Administrator later successfully
resolves the hostname and therefore remembers to use the
hostname the next time it connects instead of localhost.
But since using the actual hostname fails, you are having
to add the local server everytime you open the MMC Admin
as "Localhost". At this point, I can't seem to find a way
around this restriction.

But as you've observed earlier, once the "connection to
server" has happened by adding as localhost, there seems
to be no problem in administering the server itself. So, I
think the SDK or API code that you write will work okay,
the restriction seems to be in the Snap-in itself. For
example, on the server machine I was able to write a
script to create a publishing point on the server running
as the "WMS Admin" account (belonging to Power Users
group).

Hope this helps.

Thanks,
Ravi
--
This posting is provided "AS IS" with no warranties, and
confers no rights.