I’m looking for help here.
The image (click to embiggen) you see here is a screen capture of one of my virtual machines suffering some form of graphic corruption. It should look like this. This happens often enough now that it is seriously irritating. I can make it go away by closing VMRC and reconnecting to the server, but I’d rather not have to do so several times a day (sometimes multiple times an hour).
I’m running Virtual Server 1.1.603.0 EE R2 SP1, and all my VMs have Virtual Addition version 13.813 installed. The VMRC client which came with R2 SP1 is version 1.1.603.0.
The same corruption is visible from machines with ATI and NVidia graphics cards, running XP SP2, Vista or Server 2003.
So - why is this happening, and how can I stop it?
Anyone?
Most people who know me well were probably taking bets about how much time would elapse from Jobs’ unveiling of the MacBook Air and one ending up in the digital magpie like hands of a certain geek.
Well, there it is. Earlier than most and for good reason… Continue reading ‘My MacBook Air’
This is a bit of code I wish I’d found sooner. There is a - it seems mostly undocumented - feature of the ldap provider in Server 2003 that allows you to form an ldap query just on the SID of an account:
bindSid = "LDAP://<sid =" & SID & ">"
set oVal = GetObject(bindSid)
Result = oVal.Get("cn")
set oVal = Nothing
So if you have a list of SIDs and want to translate them into meaningful account names, this will do it without relying on using WMI - which on a lot of secure networks is locked down (or at least should be!).
Why do I need this? It’s a part of a larger script I’m writing that will archive specific Group Policy Objects from the \SYSVOL\<domainname>\Policies\ folder of a PDCe. One of the files in a GPO is the GptTmpl.inf file which gives a list of the User Rights Assignments (SeBackupPrivilege, SeShutdownPrivileg etc) along with the SIDs of the accounts that have been given those privileges (e.g. S-1-5-19). I wrote a script that reads the SIDs and queries the DC for the account names. This code fragment works more reliably (and I think faster) than the WMI calls I was previously using.
Recent Comments