Fix WordPress “Destination Folder Already Exists”Issue

I encountered an issue with my WordPress hosted site when I was attempting to install a plugin, in this case the WP Statistics plugin. I know I had previously installed this plugin but it did not show up in my installed plugin list in the WordPress Admin dashboard. The installation fails with an error: “Installation failed: Destination folder already exists.”

When you install a WordPress theme or plugin, WordPress will extract and copy the folder from a zip file into the wp-content/themes or wp-content/plugins directory. If the folder already exist, then WordPress is unable to copy the files and therefore generates the error. This can happen if the theme or plugin files that are already installed are missing or corrupted.

Here’s the fix for this issue:

  • Use a FTP client such as FileZilla, and connect to your WordPress site.
  • Drill down into the wp-content/plugins directory and delete the plugins folder which you are having issues with. In my case the WP Statistics plugin folder.
  • Once the folder is deleted, go back to your WordPress admin site and reinstall the plugin. You should see a successful installation and at which point, you can activate the plugin and configure the settings if necessary.
Please like & share:

Finding and Removing Unused VMware Horizon View Replica Virtual Machines

vmware-vr-1

Purpose

This article provides steps to find one or more unused replicas in the datastore and to safely remove them.

Resolution

If the parent virtual machine or snapshot is changed in the pool settings, a new replica virtual machine is created. The previous replica becomes unused and is deleted after the recompose completes. The View composer automatically deletes the replica from vCenter Server and the Composer database. Under certain conditions, the replica virtual machine information may exist in the Composer database and the vCenter Server Inventory after any linked clone associated with the replica is deleted. This results in an unused replica.

Finding and removing unused replicas

To find and remove unused replicas:
  1. In vCenter Server or the server where the composer is installed, stop the VMware View Composer service.Note: When this service is down, no recompose, refresh, or provisioning operations occur. Use a convenient maintenance window.
  2. Click Start, type Services, and Press Enter.
  3. Click VMware View Composer Service.
  4. Click Stop.
  5. Click Start > Run, type cmd, and click OK. The command prompt opens.
Note: In the Windows Server 2008 machines, the command prompt must be run as an Administrator.
To run the command prompt as an Administrator:
  1. Click Start > Run, type cmd, and click OK. The command prompt opens.
  2. Hold Ctrl + Shift, and press Enter.
  3. Navigate to the View Composer install directory.
    • On a Windows 32-bit server, navigate to C:\Program Files\VMware\VMware View Composer.
    • On a Windows 64-bit server, navigate to C:\Program Files (x86)\VMware\VMware View Composer.
  4. Run the sviconfig.exe command with the FindUnusedReplica operation:

    SviConfig.exe -operation=FindUnusedReplica -DsnName=DSN_Name -Username=User_Name -Password=Password

    Where:

    • DSN_Name is the name of the compose database DSN
    • User_name is the user name of composer database owner
    • Password is the password of composer database ownerFor example:SviConfig.exe -operation=FindUnusedReplica -DsnName=ComposerDB -Username=sa -Password=secretNotes:
    • If the DsnName contains spaces, use quotes around the value.
    • If there are two composer databases on the server due to an older database, and the command is run against the incorrect database, the currently used replicas is moved to the unused folder as the old database does not recognize them.

    To determine the Composer DB DSN, user and password:

    1. In the vCenter Server hosting the Composer service, Click Start > Programs > Administrative Tools > Data Sources (ODBC).
    2. Click the System DSN tab.
    3. Click the Composer database entry. This is the value you enter for DsnName in the sviconfig command.
    4. Click Edit.
    5. The username is visible and should match the entry in the Composer configuration in the View Manager.
  5. If the command finds any unused replicas, they are listed in a new file created in the current directory ( unused-replica-*.txt).
  6. Unused replicas can be unprotected and moved to a unique folder with the parameter:-move=trueFor example:SviConfig.exe -operation=FindUnusedReplica -DsnName=ComposerDB -Username=sa -Password=secret -Move=trueNotes:
    • When using the move=true option, you receive warning pop-ups. These are safe to ignore.
    • Note the UnusedViewComposerReplicaFolder is created automatically if it does not exist, and unused replicas are moved to this folder.
  7. Open a vSphere Client and connect to vCenter Server.
  8. Click Inventory > VMs and Templates.
  9. Remove the replicas located at the UnusedViewComposerReplicaFolder.
  10. Start the VMware View Composer service.
Note: To view the help file for findUnusedReplicas:
  1. Click Start > Run, type cmd, and click OK. The command prompt opens and navigate to the View Composer install directory.
  2. Run this command:SviConfig.exe -operation=findUnusedReplica

Additional Information

See Also

Please like & share:

PCoIP connections to VMware Horizon View 5.1.x / 6.1 Desktops With Multiple Network Adapters Fail

PCoIP connections to VMware Horizon View 5.1.x / 6.1 desktops with multiple network adapters fail (2062604)

Symptoms

  • Attempting to connect to Horizon View desktops with multiple network adapters fail.
  • You see errors similar to:
    • Unable to launch from Pool <pool> for user <domain/user>: There were no machines available that reported protocol [PCoIP] as ready
    • The Display Protocol For this Desktop is currently not available
    • The connection to the remote computer ended
Note: The issue can also be observed when connecting to View desktops having single network adapter.

Resolution

To resolve this issue, configure the subnet that the View Agent uses by setting the value for the subnet mask registry in Parent Virtual Machine.
Warning: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information, see Microsoft KB article 136393.
Note: The preceding link was correct as of June 17, 2015. If you find a link is broken, provide a feedback and a VMware employee will update the link.
To open the Windows Registry:
  1. Click Start > Run, type regedit, and click OK.
  2. Go to the registry key – HKEY_LOCAL_MACHINE\software\vmware inc\vmware vdm\node manager\subnet.

    For View 6.1 – Go to the registry key HKEY_LOCAL_MACHINE\software\vmware inc\vmware vdm \IpPrefix
  3. Set the value to n.n.n.n/m (REG_SZ). Note: where n.n.n.n is the TCP/IP subnet and m represents the number of bits in the subnet mask.
For more information:

Source: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2062604

Please like & share:

Microsoft Deployment Toolkit (MDT 8456) Released

The Microsoft Deployment Toolkit (MDT) has been released and the most current build (8456) which can be downloaded from the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10 version 1809 (10.1.17763.1) which is available for download on the Microsoft Hardware Dev Center.

The official MDT release note are available here:
https://docs.microsoft.com/en-us/sccm/mdt/release-notes

Some of the significant changes in this update include:

  • Supported configuration updates
    • Windows ADK for Windows 10, version 1809
    • Windows 10, version 1809
    • Configuration Manager, version 1810
  • Major changes
    • Nested task sequence support for LTI scenario
    • Modern language pack supportNote 1
    • Support for Configuration Manager version 1810Note 2
    • IsVM evaluates to False on Parallels VMs
    • IsVM = False when VMware VM is configured with EFI boot firmware
    • Gather doesn’t recognize All-in-One chassis type
    • MDT doesn’t automatically install BitLocker on Windows Server 2016
    • BDEDisablePreProvisioning typo in ZTIGather.xml

Check out Johan Arwidmark’s “A Geeks Guide for upgrading to MDT 8456” blog post for steps to upgrade MDT as a standalone and in ConfigMgr.

The following post provides some information on How to get help with MDT, in case you need it.

Please like & share:

Windows ADK 1809 For Windows 10 Now Available with Add-On

With the release of Windows 10 version 1809, the following tool to support this latest Windows 10 build, Windows Assessment and Deployment Kit (ADK) version 1809 is now available.
You can download it from: Windows 10 Assessment and Deployment Kit (ADK).

NOTE: There is a new change with this ADK which requires an add-on installation to include Windows PE.

Starting with Windows 10, version 1809, Windows Preinstallation Environment (PE) is released separately from the Assessment and Deployment Kit (ADK). To add Windows PE to your ADK installation, download the Windows PE Addon and run the included installer after installing the ADK. This change enables post-RTM updates to tools in the ADK. After running the installer for the WinPE add-on, the WinPE files will be in the same location as they were in previous installs of the ADK.

See Download and install the Windows ADK and ADK tools to get the ADK and WinPE add-on.

Johan Arwidmark has written a nice PowerShell script to automate the installation of the Windows ADK and Windows PE Add-On. You can grab it from his script repository on GitHub. This is very useful.

The Windows ADK is also available to Windows Insiders. Join the Windows Insider Program to get the Windows ADK Insider Preview.

The latest version of the Windows ADK includes:

  • The Windows Assessment Toolkit and the Windows Performance Toolkit to assess the quality and performance of systems or components.
  • Deployment tools such as WinPE, Sysprep, DISM and other tools that you can use to customize and deploy Windows 10 images.

Learn more about Windows ADK v1809 for Windows 10.

Please like & share:

ADMX Template For Windows 10 April 2018 Update (1803) Now Available

On April 30, 2018, Microsoft released the Windows 10 April 2018 Update (1803) build to customers worldwide. The following tools to support this latest release has been made available, which includes Windows 10 Administrative Templates (.ADMX), Windows Assessment and Deployment Kit (ADK), and the Remote Server Administration Tools (RSAT) for Windows 10 April 2018 Update.

Windows 10 Administrative Template (.ADMX)

Remote Server Administration Tools for Windows 10 (RSAT)

Windows 10 Assessment and Deployment Kit (ADK)

Microsoft Office 2016 Administrative Templates and Office Customization Tool is also available for download.

Follow @Hoorge on Twitter and join Tech Konnect on Facebook and Twitter to stay current on technology related matters.

Please like & share:

Remote Server Administration Tools (RSAT) For Windows 10 v1803

The latest version of the Remote Server Administration Tools (RSAT) for Windows 10 April 2018 Update v1803 have been released. The download is available here. You will find the following download files available for version 1.0 corresponding to x86 or x64 Operating Systems:

  • WindowsTH-RSAT_WS_1803-x64.msu (95.1MB)
  • WindowsTH-RSAT_WS_1803-x86.msu (69.9MB)
  • WindowsTH-RSAT_WS2016-x64.msu (92.3MB)
  • WindowsTH-RSAT_WS2016-x86.msu (69.5MB)

See here if you would like to determine if a computer is running 32-bit or 64-bit Windows OS.

Additional Information:

When to use WS_1803 RSAT Package: When managing Windows Server, version 1803 or Windows Server, version 1709
When to use WS2016 RSAT Package: When managing Windows Server 2016 or previous versions

Known Issues that may impact RSAT functionality:

Issue: DNS Tools missing
Impact: WS_1709 RSAT package users
Resolution: Use the WS_1803 or WS2016 RSAT package or apply this workaround

Issue: Cannot turn off individual RSAT components
Impact: WS_1803 and WS_1709 RSAT package users on Windows 10 1803/1709 (April 2018 Update/Fall Creators Update)
Resolution: Use the WS2016 RSAT package on Windows 10 1607 (Anniversary Update)

Issue: Tabs missing from MMC Properties
Impact: Windows 10 clients before 1607 (Anniversary Update)
Resolution: Update to the latest version of Windows 10 client and reinstall RSAT

Issue: Shielding Data File Wizard cannot create shielding data files
Impact: WS_1709 RSAT package users on Windows 10 1709 (Fall Creators Update)
Resolution: Use the WS_1803 RSAT package on Windows 10 1803 (April 2018 Update), or use the WS2016 RSAT package on Windows 10 1607 (Anniversary Update) to create shielding data files for Windows shielded VMs, or the built-in RSAT tools in Windows Server, version 1709 to create shielding data files for both Windows and Linux shielded VMs.

Issue: Template disks created from the Template Disk Wizard do not boot
Impact: WS_1709 RSAT package users on Windows 10 1709 (Fall Creators Update)
Resolution: Use the WS_1803 RSAT package on Windows 10 1803 (April 2018 Update), or use the WS2016 RSAT package on Windows 10 1607 (Anniversary Update) to create template disks for Windows shielded VMs, or the built-in RSAT tools in Windows Server, version 1709 to create shielding data files for both Windows and Linux shielded VMs.

Follow me (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

Windows ADK 1803 For Windows 10 Now Available

With the release of Windows 10 version 1803, the following tool to support this latest Windows 10 build, Windows Assessment and Deployment Kit (ADK) version 1803 is now available.
You can download it from: Windows 10 Assessment and Deployment Kit (ADK).

Note: You must use Windows 10 build 1803 with this version of the ADK.
The Windows ADK is also available to Windows Insiders. Join the Windows Insider Program to get the Windows ADK Insider Preview.

The latest version of the Windows ADK includes:

  • The Windows Assessment Toolkit and the Windows Performance Toolkit to assess the quality and performance of systems or components.
  • Deployment tools such as WinPE, Sysprep, DISM and other tools that you can use to customize and deploy Windows 10 images.

Learn more about Windows ADK v1803 for Windows 10.

 

Please like & share:

Microsoft Deployment Toolkit (MDT 8450) Released

The Microsoft Deployment Toolkit (MDT) has been released and the most current build (8450) can be downloaded from the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10 version 1709 (10.1.16299.15) which is available for download on the Microsoft Hardware Dev Center.

Some of the significant changes in this update include:

  • Supported configuration updates
    • Windows ADK for Windows 10, version 1709
    • Windows 10, version 1709
    • Configuration Manager, version 1710
  • Quality updates
    • Win10 Sideloaded App dependencies and license not installed
    • CaptureOnly task sequence doesn’t allow capturing an image
    • Error received when starting an MDT task sequence: Invalid DeploymentType value “” specified. The deployment will not proceed
    • ZTIMoveStateStore looks for the state store folder in the wrong location causing it to fail to move it
    • xml contains a simple typo that caused undesirable behavior
    • Install Roles & Features doesn’t work for Windows Server 2016 IIS Management Console feature
    • Browsing for OS images in the upgrade task sequence does not work when using folders
    • MDT tool improperly provisions the TPM into a Reduced Functionality State (see KB 4018657 for more information)
    • Updates to ZTIGather chassis type detection logic
    • Upgrade OS step leaves behind SetupComplete.cmd, breaking future deployments
    • Windows 10 ADK 1607 and later UEFI boot issue on some hardware
    • Includes updated Configuration Manager task sequence binaries

The following post provides some information on How to get help with MDT, in case you need it.

Please like & share:

Windows ADK 1709 For Windows 10 Now Available

With the release of Windows 10 version 1709, the following tool to support this latest Windows 10 build, Windows Assessment and Deployment Kit (ADK) version 1709 is now available.
You can download it from: Windows 10 Assessment and Deployment Kit (ADK).

Note: You must use Windows 10 build 1709 with this version of the ADK.
The Windows ADK is also available to Windows Insiders. Join the Windows Insider Program to get the Windows ADK Insider Preview.

Update: April 6, 2017
** Known Issues for ADK 1703 **
ADK Drivers don’t install on systems with secure boot enabled:
Drivers on the ADK Deployment tools will not install on systems with Secure Boot (SB) enabled.  To work around the issue, disable SB on these systems.This only impacts systems with Secure Boot enabled. More info here!

Follow me (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share: