WSHRemote, mstest and Launching User   

I have the following configuration:

Two Windows 2003 Servers with local user Build and the same password. First 
machine executes remotely VBScript on second machine using WSHRemote.

WSHRemote configuration that works:

Open WSHRemote PRoperties -> Identity Tab -> select "This User" radio button 
and type Build user id and password.

WSHRemote configuration that does not work:

The launching user radio button is checked.

Question: the launching user is always a Build user on remote control 
machine, so there should be no problem. In fact configuration that works 
simply specifies the same build user explicitly. So, why does launching user 
not work?

I had this problem a long time ago, so I don't remember details. I think I 
observed that mstest.exe (Visual Studio Unit Test program) had some security 
error. So, basically code started to execute, but there was some restriction 
even if user id was basically the same.

date: Wed, 23 Jul 2008 11:25:21 -0700   author:   am

RE: WSHRemote, mstest and Launching User   

Hi,

Based on my understanding, you have two Win2003 machines both have local 
users on them. Now, you want to use WSHRemote to execute the script on the 
remote machine. You find that it will succeed while using an explicitly set 
username/password, but fail using "The launching user" option. If I have 
misunderstood you, please feel free to tell me, thanks.

Do the two local users have the same user name? This type security 
trust(NTLM authentication) just requires the two users have both the same 
username and password. Additionally, can you tell me the symtom of "does 
not work"? Do you get any error message? 

For this issue, I suspect "The launching user" option may not use the 
correct user to launch the application. I recommend you examine the 
"Security" category of Event Viewer on the remote machine for both the 
working and not working scenario. There should be records indicating what 
accounts that are logging on the remote machine. Are they the same? 

Finally, is it possible for you to provide two sample scripts with detailed 
steps to help me reproduce this issue locally? Once I can reproduce it, I 
can understand it better and help you to troubleshoot it more efficiently. 

Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and 
suggestions about how we can improve the support we provide to you. Please 
feel free to let my manager know what you think of the level of service 
provided. You can send feedback directly to my manager at: 
msdnmg@microsoft.com.
==================================================
Get notification to my posts through email? Please refer to 
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues 
where an initial response from the community or a Microsoft Support 
Engineer within 1 business day is acceptable. Please note that each follow 
up response may take approximately 2 business days as the support 
professional working with you may need further investigation to reach the 
most efficient resolution. The offering is not appropriate for situations 
that require urgent, real-time or phone-based interactions or complex 
project analysis and dump analysis issues. Issues of this nature are best 
handled working with a dedicated Microsoft Support Engineer by contacting 
Microsoft Customer Support Services (CSS) at 
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

date: Thu, 24 Jul 2008 06:42:48 GMT   author:   (Jeffrey Tan[MSFT])

Re: WSHRemote, mstest and Launching User   

I just set option "The launching user" and re-run system.

Remote execution on vbscript side worked just fine. Unfortunately Visual 
Studio mstest.exe has failed with the following error message that only 
happens when I use "The Luanching User" option:

    Final Test Results:
    Results               Top Level Tests
    -------               ---------------
    Not Executed          TestNameGoesHere

Run has the following issue(s):
    Failed to queue test run 'Build@Hostname 2008-07-24 10:53:11': Failed to 
connect to an IPC Port: Access is denied.


""Jeffrey Tan[MSFT]""  wrote in message 
news:qLUuCiV7IHA.5288@TK2MSFTNGHUB02.phx.gbl...
> Hi,
>
> Based on my understanding, you have two Win2003 machines both have local
> users on them. Now, you want to use WSHRemote to execute the script on the
> remote machine. You find that it will succeed while using an explicitly 
> set
> username/password, but fail using "The launching user" option. If I have
> misunderstood you, please feel free to tell me, thanks.
>
> Do the two local users have the same user name? This type security
> trust(NTLM authentication) just requires the two users have both the same
> username and password. Additionally, can you tell me the symtom of "does
> not work"? Do you get any error message?
>
> For this issue, I suspect "The launching user" option may not use the
> correct user to launch the application. I recommend you examine the
> "Security" category of Event Viewer on the remote machine for both the
> working and not working scenario. There should be records indicating what
> accounts that are logging on the remote machine. Are they the same?
>
> Finally, is it possible for you to provide two sample scripts with 
> detailed
> steps to help me reproduce this issue locally? Once I can reproduce it, I
> can understand it better and help you to troubleshoot it more efficiently.
>
> Thanks.
>
> Best regards,
> Jeffrey Tan
> Microsoft Online Community Support
>
> Delighting our customers is our #1 priority. We welcome your comments and
> suggestions about how we can improve the support we provide to you. Please
> feel free to let my manager know what you think of the level of service
> provided. You can send feedback directly to my manager at:
> msdnmg@microsoft.com.
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no 
> rights.
>

date: Thu, 24 Jul 2008 11:07:10 -0700   author:   am

Re: WSHRemote, mstest and Launching User   

Hi Sergei,

Thank you for the feedback.

Oh, it seems that this problem occurs on the remote machine related with 
mstest.exe. The strange part is that it only fails for "The launching user" 
but succeeds for hard-coded username/password. 

In this situation, can you try to use the Process Explorer to examine the 
processes launching tree for mstest.exe on remote machine? The logic is 
that you can examine it by using both "The launching user" and hard-coded 
username/password. There must be some difference here, but I am not sure 
without local reproduce yet. I am not a mstest expert, but mstest.exe 
should try to launch the "vstesthost.exe" to perform the work. In the 
Process Explorer, you may examine if "vstesthost.exe" is launched 
correctly. Furthermore, for the Process tree, we can also examine the 
running accounts of mstest.exe in both scenarios.

Finally, I would still ask, is it possible for you to provide sample 
scripts with detailed steps to help me reproduce the problem locally? 
Without reproducing it, it is not very convenient for us to perform the 
troubleshooting or debugging. Thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
=========================================
Delighting our customers is our #1 priority. We welcome your comments and 
suggestions about how we can improve the support we provide to you. Please 
feel free to let my manager know what you think of the level of service 
provided. You can send feedback directly to my manager at: 
msdnmg@microsoft.com.

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

date: Fri, 25 Jul 2008 03:38:55 GMT   author:   (Jeffrey Tan[MSFT])