Wednesday, January 16, 2019

VMware Tools ISO Does Not Exist

1. You attempt to Install VMware Tools and you get the following error:

The required VMware Tools ISO image does not exist or is inaccessible. vix error code = 21001 Unable to install VMware Tools. An error occurred while trayin got access image file "/user'/lib/vmware/isoimages/windows.iso" needed to install VMware Tools: 2 (no such file or directory). Please refer the product documentation or KB article 2129825 for details....blah blah blah you get the point.

First...that KB article is wrong. It's 1036810:

2. Go to the latest VMware Tools of your OS (You don't need to be logged in):

3. Download the ISO and then WinSCP the file or whatever method you want to use to copy the file to /usr/lib/vmware/isoimages/

The quick and easy way is to just mount it and then install the VMware Tools. If you want to get gritty! Follow on!

4. If you don't know how to copy files to Linux. Use Linux Academy. It's way too much to try to type here: 

5. Access the VCSA UI from the browser with port: 5480 (e.g.

6. Enable SSH Login and Bash Shell under Access on the Appliance.

7. VCSA 6.7U1 doesn't not have "isoimages" under the /usr/lib/vmware/ path so you need to create it. 

8. mkdir isoimages && cd isoimages

9. If you have external internet connectivity. Grap the file with wget


mv VMware-tools-windows-10.3.5-10430147.iso (space and then type) windows.iso


Tuesday, January 15, 2019

How to Rename a Windows 2019 Server from the Command Line

1. From VMware (CTRL+ALT+Insert)

2. Check hostname post installation

3. hostname

4. netdom renamecomputer WIN-BLAHBLAH /newname:WS2016-BLAH /reboot 0

6. Y

7. Reboot

8. Login (CTRL+ALT+Insert)

9. Don't be scared little buddy. It's just the command line. =) The Windows Server CLI experience is not for newbies. Use the Desktop Experience if you find it extremely difficult and PowerShell very hard. It's not like Linux.

10. typing the command sconfig will take you into the base configurations of the server. Remember. Windows Server 2016 does not allow you to just turn on Desktop Experience. You have to clean install a new OS.

11. You need to run sconfig in order to enable RDP, etc.


Thursday, December 27, 2018

How to Delete an AzureAD object that Won't Delete

1. Ok. You deleted a user from your on-premise Active Directory and it's still showing that bugger in Azure Active Directory. Your Google Kung-Fu is strong, but you can't find the dang commands. Here is what worked for me.

2. Get Connected via Powershell to Office365 / AzureAD: (Install) (Install)

3. Install-Module -Name AzureAD

4. After your connected. Run the following command:

PS C:\Windows\system32> Remove-MsolUser -UserPrincipalName

Continue with this operation?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y

5. Check your AzureAD portal to make sure it's gone.

6. Freaking dance man!

Reference Links:

Unhelpful Real World Training Junk:

How to Connect Powershell to Office365

1. Install the Microsoft Online Services Sign-In Assistant for IT Professionals RTW MSI application. You cannot perform the next steps without it being installed:

2. Open Powershell and install the Install-Module MSOnline module. (Note: Use the Administrator elevated PS)

3. URL for Powershell commands to Manage User accounts and licenses with Office 365 PowerShell:

4. PS Command to Connect to O365: Connect-MsolService -Credential $credential

5. You will be prompted to log in with your O365 administrator account (you cannot use a regular account).

6. Run commands without headaches if your environment permits it: Set-ExecutionPolicy Unrestricted -Force

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


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"