Month: April 2017

VSphere tip: removed VM from a datastore cluster but rules still applying to it

Found this issue last week and wanted to note it for future reference for myself (getting old and best way for me to remember as much as anyone:)).

So removed a VM from one of our datastore clusters. Now this machine had an affinity rule applied to it which i wasn’t aware of. Interestingly found i couldn’t remove the rule even  wanted to from the datastore cluster.

Turns out the solution was slightly inelegant but it worked.

i) Moved said VM back into the datastore cluster

ii) In the vSphere client (or web) browse to the datastore cluster.

iii) Click the Manage tab and select Settings

iv) Under Configuration, click Rules

v) Pick out your offending rule you want deleted and click Remove and click Ok

Advertisements

Enabling logging for troubleshooting app-v issues in your citrix environment

When troubleshooting App-v issues in your citrix environment one of the first usual port of calls will be to enabling logging.

To enable Studio and VDA logs used for App-V, you must have administrator privileges. You will also need a text editor such as Notepad.

To enable the Citrix Studio logs:

  1. Create the folder C:\AppvLogs.
  2. Navigate to C:\ProgramFiles\Citrix\StudioAppVIntegration\SnapIn\Citrix.Appv.Admin.V1. Open CtxAppvCommon.dll.config in a text editor and uncomment the line: <add key =”LogFileName” value=”C:\AppvLogs\log.txt”/>
  3. Restart the Broker service to start logging.

To enable VDA logs:

  1. Create the folder C:\AppvLogs.
  2. Go to C:\ProgramFiles\Citrix\ Virtual Desktop Agent. Open CtxAppvCommon.dll.config in a text editor and uncomment the following line: <add key =”LogFileName” value=”C:\AppvLogs\log.txt”/>
  3. Uncomment the line and set the value field to 1: <add key =”EnableLauncherLogs” value=”1″/>
  4. Restart the machine and logging should be working

Remote nano server admin : quick few commands needed to get you access to box

Recently was given a project with a proof of concept involving the use of Windows 2016 nano servers (don’t even know if that’s there official title :)). Anyhow as not quite your conventional windows servers took a wee bit of lurking to find what i needed to get access.

Bit of background:

So Nano server comes with a rebuilt subset of Windows Powershell and they’ve called it Core PowerShell. Feature-set wise seems to have everything i need, full remoting capability, language compatibility etc.

As it does come with Windows Powershell Remoting it indeed is our gateway to access the server.

Requirements

i) Need to have administrator level privileges to the Nano Server

ii) Add its IP to the managed machine’s trusted hosts(assuming 192.168.1.1 is the Nano Server’s IP) to do

PS c:\> set-Item WSMAN:\\localhost\Client\TrustedHosts “192.168.1.1”

Next you can start an interactive remoting session:

PS C:\NanoServer> $ip = “192.168.1.1”

PS C:\NanoServer> $user = “Administrator”

PS C:\NanoServer> $Enter-PSSession -ComputerName $ip -Credential $user

After that you are good to go, can run commands as if you were entering directly on the nano server console eg

[192.168.1.1]: PS c:\users\test\documents> ipconfig

To get the full list of commands available

[192.168.1.1]: PS c:\users\test\documents> Get-Command -CommandType Cmdlet

 

Quick and handy AppDNA tip: Experiencing locks running analysis? here’s where to release them

Doing some bulk analysis of apps recently and server experienced a crash. After coming back up and trying to do a re-analysis of the apps i got a “task locked” message trying to re-run.

Luckily didn’t need to chase up a DBA to release the lock from the SQL console option handily available from AppDNA console. To do click Administration | Tasks and in there will see the option to Release Locks click the offending task and release and your good to go.