I couldn't find a discussion for this. It doesn't appear the Update 1 vSphere versions of either the Power CLI or the vSphere CLI are supported in WIndows 7 (at least according to the release notes).
Is anyone using these under Windows 7 now?
Were there any precautions or system modifications you made?
Any ideas on when these tools will be supported on Windows 7?
Most of PowerCLI is purely managed .NET code, I would expect the majority of our cmdlets to work fine on W7. This is not a guarantee, just my guess.
The exception is we have some cmdlets that use the VIX library. This is what gives us various guest operations. This includes Invoke-VMScript, Copy-VMGuestFile, etc. These things may very well not work on W7. When we have official support for W7 part of it will be to ensure that this stuff is working.
=====
Carter Shanklin
Read the PowerCLI Blog
[Follow me on Twitter|http://twitter.com/cshanklin]
We don't claim official support for W7 yet. We have reports that it works. If you're experiencing any trouble on Windows 7 the fail-safe is to launch an ordinary PowerShell window and add PowerCLI by running
Add-PSSnapin VMware.VimAutomation.Core
=====
Carter Shanklin
Read the PowerCLI Blog
[Follow me on Twitter|http://twitter.com/cshanklin]
OK. Thanks. Would you suspect if ther were issues they would be related to actually runnibng it (as opposed to being issues that could negatively affect the virtual environment)?
Most of PowerCLI is purely managed .NET code, I would expect the majority of our cmdlets to work fine on W7. This is not a guarantee, just my guess.
The exception is we have some cmdlets that use the VIX library. This is what gives us various guest operations. This includes Invoke-VMScript, Copy-VMGuestFile, etc. These things may very well not work on W7. When we have official support for W7 part of it will be to ensure that this stuff is working.
=====
Carter Shanklin
Read the PowerCLI Blog
[Follow me on Twitter|http://twitter.com/cshanklin]
OK. Sounds good. Thanks for the information.