Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

closed as not a real question by GregD, Zypher, Warner, Chris S, Izzy Aug 25 '10 at 19:17

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

The answer to the second question has nothing to do with runas. The answer relates to how IE does authentication. – Zoredache Aug 25 '10 at 18:10
Which is the second question? If it is [2], then it tells also about SSMS. They are just exactly 2 and only cases (IE, SSMS) that I, as developer, need, i.e. to runas under domain user from non-domained computer – Gennady Vanin Геннадий Ванин Aug 25 '10 at 18:24
@Zoredache, see Update1. It is difficult for me to understand that using/entering RunAs has nothing to do with RunAs. What do you mean by this? – Gennady Vanin Геннадий Ванин Aug 26 '10 at 1:08
up vote 5 down vote accepted

In the 2nd link, the use of runas with the /netonly switch tells runas to run the specified program and if the program is ever asked for remote authentication to use the supplied credentials. The program is still executed as a local user.

The 1st link has the questioner attempting to actually run the program as a domain user, which will not work(link).

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.