Wap-Subscription
-
Adding existing VM’s to WAP Subscription using PowerShell
Edit: added Cloud parameter to the script. Deploying WAP for clients, they start creating new clouds, plans and subscriptions which is great!! But how do they add existing VM’s to new users in WAP? Easy….. you guessed it…. PowerShell! So I can’t take the credit here, my sources are found here & here. Ok, that’s out of the way.. here it is… Requirements: You must have an existing tenant account That tenant must have an existing VM (I usually just kick off a quick VM deployment in WAP and delete it once done) I like to use Out-GridView to keep the script portable. -
Change default PHP settings in Windows Azure Pack (IIS WebFarm)
Had a user try to upload a theme to a Wordpress site they had published using Windows Azure Pack but were getting a file exceeded size limit error as exampled below. “The uploaded file exceeds the upload_max_filesize directive in php.ini” Typically you would just go into the php.ini located on the local webserver but how do I do this in a WAP Websites WebFarm? PowerShell of course!!! Ok, I do this from the websites controller server: -
Migrate multiple VM’s from one Hyper-V cluster to another Hyper-V cluster with different Logical Switch using PowerShell.
Another fast publish! (I really should get back and clean these up…) Recently upgraded one of our Hyper-V clusters and had to migrate workloads to a new Hyper-V cluster. The naming conventions of our logical switches etc were different so when migrating a VM using Hyper-V manager we were prompted to choose the new logical switch. Handling this via PowerShell in isolation is simple enough using this script but I wanted to do a whole stack of VM’s at once. -
VM Template network settings for WAP
Quick scribble: add images and detail 3 steps Template > NIC > Set Connected > Set static IP & Static MAC > OK Template > NIC > Set No Connected > Confirm static IP & Static MAC > OK Template > NIC > Set Connected > VM Network None > Confirm static IP & Static MAC > OK Do in each template AND hardware profile Deploying in WAP should work with or without a virtual network.