Over the years I have had the opportunity to work on quite a few Office 365 migrations and setups. This post covers somethings that I have found useful to ensuring a successful migration and making day 2 operations easier.
Picking the Name
So the tenant name (contoso.onmicrosoft.com) does’t show up in too many places but it will be visible to some users. Mainly when you are looking at Team sites or SharePoint, but also in the aliases for hybrid setups. Bottom line you won’t have to type it in all the time but you probably don’t want to pick something like (myfavpet.onmicrosoft.com) because someone will eventually ask and you can’t change it, ever. This tool will let you quickly check the available tenant names without having to go through the setup processes, you can send this over to the people that care and get them to pick the name for you. As you can see myfavpet is available and ready for your new migration 🙂
VMware announces intent to acquire Bitnami, a leader in application packaging for multi-cloud environments. Find out how #Bitnami will help #VMware accelerate our #multi-cloud and #Kubernetes offerings and efforts!
Organizations today are on a multi-cloud journey, and VMware is committed to investing in solutions that address the core needs of our customers. In that spirit, VMware is announcing its intent to acquire Bitnami, a leader in application packaging solutions providing the largest catalog of click-to-deploy applications and development stacks for major cloud and Kubernetes The post VMware to Acquire Bitnami appeared first on VMware Cloud Community.
While having an admin account for your primary mailbox isn’t a great idea for a lot of good reasons, it is sometimes helpful to have for testing.
If you happened to get your admin account by copying the default admin account in AD or maybe you copied another admin you may notice that you mailbox doesn’t work on your phone. I’ve seen people freak out during maintenance windows “testing” with their admin account and finding that mobile access isn’t working. There are two things that you can do to fix this.
Stop coming up with the test during the maintenance window. I have had good experience putting them in the change request so that everyone is on the same page for how success is measured. This also means that if the change doesn’t work it was because X failed not because YOU failed. Perception can go for a lot and change windows can have a lot of moving parts.
The issue with the mailbox/account is probably that inheritance is not enabled on the account. This is not enabled by default for the admin account. Follow the steps below to enable it.
Enable inheritance on a user account
Open Active Directory Users and Computer
Enable Advanced Features in the View menu
Open the properties of the affected admin account
Select the Security tab and click the advanced button
Now we get to see the magic button!!! Click enable
You may get a warning if there are going to be a lot of additional ACLs applied. Not to worry its only our admin account 🙂 you didn’t tie it to anything else did you?
Click apply or OK to save everything and close out
For this I forced an AD sync to make sure that my change went out to all the servers, is was successful
It took a few minutes for my phone to update but it works now
Recently I needed to configure LACP on a distributed switch that was already setup. With about 20 PortGroups (VLANs) already configured, the idea of clicking through each one to update the uplinks to the LAG from the standard uplinks sounded really boring.
I found this post by Ben Liebowitz on automating the creation of new port groups and stole the peices that I needed to just update the PortGroup active uplinks. So here it is.
Afterwards, I realised that it also updated the the active uplinks on the uplink port group. This change is not visible in the GUI and I’m not sure what the impact of this is but I figured that reverting it back was the best plan. So here is the command for that, if you were going to roll this out multiple times it would probably be a good idea to filter the above command based on the name of the uplink portgroup to avoid this change.
Recently I ran into an issue where HA triggered on a cluster but failed. This generated an alert on several hundred VMs. Hating to click each one to reset the alarm that wasn’t clearing I found the following solution.
PowerCLI to vCenter
Run the following command to disable the alarm
Get-AlarmDefinition "vSphere HA virtual machine failover failed" |Set-AlarmDefinition -Enabled:$false
The alarm should clear almost instantly for all VMs
Re-enable the alarm
Get-AlarmDefinition "vSphere HA virtual machine failover failed" |Set-AlarmDefinition -Enabled:$true