Apr 12 2013

VMware Horizon Workspace Management URLs

URL Function Explanation
https://HorizonWorkspaceFQDN/admin Administrator Web interface (Active Directory user) Manage the Catalog, users and groups, entitlements, reports, etc. (Login as Active Directory user with administrator role.)
https://HorizonWorkspaceFQDN/SAAS/login/0 Administrator Web interface (non-Active Directory user) Use this URL if you cannot login as the Active Directory user with the administrator role. (Log in as an administrator using the username admin and the password you set during configuration.)
https://HorizonWorkspaceFQDN/web Web Client (end user) Manage files, launch applications, or launch View pools. (Login as an Active Directory user or virtual user.)
https://ConnectorHostname/hc/admin/ Connector Web interface Configure additional ThinApp settings, View pool settings, check directory sync status, or alerts. (Log in as an administrator using the password you set during configuration.)
https://ConfiguratorHostname/cfg Configurator Web interface See system information, check modules, set license key, or set admin password. (Log in as an administrator using the password you set during configuration.)

 

See also http://virtualisedreality.com/2013/04/11/horizon-workspace-management-urls/

Permanent link to this article: http://ituda.com/vmwarehorizon-workspace-management-urls/

Mar 19 2013

How to install VMware Horizon Mirage

Below are the notes I created while I was installing VMware Horizon Mirage for a test environment.More information on the product can be found on the VMware website

Preperation

  • Download the software from the VMware website
  • Create the mirage server
    • Server Name: mirageserver
    • Details: Windows 2008 R2 64 bit: 4 CPU, 8 GB RAM
    • Change drive letter of CD-Rom to drive Z:
    • Add 2nd HDD of 500 GB (thin provisioned) and map to drive D:
      • System Label: Mirage
    • Disable Windows Firewall
    • Database for Mirage:
      • SQL 2008 R2 Express
      • Install locally on mirageserver
      • Supports up to 5000 mirage users
      • Needs +/- 1 GB per 1000 users
  • Create a mirage service account in Active Directory:
    • DOMAIN\horizonserviceaccount
  • Create Global Security Group:
    • DOMAIN\gs-mirageadmins
    • Members: DOMAIN\horizonserviceaccount
  • Create Domain Local Security Group
    • DOMAIN\ls-mirageadmins
    • Members: DOMAIN\gs-mirageadmins, DOMAIN\horizonserviceaccount
  • Add DOMAIN\gs-mirageadmins to the local administrator group of server mirageserver
  • NOTE:
    • Because Mirage will not search recursively through “groups of groups”, user accounts need to be member of the Mirage Administrator Group specifically, and not through the means of another group membership.
    • Built-in AD groups cannot be used as a Mirage Administrator group

Installation

  • Install Microsoft .NET 3.5 Framework SP1 on mirageserver
    • START – Control Panel – Turn Windows features on or off
    • Server Manager – Features – Add feature
    • Select .NET Framework 3.5.1 feature
    • Select “Add Required Role Services”
    • Add features Wizard – Select Features
      • Click NEXT
    • Add features Wizard – Web Server (IIS)
      • Click NEXT
    • Add features Wizard – Select Role Services
      • Select “Web Server – Common HTTP features”
      • Select “Application Development – ASP .NET”
      • Select “Add Required Role Services”
      • Select all options under  “Management Tools”
      • Click NEXT
    • Add features Wizard – Confirm Installation Selections
      • Click INSTALL
    • Add features Wizard – Progress
    • Wait for install to finish
    • Add features Wizard – Installation Results
      • Verify Installation results
      • Click CLOSE
  • Install SQL Server 2008 R2 Express on mirageserver
    • Launch SQLEXPRWT_x64_ENU.exe
    • Installation screen
      • Click “New installation or add features to an existing installation”
        • License terms screen
          • Select “I accept the license terms”
          • Click NEXT
    • Feature Selection
      • Select All features
      • Shared feature directory: D:\Program Files\Microsoft SQL Server\
      • Shared feature directory (x86): D:\Program Files (x86)\Microsoft SQL Server\
      • Click NEXT
    • Instance Configuration
      • Named instance: SQLEXPRESS
      • Instance ID: SQLEXPRESS
      • Instance root directory: D:\Program Files\Microsoft SQL Server\
      • Click NEXT
    • Server Configuration:
      • Service Accounts:
        • SQL Server Database Engine:
          • Account Name: NT AUTHORITY\NETWORK SERVICE
          • Startup Type: Automatic
        • SQL Server Browser:
          • Account Name: NT AUTHORITY\LOCAL SERVICE
          • Startup Type: Automatic
        • Click NEXT
    • Database Engine Configuration
      • Authentication Mode: Windows authentication mode
      • Specify SQL Server Administrators
        • Add IM\dg-mir-admins
        • Add current user
        • Click NEXT
    • Error Reporting
      • Click NEXT
    • Installation Process
      • Wait for install to finish
    • Complete
      • Click CLOSE
  • Create Directory for “Mirage Single Instance Store” on mirageserver
    • D:\Mirage_SIS
    • Enable compression of this folder
  • Create Directory for “Mirage Network Cache” on mirageserver
    • D:\Mirage_Network_Cache
    • Do not enable compression of the folder
  • Install Mirage Management Server on mirageserver
    • Launch mirage.management.server.x64.xxxxx.msi
      • Welcome screen
        • Click NEXT
      • End-User License Agreement screen
        • Select “I accept the terms…”
        • Click NEXT
      • Mirage Management Server Configuration screen
        • SQL Server: mirageserver
        • SQL Instance: SQLEXPRESS
        • Select “Create new storage areas”
        • Name of the mirage cluster storage folder: D:\Mirage_SIS
        • Click NEXT
      • Mirage Services Account Configuration screen
        • Select “Use specific user”
          • Fully qualified name of the account…: DOMAIN\horizonserviceaccount (should have db_owner rights to the database)
          • Fully qualified name of the administrators group: DOMAIN\ls-mirageadmins
          • Click NEXT
      • Ready to install screen
        • Click INSTALL
      • Click FINISH
  • Install Mirage Management Console on mirageserver
    • Launch mirage.management.console.x64.xxxxx.msi
    • Welcome screen
      • Click NEXT
    • End-User License Agreement screen
      • Select “I accept the terms…”
      • Click NEXT
    • Ready to install …screen
      • Click INSTALL
    • Click FINISH
  • Install Mirage Server
    • Launch mirage.server.x64.xxxxx.msi
    • Welcome screen
      • Click NEXT
    • End-User License Agreement screen
      • Select “I accept the terms…”
      • Click NEXT
    • Enter Mirage Server Settings
      • SQL Server: mirageserver
      • SQL Instance: SQLEXPRESS
      • Select “create new local cache area”
      • Name of the Mirage Server local cache folder: D:\Mirage_Network_Cache
      • Size of local cache in MB: 102400
    • Enter Mirage Service Account
      • Select “Use specific user”
        • Fully qualified name of the account…: DOMAIN\horizonserviceaccount
    • Ready to install …screen
      • Click INSTALL
    • Click FINISH
  • Install Mirage File Portal
    • Launch mirage.WebAccess.x64.xxxxx.msi
    • Welcome screen
      • Click NEXT
    • End-User License Agreement screen
      • Select “I accept the terms…”
      • Click NEXT
    • Mirage web access backend configuration
      • Leave default selection (install everything)
      • Click NEXT
    • VMware Mirage Management Server location
      • Type: localhost
      • Click NEXT
    • Ready to install …screen
      • Click INSTALL
    • Click FINISH
  • Reboot Server

Upgrade procedure

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

Permanent link to this article: http://ituda.com/how-to-install-vmware-horizon-mirage/

Feb 14 2013

How to delete applications from Horizon Application Manager

  • Delete the app folder from CIFS share
  • Login as org admin and delete the app from Horizon Applications tab
  • Login to the connector virtual machine as root
  • Stop the repo service using the command “/opt/likewise/bin/lwsm stop thinapprepo”
  • Delete the repo db using the command “rm /var/lib/vmware/tam/repo/repodb”
  • Start the repo service using the command “/opt/likewise/bin/lwsm start thinapprepo”
  • Re-scan at the connector
  • Verify the app is gone and then you should be able to re-add that same app again as the GUID are gone from the sqlite repodb.

Permanent link to this article: http://ituda.com/how-to-delete-applications-from-horizon-application-manager/

Dec 13 2012

VMware vCenter Orchestrator Instructional Videos

 

Read the rest of this entry »

Permanent link to this article: http://ituda.com/vmware-vcenter-orchestrator-instructional-videos/

Dec 05 2012

How to customize the View Portal for Client Download with VMware View 5.1

In some organizations end-users do not have administrative rights on their machines in order to install the VMware View Client.

In order to give these users the ability to access their VMware View Virtual Machines you could provide them with a thinapped version of the VMware View Client and make it available as a download link on your connection server.

This can be very handy for organizations that provide access for external consultants to the corporate environment through VMware View virtual desktops, where the external consultant is using a laptop provided by his own company.

For instructions on how to thinapp the VMware View client see my previous post.

Procedure

  • Log on to your VMware View Connection server
  • Create the directory C:\Program Files\VMware\VMware View\Server\broker\webapps\downloads
  • Copy your thinapped version of the VMware View Client to C:\Program Files\VMware\VMware View\Server\broker\webapps\downloads
  • Create Directory C:\ProgramData\VMware\VDM\portal
  • Copy C:\Program Files\VMware\VMware View\Server\extras\PortalExamples\portal-links.properties to C:\ProgramData\VMware\VDM\portal
  • Copy C:\Program Files\VMware\VMware View\Server\extras\PortalExamples\portal.properties to C:\ProgramData\VMware\VDM\portal
  • Edit C:\ProgramData\VMware\VDM\portal\portal-links.properties and change the following lines
# TODO: Update links to point to vmware.com alias once available
link.win=https://www.vmware.com/info?id=1109#win
link.mac=https://www.vmware.com/info?id=1109#mac
link.linux=https://www.vmware.com/info?id=1109#linux
link.unknown=https://www.vmware.com/info?id=1109

by

# TODO: Update links to point to vmware.com alias once available
link.win=https://<yourconnectionserverurl>/downloads/VMware View Client.exe
link.win.1=https://www.vmware.com/info?id=1109#win
link.mac=https://www.vmware.com/info?id=1109#mac
link.linux=https://www.vmware.com/info?id=1109#linux
link.unknown=https://www.vmware.com/info?id=1109
  • Edit C:\ProgramData\VMware\VDM\portal\portal.properties and hange the following lines
# keys based on key names in portal-links.properties
text.win=View Client for Windows

by

# keys based on key names in portal-links.properties
text.win=Thinapped View Client for Windows
text.win.1=Installable View Client for Windows
  • Reboot yur connection server

References & Documentation

Go to the VMware View 5.1 Evaluator’s Guide and search for Evaluation Tasks for View 5.1 New Features, then View Client Unbundling.

See also http://blogs.vmware.com/euc/2012/05/vmware-view-5-1-client-download-portal-customizing.html

 

Permanent link to this article: http://ituda.com/how-to-customize-the-view-portal-for-client-download-with-vmware-view-5-1/

Nov 07 2012

Thinapp Instructions for VMware View Client

14 DEC 2012: UPDATED FOR VMWARE VIEW CLIENT 5.1.2 (BUILD 937772)

Environment

Capture & build machine:

  • Windows XP SP3 – 32 bit (fully patched)
  • Install latest VMware Thinapp version (4.7.2 at the time of writing)
  • Make sure the capture & build machine has Internet access
  • Download the latest VMware View client for 32-bit Windows from http://www.vmware.com/go/viewclients
  • Copy the VMware View Client installation files to the capture & build machine
  • Install VMware Tools if they are not yet installed
  • Uninstall Microsoft Microsoft Visual C++

 

Prescan

Launch Thinapp Setup Capture

Click “Prescan”

When the prescan is finished minimize the Setup Capture wizard

 

Application installation

Install VMware View Client

  • Custom setup: Do not install “USB redirection” component
  • Default View Connection Server: leave blank or type your preferred View connection server
  • Enhanced Single Sign-On: leave defaults
  • Create Shortcuts: Only select “Desktop”
  • When the installation finished there is no need to restart as drivers are not applicable for this package

Launch View Client

Select Options

Check “Autoconnect: Always connect to this server at startup”

 

PostScan

Maximize the Setup Capture wizard

Click “Postscan”

Entry Points:

  • Select only “VMware View Client.exe”
  • Click “Next”

Manage with Horizon:

  • Click “Next”

Groups:

  • Select “Everyone”
  • Click “Next”

Isolation:

  • Select “Full write access..”
  • Click “Next”

Sandbox location:

  • Select “User Profile”
  • Click “Next”

Quality Assurance Statistics:

  • Select “No – Do not send..”
  • Click “Next”

Project Settings:

  • Inventory name: VMware View Client
  • Project location: choose location where you want to store the thinapped application
  • Click “Next”

Package Settings:

  • Do not select “Use separate .DAT file”
  • Do not select “Generate MSI package”
  • Click “Save”

Ready to build

  • Click “Open Project Folder”
  • Delete the below from the project folder

%Common AppData%\VMware\VDM\logs

> debug and log txt files

%Local AppData%\VMware\VDM\logs

> debug and log txt files

%Program Files Common%\VMware

> VMware Virtual Printing (this feature is not available in ThinApp virtual application)

%ProgramFilesDir%\VMware\VMware View\Client\bin

wswc_de_de_407.dll

wswc_fr_fr_40c.dll

wswc_ja_jp_411.dll

wswc_ko_kr_412.dll

wswc_zh_cn_804.dll

%ProgramFilesDir%\VMware\VMware View\Client\bin\messages

> all folders EXCEPT “en”

%ProgramFilesDir%\VMware\VMware View\Client\DCT

%ProgramFilesDir%\VMware\VMware View\Client\extras

> vdm_client.adm

%SystemRoot%\Installer

  • Click “Edit Package.ini”

Change Compressiontype=None to CompressionType=Fast

Change MSIStreaming=0 to MSIStreaming=1

Add the following lines just before the [Isolation] section

[Filelist]

ExcludePattern=*.bak,*.msi.*.mst,*.cab,*msp

Click “Build”

Click “Finish”

 

The end result is a single executable file of +/- 56 MB

Permanent link to this article: http://ituda.com/thinapp-instructions-for-vmware-view-client/

Oct 26 2012

VMware vSphere 5.1 now supports VMware View 5.1.x

A few weeks ago I wrote an article mentioning that VMware vSphere 5.1. did not support VMware View.

Well, this has changed now. VMware released a patch which resolves this incompatbility. See also KB article 2035268.

See also the VMware Product Interoperability Matrix

Permanent link to this article: http://ituda.com/vmware-vsphere-5-1-now-supports-vmware-view-5-1-x/

Sep 12 2012

VMware vSphere 5.1 is not supported with any version of VMware View

 

VMware View is currently not supported for vSphere 5.1. So if you are were planning to upgrade, do not do it yet, just wait for an official note from VMware that it is fully supported.

 

If you already upgraded your VMware View environment to vSphere 5.1, be aware that it is currently not supported due to the release note listed at the link below.
However, VMware View should remain stable as long as you do not attempt to enable the View Storage Accelerator (CBRC, the ‘Use host caching’ option)

https://www.vmware.com/support/vsphere5/doc/vsphere-esx-vcenter-server-51-release-notes.html#clientissues

 

VMware is currently working on a solution, but there is no exact date known when a fix will be available.

 

 

 

Permanent link to this article: http://ituda.com/vmware-vsphere-5-1-is-not-supported-with-any-version-of-vmware-view/

Sep 12 2012

Best practices for installing vCenter Server 5.1

VMware just release a KB article explaining the best practices for installing vCenter Server 5.1.

http://kb.vmware.com/kb/2021202

Permanent link to this article: http://ituda.com/best-practices-for-installing-vcenter-server-5-1/

Aug 24 2012

VMware View 5.x – Reset/Refresh/Rebalance/Recompose

Reset

  • Shuts down the desktop and restarts the session. The shutdown/logoff/disconnect is non-graceful

Refresh

  • Restores the OS disk to it’s original state and size
  • Does not effect View Composer persistent disks

Rebalance

  • Evenly redistributes linked-clone desktops among available datastores.
  • A rebalance operation also refreshed the linked clones

Recompose

  • Simultaneously updates all the linked clone desktops anchored to a parent virtual machine.
  • It is similar to a refresh operation, however a recompose allows you to choose a new snapshot within the existing parent virtual machine, or a completely new parent virtual machine.

 

Permanent link to this article: http://ituda.com/vmware-view-5-x-resetrefreshrebalancerecompose-2/

Older posts «

Switch to our mobile site