Agreed, thanks Brian for your comments.
. . . . . and I have those roles/features so something else is missing . . . . .
I accept it may be a local issue, i just don't know.
I have attached a screen print showing the Hyper-V role and features installed on the 2008 R2 server.
And just to be clear, this is also where the VisualCron Server is running, so all of this management is Local.
We don't use Server 2012 yet, but also attached is a 2012 VM with the Hyper-V Role install option (this time I get the Module for Windows Powershell which I think you are relying on ?) <Sorry can't complete the Role Add for Hyper-V as its already a VM on Hyper-V>
So to summarise:
- Windows 2008 R2 OS Physical Server
- VisualCron Server (now 6.2.2)
- Powershell 3.0
- Hyper-V Role
- Hyper-V Tools Feature (Role Administration Tools)
- Attempting Management of Local VM's on Hyper-V on the Local Server
- Powershell (on this machine) does *not* have the commands being utilised by VisualCron e.g. Get-VM
Can you confirm you have this working on 2008 R2, What version of Powershell you are running, and what Powershell modules you have.
Based on the 2012 information attached, I don't think I would have any issues if we were Windows 8 Clients / Windows Server 2012 but we don't have that stack yet and won't for a while (Windows 7 / Windows Server 2008 R2).
I have also attached the Powershell script, available from the web that we are using to manage this from VisualCron at present, using powershell. We are very interested in using the Hyper-V tasks in VisualCron to more simply and logically manage these using standard VisualCron features.
It is *slightly* modified to include an extra parameter as we call it from VisualCron using a .cmd wrapper, and we write additional Output to appear against the Task in VisualCron
Edited by user
2013-04-15T23:57:31Z
|
Reason: Include Powershell script currently in use / Typos
File Attachment(s):
KJDavie attached the following image(s):