Archive for 'Kinda Virtual'

confused

I always thought of my site as a public notepad. I guess I have once again regressed  back to putting notes in Notepad.exe and putting URLs and binaries to a web drive that no one, except perhaps me, benefits of.

It’s not like I’ve been personally doing anything fancy, I’m just gathering and building upon other peoples achievements. I’m having a bit of a rough time as my interest sphere is quite over encompassing and feeling a bit uncertain of where to at technology wise – what to consult, what to advice…I’m not sure, I’m confused and I’m undecided. Certainly my work-life points me to a certain direction, and that’s a relief, but at the same time, real-life and autistic interest point to a much broader direction.

That’s my random thought :)    

 

This yet another dump of old stuff :-)

Over the years there have been a lot of talk about tuning the Visual Effects settings in a Terminal Server environment, more recently the same talk in XP VDI scenarios. I guess I never quite understood the fuzz, except that the common suggestion of VisualFXSetting”= (your preference) doesn’t really do anything

For clarification, this is what I’m talking about:

My Computer | Properties | Advanced
-> Performance | Settings | Visual Effects

Here’s a deliverable for some customer some time ago.
Oh yeah, it’s not my batch. I found the batch when I resarched the matter. I made slight modifications to meet the demand.  All credit to the original author.

Vm, Vm, My Ware!

I remember VMware since 1999 until today. Great software, overall the best platform, even today. Now, times have changed. Being overtaxed by VMware in the data center one has to look for alternatives.

Throw it all over me, throw in the few. We have the XEN, Hyper-V and emerging KVM.

In basic we have the ~80-90 percent Widows with some RHEL and SLES thrown in the mix, the others are quite absent (or not v-candidates) in the enterprise. This leaves with a simple conclusion that the XEN, Hyper-V and KVM trio have good run in the specific rather than in the overall run – with a price mark closer to affordable.

As a technical guy I feel sadness.

In my rationale I’ll suggest to put certain offloads to XEN for performance (X->H-V waiting (?)), Use Hyper-V for all other offloads. Watch the KVM space, watch every space.

citrusDid you know that Citrix was originally supposed to be Citrus? Well, the name was already taken but that didn’t hinder them from, eventually, turning into sour. Anyhow that’s not the topic here. Broken WMI is, and that overlay product on top of TS/RDS commonly referred to as Citrix. 

//Update
Found an official Citrix article (ctx119767)  So now I might just go ahead and WMI myself silly ;-)

Original reference from Citrix Forums, courtesy of all.

Here’s some sample code (totals)  –> CitrixLicenseStatus

With Remote Desktop Connection 6.1 (RDC) some things have changed.
That you now need to use mstsc /admin to connect to the console session is common knowledge….
However, when using .RDP files we used to add “connect to console:i:1″ in the .RDP to connect to the console session, well turns out that this no longer works….

Long stroy short, here’s what you need to do:

Before…
mstsc /console = “connect to console:i:1″ in .RDP file

After…
mstsc /admin = “administrative session:i:1″ in .RPP file

A nice list of troubleshooting tools over at citrx.com

Read more here

As most of you already know, server cloning with PS4 isn’t the same walk in the park as it was with previous versions. I personally recommend against cloning PS4 boxes, but then again I know people are still doing it for various reasons…So, I decided to post my PS4 post cloning script to the community ;-) Do whatever you want with the script.

Also check out this article CTX107406

Ok, so I’m not a big fan of Citrix Access Gateway.
Anyways, today I had the sudden feeling I would like to install the damn thing on my laptop under vmare 5.5
Check this vmware forums article for details

Here’s a nice pic of CAG running in my vmware (the desktop is just black and stuff, so the pic is from the web gui)

cag

The key to get the thing running is VMware Gateway

See below for VMware Gateway and my working vmx file:

 
When you’re running published applications on MetaFrame then you’ve might have encountered the problem that child processes (and sometimes even the main executable) will be left running.

Read more here or check the solution below:

  1. HKLMSYSTEMCCCControlCitrixwfshellTWI
  2. Value Name:LogoffCheckSysModules
  3. Type:REG_SZ
  4. String:MyAppName.exe

NOTE:
Enter the list of executable names with a comma and NO spaces between them, for example:
App1.exe,app2.exe,app3.exe

//Edit (090102):  Tim Mangan also have a nice tool called LaunchIt 
Read more here
Backup copy here

Ok, so I read this in a book, and also found the the same quoted in Terminal Server news groups, so I guess It’s fair use to quote the stuff…

If remote users are able to type very quickly, screens on Terminal Services clients sometimes tend to hang. This is true for both the RDP and the ICA protocol. To improve terminal server response times, it is possible to change the time that the terminal server waits until it transmits buffered data packages. The shorter this time is, the smaller the data packages are. The time is set via the OutBufDelay registry value. This method increases the frequency with which the data packages are sent. However, this change also gives rise to a slightly increased network load.

The output buffer settings are always related to a protocol as it was created in the Terminal Services Configuration. For RDP, these two registry paths are relevant:

  1. HKLMSystemCurrentControlSetControlTerminal ServerWdsRdpwdTDStcpOutBufDelay
  2.  
  3. HKLMSystemCurrentControlSetControlTerminal ServerWinStationsrdp-tcpOutBufDelay

The parameters specify the number of milliseconds that a terminal server buffers data before transmitting it to the client. The default value is 0×64; half of that value should improve overall system response.

The ICA protocol registry entries are saved under

  1. HKLMSystemCurrentControlSetControlTerminal ServerWdsIcawdTDStcpOutBufDelay
  2.  
  3. HKLMSystemCurrentControlSetControlTerminal ServerWinStationsICA-tcpOutBufDelay