Unsolved
This post is more than 5 years old
4 Posts
0
1438
June 1st, 2011 10:00
Provision between vWorkspace, SCVMM and Virsto
I’ve created a PowerShell script that integrates the provision process between SCVMM, vWorkSpace, and Virsto.
This script simply does the following:
· Prompt the user for the number of VMs to be created
· Create the VMs on the SCVMM using a pre-configured template
· Create the VHD on Virsto then attach it to the VMs
· Import the VMs from SCVMM into vWorkspace using vWorkSpace PowerShell Module
The script is running fine but I’m facing two technical issues:
· Import-VQWComputer cmdlet in vWorkSpace module is importing only “Other/Physical computer groups” however, it should be “SCVMM computer group”. I converted it from SCVMM to Physical but we lost a few customizable features.
· After importing the computer into vWorkSpace. I can’t find them on the Web portal
HELP!!
DELL-Adam D
15 Posts
0
June 1st, 2011 18:00
Hi Amir,
Currently, we only support importing computers into an Other/Physical computer group. Although, as you mentioned, you lose some of the features by importing a computer into a Physical computer group. You should still be able to access the managed applications published to that group.
Just to clarify, when you mention the "Web portal" are you refering to vWorkspace Web Access? If this is the case you will want to ensure that you have a managed application correctly published to the Physical computer group that you imported the computers into. You also will want to make sure that the clients defined in vWorkspace have that managed applicaton assigned to them.
We are working hard on quickly expanding our PowerShell functionality so make sure to keep an eye on the community site for updates.
Adam
amirgf
4 Posts
0
June 2nd, 2011 08:00
Hi Adam,
Thank you for yours efforts in replying to my problem.
I certainly mean the vWorkspace Web Access and I will check on the managed application whether it is published to the physical computer group. I will certainly keep an eye on the site for any updates for PowerShell functionalities.
I will get back to you if I face another problem.
Thanks
Amir
amirgf
4 Posts
0
June 2nd, 2011 09:00
Hi Adam,
I am working on the provisioning with Microsoft Egypt and our reseller iSource, the contact details are below:
Sherif Talaat (v-shta@microsoft.com)
Ahmed Hussein (ahmed.hussein@isourceglobal.com)
They have requested to contact with you so that they could find a way around this solution but they require some understanding from you. Could you so kind to email them and put me on CC (aali@qe-software.com) so they can start communicating with you.
Thank you
Kind Regards
Amir Ali
PatrickRAtDell
37 Posts
0
June 3rd, 2011 14:00
Can you post your script, so we can see why it's not working?
sherif talaat
1 Message
0
June 5th, 2011 18:00
Get-QVWComputerGroup -Farm "vWorkspace Database"
Get-QVWAdministrator -Farm "vWorkSpace Database"
Get-QVWFarm -Identity "vWorkspace Database"
New-QVWComputerGroup -Farm "vWorkspace Database" -Name "CoEx" -ComputerRole Desktop -SystemType Physical -AdminCredential "VDILAB\Administrator" -Location "Location1"
Import-QVWComputer -Farm (Get-QVWFarm -Identity "vWorkspace Database") -ComputerGroup "CoEx" -Location "Location1" -Identity "Win7.vdilab.com" -Force
DELL-Andrew W1
378 Posts
0
June 20th, 2011 10:00
Good Afternoon,
I think there might be a little misunderstanding here.
You're importing the machines into the Farm. However, at no point are you creating a managed app/desktop.
Without this, nothing will show up in the Website. This is expected behaviour.
Create a managed app for your Desktop group and this managed app will launch any of the new desktops that you've just imported.
Thanks, Andrew.