This is not strictly IT but then again it is so I am posting it here. I recently purchased a 2016 Ford and found I needed to update the Sync3 software to use “CarPlay” with my phone. It sounds easy but turned out not to be.
This is a supplement to my “Ford Sync3 v3.0 ‘The installation has run out of space’ Upgrade Failure or IT Guy Buys a Truck” post which discusses my experience getting around this problem. It covers my overall take on the cause of the failure and the syntax of these upgrades.
Sometimes I run into the same incorrect opinions so often I just want to vent and do a post like this. I don’t know if anyone reads this stuff but it is therapy for me. DNS and Active Directory is one of these subjects. So here we go…….
This post discuses the design and placement of DNS for Active Directory. These design imperatives are my own and not Microsoft’s although they are derived from my experiences for twenty years as an Engineer with Active Directory design starting with the NT5 Server Beta in 1998.
Most of you probably know the ‘owner’ of a distribution group displayed in Outlook, Outlook Web App, and Active Directory Users and Computers (ADUC) is the managedBy attribute. What you may not know is that the managedBy attribute is a singled valued attribute. A Distribution Group can have multiple owners so where are the rest? The additional owners are in the multi-valued attribute msExchCoManagedByLink. Accept for the exposure of the managedBy attribute in the GUI, they are all the same. So, who cares? Well, the person exposed as the ‘owner’ is the lucky one who gets all the inquires about … Read more