Wanted – Apple iMac 27inch 5k

I’ll have a 2015 iMac available after tomorrow.

My mate (lives in Wales) and I decided it best to get it shipped to me, that way I can take full ownership for it, take some decent pics and confirm its condition. I tried to do this long distance last week but it was going to prove difficult so took it off the classifieds.

It’s a Late 2015, 27″ 5K, 3.2GHz i5, 16GB RAM, 1TB Fusion in near perfect condition (to be confirmed), both inner and outer boxes, Magic Keyboard 2, Magic Mouse 2 (rechargeable versions) and PSU. I believe he’s reset it with macOS Mojave.

Subject to inspection, it will then be up for £900 with offers considered.

Shipping would be extra but perhaps you’d consider collection from North Essex.

Keep a look out…

Go to Original Article

A progress report on digital transformation in healthcare – Microsoft Industry Blogs

Two scientists using digital tablet in laboratory

It’s been an incredible year so far for the health industry. We’ve seen the dream and the opportunity of digital transformation and AI start to really take shape in the marketplace.

We saw many examples of this last month at HIMSS 2019, many of our partners and other cloud providers are offering commoditized access to complex healthcare algorithms and models to improve clinical and business outcomes.


These examples show how cloud computing and AI can deliver on the promise of digital transformation. But for health organizations to realize that potential, they have to trust the technology—and their technology partner.

Microsoft has always taken the lead on providing cloud platforms and services that help health organizations protect their data and meet their rigorous security and compliance requirements. Recently, we announced the HIPAA  eligibility and HITRUST certifications of Microsoft Cognitive Services and Office 365.

It’s crucial for health organizations to feel utterly confident not only in their technology partner’s ability to help them safeguard their data and infrastructure, and comply with industry standards, but also in their partner’s commitment to help them digitally transform their way—whatever their needs or objectives are. Our mission is to empower every person and every organization on the planet to achieve more. So whether you’re a health provider, pharmaceutical company, or retailer entering healthcare, your mission is our mission. Our business model is rooted in delivering success rather than disruption for our customers.


Another point of vital importance as we support the movement of healthcare as an industry—and healthcare data specifically—to the cloud is ensuring that we avoid the sins of the past, specifically data silos.

To that end, we jointly announced with other leading cloud providers that we’re committed to healthcare data interoperability among cloud platforms and supporting common data standards like Fast Healthcare Interoperability Resources (FHIR). And I was particularly thrilled to see the excitement in the health industry in reaction to our launch last last month with Azure API for FHIR and our commitment to develop open source FHIR servers. I hope you’ll join the huge movement behind health interoperability fueled by FHIR and encourage your technologists to start actively using the open-source project to bring diverse data sets together—and to build systems that learn from those data sets.

As my colleague, Doug Seven, recently wrote, interoperability helps you bring together data from disparate sources, apply AI to it to gain insights, and then enrich care team and patient tools with those insights to help you achieve your mission. That’s a crucial step in the digital transformation of health.


Another crucial step is supporting health teamwork. With the changing nature of care delivery, health services increasingly require coordination across multiple care settings and health professionals. So we launched a new set of capabilities to our Teams platform that provides workflows for first-line clinical workers such as doctors and nurses that they can use to access patient information and coordinate care in real time.

The end game

Why does all of this matter? To answer that question, I always come back to the quadruple aim, which all of us in the health industry strive for: enhancing both patient and caregivers’ experiences, improving the health of populations, and lowering the costs of healthcare.

Empowering care teams and patients with data insights and tools that help them coordinate care—and that they and your health organization can trust—will help bring about the desired outcomes of the quadruple aim. Not only will this systemic change improve clinical and business outcomes, but also, at an individual level, enhance the day-to-day and digital experiences of clinical workers and patients alike—creating better experiences, better insights, and better care across the delivery system.

Learn more about real-world use cases for AI in the e-book: “Breaking down AI: 10 real applications in healthcare.”

Go to Original Article
Author: Steve Clarke

Top 10 New Features in Windows Server 2019 Failover Clustering

There is a new suite of high availability enhancements available in Windows Server 2019 Failover Clustering. The latest release for Microsoft’s private cloud datacenters focuses on hybrid cloud, application platform, and hyper-converged infrastructure (HCI) solutions. These new clustering features enable many of these scenarios by helping administrators and developers to keep their critical services online. Here are the top ten features in Windows Server 2019 Failover Clustering. Do you agree with our list?

10) Cross-Domain Cluster Migration

In previous versions of Windows Server, Failover Clustering is was not possible to change the domain of a cluster, and mixed-domain clusters were not supported. The cluster had to be destroyed and recreated, which meant that every property or every workload needed to be reconfigured and there would be downtime for a critical application. When I worked on the cluster team, we regularly heard this feature request from customers that were consolidating IT departments or phasing out earlier versions of Windows Server. With Windows Server 2019, cluster admins can move nodes and clusters between Active Directory domains, even supporting mixed-domain clusters.

9) Cluster-Shared Volumes (CSV) Improvements

Clusters Shared Volumes (CSV) disks allow multiple cluster nodes to simultaneous write to a shared disk in a coordinated fashion to avoid corruption. CSV in previous version of Failover Clustering supported Hyper-V virtual machines, SQL databases and Scale-Out File Servers. In Windows Sever 2019 it also supports the Microsoft Distributed Transaction Coordinator (MSDTC) role which allows MSDTC to run on Storage Spaces Direct (S2D) with applications like SQL Server. Additionally, the CSV cache will be enabled by default, which means that highly-virtualized workloads will perform even faster.

8) Azure-Aware Guest Clusters

When a Failover Cluster is created using virtual machines, rather than physical servers, it is called a guest cluster. Guest clusters are used to provide high-availability to an application running inside a VM, such as a virtualized instance of SQL Server. Guest clusters have been supported on private cloud deployments and in the Microsoft Azure public cloud for several releases. In the newest version, it is easier to create a guest cluster in Azure because the additional steps of configuring a load balancer were removed. The enlightened guest cluster will also recognize that it is running in Azure and proactively avoid any downtime due to planned maintenance by automatically moving virtual machines between hosts during patching cycles.

7) USB File Share Witness (FSW) for Quorum

One of the ways which Failover Clustering provides high availability while avoiding corruption is by ensuring that only one instance of a workload is running in a cluster, even when the nodes cannot communicate with each other. This is done by a voting process to determine if a quorum (majority) of cluster nodes can see a consistent view of the state of the cluster.

In a cluster with an even number of nodes (and votes), a network file share can also be given a vote to break a tie which was known as the File Share Witness (FSW). This was not a problem for larger IT departments, but for a small business deploying a 2-node cluster this required that they also had to deploy a file server and configure shares. In Windows Server 2019 Failover Clustering a simple USB device plugged into the network switch can now add this extra vote, eliminating the need to set up any extra IT infrastructure.

6) New File Share Witness (FSW) for Quorum Scenarios

In addition to the aforementioned USB File Share Witness enhancement, this release of failover clustering makes this voting mechanism even more resilient. The FSW can now run on drives without disks and under poor network connections. It also gives the FSW the ability to vote in clusters without domains, mixed-domains, or running in a DMZ without access to a domain controller, further enhancing security.

5) Cluster Sets

A new management concept is introduced into Windows Server 2019 Failover Clustering called cluster sets. This is basically a “cluster of clusters”, allowing VMs to live migrate between clusters. Although 64-node clusters are supported, they are rarely deployed. Instead, organizations that need this type of scale usually deploy numerous 2-node to 8-node clusters, with each cluster dedicated to a workload, department or region. Cluster sets now allow these enterprises to group all of their clusters into a single logical management set. This makes entire clusters resilient to outages by allowing cross-cluster failover and providing easier live migration between clusters for maintenance or load-balancing. A new distributed namespace on a Scale Out File Server is also created and shared across all clusters. This makes it easier to deploy VMs by using a single address which then places that workload on any available host within the cluster set.

4) Cluster-Aware Updating for Storage Spaces Direct (S2D)

One of the most tedious tasks for cluster administrators is applying software or hardware updates. It requires pausing a node to live migrate VMs or move applications to other hosts, patching the host, restarting, then resuming the node so that it can host workloads again. This has to be repeated on every cluster node which becomes very time-consuming. Cluster-Aware Updating (CAU) is a utility which automatically patches all nodes in a cluster. CAU determines which hosts need which updates, then serially patches them while migrating workloads between the operational cluster nodes. In the Windows Server 2019 release, Cluster Aware Updating patches nodes faster by reducing the number of required restarts. It also supports Storage Spaces Direct (S2D) by ensuring that each node has resynchronized its data during the patching process.

3) Improved Security with Certificates and Kerberos

Earlier versions of Windows Server Failover Clustering could use NTLM authentication, which has been vulnerable to security attacks in the past. Clusters no longer use any NTLM authentication, only Kerberos and certificates are supported. All nodes will now communicate with each other via certificate-based authentication to prevent network traffic spoofing.

2) Windows Admin Center (WAC) Integration

Windows Admin Center (WAC), formerly “Project Honolulu”, is a much-anticipated unified management console for small businesses using Windows Server 2019 and earlier versions. It centralizes the deployment, monitoring, and operations of Hyper-V hosts and clusters. Cluster support is currently limited to core operations, so any advanced configuration may require using Failover Cluster Manager for now. WAC lets organizations deploy highly available applications and VMs, manage clusters and workloads, view disks, switches, networks, nodes and run Cluster Aware Updating (CAU).

1) Self-Healing Failover Clusters

More intelligence was built into Failover Clustering in Windows Server 2019 by adding new resiliency features which are hidden to the administrator. These add high availability to the cluster’s communications network so that it can quickly discover and repair infrastructure issues. When a node is unable to communicate with the rest of the cluster, new attempts to automatically repair it are made so the node can rejoin the cluster. If a network becomes unavailable, then detection happens quicker, and the traffic can be rerouted through different networks for additional resiliency. If there is any problem with bringing your cluster back online, make sure that you have already backed up the cluster’s configuration using a cluster-aware provider such as Altaro.

It looks like Failover Clustering will be a key piece of many of the scenarios designed to enable hybrid cloud, application platform and hyper-converged infrastructure (HCI) solutions. Do you agree with the top features or is there something else which you would rather see? Download Windows Server 2019 today to take advantage of these great features or see what else is new in the latest release.

Thanks for Reading!

Go to Original Article
Author: Symon Perriman

What features make up Windows Server 2019 cluster sets?

Underneath the hood of the Windows Server 2019 cluster sets feature are a number of technologies working in concert to boost flexibility of important workloads and make life easier for administrators.

A cluster set is a combination of elements that work together to connect multiple clusters across different locations for less friction during the migration process and better overall VM performance due to enhanced resource sharing. Before testing or adopting Windows Server 2019 cluster sets, learn about the main elements that make up this new clustering arrangement.

Multiple components form the fabric of a cluster set

Member clusters. Each individual cluster is called a member, and a cluster set is a fabric of member clusters. Administrators configure and provision member clusters to run workloads based on VMs and storage technologies, such as Storage Spaces Direct. VMs can move freely among member clusters for tasks, including workload balancing and regular maintenance. Member clusters do not handle management tasks at the greater fabric level.

Management cluster. This cluster is distinct from the member clusters that host virtualized workloads. As the name implies, the purpose of this cluster is to operate the management functionality of the cluster set. When the administrator builds the management cluster, it creates a unified storage namespace that spans the cluster set atop the Infrastructure Scale-Out File Server (SOFS), a new role in Windows Server 2019. A management cluster adds to the overall resiliency to ensure continuous availability and support for cluster sets.

A cluster set is a combination of elements that work together to connect multiple clusters across different locations for less friction during the migration process and better overall VM performance due to enhanced resource sharing.

Cluster Set Namespace SOFS. Storage poses some unique challenges for extended clusters, which require a specialized storage server to deliver flexibility and performance from server message block (SMB) storage resources. A Cluster Set Namespace SOFS gives SMB workloads access to SMB shares hosted on member clusters. The SOFS has almost no impact on storage I/O because each client node caches SMB activity and updates as needed.

Cluster set components. A cluster set consists of a cluster set master (CS-Master) and a cluster set worker (CS-Worker). A CS-Master handles communication among member clusters. Microsoft designed the CS-Master for high availability (HA) in the face of failures in management cluster nodes and member clusters. Each member cluster has a CS-Worker, which interacts with the common CS-Master to assist in certain operations, such as determining the placement of a VM in the cluster.

Fault domains and availability sets. An administrator shapes the fault domains, or the collection of hardware and applications that could fail together, in a Windows Server 2019 cluster set. On the flip side of fault domains are availability sets, which the administrator creates to produce redundancy of clustered workloads across fault domains. This practice keeps VMs distributed on two or more availability sets that are not in the same fault domain to maintain HA.

Go to Original Article

For Sale – 27″ 5K iMac 2017

I have a 2017 27″ 5K for sale which was bought from the Apple refurb store on 11/12/18.

3.8Ghz i5
8GB Radeon Pro 580

Change of circumstances means I’m having to go back to Windows.
Absolute mint, as new condition with the remaining Apple Care until Dec 2019 and tech support until 10/03/19.

I would prefer collection but if you need it posting I will do so on the proviso it is at your own risk and cost.

IMG_0106.JPG IMG_0107.JPG IMG_0109.JPG IMG_0110.JPG

Price and currency: £1750
Delivery: Delivery cost is not included
Payment method: Cash on collection or BT
Location: Chorley, Lancs
Advertised elsewhere?: Not advertised elsewhere
Prefer goods collected?: I prefer the goods to be collected

This message is automatically inserted in all classifieds forum threads.
By replying to this thread you agree to abide by the trading rules detailed here.
Please be advised, all buyers and sellers should satisfy themselves that the other party is genuine by providing the following via private conversation to each other after negotiations are complete and prior to dispatching goods and making payment:

  • Landline telephone number. Make a call to check out the area code and number are correct, too
  • Name and address including postcode
  • Valid e-mail address

DO NOT proceed with a deal until you are completely satisfied with all details being correct. It’s in your best interest to check out these details yourself.

Go to Original Article