Our community is talking about the new Dell Technologies. Join the discussion in the Dell EMC Community Network:
This blog was originally written by Navya SM from OS Engineering team in Dell
Windows containers is a concept introduced with Windows server 2016 TP3 on both Core and GUI based OS image. A container looks a lot like a virtual machine (VM)-and is often considered a type of virtualization-but the two are distinctly different. Both host an operating system (OS), provide a local file system, and can be accessed over a network, just like a physical computer. However, a VM provides a full and independent OS, along with virtualized device drivers, memory management, and other components that add to the overhead. A container shares more of the host’s resources and consequently is more lightweight, quicker to deploy, and easier to scale across data centers. In this way, the container can offer a more efficient mechanism for encapsulating an application, while providing the necessary interface to the host system, all of which leads to more effective resource usage and greater portability. More details about the containers can be found at https://msdn.microsoft.com/en-us/virtualization/ windowscontainers/about/about_overview.
Windows Server 2016 actually offers two different types of container run times, each with different degrees of application isolation.
Windows Containers offer isolation through namespace and process isolation, whereas Hyper-V Containers isolate each container via VMs. Windows Containers share a kernel with the container host and all the containers running on the host. In contrast, with Hyper-V Containers the kernel of the container host is not shared with the Hyper-V Containers. The Container Host can be either full OS or Core OS or a Nano edition. Both the types of Containers can be managed using Docker.
Note: For the Container feature to work better all the Microsoft updates should be installed along with the OS.
Windows Containers on Full OS:
3. Configure the firewall on the container host for the docker and configure the docker to listen on both the tcp and pipe using the commands given below.
4. Windows Containers need a base image to be installed. Base OS images are available with both Windows Server Core and Nano Server as the underlying operating system and can be installed using docker pull.
a. docker pull microsoft/windowsservercore or
b. docker pull microsoft/nanoserver
5. The docker command set is used to manage and work with containers. To create a new container and run commands on it we will have to use “Docker run” command and “docker ps” lists the containers that are running.
6. To run commands on the existing container we can use “docker exec <container name> <cmd>”
7. To start or stop a container we can run using “docker start/stop <container ID>”.
8. Hyper-V containers on the other hand needs nested virtualization to be enabled (before installing Hyper-V role) as the Hyper-V host will be a VM and the containers will be the nested VMs on top of it. Below are the steps to create Hyper-V containers
The rest of the steps remain same on the Hyper-V container host
Windows Containers on Nano Server:
Install-Module -Name DockerMsftProvider -Repository PSGallery –Force
Install-Package -Name docker -ProviderName DockerMsftProvider
5. The container host needs base OS image to hold the containers. The Windows Server Core and Nano Server has got the base OS image as the underlying OS. We can pull the base OS images using the docker pull cmd which fetches the ready image for use.
If the hyper-V containers are needed the also get the server core image using
6. We need a remote system to manage docker on Nano server and so we need to configure the following for the same by installing docker on the remote server.
7. Now we can create and connect to the container by using docker commands as same as that of the full Windows server OS
The same can be seen using “docker ps –a” command as shown. We have to start the container using “docker start <container ID>” and can stop the container using “docker stop <container ID>”. To execute a command on a running container “docker exec <container ID> <cmd>”
If the Nano server is installed on a VM, then the Hyper-V role has to be installed to create the Hyper-V container with nested virtualization being enabled but the rest of the steps remain same.
This part is to cover the creation of containers, but to use the containers we have to get the network connections for the same.
Content of this blog is originally written by Shubhrata Priyadarshinee.
This blog provide steps for TPM 2.0 enablement in bios, kernel, TPM-2.0 user space utility and uses of TPM ownership in TPM 2.0 in SLES12 SP2.
It also helps to find out solutions to the below error messages.
Dell PowerEdge have the TPM 2.0 chip built on the motherboard. However, it is not enabled by default. Therefore, we need to enable the TPM in the BIOS.
To enable TPM 2.0 in BIOS:-
Press F2 while system boots -> System setup -> System BIOS -> System Security -> TPM security -> turn ON TPM security if not and Enable TPM hierarchy
Under TPM advanced security do the following
Screenshot showing TPM configuration setup page for 13G dell PowerEdge server.
Screenshot showing TPM advanced configuration page for 13G dell PowerEdge server.
#cat /boot/config-4.4.21-69.1.x86_64 | grep TPM
output will look like this: CONFIG_TCG_TPM=Y
# cat /sys/class/tpm/tpm0/device/description
output of above command will look like this: TPM 2.0 Device
# lsmod | grep -i tpm
Output will look something like this.
TPM 2.0 uses tpm2-0-tss package that provides an open-source TCG software stack (TSS) implementation and tpm2.0-tools package that provides the tpm-2.0 tools based on tpm2.0-tss.
TPM 2.0 does not work with TPM 1.2 trousers package and tpm-tools. So when working with TPM 2.0, install below two packages.
Mount SLES 12SP2 GM DVD or configure SLES12 SP2 repository and install both of the packages, by running below commands.
#zypper install tpm2-0-tss
#zypper install tpm2.0-tools
#systemctl status resourcemgr.service
#systemctl enable resourcemgr.service
#systemctl start resourcemgr.service
#tpm2_takeownership -o new -e new -l new
#tpm2_takeownership -o new1 -e new1 -l new1 -O new -E new -L new
This blog post is originally written by Shubhra Rana and Vinay Patkar from Windows Engineering Team
Cloud security is one of the trending areas due to high adoption rates by small and huge businesses alike. Security of the virtual layer is very important from the customer’s perspective as all the private data is hosted over virtual machines. This paper is aimed at describing the role of TPM 2.0 chip in guaranteeing the best security features to the VMs hosted in a third party environment in collaboration with the Hyper-V Shielded VM security feature introduced by Microsoft.
Refer to the white paper located at Dell TechCenter which provides some useful information for users who plan to use Shielded Virtual Machines on Dell PowerEdge servers with Windows Server 2016 Installed.
Dell EMC has announced an update to the PowerEdge C6320p modular server, introducing support for the Intel® Xeon Phi x200 processor with Intel Omni-Path™ fabric integration (KNL-F). This update is a processor-only change, which means that changes to the PowerEdge C6320p motherboard were not required. New purchases of the PowerEdge C6320p server can be configured with KNL or KNL-F processors. For customers utilizing Omni-Path as a fabric, the KNL-F processor will improve cost and power efficiencies, as it eliminates the need to purchase and power discrete Omni-Path adapters. Figure 1, below, illustrates the conceptual design differences between the KNL and KNL-F solutions.
Late last year, we introduced the Dell EMC PowerEdge C6230p Server, which delivers a high performance processor node based on the Intel Xeon Phi processor (KNL). This exciting server delivers a compute node optimized for HPC workloads, supporting highly parallelized processes with up to 72 out-of-order cores in a compact half-width 1U package. High-speed fabric options include InfiniBand or Omni-Path, ideal for data intensive computational applications, such as life sciences, and weather simulations.
Figure 1: Functional design view of KNL and KNL-F Omni-Path support.
As seen in the figure, the integrated fabric option eliminates the dependency on dual x16 PCIe lanes on the motherboard and allows support for a denser configuration, with two QSFP connectors on a single carrier circuit board. For continued support of both processors, the PowerEdge C6230p server will retain the PCIe signals to the PCIe slots. Inserting the KNL-F processor will disable these signals, and expose a connector supporting two QSFP ports carried on an optional adapter using the same PCIe x16 slot for power.
Additional improvements to the PowerEdge C6320p server include support for 64GB LRDIMMs, bumping memory capacity to 384GB, and support for the LSI 2008 RAID controller via the PCIe x4 mezzanine slot.
Dell EMC offers several HPC solutions optimized for customer usage and priorities. Domain-specific HPC compute solutions from Dell EMC include the following scalable options:
For HPC storage needs, Dell EMC offers two high performance, scalable, and robust options:
The Dell EMC HPC System for Research, an ideal HPC platform for IT administrators serving diverse and expanding user demands, now supports KNL-F, with its improved cost and power efficiencies, eliminating the need to purchase and power discrete Omni-Path adapters.
Dell EMC is the industry leader in HPC computing, and we are committed to delivering increased capabilities and performance in partnership with Intel and other technology leaders in the HPC community. To learn more about Dell EMC HPC solutions and services, visit us online.
Dell EMC World 2017 has officially kicked off and there are a number of activities going on both on the ground, and virtually.
To keep track of the event agenda, visit http://www.dellemcworld.com/agenda.htm for more details and view live streams.
If you want to keep track of what's going on with the Dell EMC Elect, here is the calendar of events they will be participating in.
The podcasts can be listened to at the following links:
itunes podcast link
If you are there in person or following online, you'll know where they will be:
Over the last few week since the Azure Stack Airlift for EAI customers, we had the opportunity to listen to Service Providers from around the world and discuss our platform for Azure Stack, including our solutions for Data protection and Security. While Azure stack cannot come any sooner, there was universal recognition that we need not wait. With the single node Dell EMC developer edition, you have the opportunity to get started today.
With a continuous stream of updates to both the experience as well as Azure Services delivered since TP2, there is an opportunity to get started today. The single node enables you to setup evaluation units:1. As a MSP/SP, you can start to develop your Azure Stack business model (packaging and pricing). Build and evaluate plans and offers. At Dell EMC, we offer a flexible consumption model for the infrastructure to enhance the Microsoft Azure Stack business model.2. Evaluate PaaS with Azure App Service, Azure functions and eventually Blockchain and more3. How to extend Azure on premises to augment your Azure Strategya. Look at edge and disconnected solutions to address a growing customer needb. Modernize applications and start to develop on-prem4. Integrate into your infrastructure with Azure AD and ADFS scenarios This means, developers or evaluators can immediately access their own Azure Stack portal, access pre-created plans and offers, start to develop use cases around modernizing applications, exploring the consistency with Azure and how to architect and develop hybrid apps.
And yes, you can do all this on a single node for less that $10,000 and you are not paying for any of the Azure Services consumed on this box.
Below is what our single node edition for developers and evaluators :
Additionally, talk to our Customer Solution Centers to schedule a demo. Reach us at email@example.com What is coming next? We will continue to work with our early adopters as well as early customers to ensure you are ready on Day 1 to adopt and derive value from your implementation for Azure Stack. The developer edition is a key step in that direction and will get a GA code update and continue to be available beyond GA. We will also continue to engage you through our Dell Customer Solution Centers and partnering with Microsoft Technology Centers to deliver PoCs, webinars and workshops to keep you educated and updated on Azure Stack. Also, for any questions, please email firstname.lastname@example.org for more information.
Next Steps:Get the Dell EMC developer node (PE R630): mailto:email@example.comGet TP3 code: https://azure.microsoft.com/en-us/overview/azure-stack/try/Azure Stack documentation: https://docs.microsoft.com/en-us/azure/azure-stack/
Other useful linksTP3 Blog: https://azure.microsoft.com/en-us/blog/hybrid-application-innovation-with-azure-and-azure-stack/Business model: https://channel9.msdn.com/Blogs/azurestack/Azure-Stack-extends-cloud-economic-model-on-premises-with-pay-as-you-use-pricing
Updated monthly, this publication provides you with new and recently revised information and is organized in the following categories; Documentation, Notifications, Patches, Product Life Cycle, Release, Knowledge Base Articles.
Subscribe to the RSS (Use IE only)
228613 - Mandatory Hotfix 654037 for 8.6 MR3 Mac Connector
This mandatory hotfix addresses the following issues: Picture is pasted instead of copied text when copying from Excel 2016 to Mac version of...
Created: April 21, 2017
228607 - Mandatory Hotfix 654123 for 8.6 MR3 Linux Connector
This mandatory hotfix addresses the following issues: It is impossible to launch any application with non-English user name if Cred SSP is...
228830 - Mandatory Hotfix 654125 for 8.6 MR3 Android Connector
Created: April 26, 2017
228414 - Quest Metaprofile Server (pnmfps service) not listening on any port 5206
After setting the Storage Servers in User Profile Management | Properties, Profiles are not stored. The other symptoms are: No file...
Created: April 18, 2017
228827 - vWorkspace 8.6.x patch installers
When trying to upgrade vWorkspace 8.6 to mr1, mr2 or mr3 running the setup in the full installer package does not appear to upgrade the version...
227781 - How to set the minimum memory with Hyper-V
The Hyper-V role in Windows 2012 has an improved Dynamic memory feature that adds a property called Minimum Memory. This allows you to specify a...
Revised: April 4, 2017
224308 - Hyper-V host is showing offline and is unable to be initialized.
Hyper-V host fails to initialize and is showing offline. The following message may be seen in the vWorkspace console: "Remote computer could not...
Revised: April 14, 2017
228413 - PNTools versions are detected as outdated after upgrade.
vWorkspace Monitoring and Diagnostics detected PNTools versions to be outdated after an upgrade. Alarm was triggered and you could be...
Revised: April 21, 2017
73446 - How To: Improve Performance to a Virtual Desktop VDI Session
When connecting to a VDI over a slow connection users report that the performance on the VDI is degraded, or sessions are disconnected often.
Revised: April 26, 2017
63874 - The Remote Computer requires Network level authentication error.
When trying to connect to a machine, an error occurs. The Remote Computer requires Network level authentication error.
Revised: April 27, 2017
Revised: April 28, 2017
Product Life Cycle -vWorkspace
Revised: April 2017
Adopting a hybrid cloud strategy as a means to achieving digital transformation can be a very difficult endeavor, often IT and the organization they support have processes, procedures, personnel and tools that are not aligned for optimal cloud brokerage and consumption.
The most common hurdles to overcome are complexity of disaggregate apps and tools, legacy IT vs cloud competency, confidence that anytime, anywhere, always-on availability is achievable and that the cost of acquisition is affordable.
Enterprise IT organizations are expected to deliver a consistent end-user experience but most public and private cloud implementations are not reflective of one another making all phases of the life-cycle; acquisition, deployment, operation, maintenance more of a kludge, than a repeatable, predictable, positive experience.
Today we announced the new Dell EMC Cloud for Microsoft Azure Stack, a platform specifically intended to mitigate the risks associated with hybrid cloud adoption so customers can realize their vision for hybrid cloud success and digital transformation.
The platform is quite an achievement, as it takes what would normally be a very complicated planning, design, acquisition and deployment experience and makes it genuinely simple by providing a turn-key, IaaS ready platform the day of deployment with PaaS capabilities in its future as development continues.
The platform is built on a proven hyper-converged foundation using the Dell EMC PowerEdge R730XD and Dell EMC S-Series switches as a backbone but more importantly the platform has many years of customer inspired design, engineering, testing and update process rigor behind it. Our history of partnership with Microsoft when it comes to cloud and advanced virtualization solutions is extensive and unique. Dell EMC is the only Microsoft Azure Stack partner to collaboratively engineer cloud solutions: CPS-Premium Private Cloud, Private Cloud for Microsoft Fast Track, Hybrid Cloud System for Microsoft CPS-Standard, Ready-nodes and now Dell EMC Cloud for Microsoft Azure Stack.
With Microsoft Azure Stack the APIs, tools, apps and services that are behind the firewall are consistent with, reflective of, and interact seamlessly with the customer’s Azure public cloud experience. This means that the customer cloud journey no longer needs to end in disappointment due to unforeseen deployment and life-cycle operation complexity, or project cost over-runs. The Dell EMC Cloud for Microsoft Azure Stack delivers on the promise of a predictable, repeatable, Azure consistent experience whether accessing and writing to Azure public resources or those behind the datacenter firewall.
For Microsoft Azure customers who want to begin their hybrid cloud journey today using Dell EMC Cloud for Microsoft Azure Stack the place to start is with the “single-node” PowerEdge R630 for development and testing. Dell EMC began making it available in March and will continue to support it over the life of the platform. Customers can use “single-node” to test and develop on generally available software, and gain insight into the administration and tenant experience. They can also explore what DevOps and infrastructure-as-code may mean to them as they discover how Azure Resource Manager templates work. Developers can play with PowerShell and Visual studio on validated hardware without disrupting production environments, and at minimal acquisition cost. Customers can download the TP3 software from Microsoft from their website here and find instructions here.
With the Dell EMC Cloud for Microsoft Azure Stack there is no need to learn new tools to support new services implementations or to administrate, automate, and orchestrate lifecycle maintenance and operations tasks. Once a customer understands how to use the tools within Azure public cloud, they know how to use Azure Stack. Dell EMC provides add-on services for application backup, recovery, archiving and security, and enterprise level single-contact support.
No more kludge, no more complexity.
Dell EMC Senior VP, Peter Cutts discusses the announcement and what it means for customers here.
For more information about the Dell EMC Hybrid Cloud for Microsoft Azure Stack contact your Dell EMC sales contact or simply inquire by emailing firstname.lastname@example.org
This is a mandatory hotfix for:
The following is a list of issues resolved in this release.
It is impossible to launch any application with non-English user name if Cred SSP is enabled for the farm properties
This hotfix is available for download at:
Just a friendly reminder that Wyse Thin Clients are not intended to be used as PCs i.e with their Write Filter turned off permanently (This excludes routine maintenance where WF is turned off for Windows Updates or application installation).
Please be advised that Dell Wyse Windows Embedded Thin Clients are intended to be used as thin clients only and not as personal computers. Dell Wyse is not responsible for, and will not, warrant, support, repair or replace any thin client device or component that is not used for its intended purpose. As an example, and without limitation, any operation of a Wyse Windows Embedded Thin Client with the write filter turned off during regular use (except as required for image upgrades, applying security patches, registry changes and application installation) is beyond the scope of the intended purpose, will prematurely wear out your Flash/SSD storage and will invalidate the thin client product warranty. In addition, enabling the Windows Page File is beyond the scope of the intended purpose and will invalidate the thin client product warranty.