Microsoft Knowledge Base Email Alertz

(830531) - When you try to install Microsoft Office Live Communications Server 2003 in the following scenario: You start a command prompt (Cmd.exe) by using the runas command together with the /netonly parameter. In the runas command, you specify the credentials...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 830531 - Last Review: October 17, 2003 - Revision: 1.1

Setup Does Not Immediately Notify You About Incorrect Credentials When You Use RUNAS to Install Live Communications Server

SYMPTOMS

When you try to install Microsoft Office Live Communications Server 2003 in the following scenario:
  1. You start a command prompt (Cmd.exe) by using the runas command together with the /netonly parameter.
  2. In the runas command, you specify the credentials of a domain user who does not have the correct permissions to install Live Communications Server in the Active Directory directory service. For example, you specify the credentials of a user who is not a member of the Domain Admins security group.
  3. You run Live Communications Server Setup from this command prompt.
You receive an error message that is similar to the following:
Error 27649. Error '0x80070005' getting/creating Microsoft Connection Point under the computer object in Active Directory during 'InstallADEntry'.
When you click OK, the installation is rolled back.

You expect to receive this error message because the account that you specified in the runas command does not have the correct permissions to install Live Communications Server in Active Directory. However, you expect Setup to notify you of these incorrect credentials before it starts the installation of Live Communications Server.

CAUSE

This behavior occurs when you are logged on to the local computer with an account that has administrative permissions on that local computer.

WORKAROUND

To work around this issue, when you use the runas command together with the /netonly parameter, specify the credentials of an account that is a member of the Domain Admins security group and that is a member of the RTCDomainServerAdmins group.

MORE INFORMATION

When you type runas /? from a command prompt, the following Help information appears for the /netonly parameter:
Use if the credentials specified are for remote access only.
This information means that when you specify the /netonly parameter during your runas session, programs that you install use the credentials that you specified in the runas command only for remote operations. In contrast, all local operations are performed by using the credentials you supplied when you logged on to the local server. Because of this difference, when you try to install Live Communications Server, and you are logged on with sufficient permissions to install programs on the local computer, Setup does not immediately warn you that you do not have the correct permissions to install Live Communications Server. Setup starts the installation of Live Communications Server. However, when Setup must contact Active Directory, it submits the credentials that you supplied in the runas command. Because these credentials do not have sufficient permission to modify Active Directory, the installation of Live Communications Server is unsuccessful, and you receive the error message that is described in the "Symptoms" section of this article.

APPLIES TO
  • Microsoft Office Live Communications Server 2003
Keywords: 
kberrmsg kbprb KB830531
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate