Thursday, December 13, 2018

How to Connect to AWS Snowball and Copy Data

1. Order the AWS Snowball from your AWS Account and have it shipped to you.

Note: Good YouTube Video by AWS:

2. Download the AWS Snowball Client

3. Download the Manifest File

Note: (Security Alert!) Protect the location of the file. King of the Kingdom access if someone snatches it or accesses it unauthorized for the workload/data.

4. Make sure the manifest file is in a path you can access easily. If it's on your workstation, it may be a delay. Use a jump server.


Wednesday, December 12, 2018

How to Remove a Failed Move Request for the Current Batch of Exchange 2013 to Office 365

1. MS Blog:

2. Open Powershell as an Administrator and install the AzureAD Powershell Modules on your Windows 10 machine.

3.  Install-Module -Name AzureAD (Doesn't seem to work on W2012 R2 Server)

4. Login with your Office365 Account (You have to be a Global admin). Type in Connect-AzureAD

5. After you type in the password you will get this screen:

6. Connect to Office 365 through PowerShell from the elevated prompt on your local Windows 10 Machine.

PS C:\Windows\system32> $UserCredential = Get-Credential

7. Sign-in to Office 365 with Administrator Account

8. Run this command so that you are connected via PowerShell (no there is no GUI):

PS C:\Windows\system32> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $UserCredential -Authentication Basic -AllowRedirection

9. Turn off the pain in the neck prompts:

PS C:\Windows\system32> Import-PSSession $Session -DisableNameChecking

10. Check your batch that is migrating:

PS C:\Windows\system32> Get-MigrationBatch | fl

11. Get your Move Request (See what's failed)

PS C:\Windows\system32> Get-MoveRequest

12.  Remove the Completed Jobs (Optional):

PS C:\Windows\system32> Get-MoveRequest -movestatus completed | remove-moverequest

13. Delete all of them:

PS C:\Windows\system32> Get-MoveRequest -MoveStatus Failed | Remove-MoveRequest

14. Delete one at a time.

PS C:\Windows\system32> Get-MigrationUser

Kill the failed jobs:                      Final2-12.12.2018              Failed

PS C:\Windows\system32> Remove-MigrationUser

Are you sure you want to perform this action?
Remove the migration user ""?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [?] Help (default is "Y"): A

Reference Blogs:


Monday, December 3, 2018

Default AWS Storage Gateway Password

1. After downloading the AWS Storage Gateway and importing the .OVA file into VMware you have to login after you start the VM.

2. Default login is the following:

Username: admin
Password: password

Note: It is no longer sguser / sgpassword

3. After you have logged in test your networking connectivity to AWS:

4. You will need to change the password inside the AWS Console under "Actions"


Wednesday, November 21, 2018

How to Speed Up VMware Converter 6.2

1. Taking forever to P2V or V2V a server? Disable SSL on VMware converter.

2. Edit "converter-worker.xml" with your favorite editor. Your going to have to save it as another file name because if you attempt to edit the actual file. It will bark "Access Denied" errors.

PATH: c:\programdata\vmware\VMware vCenter Converter Standalone

3. Open the "converter-worker" XML file and edit the section called:

<useSsl>true</useSsl> and change it to <useSsl>false</useSsl>

4. Save the file as converter-worker-bak.xml.

5. Delete the original converter-worker.xml file and then remove the -bak from the one you created.

6. Re-launch VMware Converter and go after that migration!

Tuesday, November 20, 2018

Top 10 IT Certifications 2019

2019 is here already! Good grief! Time is flying. Ok. So here is your Top 10 IT Certifications for 2019. If you are not working in the cloud, seriously...stop playing around and get serious about your career before one of us hungry IT people eat your lunch!

The days of playing guardian over an infrastructure and hiding what can be done in the cloud, in a colocation data center or offsite outside of your company, non-profit or organization are OVER. FUD (Fear, Uncertainty and Doubt) no longer will work to your benefit if your one of these dinosaurs in an organization scared of change. It will happen whether you like it or not.

Drumroll!!! Hands-on IT Certifications where recruiters will blow up your LinkedIn with offers!

1. AWS Solutions Architect - Associate Level (Champion):

2. AWS Solutions Architect - Professional Level:

3. Azure Solutions Architect Expert - ***NEW***NEW***NEW***

4. Certified Ethical Hacker - ***Enterprises and Defense (Globally)***

5. VMware Certified Professional 6.5 - Datacenter Virtualization

6. Cisco CCNA (Cisco Certified Networking Associate)

7. Red Hat Certified Engineer (RHCE) **Always A Hotcake**

8. Nutanix Platform Expert ***Jack of All Trades - Will Not Pass without Vast Experience***

9. Google Cloud Architect

10. Whatever you like!

Innovating Technologies that will drive Technological change:

1. Blockchain and its derivative technologies (e.g. Holochain)

2. AI (Artificial Intelligence) / ML (Machine Learning)

3. Mobile (Android and iPhone) - Full Stack Development


Saturday, November 10, 2018

How to Configure a Default Login Screen for Windows 10 with Group Policy

1. Create a folder called "Logo" under NETLOGON

2. Add the image to the folder

3. Use %logonserver% to identify multiple domain controllers since if you identify one specific DC and it goes down or there is any other problem with a particular DC, user's won't get the login screen image (the policy won't run on login).

Example: \\%logonserver%\netlogon\Logo\w10-lock-screen.jpg

4. The GPO Setting is under Personalization under Computer Configuration


Thursday, November 8, 2018

Migration from Exchange 2013 to Office365 Authentication Error

1. Verify that the Administrative user has the permission for "Application Impersonation" in the Exchange Admin Center.

2. Change all users in your local Active Directory over to the UPN for the verified (publicly resolvable Active Directory Domain). Powershell command:

$LocalUsers = Get-ADUser -Filter {UserPrincipalName -like '*domain.local'} -Properties userPrincipalName -ResultSetSize $null

$LocalUsers | foreach {$newUpn = $_.UserPrincipalName.Replace("domain.local",""); $_ | Set-ADUser -UserPrincipalName $newUpn}

3. Sync your Azure Active Directory Tool (Force the Update)

Start-ADSyncSyncCycle -PolicyType initial

4. Verify that your login with "" is working on

Password: test0!

You call that a password?

This is a password son!!: %&^*(LUIKG/73&^%HVJB)&*(YIU)(&*^UTY8567irtufgykA&*(^RTUFGYOHPI()$%^^#$%TE