This post is kinda quick note on growth of ambitious Microsoft public cloud – Azure. In public cloud arena, Amazon Web Services is at No 1 but don’t forget, its the oldest and came in 2006 while Azure in 2010. Microsoft is really growing fast and now its at no. 2 position. The growth rate of Azure is 124 % which is best of all.
Here are few links with result of survey:
With the current growth rate we will see market share of Azure will increase a lot in coming times which is good even for me as I get my bread and butter by training people on it 🙂
That’s all in this small post. See you soon with some other technical stuff. Till then take good care of yourself.
Ok, so once again i’m back after quite some time of lull. Was busy in some of my assignments. So lets begin. The question above is asked in nearly all my AD training. Here is the answer.
The infrastructure master is responsible for updating cross domain group memberships. So, if a user is member of a group which is in another domain, once username is changed you can see name got updated in “member” tab of the group . To perform this operation infrastructure master periodically scans its database for group members from other domains. For each member from a foreign domain that the infrastructure master finds, it compares the name and the security identifier (SID) of the member against a global catalog. If the name or the SID does not match, the local reference is updated with the values in the global catalog. Because a global catalog maintains a partial attribute set of every object from every domain in the forest, infrastructure master always gets updated information. Later infrastructure master will update other domain controllers (DC) in domain.
If the infrastructure master will be placed on a global catalog server, whenever it needs update it will try to find global catalog but in this case both are on same server so infrastructure master will believe that it has all updated information. Consequently, the infrastructure master is not able to determine which cross-domain references have changed and any changes (like in example above where username had changed) won’t replicate to any other DC in domain. Hence, DCs in domain will have not have updated information and for this reason, the infrastructure master should not run on a global catalog server in a forest that contains multiple domains.
However there are few exceptions as under:
- If every domain controller in a domain is a global catalog server, no cross-domain references exist which solves replication issues.
- If a given domain in a multi-domain forest contains only one domain controller, the domain controller will be infrastructure master and global catalog. In this case the replication issue is irrelevant.
- If there is only one domain in forest.
Hope this clarifies your doubts.
Today is 5th September so Happy Teachers Day and being a trainer myself its big day for me atleast for the sake of party we have in office today evening. Lol 🙂
I will see you again with some other technical stuff till then happy reading…