Lab setups for App-V
Hi guys,
recently I've been playing with the idea of setting up a test lab environment at home to test some Virtualisation solutions. Being a freelancer and wanting to keep abreast of developments in Virtualisation (I've mostly done packaging till now) I need to have something of a "playground"
I'll be setting up a server to run a number of virtual servers / clients. ( The hardware I'm looking at now would alow for about 8 VM's, this would include a SBS for my company stuff and 2 packaging machines)
Since my current client has been looking at Microsoft I thought I'd start by testing App-V. Now, having read abit online about Softgrid sequencing, the setups seem quite complicated, needing alot of different machines in a network. I'm ofcourse hoping I won't need all of em in a lab setup. Main focus of the tests would be actual virtualisation of applications, publishing and deployment if possible.
I was wondering if anyone here has any experience setting up a "home lab" for these kinds of tests, and if you'd be willing to share your experiences.
Thanks in advance for your answers.
PJ
recently I've been playing with the idea of setting up a test lab environment at home to test some Virtualisation solutions. Being a freelancer and wanting to keep abreast of developments in Virtualisation (I've mostly done packaging till now) I need to have something of a "playground"
I'll be setting up a server to run a number of virtual servers / clients. ( The hardware I'm looking at now would alow for about 8 VM's, this would include a SBS for my company stuff and 2 packaging machines)
Since my current client has been looking at Microsoft I thought I'd start by testing App-V. Now, having read abit online about Softgrid sequencing, the setups seem quite complicated, needing alot of different machines in a network. I'm ofcourse hoping I won't need all of em in a lab setup. Main focus of the tests would be actual virtualisation of applications, publishing and deployment if possible.
I was wondering if anyone here has any experience setting up a "home lab" for these kinds of tests, and if you'd be willing to share your experiences.
Thanks in advance for your answers.
PJ
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Ment
15 years ago
If you want to test the virtualization part (on the client) you don't need a server infrastructure. Load the application locally through command line, MSI (generated by sequencer) of custom tooling (like mine: google "app-v acdc").
If you want to test deployment you have to choose the deployment scenario you want to test (there are multiple):
- full management server (full options)
- streaming server (only streaming)
- configmgr 2007 r2 integrated (based of configmgr, depends if your client will use this).
There is good Microsoft documentation avaiable here: http://technet.microsoft.com/en-us/appvirtualization/cc843994.aspx
I would start with the App-V trial guide: http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/MSAppVirt45Trial_Guide_Final.docx
It helps setting up a full management server and sequences two applications and publishes it.
Hope it helps.
Regards,
Ment van der Plas
MVP App-V
If you want to test deployment you have to choose the deployment scenario you want to test (there are multiple):
- full management server (full options)
- streaming server (only streaming)
- configmgr 2007 r2 integrated (based of configmgr, depends if your client will use this).
There is good Microsoft documentation avaiable here: http://technet.microsoft.com/en-us/appvirtualization/cc843994.aspx
I would start with the App-V trial guide: http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/MSAppVirt45Trial_Guide_Final.docx
It helps setting up a full management server and sequences two applications and publishes it.
Hope it helps.
Regards,
Ment van der Plas
MVP App-V
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.