Skip to main content

Posts

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: https://www.microsoft.com/en-us/download/details.aspx?id=28177  ( Install ) https://blog.migrationking.com/2018/12/how-to-connect-powershell-to-office365.html https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-windows?view=azure-cli-latest  ( Install ) 3. Install-Module -Name AzureAD 4. After your connected. Run the following command: PS C:\Windows\system32> Remove-MsolUser -UserPrincipalName rick.james@unitedfederationofplanets.gov Confirm 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. https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/UsersManagementMenuBlade

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: https://www.microsoft.com/en-us/download/details.aspx?id=28177 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: https://docs.microsoft.com/en-us/office365/enterprise/powershell/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

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:  https://www.youtube.com/watch?v=hxIiEjmVFu0 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.

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

1. MS Blog: https://docs.microsoft.com/en-us/office365/enterprise/powershell/connect-to-office-365-powershell 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 https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirectio

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" https://console.aws.amazon.com/storagegateway/

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!

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): https://aws.amazon.com/certification/certified-solutions-architect-associate/ 2. AWS Solutions Architect - Professional Level: https://aws.amazon.com/certification/certified-solutions-architect-profes