Wednesday, June 21, 2017

VMware console won't open in Chrome after an update

So you are enjoying that shiny new version of chrome (59.0.3071.104 or higher) and realize that you can't open a VMware console any more.  It may or may not show you a flash error.  To fix, got to settings ->advanced -> content settings -> flash and click add.

Type in dns name of your Vcenter.  To do your entire domain, preface it with "[*.]" without the quotes just like in the example.


Good luck.


Tuesday, January 31, 2017

PVS Info to Environment Variables / Event Log Refreshed

In my old post I presented a Powershell startup script to grab some info from the PVS image and pump it into the eventlogs and environment variables for consumption.   I refreshed this for the VHDX disks and "Cache in Ram with overflow" cache type.  

Start by creating the event log from an elevated poweshell session by issuing the command:
New-EventLog -LogName Application -Source "Xenapp_Custom"

I run the script below in the local startup scripts on the PVS images.

------------PVS_Personality.ps1------------------------
$disk="ID not found"
$file="c:\personality.ini"

IF(Test-Path $File){
  $data=get-content $file
  Foreach ($line in $data) {
    if ($line.Contains("DiskName")){$iname=$line.replace("$","").replace("DiskName=","").replace(".vhdx","").replace(".vhd","")}
    if ($line.Contains("WriteCacheType")){$wc=$line.replace("$","").replace("WriteCacheType=","")}
    }


  switch ($wc)
  { 
  "0" {$wc1="PV"}
  "4" {$wc1="CD"}
  "6" {$wc1="CR"}
  "9" {$wc1="CRO"}
  "1" {$wc1="Server";Write-EventLog -LogName Application -Source "XenApp_Custom" -EntryType Error -EventID 911 -Message "PVS ALERT. VDisk is set to Cache on server.  Immediate action is required to prevent an outage if this is a PROD image. Image: $iname"}
default {$wc1="OTHER";Write-EventLog -LogName Application -Source "XenApp_Custom" -EntryType Warning -EventID 911 -Message "PVS ALERT. Nonstandard VDisk configuration has been detected. Image: $iname"}
}
  $disk=$iname+"_"+$wc1
  } 


ELSE 
  {$disk=$env:computername + "_Local"}

[Environment]::SetEnvironmentVariable("PVS_Disk",$disk,"Machine")
---------------END OF LINE------------

Thursday, January 26, 2017

Installing Adobe Acrobat Professional in a Sharee/Non Persistent Desktop Image Vmware / Citrix


Skip to end of metadata

Four things are required to successfully install and license Acrobat Professional for a shared desktop.

  1. The Adobe Acrobat Software
  2. The Adobe Provisioning Toolkit, Enterprise Edition (APTEE)
  3. The serial number for your product
  4. The Adobe Customization Wizard that matches your product version

Acquiring the pieces: 

Items 1-3 are obtained from the Adobe Licensing Website
Logon.  Downloads has the Software and the APTEE.  The serial number is located in "Retrieve Serial Numbers"
Item 4 can be located on the Adobe FTP site:

Creating the PROV.XML file.

The prov.xml contains the serial number and an encrypted license key.  It is generated by the APTEE executable adobe_prtk.exe.  An internet connected machine is required at this step.  No adobe products are needed other than the executable.
Open a command prompt and enter the following:
adobe_prtk.exe --tool=VolumeSerialize --generate --serial=<SERIAL NUMBER FROM ADOBE LWS> --regsupress=ss --eulasupress
Return Code 0 indicates sucess

Customize the Adobe Package

Install the Adobe Customization Wizard
Navigate to the MSI in the directory where you unzipped the Adobe Acrobat Download
Customize as required.  Save and exit.

Install in the gold image

Open a command prompt and navigate to the directory unzipped the Adobe Acrobat Download.  Issue the command:
Msiexec /i acropro.msi /t acropro.mst
This will run through the standard adobe install.  Hopefully the customizations will run and minimal input is required.  Do not do a first run at the point.
Copy the adobe_prtk.exe file and the prov.xml to the image.  I choose C:\programdata\adobe to store those files.
issue the command:
c:\programdata\adobe\adobe_prtk.exe --tool=VolumeSerialize --provfile= c:\programdata\adobe\prov.xml --stream
Open Adobe and click through any first run prompts and allow the app to remain open for a minute or two.
Seal and publish the image.

Sources: