jernstrom.org

Running a DotNet Framework 2.0 from a network share or an UNC path just plain doesn’t work. You get an error message such as the the one to the right.

I pretty much never thought much of it, because in some mysterious way I never encountered a situation where this might be an actual problem. Well. A couple a weeks ago a customer hit into this problem, and for a reason or another they really needed to run their application (not admodify.net!) from a network share.

Here’s a couple of links on the issue and remedy:

http://support.microsoft.com/kb/320268
http://msdn.microsoft.com/en-us/library/a0ke3k86(VS.71).aspx

However, for the brave one, here’s an example wildcard solution. Run it from a CMD prompt from within C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

caspol -m -ag 1 -url "file://\\*" FullTrust -exclusive on

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.

Did 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

Vista never was anything but the reincarnation of the Windows ME fiasco.

Windows 2008 (Vista ME, Server Edition) also took the hit, scarcely deployed and whenever possible discarded in favor of Windows 2003 R2.

That said. Again and again I find myself in the loosing minority, killer features never taking off, I killed a duck.

On the client side Seven beta is a no-brainer replacement of Vista ME (in corporate land – stay on XP, wait for 7). On the server side I wish that 2008 R2 can reinstate some trust so that we can move on.

ps. UAC is nowhere near reality. B1 sidebar replaced with pre-beta 6801 ditto, readily available elsewhere. x64 4801 backport is nowhere in the wild afaik.

Aside of the NTFS alternate data stream manipulation (aka. blocked content) that can be circumvented by GPO
User ConfigurationAdministrative TemplatesWindows ComponentsAttachment Manager there is the issue with CHM files over the network.

See http://support.microsoft.com/kb/896358

Got tired of the %20 in downloaded files…

mycmd

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

Allrite, so this is the way to implemt forms with
System.Web.Security.ActiveDirectoryMembershipProvider

sharepoint_v3_forms

…and this the way to do it with
System.Web.Security.SqlMembershipProvider (with roles)

sharepoint_v3_forms_sql

…you need to have the membership provider in web.config for central admin

A nice list of troubleshooting tools over at citrx.com

Read more here

Allrite, so I bought this LaCie Ethernet Disk mini 300GB to have as backup unit and to store some of the kids movies and some music. The damn thing however came delivered with fat32 filesystem (max file size=4gb but just 2gb over network + other shortcoming of fat32)

Now there was the option to format the thing with EXT3 file system; however that EXT3 thing would certainly not be readable from USB cable connection from my Windows thingies. Enter Ext2 (ext3 too!) driver for Windows and all is great again

Complete reading and writing access to files and directories of volumes with the Ext2 or Ext3 file system.
Supports features which are specific to the I/O-system of Windows: Byte Range Locks, Directory Notfication (so the Explorer updates the view of a directory on changes within that directory), Oplocks (so SMB clients are able to cache the content of files).
Allows Windows to run with paging files on Ext2 volumes.

Read more and download here
Backup copy here (v. 1.11a //090102)