Categories
Sponsors
Archive
Blogroll Badges
Community
|
Posted in Virtual Machine Manager, Windows Powershell, Windows Server | 4 Comments | 4,969 views | 22/05/2013 16:59
In this sample script, I use SCVMM 2012 to get virtual machine list.
Also you can filter specific Host Groups like in this sample.
Posted in Exchange Server, Windows Powershell | 2 Comments | 13,179 views | 22/05/2013 16:45
You can get ready and retry queue’s of Exchange Server with this script:
You can add multiple Exchange hosts to an array, it’ll just query Hub Transport servers. It only support Exchange Server 2010.
Posted in Windows Powershell | 1 Comment | 17,607 views | 22/05/2013 15:30
In this sample, I’ll show you how to get active Exchange Server CAS connections via PowerShell:
You can loop this script to get real time connection statistics.
Posted in Windows Powershell | No Comment | 2,543 views | 22/05/2013 14:17
This is an example script for PoSHServer to query cluster names via HTTP get request.
Save this script as “getclustername.ps1”. Put it into PoSHServer homedirectory. After that you can query like this:
You can query any information like this via PowerShell remoting.
Posted in Windows Powershell | 1 Comment | 3,497 views | 23/04/2013 16:55
Hello, PoSHStats for Exchange Server v2.2 is almost ready! Main Screenshot: Example of Exchange Host Reporting: Example of Mailbox Database Reporting: Example of User Mailbox Reporting: It has a nice limit information bar :) Also you can see service status of Exchange hosts: This is not the final version of PoSHStats. Tested with 3000 mailboxes, everything seems ok. First time setup will take about 5-10 minutes depends on your environment. First download setup: Install setup.exe. After installation, open PowerShell and:
Give your hostname (like reports.poshstats.net or 192.168.2.1) and port number, then you are free to go. Thanks for using PoSHStats. Yusuf.
Posted in Virtual Machine Manager, Windows Powershell | 10 Comments | 16,291 views | 04/04/2013 20:25
Hi guys and ladies! :) Update: v1.4 is here! Thanks for your feedbacks. Hyper-V VM Migration Script is ready! Now it’s possible to migrate your VMs from Hyper-V v2 to Hyper-V v3 with quick migration capabilities. It supports following scenarios: 1. Standalone Hyper-V v2 Host Update v1.4: Update v1.3: Update v1.2: So why it supports untrusted domains? Because you may not want to install Windows Server 2012 Cluster into your existing Windows Server 2008 R2 environment. If you have totally different environment for Hyper-V v3, then this script is your best friend. Advantages: 1. It supports BITS! It’s ready to move large VHD files. How to Install? 2. You can use exe or msi file to installation. I’ve just used migration.exe file to installation. 3. Change Powershell path if you have different drive path. 4. Click Install to begin installation. 5. That’s it! You can start using migration script. 6. Go to Powershell and type following to change execution policy as “AllSigned”.
7. Allow my code publishing certificate. This will prevent you to run untrusted scripts.
8. Installation is done! Now we can start migration of virtual machines. How to use? Example 1: If want to migrate VM01 from HV001 (10.10.10.2) to your local Hyper-V v3 host, use following:
BTW, -VMPath switch is the destination path. Not your current VM path. This script finds VM path automatically. Example 2: If HV001 (10.10.10.2) is a standalone machine, use following:
Example 3: If HV001 (10.10.10.2) is a member of a untrusted domain, use following:
Example 4: Having trouble with migration? Use debugging switch (-DebugMode) to see what really makes that problem:
Requirements: 1. You should install this script on to your Hyper-V v3 host. 2. This script doesn’t allow you to migrate VMs if they have snapshots. You should remove them first. 3. Requires Powershell v3. (It comes by default on Windows Server 2012) 4. Hyper-V v2 host and Hyper-V v3 host should have same network switch names. If they are different, this script connects first external network to your virtual machine. Thanks for using Hyper-V VM Migration script! -Yusuf.
Posted in Windows Powershell | 4 Comments | 23,111 views | 27/03/2013 11:03
When you remove an Exchange Mailbox from DAG or your environment, msExchHomeServerName attribute remains same. You may get problem when you try to update user mailbox due to non exist Mailbox Server. In order to achieve this problem, you should get affected mailboxes first, then you should update them with correct mailbox server name. First get all affected mailboxes:
Update them with this:
After that process, all msExchHomeServerName will be corrected. |