Fun in the lab with VMware and a Raspberry Pi

This post was originally published on this site

Note: These instructions are only intended for use in a lab environment for non-production use. Do not use the steps described here to further contribute to the number of insecure IoT devices populating our world. Assume everything described is an unsupported configuration. Finally, be mindful of the Windows 10 IoT prototyping restrictions as well as … Continue reading Fun in the lab with VMware and a Raspberry Pi

vRealize Automation 8.0 – Wildcard SSL certificate support and deployment issues – LCMVRAVACONFIG590003

This post was originally published on this site

Ok, so I’m just going to call it out straight away, when using wildcard SSL certificates with vRealize Automation 8.0, read the release notes. I did not, and caused myself quite a few headaches with the deployment, which you can read about further in this post. Cannot set wildcard certs for certain domain names, specifically … Continue reading vRealize Automation 8.0 – Wildcard SSL certificate support and deployment issues – LCMVRAVACONFIG590003

The post vRealize Automation 8.0 – Wildcard SSL certificate support and deployment issues – LCMVRAVACONFIG590003 appeared first on @Saintdle.

vRealize Automation 8.0 – Wildcard SSL certificate support and deployment issues – LCMVRAVACONFIG590003

This post was originally published on this site

Ok, so I’m just going to call it out straight away, when using wildcard SSL certificates with vRealize Automation 8.0, read the release notes. I did not, and caused myself quite a few headaches with the deployment, which you can read about further in this post. Cannot set wildcard certs for certain domain names, specifically … Continue reading vRealize Automation 8.0 – Wildcard SSL certificate support and deployment issues – LCMVRAVACONFIG590003

The post vRealize Automation 8.0 – Wildcard SSL certificate support and deployment issues – LCMVRAVACONFIG590003 appeared first on @Saintdle.

DSC Resource Kit Release October 2019

This post was originally published on this site

DSC Resource Kit Release

We just released the DSC Resource Kit!

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

Special thanks to everyone who contributed to the Hacktoberfest effort to update xWebAdministration!!! This accounted for 26 of the pull requests closed this month.

The modules updated in this release are:

  • ActiveDirectoryDsc 4.2.0.0
  • ComputerManagementDsc 7.1.0.0
  • SharePointDsc 3.7.0.0
  • StorageDsc 4.9.0.0
  • xDnsServer .16.0.0
  • xDscResourceDesigner .13.0.0
  • xExchange .30.0.0
  • xHyper-V .17.0.0
  • xWebAdministration 3.0.0.0

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

Our latest community call for the DSC Resource Kit was last Wednesday, October 23. A recording of the call is posted on the PowerShell YouTube channel. You can join us for the next call at 12PM (Pacific time) on August 28th to ask questions and give feedback about your experience with the DSC Resource Kit.

Following this resource kit release, maintainers will begin publishing as soon as they are ready rather than holding 6 weeks to do a group release. In the next community call we will discuss progress and whether we need to do a November release or not. Be sure to follow the DSC Community on Twitter for live updates as modules release.

You can find more information about our progress as a community on the DSC Community page.

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)!

Please see our documentation here for information on the support of these resource modules.

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
ActiveDirectoryDsc 4.2.0.0
  • Changes to ActiveDirectoryDsc
    • Resolved custom Script Analyzer rules that was added to the test framework.
    • Resolve style guideline violations for hashtables (issue 516).
  • Changes to ADReplicationSite
    • Added “Description” attribute parameter (issue 500).
    • Added Integration testing (issue 355).
    • Correct value returned for RenameDefaultFirstSiteName (issue 502).
  • Changes to ADReplicationSubnet
    • Added “Description” attribute parameter (issue 503)
    • Added Integration testing (issue 357)
  • Changes to ADReplicationSiteLink
    • Added Integration testing (issue 356).
    • Added ability to set “Options” such as Change Notification Replication (issue 504).
  • Changes to ActiveDirectoryDsc.Common
    • Fix Test-DscPropertyState Failing when Comparing $Null and Arrays. (issue 513)
ComputerManagementDsc 7.1.0.0
  • ComputerManagementDsc:
    • Update psd1 description – Fixes Issue 269.
  • Fix minor style issues with missing spaces between param statements and “(“.
  • SmbServerConfiguration:
    • New resource for configuring the SMB Server settings.
    • Added examples for SMB Server Configuration.
  • Minor corrections to CHANGELOG.MD.
  • ScheduledTask:
    • Fixed bug when description has any form of whitespace at beginning or end the resource would not go into state – Fixes Issue 258.
  • SmbShare:
    • Removal of duplicate code in Add-SmbShareAccessPermission helper function fixes Issue 226.
SharePointDsc 3.7.0.0
        • SPConfigWizard
          • Fixed issue with incorrect check for upgrade status of server
        • SPDistributedCacheService
          • Improved error message for inclusion of server name into ServerProvisionOrder parameters when Present or change to Ensure Absent
        • SPFarm
          • Removed SingleServer as ServerRole, since this is an invalid role.
          • Handle case where null or empty CentralAdministrationUrl is passed in
          • Move CentralAdministrationPort validation into parameter definition to work with ReverseDsc
          • Add NotNullOrEmpty parameter validation to CentralAdministrationUrl
          • Fixed error when changing developer dashboard display level.
          • Add support for updating Central Admin Authentication Method
        • SPFarmSolution
          • Fix for Web Application scoped solutions.
        • SPInstall
          • Fixes a terminating error for sources in weird file shares
          • Corrected issue with incorrectly detecting SharePoint after it has been uninstalled
          • Corrected issue with detecting a paused installation
        • SPInstallLanguagePack
          • Fixes a terminating error for sources in weird file shares
        • SPInstallPrereqs
          • Fixes a terminating error for sources in weird file shares
        • SPProductUpdate
          • Fixes a terminating error for sources in weird file shares
          • Corrected incorrect farm detection, added in earlier bugfix
        • SPSite
          • Fixed issue with incorrectly updating site OwnerAlias and SecondaryOwnerAlias
        • SPWebAppAuthentication
          • Fixes issue where Test method return false on NON-US OS.
StorageDsc 4.9.0.0
  • Disk:
    • Added Location as a possible value for DiskIdType. This will select the disk based on the Location property returned by Get-Disk
    • Maximum size calculation now uses workaround so that Test-TargetResource works properly – workaround for Issue 181.
  • DiskAccessPath:
    • Added Location as a possible value for DiskIdType. This will select the disk based on the Location property returned by Get-Disk
  • WaitForDisk:
    • Added Location as a possible value for DiskIdType. This will select the disk based on the Location property returned by Get-Disk
xDnsServer 1.16.0.0
  • Changes to XDnsServerADZone
    • Raise an exception if DirectoryPartitionName is specified and ReplicationScope is not Custom. (issue 110).
    • Enforce the ReplicationScope parameter being passed to Set-DnsServerPrimaryZone if DirectoryPartitionName has changed.
  • xDnsServer:
    • OptIn to the following Dsc Resource Meta Tests:
      • Common Tests – Relative Path Length
      • Common Tests – Validate Markdown Links
      • Common Tests – Custom Script Analyzer Rules
      • Common Tests – Required Script Analyzer Rules
      • Common Tests – Flagged Script Analyzer Rules
xDscResourceDesigner 1.13.0.0
  • Fix Parameter Blocks to conform to Dsc Style Guidlelines issue 79.
  • Fix README.md MarkDownLint Errors and Formatting Issues
xExchange 1.30.0.0
  • Resolved custom Script Analyzer rules that was added to the test framework.
  • Added xExchAcceptedDomain resource
  • Resolved hashtable styling issues
  • Added xExchRemoteDomain resource
xHyper-V 3.17.0.0
  • MSFT_xVMNetworkAdapter:
    • Added NetworkSettings to be able to statically set IPAddress.
    • Added option for Vlan tagging. You can now setup a Network Adapeter as an access switch on a specific Vlan.
xWebAdministration 3.0.0.0
  • Changes to xWebAdministration
    • Changes to PULL_REQUEST_TEMPLATE.md
      • Improving descriptive text around the CHANGELOG.md entry.
      • Adding note that entry in CHANGELOG.md is mandatory for all PRs.
    • Resolved custom Script Analyzer rules that was added to the test framework.
    • Moved change log from README.md to a separate CHANGELOG.md (issue 446).
    • Remove example “Creating the default website using configuration data” from README.md (issue 488).
    • Removed examples README.md as it was obsolete (issue 482).
    • Updated Ensure property description for xIisHandler resource to match schema.mof
    • Moved examples from Readme.md to respective /Examples/Resources/ folders (issue 486).
    • Created new folder structure for examples so that examples will be placed in /Examples/Resources/$resourceName (issue 483).
    • Added a table of contents for the resource list (issue 450).
    • Alphabetized the resource list in the README.md (issue 449).
    • Optimized exporting in the module manifest for best performance (issue 448).
    • Updated hashtables in the repo to adhere to the style guidelines described at https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.mdcorrect-format-for-hashtables-or-objects (issue 524)
    • Moved example Sample_EndToEndxWebAdministration from readme.md to a separate .ps1 in /examples/ (issue 491)
    • Removed example “Create and configure an application pool” from README.md (issue 489).
  • Changes to xIisHandler
    • Updated schema.mof to include descriptions for each property (issue 453).
    • Moved MSFT_xIisHandler localization strings to strings.psd1 (issue 463).
  • Changes to xWebSite
    • Fix Get-TargetResource so that LogFlags are returned as expected array of strings (one for each flag) rather than an array containing a single comma-separated string of flags” (issue 332).
    • Moved localization strings to strings.psd1 file (issue 475)
    • Updated schema.mof so that each property has an appropriate description (issue 456).
    • Updated schema.mof and README so that SourceType and SourceName properties for MSFT_xLogCustomFieldInformation are associated with the appropriate descriptions and valuemaps/values (issue 456).
    • Move examples from README.md to resource examples folder (issue 487).
    • Fix case of resource name from xWebsite to xWebSite (issue 535).
  • Changes to xIISLogging
    • Fix Get-TargetResource so that LogFlags are returned as expected array of strings (one for each flag) rather than an array containing a single comma-separated string of flags (issue 332).
    • Moved MSFT_xIisLogging localization strings to strings.psd1 (issue 464).
  • Changes to xSslSettings
    • Updated casing of xSslSettings in all file names, folder names, schema, and documentation (issue 461).
    • Updated casing of xSslSettings in all file names, folder names, schema, and documentation (issue 536).
    • Moved MSFT_xSslSettings localization strings to strings.psd1 (issue 467).
  • Changes to xWebConfigKeyValue
    • Updated schema.mof to include a description for the Ensure property (issue 455).
    • Move localization strings to strings.psd1 file (issue 472).
  • Changes to xWebAppPoolDefaults
    • Move localization strings to strings.psd1 file (issue 470).
    • BREAKING CHANGE: Changed ApplyTo key parameter to IsSingleInstance to bring the resource into compliance with published best practices (issue 462).
  • Changes to xWebApplication
    • Move localization strings to strings.psd1 file (issue 468)
    • Add description on class MSFT_xWebApplicationAuthenticationInformation (issue 454).
  • Changes to xIisModule entry
    • Moved xIisModule localization strings to strings.psd1 (issue 466).
  • Changes to xIisMimeTypeMapping
    • Moved MSFT_xIisMimeTypeMapping localization strings to strings.psd1 (issue 465).
  • Changes to xWebVirtualDirectory
    • Moved MSFT_xWebVirtualDirectory localization strings to strings.psd1 (issue 477).
  • Changes to xWebSiteDefaults
    • Move localization strings to strings.psd1 file (issue 475).
    • BREAKING CHANGE: Changed ApplyTo key parameter to IsSingleInstance to bring the resource into compliance with published best practices (issue 457).
    • Fix case of resource name from xWebsiteDefaults to xWebSiteDefaults (issue 535).
  • Changes to xWebConfigProperty
    • Move localization strings to strings.psd1 file (issue 473).
  • Changes to xWebConfigPropertyCollection
    • Move localization strings to strings.psd1 file (issue 474).
  • Changes to xIisFeatureDelegation
    • Moved MSFT_xIisFeatureDelegation localization strings to strings.psd1 (issue 459).
  • Changes to xWebAppPool
    • Moved MSFT_xWebAppPool localization strings to strings.psd1 (issue 469).

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 starting in WMF 5.0) to find modules with DSC Resources:

# To list all modules that tagged as DSCResourceKit
Find-Module -Tag DSCResourceKit 
# To list all DSC resources from all sources 
Find-DscResource

Please note only those modules released by the PowerShell Team are currently considered part of the ‘DSC Resource Kit’ regardless of the presence of the ‘DSC Resource Kit’ tag in the PowerShell Gallery.

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

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:

Update-Module

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

Get-DscResource

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 CertificateDsc module, go to:
https://github.com/PowerShell/CertificateDsc.

All DSC modules are also listed as submodules of the DscResources repository in the DscResources folder and 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:
https://github.com/PowerShell/xPSDesiredStateConfiguration/issues

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.

Michael Greene
Principal Program Manager
PowerShell DSC Team
@migreene (Twitter)
@mgreenegit (GitHub)

The post DSC Resource Kit Release October 2019 appeared first on PowerShell.

AppVolumes Replication – Writables and Appstacks

This post was originally published on this site

Hello Everyone,

 

I’m currently working on getting our Cloud POD completed and the last piece I have to set is the AppVolumes replication between our two sites. Ideally I want to have users with homesites where 50% of users are using Site1 and 50% Site 2. I have two standalone vcenters and App Volumes Managers in each site. For the storage we have Pure and I have already enabled Async replication. With Appvolumes I have created a storage group and I was able to import all appstacks. Then I used the powershell script and was able to replicate all entitlements with no problems. At some point I would like to automate it because right now I’m only snapshoting a replicated Appstack datastore in Site 1 and sending it across to Site 2 and then i have to manually go in and restore it to non-attachable Datastore so then AppVolumes replicates it using storage group and imports it.

 

As for writables I was trying to accomplish it the same way however it looks like Storage groups either don’t apply to writable or it just doesn’t work. I looked at the Horizon reference architecture-multi site reference guide and the only thing I can find in it is as follows:

 

In use cases where writable volumes are being used, there are a few additional steps: 1. Mount the replicated datastore that contains the writable volumes.2. Perform a rescan of that datastore. If the datastore was the default writable volume location, App Volumes Manager automatically picks up the user entitlements after the old assignment information has been cleaned up.3. (Optional) If the datastore is not the default writable volume location, perform an Import Writables operation from the App Volumes Manager at Site 2.”

 

 

What I’m seeing though is that storage group doesn’t really work on Writables like with appstacks. It doesn’t replicate between datastores. Also, If I manually drop a writable vmdk and metadata file to the default writable location, the manager never imports it automatically like mentioned in the article.

 

At the end of the day what I want to achieve is to have 2 sites and appstacks and writables available at both sites at all times. A user at Site 2 might never have to log in to Site 1 but in case of disaster I would like to have that synchronized and available in both places

 

Can someone share how this could be achieved or if you are currently doing it, maybe share you setup?

 

Thank you

 

 

 

 

VM Workstation 15.5 choppy usb audio

This post was originally published on this site

I am using Windows 10 as a guest OS (as well as host) and when connecting any usb audio to the guest OS i am getting it choppy

I have follow other topics on this community yet found no working solution so far

 

issue happens with all type of usb audio (dongles, jabra, etc)

audio is choppy and distorted

reinstalling vm tools did not helped

usb 3.0 support is enabled in vm

 

any suggestions?

Windows 10 guest "sudden death" on VMWare Fusion 11.5 on MacOS Catalina

This post was originally published on this site

Hi to all,

I am experiencing a Windows 10 guest “sudden death”. The VM quits abruptly and all I see is the VMware “play” triangle on a black background, as if I had shut down the guest.

I have 2 Windows 10 guests on VMWare Fusion 11.5 on MacOS Catalina, each one running in full screen on a dedicated screen (I have a 3 screens setup).

This tends to happen freshly after I restarted the whole system (MAC + VMs), sometimes on one Windows 10 VM, sometimes on the other Windows 10 VM, sometimes on both Windows VMs (but not at the same time).

 

I am just furious about this. In the middle of the work, the VM simply dies, as if someone had pulled the cord. All of the non-saved data is lost, and my fear is, that the VM file(s) will get corrupted at some time.

 

Due to the fact that it has happened several times, I activated the “Hang/Crash” Troubleshooting.

This is the log of the last moments of my VM:

 

2019-10-29T07:35:04+01:00[+0.000]| keyboard| W115: Caught signal 11 — tid 9398 (addr 625BC7714)

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: rip 0x7fff67082dc6 rsp 0x70000e729de0 rbp 0x70000e729de0

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: rax 0x625bc7714 rbx 0x7fa716dedb68 rcx 0x1 rdx 0x1 rsi 0x7fa716dedb68 rdi 0x625bc7714

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125:         r8 0x0 r9 0x0 r10 0x114e4cc48 r11 0xffff805f0edd9bac r12 0x625bc7714 r13 0x0 r14 0x625bc7700 r15 0x1

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: stack 70000E729DE0 : 0x000070000e729e20 0x00007fff32951003

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: stack 70000E729DF0 : 0x0000000000001700 0x0000000625bc6000

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: stack 70000E729E00 : 0x00007fa716dc2d30 0x00007fa746c7c4d0

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: stack 70000E729E10 : 0x0000000000010000 0x00007fa717038b70

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: stack 70000E729E20 : 0x000070000e729e70 0x0000000114e4306c

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: stack 70000E729E30 : 0xaaaaaaaaaaaaaaaa 0x00007fa716dedb30

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: stack 70000E729E40 : 0x00007fa716df7390 0x0000000000000000

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SIGNAL: stack 70000E729E50 : 0x00007fa716ddb5b0 0x00007fa716dc2d30

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: Backtrace:

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: Backtrace[0] 000070000e729820 rip=00000001101e1cb0 rbx=000070000e7298b8 rbp=000070000e729880 r12=000070000e729de0 r13=00000000000001f6 r14=000000000000000b r15=00000001105b2ee3

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: Backtrace[1] 000070000e729890 rip=00007fff67085b1d rbx=000070000e729d28 rbp=000070000e729890 r12=36dca36955e0aa1c r13=0000000000000000 r14=0000000625bc7700 r15=0000000000000001

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SymBacktrace[0] 000070000e729820 rip=00000001101e1cb0 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx-debug loaded at 000000010f7b5000

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SymBacktrace[1] 000070000e729890 rip=00007fff67085b1d in function _sigtramp in object /usr/lib/system/libsystem_platform.dylib loaded at 00007fff67081000

2019-10-29T07:35:04+01:00[+0.000]| keyboard| E105: PANIC: Unexpected signal: 11.

2019-10-29T07:35:04+01:00[+0.000]| keyboard| E105: PANIC: Loop on signal 11.

2019-10-29T07:35:04+01:00[+0.000]| keyboard| E105: Panic loop

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: Backtrace:

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: Backtrace[0] 000070000e728540 rip=000000010f802930 rbx=000070000e728540 rbp=000070000e728a20 r12=000070000e728ed0 r13=00000000000001f6 r14=00007fff93cbd070 r15=000070000e728f38

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: Backtrace[1] 000070000e728a30 rip=00000001101e1e1f rbx=0000000000000160 rbp=000070000e728a90 r12=000070000e728ed0 r13=00000000000001f6 r14=000000000000000b r15=000070000e728f38

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: Backtrace[2] 000070000e728aa0 rip=00007fff67085b1d rbx=000070000e728f38 rbp=000070000e728aa0 r12=36dca36955e0b80c r13=0000000000000000 r14=0000000625bc7700 r15=0000000000000001

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SymBacktrace[0] 000070000e728540 rip=000000010f802930 in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx-debug loaded at 000000010f7b5000

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SymBacktrace[1] 000070000e728a30 rip=00000001101e1e1f in function (null) in object /Applications/VMware Fusion.app/Contents/Library/vmware-vmx-debug loaded at 000000010f7b5000

2019-10-29T07:35:04+01:00[+0.000]| keyboard| I125: SymBacktrace[2] 000070000e728aa0 rip=00007fff67085b1d in function _sigtramp in object /usr/lib/system/libsystem_platform.dylib loaded at 00007fff67081000

 

I also found this in the log, just 40 seconds earlier:

 

2019-10-29T07:34:23.562+01:00| vcpu-1| I125: TOOLS call to Ïltú  failed.

2019-10-29T07:34:23.581+01:00| vcpu-1| I125: TOOLS call to n%mtú  failed.

2019-10-29T07:34:23.598+01:00| vcpu-1| I125: TOOLS call to Nîmqú  failed.

2019-10-29T07:34:23.606+01:00| vcpu-0| I125: TOOLS call to ßltú  failed.

2019-10-29T07:34:23.622+01:00| vcpu-0| I125: TOOLS call to Ïltú  failed.

2019-10-29T07:34:23.636+01:00| vcpu-1| I125: TOOLS call to œçltú  failed.

 

These weird names do sound strange to me, but I don’t know if this could have something to do with my issue.

I also have triggered the “Collect Support Information”, and I am willing to send it to VMware, in case someone from the Customer Support needs it (it’s a 412 MB .zip).

 

Did this happen to anyone else before?

What can I do to avoid this umpteenth crappy bug of this disgraceful beta-like software?

 

My gear is the following:

  • iMac (27-inch, Late 2013)
  • Processor: 3.4 GHz Quad-Core Intel Core i5
  • Memory: 32 GB 1600 MHz DDR3
  • Graphics: NVIDIA GeForce GTX 775M 2 G
  • 2 external DELL monitors
  • VmWare Fusion 11.5
  • MacOS Catalina 10.15 (19A602)
  • 2 Windows 10 VMs (both Version 1903, OS Build 18362.418)
  • Keyboard: Microsoft Digital Media Pro
  • Mouse: Logitech RX1000

Bridging the Gap Between NHS and Public Cloud with VMware Cloud on AWS

This post was originally published on this site

Following on from How VMware is Accelerating NHS Cloud Adoption, this post dives into more detail around how the UK National Health Service (NHS) can use VMware Cloud on AWS to bridge the gap between existing investments and Public Cloud. Part 1: How VMware is Accelerating NHS Cloud Adoption Part 2: Bridging the Gap Between NHS […]

NSX-T Data Center 2.4 Management and Control Plane agents

This post was originally published on this site


As in the previous article I have illustrated about the NSX-T DC 2.4 management plane and Central control plane which is now conversed into one nsx manager node.



MPA (Management Plane Agent): This agent is located on each transport node which communicate with the NSX manager


NETCPA:  It provides communication between central control plane and the hypervisor.

The management plane and the central control plane (CCP) run on same virtual appliance but they perform different functionality and will cover about they technical aspects below.

The NSX cluster can scale to max of 3 NSX manager nodes run on the management and CCP.


Communication process

The nsx-mpa agent on transport node get communicated with NSX manager over Rabbitmq channel which is on port 5671

Now, the CCP communicate with transport node through nsx-proxy through port 1235

The task of NSX manager is to push the config to the CCP. The CCP configures the dataplane through nsx-proxy, which is one of the component of LCP (Local control plane)



*MPA ( Management Plane Agent)
*NETCPA (Network Control Plane Agent)
*CCP (Central Control Plane)
*LCP (Local Control Plane) 

Happy learning…. 🙂