Connect-VIServer and Single Sign-on

[Flapoly]

Hi all,

As part of update2 release note there is this section

Windows Single Sign-on Support

You can now automatically authenticate to VirtualCenter using your current Windows domain login credentials on the local workstation, as long as the credentials are valid on the VirtualCenter server. This capability also supports logging in to Windows using Certificates and Smartcards. It can be used with the VI Client or the VI Remote CLI to ensure that scripts written using the VI Toolkits can take advantage of the Windows credentials of your current session to automatically connect to VirtualCenter.

So I have expected to be able to use VIPowerShell (now named VIToolkit) without providing credential during the Connect-Viserver... But this does not works (I use the upd2 VC & upd2 VIPSToolkit)

Does some-one has been able use the Connect-VIServer in real sigle sign-on ?

[Flapoly]

I have done some progress...

It does works well from my XP Workstation

It does not work from my W2K3-X64 server.

It does works well from my W2K3-X64 server... but using X86 (32bit) Powershell

=> So I suspect a bug/issue with powershell 64bit & single sign-on

[LucD]

Perhaps you could check the vpxd log on the VC.

First check (and eventually change) the logging level.

Look for SSPI entries in the log.

[CITITECHS]

I also have the same issue on WIN2K3-32bit

I havent tested with XP nor can I.

But does it have anything to do with the Version of Virtual Center running ? If so am running 2.0.2.61426

My toolkit version is

VI Toolkit Version

-

---

VMware VI Toolkit for Windows 1.0 build 103777

[admin]

I wanted to pass along an update from our QA team, we have confirmed that this is a problem on 64 bit OSes. We're still pinning down what exactly the problem is.

As Flapoly mentions this seems to work in 32 bit mode when running on a 64 bit OS.

To start the toolkit in 32 bit mode you can:

1. Start PowerShell using the 32-bit shortcut, then type "Add-PSSnapin VMware.VimAutomation.Core"

2. You can create your own shortcut that references the 32-bit version of PowerShell to launch the toolkit.

[bkboyer]

In case anyone else has the problem with single sign-on and using RunAs:

Adding the following lines to the global profile fixed the issue.

$USER=$env:username

$env:appdata = "C:\Documents and Settings\" + $USER + "\Application Data"