VMware and SAP Are Changing The Mobile Landscape

This post was originally published on this site

VMware and SAP Are Changing The Mobile Landscape |VMware Communities

Skip navigation

Error: You don’t have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page.

0 Replies Latest reply on Aug 28, 2017 9:31 PM by nicolekristen

The portable period has expanded the interest for additionally enhances to email designs inside associations. Associations need to give further developed portable applications to better suit the advancing procedures of their end clients, the more vigorous the better, and the better the substance conveyance, the more viable the administration. Versatile applications keep on offering associations the capacity to reclassify business process and the end client’s understanding. By building, conveying, overseeing and breaking down portable applications, they intend to have a major effect to their end client’s work process administration. VMware and SAP seem to be the ones to improve this administration later on.

VMware is the main SAP Partner to coordinate the AirWatch undertaking Mobility Management stage with Sap Mobile Secure Mobile App Management. To improve the Mobile application conveyance for end clients through the mix of Mobile Place (from the SAP Mobile Secure portfolio) and AirWatch by VMware arrangements. VMware will empower clients to use the Airwatch by VMware Platform with SAP portable applications fabricated utilizing SAP Mobile Platform. VMware are hope to utilize SAP SD Training Mobile Secure Portfolio and the AirWatch Enterprise Mobile Management (TM) (EMM) stage to convey applications, they have collaborated with SAP to make a standard administration. The joint effort is required to give an overall more upgraded understanding for all applications utilized for working crosswise over corporate possessed, line-of-business and bring your own gadget (BYOD) situations.

Breakthrough Visibility

This post was originally published on this site

VMware Skyline™ is radically transforming customer support

By: Dale Ferrario

Customers like you that run business-critical operations on VMware environments need an infrastructure that’s always-on and optimized for peak performance. You expect fast, environment-specific remediation recommendations, and proactive analytics that identify problems before they occur.

We’re addressing these needs with VMware Skyline™: an innovative support technology, developed entirely by VMware Engineering, that provides VMware technical support engineers with extreme visibility into your environment.

Imagine if we knew your environment as well as you do. We could tell you – in advance – of a problem you’d have in the future. And then we gave you proactive, prescriptive, and predictive recommendations to fix the issue. And if you do need to call us with a problem, we have the visibility into your environment that lets us quickly diagnose your situation without a lot of effort and hours on your part.

Here’s how it works. Customers with active support subscriptions install the VMware Skyline Collector, a standalone appliance that automatically and securely collects product usage data such as configuration, feature, and performance data.

It then listens for changes, events and patterns and analyzes the information using a robust rules and machine learning engine. The rules engine is where an ever-growing library of support intelligence, product knowledge, and logic is stored to analyze inbound streams of product information.

It will alert when a customer has deviated from a VMware Validated Design or needs to align to a best practice configurations or patch level. Issues identified are fed into the analytics library – consisting of hundreds of detection rules – to allow us to solve the issue for multiple customers.

And you can rest assured knowing that we take privacy and security seriously – VMware Skyline has a robust privacy program. Customer data is transferred to VMware over an encrypted channel and is stored in a secure VMware repository in the US, operated by VMware.

Then the VMware Technical Support Engineer takes the analyzed, environment-specific data to provide prescriptive recommendations back to you to improve your environment’s reliability and stability.

Aligned to Global Services offerings, VMware Skyline is initially available for Premier Support customers with Production Support customer availability coming next year. Today VMware Skyline provides increased visibility for VMware vSphere and VMware NSX environments.  Additional products will be added over time.

With minimal administration, a rigorous privacy and security policy, and transformational value, VMware Skyline is a game changer for your support experience with VMware.

Sign up today to join our Managed Access program at   https://www.vmware.com/support/services/skyline.html

Windows PowerShell 2.0 Deprecation

This post was originally published on this site

We recently announced that Windows PowerShell 2.0 is being deprecated in the Windows 10 Fall Creators Update. Deprecation is a process whereby technologies or applications are marked as legacy, signalling to users that they may be removed in the future, and that should move away from them and towards newer alternatives.

We do not currently have a timeline to remove Windows PowerShell 2.0, but as we continue to evaluate its usage in the PowerShell ecosystem, we will be working to remove it in a future release. When this decision is made, we will give plenty of notice via official Windows deprecation channels (like the above support link), as well as this blog. However, at this time, we recognize that it’s usage is still prevalent, and we won’t make this decision without giving ample time for users to migrate away from it.

I’m a PowerShell expert, just give me the quick version

If you’re very familiar with the PowerShell ecosystem, this is a quick guide for moving off of Windows PowerShell 2.0. If not, read on through the rest of the blog for a better explanation of the technical details.

If you’re running any scripts using powershell -version 2, you should use a later version of PowerShell (like Windows PowerShell 5.1 or PowerShell Core 6.0).

If you’re hosting any PowerShell assemblies (e.g. System.Management.Automation.dll) in a .NET CLR2 (i.e. .NET Framework 2.0 – 3.5) application, you should work to move your application to CLR4 (i.e. .NET Framework 4.6+) or .NET Core.

What is Windows PowerShell 2.0?

Windows PowerShell 2.0 first shipped as the version of Windows PowerShell built into Windows 7 (where it was not an optional feature). It was also shipped, via the Windows Management Framework (WMF) to older versions of Windows, including:

  • Windows Server 2008
  • Windows Vista
  • Windows Server 2003
  • Windows XP

When Windows PowerShell 3.0 was released as part of Windows 8, Server 2008 R2, and WMF 3.0, Windows PowerShell moved to a newer version of the .NET Framework (CLR4) that was not compatible older applications. In order to maintain backwards compatibility with these older applications, we kept Windows PowerShell 2.0 as an optional, side-by-side component in later versions of Windows and Windows Server. You could take advantage of this optional component by using powershell -version 2 to start the older version of the engine, or by continuing to use a PowerShell assembly in a .NET CLR2 application. Note: specifying any version higher than 2 with -version (e.g. 3, 4, or 5) will load the latest, non-2.0 version of Windows PowerShell on the machine, regardless of the number specified.

Why is it being deprecated?

Windows PowerShell 5.x has some great new features that enhance security including enhanced transcription logging and AMSI protection.

As PowerShell Core 6.0 enters the marketplace, we’d like to reduce the complexity of the PowerShell ecosystem. Removing an outdated version of .NET from the equation makes development easier for cmdlet and script authors by focusing on the .NET Standard ecosystem that includes only .NET Framework 4.6+ and .NET Core 2.0.

What does this mean for me?

You can check whether Windows PowerShell 2.0 is installed by running the following (as an administrator).

On Windows 7/8.1/10, the following will return a State as either Enabled or Disabled:

Get-WindowsOptionalFeature -Online -FeatureName MicrosoftWindowsPowerShellV2

On Windows Server, the following will return an InstallState of either Installed or Removed:

Get-WindowsFeature PowerShell-V2

If Windows PowerShell 2.0 is not installed on your machine(s) and everything is working fine, you probably don’t need to worry about deprecation.

If Windows PowerShell 2.0 is installed, there are a few cases where you might be using it:

Scripting with Windows PowerShell 2.0

  • You’re running powershell.exe -version 2 (often shortened to powershell -v 2) when running scripts or as a shell. This is the easiest to mitigate: simply try running your scripts without the -version 2. If it works fine, stop using -version 2.
  • You’re running a PowerShell script that calls #requires -version 2 at the top. If Windows PowerShell 2.0 is installed, this will automatically start and run the script with it regardless of where the script is executed. (Note: if Windows PowerShell 2.0 is not installed, this line is ignored and the script is executed with whatever version of Windows PowerShell is installed.)

Hosting Windows PowerShell 2.0 in a .NET 2.0/3.5 Application

If you’ve developed an application with .NET 2.0/3.5 (aka CLR2), and you’re hosting a PowerShell assembly like System.Management.Automation.dll, then you’re using the Windows PowerShell 2.0 version of those assemblies. If this is the case, you should work to migrate your application to .NET 4.6+ (aka CLR4) using reference assmeblies from Windows PowerShell 3.0 or later. That way, you’ll be using the latest version of the Windows PowerShell assemblies available on the box. (Note: this may require that your Windows 7 or Server 2008 R2 users install .NET 4.6+ and/or WMF 3.0 or higher.)

Installation Checks for Windows PowerShell 2.0

You may also have a legacy application that checks for the existence of Windows PowerShell on the box via the registry, particularly for the existence of HKLM:SoftwareMicrosoftWindowsPowerShell1PowerShellEngine. As long as your application only targets supported versions of Windows and Windows Server (7/8.1/10 and Server 2008R2/2012/2012R2/2016), you can remove this validation altogether.

If not, you should instead check for the existence of the file %systemroot%system32WindowsPowerShellv1.0powershell.exe. If your installer absolutely requires a registry-based validations, you should first check for HKLM:SoftwareMicrosoftWindowsPowerShell3PowerShellEngine (note the 3) before falling back to HKLM:SoftwareMicrosoftWindowsPowerShell1PowerShellEngine.

Using a Microsoft Application Leveraging Windows PowerShell 2.0

There are a number of first-party Microsoft applications that continue to use Windows PowerShell 2.0 under the hood, including some System Center applications, some versions of SQL Server, some versions of Exchange, and others. We will be working with these teams over the coming months to migrate them off of Windows PowerShell 2.0. In the meantime, Windows PowerShell 2.0 will remain a part of Windows 10 and Windows Server 2016, and we have no plans to remove it until those dependencies are mitigated.

That’s it!

In summary, the deprecation of Windows PowerShell 2.0 doesn’t mean that it’s being removed yet, but you should work to move off of it, as we may decide to remove it in a future release. When we do have more concrete plans to remove it, we’ll give fair warning before taking it out. In the meantime, do your best to migrate away from it, using the above as a guide.

Joey Aiello
Program Manager, PowerShell

EUC at VMworld 2017 U.S. Checklist: 10 Things to Know Before You Go

This post was originally published on this site
Ashley Speagle

Author: Ashley Speagle

Ashley is a content marketing specialist for VMware.

Share This Post On

What will Pat announce next on stage at VMworld? What’s in store for Sumit and Shawn’s new end-user-computing (EUC) Showcase Keynote? (Hint: This demo-packed keynote deserves a space on your schedule.)

Before we get into the major news, here’s what you, our Vegas-bound mobility pros, need to know before you go.

1. First things first. Pick up your badge.

Bring your photo ID to pick up your conference badge at the VMworld registration desk, on Level 1 of the South Convention Center, during these hours:

  • Sunday, 7 a.m.–7:30 p.m.
  • Monday, 7 a.m.–6 p.m.
  • Tuesday, 7 a.m.–6 p.m.
  • Wednesday, 7 a.m.–7 p.m.
  • Thursday, 8 a.m.–2 p.m.

You can also visit self-serve kiosks in Bayside C, Level 1, and we’re also offering Express Check-In QR codes to move things along. Just check the VMworld mobile app for yours! (Download the VMworld 2017 U.S. app here.)

2. First time? Start here.

There’s a lot going on at VMworld. So Sunday at 4 p.m., we’re offering an hour-long info session just for first-time attendees at the Mandalay Bay Convention Center. Add the New V Welcome Session to your schedule via the Content Catalog.

3. Trust us, everyone will be talking about these EUC sessions.

These are the biggies—add to your schedule accordingly:

Be one of the first 500 attendees at our keynote to receive a free anniversary boxed edition of VMware Fusion and to be entered into a raffle to win a Samsung Chromebook. Last, but not least, score your special EUC button at these spotlight sessions!

4. We’re throwing these events just for you!

Outside of the Customer Appreciation Party, we’re hosting more intimate events just for EUC-minded attendees. Tuesday, following the VMworld Hall Crawl, we’re throwing a huge EUC Networking Reception, sponsored by Google, 6–9 p.m. at the Libertine Social at Mandalay Bay.


RSVP for the EUC Networking Reception

5. Want to make waves in your industry? Sign up here.

VMworld 2017 offers four half-day industry workshops on Sunday, several industry-focused breakout sessions and an entire demo showcase of industry solutions.

6. Meet us at the Digital Workspace Lounge.

We’re offering a dedicated lounge area, theater and meeting space directly behind the registration area (in the VMvillage) where you can expand on what you’ve learned so far. Ask questions in group discussions, and meet with our EUC experts to learn more about the digital workspace.

7. Discover new solutions at the Mobility Zone.

This dedicated space in the Solutions Exchange features solutions that integrate with and complement your EUC investments, from rugged device partners to members of the VMware Mobile Security Alliance. Click here for a snapshot of who will be there and booth numbers.

“And if you’re on the ground in Vegas, be sure to stop by the Mobility Zone, which is an amazing new experience at VMworld—one you won’t want to miss. We’ve packed more than ever into this year’s event.”
—VMware EUC VP of Product Marketing Dave Grant

The entire Solutions Exchange includes more than 220 companies, including EUC partners like Dell, Google, Intel and more.

8. Learn for free at Hands-on Labs.

Choose your own adventure: self-paced labs or expert-led workshops in the South Pacific Ballroom. You can take self-paced labs anytime and as many times as you like—each is 15–60 minutes. At expert-led workshops, on the other hand, you can receive additional instruction and group interaction.

You don’t need to schedule EUC self-paced labs ahead of time—these are offered on a first-come, first-serve basis. Expert-led workshops do require advanced sign-up, and you need to show up early—at least 5 minutes.

“When it comes to education, one place I always tell folks to check out is our Hands-On Labs, where attendees unleash their inner mad scientist. Here you can roll up your sleeves and see for yourself the latest and greatest from VMware.”
—VMware CEO Pat Gelsinger

VMworld2017_training_certification9. Remember, you get special discounts on training and certification!

When you take a certification exam on site, you get 50% off the price, and on-demand courses for AirWatch and Horizon are 25% off. Plus, VMworld offers unique, two-day training led by instructors Aug. 25–26, including an accelerated AirWatch bootcamp and a Horizon 7 seminar. Click here for the special offers!

10. Grow at Partner Exchange @ VMworld 2017 U.S.

Sunday is entirely devoted to VMware partners, and we highly recommend this Business Growth Keynote from Sumit and Business Futurist Greg Verdino on embracing digital transformation. Plus, attend for a chance to win a Samsung Chromebook Elite!


This is your last chance to register before rates increase again! Keep in mind that VMworld is expected to be the biggest EUC event of the year, as Dave Grant told VMware Radius:

“There are multiple vendor conferences throughout the year, but they all focus on individual vendor stacks, creating cumbersome silos of solutions for IT professionals to manage. VMworld U.S. and Europe will be the only industry events this year that focus on end-user computing in the enterprise, helping to eliminate silos to transform the management and end-user experience.”

EUC mobility virtualization VMworld 2017

Here’s more to plan your trip to VMworld 2017 U.S.:

Subscribe to the right to follow VMworld news on the VMware EUC Blog, and follow us @WorkspaceONE, @VMwareHorizon and @AirWatch for updates.

How to attract digital talent at work?

This post was originally published on this site

August 24, 2017

How to attract digital talent at work?

The increasing advances in technology have allowed remote and flexible working to be more available in businesses than ever before. Indeed, graduates entering into the world of work have heightened expectations when it comes to working lifestyles, and rightly so.

Their experience with more advanced technology throughout their time in education has created a demand for various tools and technologies they need to do their jobs in the most flexible way.

With one in ten millennials viewing flexible working as the most important factor in choosing a new job, we want to find out how these demands compare against more traditional benefits and whether companies are achieving the standards that are needed to attract a new breed of workers?

  • What are the most important benefits to your working life when looking to apply to a new company?
  • What are your biggest frustrations at work?
  • Would you leave your current employer to go to another company if they offered better technology for mobile working?

IT Teams Need To Finally Implement Self-Service Automation

This post was originally published on this site

Seven things, including Self-Service Automation, that IT teams must do to retain relevance with end users.

I was talking with an industry analyst (think Gartner, Forrester, IDC) the other day around a broad range of trends impacting IT. Somehow we got onto a discussion around the issue of IT teams losing relevance with their line of business customers. I can’t recall the conversation exactly but it went something like this. “David, I talk with different IT teams every week and many of them ask me the same question: “What can we as IT do to be more relevant to our end users [line of business]?”.

Jim (not his real name) told me that the first question he asks these teams in response is “Are you offering your customers self-service?”. This analyst told me that the answer he hears back most often is “no, we haven’t gotten to that yet”. Jim then goes on to advise these teams to A) leverage an automated approach to service delivery to speed up resource delivery (if they are not already doing so); and B) be sure to also implement self-service that makes it drop dead easy for end users to get the services they want.

If you think about it, not implementing self-service is denying the reality that line of business partners have choices beyond enterprise IT. It also fails to recognize that increasingly our expectations of how things should work, at work, are shaped by our personal and consumer experiences. Self-service and the near instant gratification that comes from it just makes more sense today than submitting tickets and waiting weeks for resources to be available for your next critical project.

My Top “X” List For IT

This exchange got me thinking about the big-ticket items that most IT teams must tackle to be more relevant to their end users. If the # 1 thing that IT teams must do to retain or regain relevance is embrace self-service; what does a top ten list look like? Sorry to disappoint but I don’t have a top ten list. There are however some things that I feel do stand apart from the rest of the pack when it comes to looking at how IT operates. So, in that spirit here is my list of the top seven things IT must do to remain relevant.

1. Implement Self Service for Resource Requests
2. Market IT Services to your End Users
3. Enable Infrastructure as Code
4. Become an IT Developer
5. Begin to Think about Multi-Cloud Networking
6. Go Beyond Infrastructure and Deliver Complete Stacks
7. Help App Dev Teams Move Containers to Production

There are undoubtedly other things that IT teams can do that would increase their relevance to line-of-business (LOB) partners. Having said that, I do think this is a pretty good list to start with. There’s too much here to cover in a single blog so I’ll elaborate on each of these in this blog and several others that will follow. Hopefully, along the way I will provide you enough insight on each to give you a good idea of what it is that IT must do along with some additional thoughts on how to get it done.

Starting with Self Service

According to Wikipedia and depending on how you look at it, Amazon Web Services has been around since 2002 or 2006. Early adopters flocked to it because of two reasons in my opinion. The first reason was an ability to get infrastructure fast. The second reason was the ability to get these resources without having to file one or more tickets with the help desk.

Today, implementing the ability to get end users resources fast is simply a matter of automation. Many organizations have adopted automation to dramatically speed up the provisioning of infrastructure resources. Application level resources is a different matter but we’ll cover that elsewhere.

I have first-hand experience talking with many IT teams who used to take 4 or more weeks to provision resources in the past but now routinely do it in under in under thirty minutes. Of course, with Amazon you can get those resources in just a few minutes, so taking 30 minutes or so is still longer than what it would take using AWS. But let’s be honest – how many developers find out about a project and then need to be coding it 5 minutes later? Thirty minutes is plenty fast for most needs.

While many organizations have, or are in the process of adopting automation to speed up service delivery, not nearly as many have implemented self-service as part of that process. Many still rely on existing request fulfilment processes that existed before automation was implemented. The most common example of this is organizations using Service Now for requesting resources, which in turn generates a ticket to the platform automation team which then initiates an automated process to fulfill the request.

Leveraging an existing ticketing process isn’t necessarily a bad approach and there are some good reasons for doing it. The main reason that I am aware of is that this approach means that any existing process for determining who has access to specific resources doesn’t need to be re-codified into the automation that supports self-service.

That’s not a bad reason to keep the existing process, but remember that if you are an internal IT team, your competing with the public cloud and on the public cloud – self-service means self-service. No tickets and no help desk. So, going the extra mile to enable true self service where entitlements and other forms of governance are matched between users and resources might be worth it for your IT team given the world we live and compete in.

Now a few caveats around the idea of self-service. Different end users have different needs. Many end users are perfectly happy selecting resources from a pre-populated catalog. VMware vRealize Automation is a great example of an automation platform that supports this model of self-service.

In this model, blueprints can be created to represent everything from a single machine to a complex, multi-tier application, with storage, networking, security and even monitoring agents all represented in the blueprint. These blueprints then become catalog items that once selected by end user are instantiated in near real time.

Other users might prefer a self-service model that is closer to what they would experience on Amazon. This model is declarative in nature and resources are requested either through a CLI or through an API (using scripts or through another tool) in the form of small building blocks that represent infrastructure elements such as compute, storage, or network. For IT teams looking for such a model to satisfy their end users, VMware Integrated OpenStack (VIO) might be the best choice for a service delivery automation platform.

A hybrid model might be the best choice for others. In this model vRealize Automation is used to offer VM level resources from a catalog but it is also used to reserve resources for a VIO based developer cloud that an App Dev team would like to implement. In this model vRealize Automation would also be used to provision the components necessary to instantiate a VIO based Developer Cloud for that same App Dev team.

Just for completeness, I should point out that vRealize Automation can also support the idea of blueprints as code, where blueprints are created or modified using YAML. These blueprints can then be imported into vRealize Automation and offered to end users through the catalog. These same blueprints can of course be exported as YAML as well.

The Right Self-Service Model for Your End Users

Hopefully you can see that solutions to the self-service problem exist along a continuum. Figuring out what type of self-service model to implement is very much a function of understanding your users. There are different approaches and you won’t be sure which approach makes the most sense unless you are actively engaged in understanding the needs of your users.

Having a deep understanding of what your end users need is also the prerequisite for our next “must do item” which is effectively marketing what you do offer to your end users. More to come on that in the next installment of this series.

Learn More

• Visit VMware vRealize product page
• Visit VMware Integrated OpenStack product page
• Try our Automate IT Hands-on Labs
• Try our Intelligent Operations Hands-on Labs

IT and DevOps: Hear from our GM and Customers

This post was originally published on this site

Spotlight session MGT3136SU at VMworld 2017 Las Vegas:

How DevOps Is Transforming IT: People, Process, Technology

In this spotlight session, Ajay Singh, VMware Cloud Management General Manager and SVP, will interview a group of our top customers about how IT can support DevOps.

As companies are continuing innovation on the path to digital transformation, they need new tools, skill sets, and organizational structures to support the new DevOps paradigms. Hear from the CIOs of some of our major customers about the challenges they have met and the solutions they have put in place, and our own VP of Engineering – the internal VMware DevOps “customer 0”.

Julie Ray
, SVP, ECIO, Fannie Mae

David Coker, Senior VP, Information Systems, Polaris Alpha

Sandhya Sridharan, Vice President Engineering, VMware

Drinking our own Champagne

Learn about VMware usage of our own tools for DevOps to drive efficiencies into the VMware organization while improving products we are building for customers. We will talk about the project Cava and how we do DevOps using our own vRealize solutions at the Cloud Management Business Unit of VMware. We will show a demo of a self-service portal for provisioning the infrastructure and applications used by 450+ software developers and release engineers on a daily basis. See how we drink our own champagne!

How to Register

Planning to attend the upcoming VMworld 2017 in Las Vegas or Barcelona? This is still a good time to register, and see you soon!

DSC Resource Kit Release August 2017

This post was originally published on this site

We just released the DSC Resource Kit!

This release includes updates to 10 DSC resource modules. In these past 6 weeks, 91 pull requests have been merged and 74 issues have been closed, all thanks to our amazing community!

The modules updated in this release are:

  • SecurityPolicyDsc
  • xCertificate
  • xComputerManagement
  • xDhcpServer
  • xDnsServer
  • xExchange
  • xFailOverCluster
  • xNetworking
  • xPSDesiredStateConfiguration
  • xSqlServer

For a detailed list of the resource modules and fixes in this release, see the Included in this Release section below.

Our last community call for the DSC Resource Kit was last week on August 16. A recording of our updates as well as summarizing notes are available. Join us for the next call at 12PM (Pacific time) on September 27 to ask questions and give feedback about your experience with the DSC Resource Kit. You can download a calendar event for the next call here.

We strongly encourage you to update to the newest version of all modules using the PowerShell Gallery, and don’t forget to give us your feedback in the comments below, on GitHub, or on Twitter (@PowerShell_Team)!

All resources with the ‘x’ prefix in their names are still experimental – this means that those resources are provided AS IS and are not supported through any Microsoft support program or service. If you find a problem with a resource, please file an issue on GitHub.

Included in this Release

You can see a detailed summary of all changes included in this release in the table below. For past release notes, go to the README.md or Changelog.md file on the GitHub repository page for a specific module (see the How to Find DSC Resource Modules on GitHub section below for details on finding the GitHub page for a specific module).

Module Name Version Release Notes
  • Refactored user rights assignment to read and test easier.
  • Add CodeCov.io code coverage reporting.
  • Opted into “Common Tests – Validate Example Files”.
  • Fixed bugs in examples.
  • Updated License and Manifest Copyright info to be 2017 Microsoft Corporation.
  • xCertReq:
  • Added .github support files:
  • Opted into Common Tests “Validate Module Files” and “Validate Script Files”.
  • Converted files with UTF8 with BOM over to UTF8 – fixes Issue 87.
  • Converted to use auto-documentation/wiki format – fixes Issue 84.
  • xComputer: Changed comparison that validates if we are in the correct AD Domain to work correctly if FQDN wasn”t used.
  • Updated AppVeyor.yml to use AppVeyor.psm1 module in DSCResource.Tests.
  • Removed Markdown.md errors.
  • Added CodeCov.io support.
  • xScheduledTask
    • Fixed incorrect TaskPath handling – Issue 45
  • Change examples to meet HQRM standards and optin to Example validation tests.
  • Replaced examples in README.MD to links to Example files.
  • Added the VS Code PowerShell extension formatting settings that cause PowerShell files to be formatted as per the DSC Resource kit style guidelines – Issue #91.
  • Opted into Common Tests “Validate Module Files” and “Validate Script Files”.
  • Converted files with UTF8 with BOM over to UTF8 – fixes Issue 90.
  • Updated Year to 2017 in License and Manifest – fixes Issue 87.
  • Added .github support files – fixes Issue 88:
  • Resolved all PSScriptAnalyzer warnings and style guide warnings.
  • xOfflineDomainJoin:
    • Changed to use CommonResourceHelper to load localization strings.
    • Renamed en-US to be correct case so that localization strings can be loaded.
    • Suppress PSScriptAnalyzer rule PSAvoidGlobalVars for $global:DSCMachineStatus = 1.
  • xComputer:
    • Suppress PSScriptAnalyzer rule PSAvoidGlobalVars for $global:DSCMachineStatus = 1.
  • xVirtualMemory:
    • Suppress PSScriptAnalyzer rule PSAvoidGlobalVars for $global:DSCMachineStatus = 1.
  • Added xDhcpServerClass
  • Converted AppVeyor.yml to pull Pester from PSGallery instead of Chocolatey
  • Fixed bug in xDnsServerADZone causing Get-TargetResource to fail with an extra property.
  • Add missing parameters to xExchClientAccessServer
  • Changes to xFailOverCluster
    • Added a common resource helper module with helper functions for localization.
      • Added helper functions; Get-LocalizedData, New-InvalidResultException, New-ObjectNotFoundException, New-InvalidOperationException and New-InvalidArgumentException.
    • Fixed lint error MD034 and fixed typos in README.md.
    • Opt-in for module files common tests (issue 119).
      • Removed Byte Order Mark (BOM) from the files; CommonResourceHelper.psm1 and FailoverClusters.stubs.psm1.
    • Opt-in for script files common tests (issue 121).
      • Removed Byte Order Mark (BOM) from the files; CommonResourceHelper.Tests.ps1, MSFT_xCluster.Tests.ps1, MSFT_xClusterDisk.Tests.ps1, MSFT_xClusterPreferredOwner.Tests.ps1, MSFT_xWaitForCluster.Tests.ps1.
    • Added common test helper functions to help test the throwing of localized error strings.
      • Get-InvalidArgumentRecord
      • Get-InvalidOperationRecord
      • Get-ObjectNotFoundException
      • Get-InvalidResultException.
    • Updated year to 2017 in license file and module manifest (issue 131).
  • Changes to xClusterDisk
    • Enabled localization for all strings (issue 84).
    • Fixed the OutputType data type that was not fully qualified.
    • Minor style changes.
    • Fixed Script Analyzer warnings for Write-Verbose.
  • Changes to xClusterNetwork
    • Replaced the URL for the parameter Role in README.md. The new URL is a more generic description of the possible settings for the Role parameter. The previous URL was still correct but focused on Hyper-V in particular.
    • Fixed typos in parameter descriptions in README.md, comment-based help and schema.mof.
    • Enabled localization for all strings (issue 85).
    • Minor style changes.
    • Fixed Script Analyzer warnings for Write-Verbose.
  • Changes to xCluster
    • Resolved Script Analyzer rule warnings by changing Get-WmiObject to Get-CimInstance (issue 49).
    • Minor style change in tests. Removed “-” in front of “-Be”, “-Not”, “-Throw”, etc.
    • Enabled localization for all strings (issue 83).
    • Added tests to improve code coverage.
      • Fixed random problem with tests failing with error “Invalid token for impersonation – it cannot be duplicated.” (issue 133).
    • Minor style changes.
    • Fixed Script Analyzer warnings for Write-Verbose.
  • Changes to xWaitForCluster
    • Refactored the unit test for this resource to use stubs and increase coverage (issue 78).
    • Now the Test-TargetResource correctly returns false if the domain name cannot be evaluated (issue 107).
    • Changed the code to be more aligned with the style guideline.
    • Updated parameter description in the schema.mof.
    • Resolved Script Analyzer warnings (issue 54).
    • Enabled localization for all strings (issue 88).
    • Minor style changes.
  • Changes to xClusterQuorum
    • Refactored the unit test for this resource to use stubs and increase coverage (issue 77).
    • Changed the code to be more aligned with the style guideline.
    • Updated parameter description in the schema.mof.
    • Added example (issue 47)
      • 1-SetQuorumToNodeMajority.ps1
      • 2-SetQuorumToNodeAndDiskMajority.ps1
      • 3-SetQuorumToNodeAndFileShareMajority.ps1
      • 4-SetQuorumToDiskOnly.ps1
    • Added links to examples from README.md.
    • Minor style changes.
    • Enabled localization for all strings (issue 87).
  • Changes to xClusterPreferredOwner
    • Enabled localization for all strings (issue 86).
    • Fixed typo in the returned hash table from Get-TargetResource.
    • Minor style changes.
  • MSFT_xDhcpClient:
    • Corrected style and formatting to meet HQRM guidelines.
    • Converted exceptions to use ResourceHelper functions.
    • Cleaned up badges by putting them into a table.
  • MSFT_xDnsConnectionSuffix:
    • Corrected style and formatting to meet HQRM guidelines.
    • Converted exceptions to use ResourceHelper functions.
    • Converted badges to use branch header as used in xSQLServer.
  • Added standard .markdownlint.json to configure rules to run on Markdown files.
  • MSFT_xDnsClientGlobalSetting:
    • Corrected style and formatting to meet HQRM guidelines.
    • Converted exceptions to use ResourceHelper functions.
  • Updated year to 2017 in LICENSE and module manifest.
  • MSFT_xDnsServerAddress:
    • Fix error when setting address on adapter where NameServer Property does not exist in registry for interface – see issue 237.
    • Corrected style and formatting to meet HQRM guidelines.
  • MSFT_xIPAddress:
    • Improved examples to clarify how to set IP Address prefix – see issue 239.
  • MSFT_xFirewall:
    • Fixed bug with DisplayName not being set correctly in some situations – see issue 234.
    • Corrected style and formatting to meet HQRM guidelines.
    • Converted exceptions to use ResourceHelper functions.
  • Added .github support files:
  • Opted into Common Tests “Validate Module Files” and “Validate Script Files”.
  • Converted files with UTF8 with BOM over to UTF8 – fixes Issue 250.
  • MSFT_xFirewallProfile:
    • Created new resource configuring firewall profiles.
  • MSFT_xNetConnectionProfile:
    • Corrected style and formatting to meet HQRM guidelines.
    • Added validation for provided parameters.
    • Prevent testing parameter values of connection that aren”t set in resource – fixes Issue 254.
    • Improved unit test coverage for this resource.
  • xService
    • BREAKING CHANGE: The service will now return as compliant if the service is not installed and the StartupType is set to Disabled regardless of the value of the Ensure property.
  • Fixed misnamed certificate thumbprint variable in example Sample_xDscWebServiceRegistrationWithSecurityBestPractices
  • Changes to xSQLServer
    • Added back .markdownlint.json so that lint rule MD013 is enforced.
    • Change the module to use the image “Visual Studio 2017” as the build worker image for AppVeyor (issue 685).
    • Minor style change in CommonResourceHelper. Added missing [Parameter()] on three parameters.
    • Minor style changes to the unit tests for CommonResourceHelper.
    • Changes to xSQLServerHelper
    • Opt-in for module files common tests (issue 702).
      • Removed Byte Order Mark (BOM) from the files; CommonResourceHelper.psm1, MSFT_xSQLServerAvailabilityGroupListener.psm1, MSFT_xSQLServerConfiguration.psm1, MSFT_xSQLServerEndpointPermission.psm1, MSFT_xSQLServerEndpointState.psm1, MSFT_xSQLServerNetwork.psm1, MSFT_xSQLServerPermission.psm1, MSFT_xSQLServerReplication.psm1, MSFT_xSQLServerScript.psm1, SQLPSStub.psm1, SQLServerStub.psm1.
    • Opt-in for script files common tests (issue 707).
      • Removed Byte Order Mark (BOM) from the files; DSCClusterSqlBuild.ps1, DSCFCISqlBuild.ps1, DSCSqlBuild.ps1, DSCSQLBuildEncrypted.ps1, SQLPush_SingleServer.ps1, 1-AddAvailabilityGroupListenerWithSameNameAsVCO.ps1, 2-AddAvailabilityGroupListenerWithDifferentNameAsVCO.ps1, 3-RemoveAvailabilityGroupListenerWithSameNameAsVCO.ps1, 4-RemoveAvailabilityGroupListenerWithDifferentNameAsVCO.ps1, 5-AddAvailabilityGroupListenerUsingDHCPWithDefaultServerSubnet.ps1, 6-AddAvailabilityGroupListenerUsingDHCPWithSpecificSubnet.ps1, 2-ConfigureInstanceToEnablePriorityBoost.ps1, 1-CreateEndpointWithDefaultValues.ps1, 2-CreateEndpointWithSpecificPortAndIPAddress.ps1, 3-RemoveEndpoint.ps1, 1-AddConnectPermission.ps1, 2-RemoveConnectPermission.ps1, 3-AddConnectPermissionToAlwaysOnPrimaryAndSecondaryReplicaEachWithDifferentSqlServiceAccounts.ps1, 4-RemoveConnectPermissionToAlwaysOnPrimaryAndSecondaryReplicaEachWithDifferentSqlServiceAccounts.ps1, 1-MakeSureEndpointIsStarted.ps1, 2-MakeSureEndpointIsStopped.ps1, 1-EnableTcpIpWithStaticPort.ps1, 2-EnableTcpIpWithDynamicPort.ps1, 1-AddServerPermissionForLogin.ps1, 2-RemoveServerPermissionForLogin.ps1, 1-ConfigureInstanceAsDistributor.ps1, 2-ConfigureInstanceAsPublisher.ps1, 1-WaitForASingleClusterGroup.ps1, 2-WaitForMultipleClusterGroups.ps1.
    • Updated year to 2017 in license file (issue 711).
    • Code style clean-up throughout the module to align against the Style Guideline.
    • Fixed typos and the use of wrong parameters in unit tests which was found after release of new version of Pester (issue 773).
  • Changes to xSQLServerAlwaysOnService
    • Added resource description in README.md.
    • Updated parameters descriptions in comment-based help, schema.mof and README.md.
    • Changed the datatype of the parameter to Uint32 so the same datatype is used in both the Get-/Test-/Set-TargetResource functions as in the schema.mof (issue 688).
    • Added read-only property IsHadrEnabled to schema.mof and the README.md (issue 687).
    • Minor cleanup of code.
    • Added examples (issue 633)
      • 1-EnableAlwaysOn.ps1
      • 2-DisableAlwaysOn.ps1
    • Fixed PS Script Analyzer errors (issue 724)
    • Casting the result of the property IsHadrEnabled to [System.Boolean] so that $null is never returned, which resulted in an exception (issue 763).
  • Changes to xSQLServerDatabasePermission
  • Changes to xSQLServerScript
  • Changes to xSQLServerSetup
    • Added Swedish localization (issue 695).
    • Now Get-TargetResource correctly returns an array for property ASSysAdminAccounts, and no longer throws an error when there is just one Analysis Services administrator (issue 691).
    • Added a simple integration test (issue 709).
    • Fixed PS Script Analyzer errors (issue 729)

How to Find Released DSC Resource Modules

To see a list of all released DSC Resource Kit modules, go to the PowerShell Gallery and display all modules tagged as DSCResourceKit. You can also enter a module’s name in the search box in the upper right corner of the PowerShell Gallery to find a specific module.

Of course, you can also always use PowerShellGet (available in WMF 5.0) to find modules with DSC Resources:

# To list all modules that are part of the DSC Resource Kit
Find-Module -Tag DSCResourceKit 
# To list all DSC resources from all sources 

To find a specific module, go directly to its URL on the PowerShell Gallery:
http://www.powershellgallery.com/packages/< module name >
For example:

How to Install DSC Resource Modules From the PowerShell Gallery

We recommend that you use PowerShellGet to install DSC resource modules:

Install-Module -Name < module name >

For example:

Install-Module -Name xWebAdministration

To update all previously installed modules at once, open an elevated PowerShell prompt and use this command:


After installing modules, you can discover all DSC resources available to your local system with this command:


How to Find DSC Resource Modules on GitHub

All resource modules in the DSC Resource Kit are available open-source on GitHub.
You can see the most recent state of a resource module by visiting its GitHub page at:
https://github.com/PowerShell/< module name >
For example, for the xCertificate module, go to:

All DSC modules are also listed as submodules of the DscResources repository in the xDscResources folder.

How to Contribute

You are more than welcome to contribute to the development of the DSC Resource Kit! There are several different ways you can help. You can create new DSC resources or modules, add test automation, improve documentation, fix existing issues, or open new ones.
See our contributing guide for more info on how to become a DSC Resource Kit contributor.

If you would like to help, please take a look at the list of open issues for the DscResources repository.
You can also check issues for specific resource modules by going to:
https://github.com/PowerShell/< module name >/issues
For example:

Your help in developing the DSC Resource Kit is invaluable to us!

Questions, comments?

If you’re looking into using PowerShell DSC, have questions or issues with a current resource, or would like a new resource, let us know in the comments below, on Twitter (@PowerShell_Team), or by creating an issue on GitHub.

Katie Keim
Software Engineer
PowerShell DSC Team
@katiedsc (Twitter)
@kwirkykat (GitHub)

Wavefront and Microservices Architectures

This post was originally published on this site

Microservice architectures improve the ability of IT organizations to more rapidly deliver business critical services to their customers, but this improved agility often comes at the cost of added complexity.  This complexity is manifested by the increasing scale-out and ephemeral nature of this application architecture pattern.  The transformation from monolithic applications to microservices means that in many cases, the complexity which resided on the “inside” of the application shifts towards the “outside” of the microservice as IT organizations now need to account for additional infrastructure components needed to support the microservice plus there are the additional communications pathways that will occur within the microservice ecosystem.  In terms of the microservice lifecycle, data collected by companies such as New Relic confirms the trend towards increasingly short-lived microservices (with many running for less than one minute).

What is often lost in the discussion of microservices is the need to re-examine how an IT organization will be able to manage this new environment for the issues just raised can often “break” existing tooling.   Let’s just look at one outcome – the missing or invisible container.  Tools which perform coarse-grained data collection may not be able to observe a microservice for its entire lifecycle could occur in-between data collection operations.  That’s why IT organizations may need to reconsider their existing monitoring tool portfolio to ensure that they have the necessary degree of fine-grained observability required for an increasingly dynamic environment.  Returning to the “inner” versus “outer” architecture ramifications, IT organizations will also need tools that can not only store large amount of information, but also enable the rapid identification of patterns of microservice behavior that may not be obvious to the human operator.

VMware understands these issues and thus this was the impetus for our investment in Wavefront.  We’ll continue to focus on transforming the manageability of an increasingly complex environment so that IT organizations can focus their energies on transforming their business.

The Samsung Galaxy Note8: A Bigger, More Powerful Device for the Enterprise

This post was originally published on this site

There has been a long anticipated wait for the next version of the Samsung Galaxy Note line of devices. Announced today from Samsung Unpacked, we’re seeing big things from this latest device. From the large, crisp infinity display to the S Pen that lets you easily express yourself, this device is one that will provide an amazing experience to both consumers and business users alike.

[embedded content]

Samsung devices come with built-in capabilities that enable unique ways to deploy and secure them. The devices power a range of organizations—government, healthcare, retail/hospitality, education and financial services. With customizable solutions, Samsung innovations are a fit for every industry.

Samsung and VMware work together on a multitude of solutions to enable business users on the Galaxy Note8 device and to unify the mobile and desktop computing experience.

  • Knox Mobile Enrollment: The first step in managing mobile devices is to onboard them to deliver apps and resources to end users. To make sure this gets completed, it’s beneficial to make it as easy as possible for the end user and IT. So, Samsung has Knox Mobile Enrollment to bulk provision devices out of the box. As soon as the device is connected to Wi-Fi, everything needed gets automatically sent to the device, and the device is enrolled with minimal interaction.


  • Samsung_KnoxSamsung Knox: The Note8 features Samsung Knox, a defense-grade, hardware-based platform that protects the phone from the moment it boots up all the way through launching an app. When combined with VMware AirWatch unified endpoint management (UEM), the device is secured from the ground up with data loss prevention policies, remote actions and automated compliance and remediation.  The Knox Workspace, which can be deployed from AirWatch, isolates and encrypts just the work data, keeping it separate from personal apps and data on the device. Click here for more on Samsung Knox management.
  • Samsung DeX: With Samsung DeX (or desktop experience), users can plug in their device to the DeX Station, along with peripherals, and get a full desktop version of their device. Using VMware Horizon, organizations can deliver full screen virtual Windows 10 desktops to Note8 devices, making the device a portable, easy-to-use thin client. In addition to full-screen capabilities, users can also simultaneously run multiple Windows applications on screen. DeX was first available starting with the S8 and S8+, and we cannot wait to see how the Note8, along with its 10nm processor and 6GB RAM, can continue to enable efficiency and business mobility. Click here for more on DeX and VMware Workspace ONE.


  • E-FOTA: Now you have these new devices, how do you make sure that new OS updates won’t affect your company app or that devices all are updated to have the latest security patches? The answer is with Samsung Enterprise Firmware Over-the-Air (E-FOTA). VMware is working extensively with Samsung to integrate the E-FOTA feature with the AirWatch console so IT administrators can deploy these features alongside enterprise apps and policies. AirWatch integration with Samsung E-FOTA is expected to be generally available this fall.

The Galaxy Note8 will be available for preorder starting tomorrow. To hear how the Note8 will transform business mobility, visit Samsung at their Mobility Zone booth at VMworld (Booth 333), and check out their session to learn how Samsung and VMware are converging mobile and desktop management.

VMworld 2017 Breakout Session:
“One Device to Rule Them All: Samsung & VMware Converge Mobile & Desktop”
Add #ADV3370BUS via VMworld U.S. schedule builder.
EUC at VMworld