addfakeservers.ps1 and removefakeservers.ps1
NOT standalone. Makes it looks like your demo setup has more than one server. We use a very useful feature of Exchange 2007 setup to make this work. Basically we use the /provisionedserver switch to create pre-provisioned servers (AD objects). The admin interface detects these as servers, even though the hardware has not been installed yet. This enables server delegation and pre-provisioning in Exchange topologies.
Standalone. This script shows how you can use PowerShell to easily load balance mailboxes by size across servers. Key thing is the use of get-mailboxstatistics and move-mailbox.
cleanup.ps1 and generate.ps1
NOT standalone. Cleanup.ps1 completely restores your demo environment to a basic-just-installed-Exchange state. New car smell not included. Generate kicks off everything else to generate the demo environment.
NOT standalone. Standard variables shared by all the scripts. Called by generate.ps1. MAKE SURE TO EDIT THIS FILE to customize this for your environment.
mailstorm.ps1 and mailstorm2.ps1
Standalone with caveats. What's a demo Exchange environment without some email? BTW: this is the one script that is likely to not just work automatically in your environment. This is because we assume some basic auth settings to make the Hub server accept mail. This step is done in generate.ps1 so make sure you do that if you plan to use this script by itself.
Standalone. Totally totally useless. But cool. This is the matrix unloaded... er... powershelled.
Standalone, with caveats. Just like the name implies, sends content over mail. It uses the "from" from initvars.ps1 so make sure to copy those lines as needed to make it standalone.
out-html.ps1 and out-ie.ps1
Standalone. I already posted these to http://www.viveksharma.com/techlog earlier.
To get the goodies, go here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.