Top Posts & Pages
- Azure Stack PoC deployment stops at step 60.140.149 on HP Server
- Azure Stack RTM PoC Deployment stops @ Step 60.120.121 – deploy identity provider
- Once MVP, always part of the MVP community! – Awarded with MVP Reconnect
- Times change … sometimes faster as expected
- My #Azure #ExpressRoute Session from #CDCGermany
A few weeks ago I recieved a mail from IB Remarketing. That ask me to answer some questions. The questions where very exciting and so I answer.
Two days ago I got a tweet that I was named as #8 of 10 most creative IT influencers of today.
It is such an honore for me to be seen in the same row like Ravicanth Changanti and Adam Harris.
If you want to see the other or read more please click here.
Cools things happen. As some of you know I’m a renewed Dell TechCenter Rockstar. Now the TechCenter Team interviewed me and asked my some question about my self and my passions.
To read the interview just click here.
Download the update here.
Issues that are fixed in this update
The PowerShell cmdlets Get-MgmtSvcSubscription, Get-MgmtSvcPlan and Get-MgmtSvcAddOn cannot retrieve a Subscription, a Plan, or AddOn through a specific Subscription, Plan, or AddOn ID, respectively.
Symptoms When you use these PowerShell cmdlets to retrieve any of these three objects, you notice that the command allows only the retrieval operation through the specific name of the objects, that you cannot retrieve base on a specific ID.
Resolution Now the parameter with a corresponding ID can be used to retrieve the corresponding object.
Usage Collector Service loses its configuration after Windows Azure Pack Update 1 is applied.
Symptoms When you deploy Update 1 over an existing deployment by having the Usage Collector Service configured and fully functional, you notice that the Usage Service stops working.
Resolution This issue does not occur in Update 2. The Usage Service configuration is preserved and no manual steps are required.
The Plan Creation Event provides NULL for the Plan Display Name to Services registered to receive this notification.
Symptoms For any Service that is registered to receive notifications, the Plan Display Name is passed as NULL when a Plan Creation event is generated.
Resolution In Update 2, the Display name value is passed instead of NULL.
The Web Application Gallery Service generates a large amount of temp files in its Temp folder.
Symptoms Every time that the WebAppGallery service restarts, it creates a new temp folder. The temp folder stores the cached feeds that contains the Metadata of the available gallery applications and their dependencies and the actual application packages. The service is scheduled to restart every 1,740 minutes. This causes the growing number of temp files over time.
Resolution In Update 2, the Display name value is passed instead of NULL.
Resizing dynamic memory virtual machines through machine profiles causes an error when the new maximum memory exceeds the original maximum memory. Also, changing between static to dynamic or vice versa in the machine profile results in an error.
Symptoms When a tenant user sets the value of the dynamic memory virtual machine to a value that is greater than the original maximum value, an error is generated and the operation fails.
Resolution This process is now possible in Update 2 and no errors are generated.
Active Directory was not enabled for Windows Azure Pack WebSites Resource Provider.
Symptoms Administrators had no way to configure WebSites Clouds to use Active Directory. Tenants have no way of enabling Active Directory Account Management and Authentication for their websites.
Resolution In Update 2, this functionality is available for Administrators to configure and for Tenants to use.
It is difficult to discover how to create Co-Administrators for an existing subscription.
Symptoms Tenant users typically go to “My Account” and “Subscription” drawer and pane, but do not see an option there to create Co-Administrator.
Resolution In this Update, a new link is added to the “My Account” drawer set of options.
Error messages in Administration Site that refer to un-configured services in a Plan do not specify the problems.
Symptoms When you try to update a Plan, such as when you make it public, an error is generated if any of the Resource Providers it contains are not configured. This message does not specify the problem or which Resource Providers are affected.
Resolution In Update 2, the messages are more informative, and the user can take corresponding actions.
Subscription Update Events are provided in the Pending Approval state instead of the Acknowledge state.
Symptoms Billing System receives the Subscription Update Event in the Pending Approval state.
Resolution In Update 2, the Billing System receives the Subscription Update Event in the correct state.
An obscured error is returned when a Tenant creates a database by using a security token whose corresponding password does not meet the SQL Server domain policies.
Symptoms The user receives an unrelated SQL error about a SELECT statement that contains an invalid column.
Resolution In Update 2, the tenant sees the correct error and can resolve it by changing the credential password.
During my daily work in the field I often have to explain how a Failover cluster in the Microsoft world is working. Currently I mostly discribe three kinds of clusters. First is the Clustertyp which is used for DHCP Failover Cluster, like discribed in a former blogpost. The other is a DAG or Database availability group, how it is used in Exchange and Failover Cluster how it works in Scale out Fileserver and Hyper-V Cluster.
Today I want to focus on the Fileserver and Hyper-V Failover Cluster and try to explain it.
At first, you need to know such a failover cluster must have an uneven number of cluster members.
Why do we need an uneven number of cluster member? The reason for is a thing named split brain.
Split-brain is a term in computer jargon, based on an analogy with the medical Split-brain syndrome. It indicates data or availability inconsistencies originating from the maintenance of two separate data sets with overlap in scope, either because of servers in a network design, or a failure condition based on servers not communicating and synchronizing their data to each other. This last case is also commonly referred to as a network partition.
An uneven number of cluster members? But dies this mean I can only have 1,3,5, … etc. servers in my cluster?
Normally yes but hear comes the Magic. The uneven member do not need to be a Server, it could also be a share or LUN. This share is named Cluster Shared Volume (CSV) or cluster witness. Every Server and the cluster witness have the same wight in the cluster.
Now one server catches the witness and becomes the “clustermaster” and has more votes in the cluster. He will give the direction for the other nodes.
What happens if one cluster when the cluster master files? Very easy, together with the cluster master, the cluster shared volume fails too. That means at the end we will have an uneven number of cluster nodes and there won’t be a split brain.
If a cluster member failes, the witness will be disconnected and deaktivated. That will also bring an uneven number of cluster nodes and we won’t run in split brain.
Now you will ask, I have more than two nodes. What will happen if the connection splits the cluster in two halfes? which means it would force the split brain issue again!
The cluster member will notice their numbers on both sides. Than the cluster will go and run on the uneven cluster half.