The purpose of this project is to create a module that will simplify and make more efficient the querying and expansion of windows servers that are VM's in the VMware architecture.

It introduces 5 cmdlets and 5 intermediate functions.

1. Initialize-Connection $ComputerName : This function loads the PowerCLI environment and connects to the VSphere server indicated by $ComputerName.

2. Remove-Stalelogs $ComputerName : This function removes logs on $Computername that are older than 8 days from the below common log repositories. It then shows a report in the console of the change in space achieved.

   a. Windows Temp Files.

   b. Default Web Site 1 Logs.

   c. Exchange POP3 Logs.

   d. IIS HTTPerr Logs.

   e. Lucasware Logs.

   f. IIS logs for default website.

   g. WID logs.

3. Get-DiskSpaceUpgrade $ComputerName : This function queries the server indicated in $Computername via WMI for freespace and capacity of attached drives and, if there is less than 30% freespace, calculates the amount of space required to bring the drive to 35% freespace.

4. Get-DiskSpaceResult $ComputerName : This function does the same thing as Get-DiskSpaceUpgrade except it queries the Vsphere server as well to correlate the drives/partitions to specific virtual disk files in Vsphere. It will also determine if the server should not be automatically expanded, given certain conditions.

5. Add-Diskspace $ComputerName : This function uses every other cmdlet in the following order:

   a. If not connected to a Vsphere server, executes Initialize-connection.

   b. Execute Remove-StaleLogs.

   c. Execute Get-DiskSpaceResult and display needed changes, if any.

   d. For each of the drives that need additional space, expand the vmdk in VSphere. Then construct a diskpart bat script to extend the drive, move it to the remote computer, and then execute it.

   e. After all drives are completed, executes Get-DiskSpaceUpgrade to validate the changes and displays the result in console.

   f. Failure reasons include:

   i. Resulting drive would exceed 2 TB.

   ii. Hostname contains "DFS" or "Mailbox" in the name.

   iii. There is an existing snapshot.

   iv. Adding the requested amount to the server would result in the datastore being brought below 20% available space.

1. Configure cmdlet binding and enable pipeline use for all functions that are intended to be used as cmdlets.

2. Rename functions that are not intended to be used as cmdlets from the verb-noun nomenclature to a simple description of their use.

3. Determine other paths that might need to be evaluated for removing in Remove-StaleLogs

4. Find a way to deal with expanding drives that do not have an error when another drive does have an error. a. Example: Server A has 2 drives, C: and E:. Drive C: has 100 GB provisioned, but needs to be expanded to 120 GB. Drive E: has 1800 GB provisioned, but needs to be expanded to 2200 GB. Because this would bring that drive above 2048 GB, neither drive will be expanded. Ideally, I would want the C: drive to be expanded and the E: drive to expand to 2048 and report that there was an issue.

5. Configure Add-Diskspace additional optional parameters, specifing which drive letter, vmware hard disk, or windows disk/partition to expand.

6. Determine if there is a way to detect what vsphere servers exist on a network without knowing their names, and automate connecting to them.

7. Package this group of cmdlets into a module.