Check out the new OneDrive client for both Windows and Mac OSX!

https://preview.onedrive.com/sync/setup.html

Kiss those pesky limitations goodbye!

Actually your distribution groups are a great way to do this. On S4B just type the name of a distro group in Exchange online and it should populate those users and group for you by right clicking and add to favorites.
Sometimes I create a separate book just for departments etc.

#Allow Remote Scripts To Run
Set-ExecutionPolicy RemoteSigned

#Store Office 365 Global Admin Creds and connect to MS online
$credential = Get-Credential
Import-Module MsOnline
Connect-MsolService -Credential $credential

#Verify Active Directory Sync Has Been Disabled - Money Command will not run with it on
$IsDirSyncEnabled = (Get-MsolCompanyInformation).DirectorySynchronizationEnabled
If($IsDirSyncEnabled -eq $false) {Write-Host "Office 365 Active Directory Sync Disabled - Good to go!"} else {Write-Host "Please disable Active Directory Sync and Wait" Exit}
Start-Sleep -Seconds 5

#If you want to dump your existing AD to text file for reference uncomment the next line
#ldifde -f C:\export.txt -r "(Userprincipalname=*)" -l "objectGuid, userPrincipalName"

do{

Query the local AD and get all the users output to grid for selection

$ADGuidUser = Get-ADUser -Filter * | Select Name,ObjectGUID | Sort-Object Name | Out-GridView -Title "Select Local AD User To Get Immutable ID for" -PassThru
#Convert the GUID to the Immutable ID format
$UserimmutableID = [System.Convert]::ToBase64String($ADGuidUser.ObjectGUID.tobytearray())

Query the existing users on Office 365 and output to grid for selection

$OnlineUser = Get-MsolUser | Select UserPrincipalName,DisplayName,ProxyAddresses,ImmutableID | Sort-Object DisplayName | Out-GridView -Title "Select The Office 365 Online User To HardLink The AD User To" -PassThru

#Uncommend the ###Careful### out of the following command to purge all the deleted users from the users recycle bin on Office 365
#This will only query for users that are unlicensed so it will skip users with mailboxes but still use at your own risk
###Careful### Get-MsolUser -ReturnDeletedUsers | Where-Object {$_.isLicensed -NE "false"} | Remove-MsolUser -RemoveFromRecycleBin -Force

Money command that sets the office 365 user you picked with the OnPrem AD ImmutableID

Set-MSOLuser -UserPrincipalName $OnlineUser.UserPrincipalName -ImmutableID $UserimmutableID

#Verify ImmutableID has been updated
$Office365UserQuery = Get-MsolUser -UserPrincipalName $OnlineUser.UserPrincipalName | Select DisplayName,ImmutableId
Write-Host "Do the ID's Match? if not something is wrong"
Write-Host "AD Immutable ID Used" $UserimmutableID
Write-Host "Office365 UserLinked" $Office365UserQuery.ImmutableId

Ask To Repeat The Script

$Repeat = read-host "Do you want to choose another user? Y or N"
}
while ($Repeat -eq "Y")

#List Users and ImmutableId
Get-MsolUser | Select DisplayName,ImmutableID | Sort-Object DisplayName | Out-GridView -Title "Office 365 User List With Immutableid Showing"

#Close your PS Office 365 Connection
Get-PSSession | Remove-PSSession

I hope you did a backup before sysprep...

Restore from backup
Power on VHD on Hyper-V 2012 and update the integration drivers
Shutdown the VHD
Copy the VHD to your Storage Blob Using How-To
http://community.spiceworks.com/how_to/120949-migrate-hyper-v-vms-to-azure-with-os-disks-bigger-than-128gb-using-powershell

When I was running Screen Connect on Linux it would fail on occasion like this and I would just download the Tar file and reinstall over the top and it would usually get it going again.
https://www.screenconnect.com/Download

Post the script as you have it now

I usually use AD modify for this.. much easier and has a rollback feature in case you mess something up.
http://admodify.codeplex.com/

Let me know if that works for you if not then I will look over the script and test it on a clean AD for you.

This write up is what I point people to when they have these questions (*the one my MS rep from SW said is gospel)
http://www.microsoft.com/OEM/en/licensing/sblicensing/Pages/downgrade_rights.aspx#fbid=D7zcRxMWVLN

DC's will only slow you down if you have many calls for tokens. unless you have some LOB - SSO sitution the lowest tier I would go is A1.

My 2 cents

good luck

My Dad, A long time IT Administrator for mainframes would tell me over and over your only as good as your last viable backup. I am religious about backups and copy's of data, especially with big moves like this.

And I second the notion that most if not any of your users do not fully understand what is going to happen. Add on top that almost all are convinced of the "Clouds" ability to retain your data indefinitely. And you have a recipe for disaster.

And you look like the hero too when / if they need that data.

So get a nice external USB 3.0 HDD and dump the data there and save it.

Authenticate to Azure Account

Add-AzureAccount

Select Azure Subscription

$subscription = (Get-AzureSubscription).SubscriptionName | Out-GridView -Title "Select Azure Subscription" -PassThru
Select-AzureSubscription -SubscriptionName $subscription -Current

Select Azure Storage Account

$storageAccount = Get-AzureStorageAccount | Select Label,Location | Out-GridView -Title "Select Azure Storage Account" -PassThru
Set-AzureSubscription -SubscriptionName $subscription -CurrentStorageAccountName $storageAccount

Select Azure VM

$vm = Get-AzureVM | Select ServiceName | Out-GridView -Title "Select a VM Service Name ..." -PassThru
$vmname = $vm.ServiceName

Select Data Disk to resize

$disk = Get-AzureVM -ServiceName $vmname -Name $vmname | Get-AzureOSDisk | Out-GridView -Title "Select a data disk to resize" -PassThru
$diskName = $disk.DiskName

Stop and Deallocate VM prior to resizing data disk

Stop-AzureVM -ServiceName $vmname -Name $vmname -Force

Specify new Data Disk size – must be larger than current size

do {$size = Read-Host -Prompt "New size in GB"} until ( $size -gt $disk.LogicalDiskSizeInGB )

Resize Data Disk to Larger Size

Update-AzureDisk -Label "$diskName" -DiskName "$diskName" -ResizedSizeInGB $size

Start VM

Start-AzureVM -ServiceName $vmname -Name $vmname

To me if you still can connect to the network through the VM on that box then something with the Virtual Switch / Allow Management to Share option might have been reset. Check those settings and if you still cannot pin it down shut down the VM and then export it to a safe spot and uninstall Hyper-V. Reboot and test the network at that point and report back your findings.

On screen connect the Relay port and all communications on that port are already encrypted the only bit you need to encrypt is the web portal. In order to properly encrypt the web portal you also need to apply an SSL certificate then you should be able to work HTTPS.
What I would do at this moment is reinstall Screen Connect from scratch leaving all the default ports and test it to be sure you can get it working.

Once you are sure you have it working then go about changing the web portal port to 443 / HTTPS leaving the default relay port on 8041. I use this configuration on a few Screen Connect instances and it works well.

Also be sure this box does not have any other web services installed as that can interfere with your ports.

http://help.screenconnect.com/SSL_certificate_installation

http://help.screenconnect.com/Changing_default_ports

$computers = Get-Content -path C:\fso\computers.txt
$user = "aUser"
$password = "MyNewPassword!"
Foreach($computer in $computers)
{
$user = [adsi]"WinNT://$computer/$user,user"
$user.SetPassword($Password)
$user.SetInfo()
}

http://blogs.technet.com/b/heyscriptingguy/archive/2009/03/25/how-can-i-change-the-passwords-of-multiple-local-computer-accounts.aspx

Your best internet troll / hater story and how you dealt with it please?

Woot!

They are marking those meeting requests as tentative automatically
you can turn this Automatic off
File - Options - Mail - Tracking - Uncheck Automatically Process Meeting Requests...

http://www.msoutlook.info/question/do-not-automatically-accept-meeting-as-tentative

Report back your findings

Autocomplete corruption will do this, I bet it is one or two particular email addresses she uses that crashes Outlook. Hence the random nature of this.

Couple things to try:

ID the last user she tries to send to before Outlook crashes and delete that from the Autocomplete list. Type it Anew and see if you can get it to send without crashing

Second would be to clear the whole Autocomplete list and start over fresh but that is usually to disruptive for most users.

http://support.sherweb.com/Faqs/show/how-to-clear-the-outlook-2013-autocomplete-cache

Start Outlook in safe mode and see if it is a plugin
Start - Run - Outlook,exe /safe

Reinstall / Repair Office to fix the mso.dll association and registration.

Report back your findings

Youtube Video

Patching Flash now... Looks like we still need to wait for the Windows Patch