MigrationKing

As you get started. Make sure your VPC configurations for Inbound and Outbound traffic are correct. If you are using a VPN. Make sure the AWS CIDR and your Local CIDR's are there. The local CIDR range is also your local AWS CIDR, not just your on-premise CIDR block range. 1. In order to establish a connection between your on-premises Active Directory and the AWS Cloud AWS Managed Microsoft Active Directory you must setup both the on-premise server ( LOCALDOMAIN.COM ) and your AWS Domain ( AWSDOMAIN.LOCAL ). 2. Create an AWS EC2 VM that will be joined to your awsdomain.local domain. After you have created the VM. Login to the VM and add the DNS addresses that are listed for AWSDOMAIN.LOCAL in the AWS Directory Service. Do an ipconfig /all to make sure that the DNS IP addresses are correct or nslookup will fail. 3. FYI. You cannot RDP into the AWS DC's for the AWS Managed Microsoft AD. You have to use the Server Manager Tools on the server that is joined to the the AWS

1. Open PowerShell 2. Get-Item WSMan:\localhost\shell\allowremoteshellaccess 3. Open GPEdit and Turn it off. Restart the installation for the File Server and then you can turn it back on. Computer Configuration > Administrative Templates > Windows Components > Windows Remote Shell > Allow Remote Shell Access 4. gpupdate 5. Now run the app again. Thank you XIA!! https://www.centrel-solutions.com/media/xiaconfiguration/adminguideweb/RemoteShellRequests.html

1. Launch Powershell as an Administrator 2. Connect to Office365 via the CLI (You can't do this from the GUI/Browser) https://blog.migrationking.com/2018/12/how-to-connect-powershell-to-office365.html 3. You will need both GUID's to move the old mailbox data that was soft deleted to the new mailbox that was created. NOTE: Background on how this would be applicable. The reason you would have to do this is if you had a local hybrid Active Directory and you did not migrate one mailbox to Office365 or whatever other reason you had a local mailbox stuck on the local exchange DB. You deleted the mailbox in OWA and Microsoft Active Directory Sync wiped out your Office365 account because the local AD account was wiped/deleted when you were fixing the OWA on-premise. You created a new account and when it was replicated to Azure Active Directory and you enabled the Mail license, you now need to copy the data from the old mailbox to the new Mailbox. Either way, you have a new mai

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: https://kb.vmware.com/s/article/1036810 2. Go to the latest VMware Tools of your OS (You don't need to be logged in): https://packages.vmware.com/tools/esx/latest/index.html 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

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.