About Terminal Server, Citrix, Delphi and other stuff
If you have read my earlier blogs about the RNS 510 then you may know I have been working on creating custom startup logo’s for some time.
For some time now I know how the images are encoded and decoded between Windows bitmap and the native RNS 510 image format.
Recently I identified the checksums in the image data, and the differing parameters for the Seat, Skoda and VW versions of the RNS 510 firmware.
In part 1 we saw that a corrupted rule made the Mailbox Move fail.
I wanted to know if I had really a corrupted mailbox or maybe even corruption in the store or another problem.
So in this part I will describe how to break down the Mailbox Move Log.
First go to the Failed Move Request and select Properties:
I am currently working on a migration project from Exchange 2003 to Exchange 2010.
Most Exchange migration projects use Mailbox Moves to move the mailbox data to the new Exchange environment.
But there are some things I observed during Mailbox Moves (from Exchange 2003 to 2010) that are worth mentioning.
Today I was asked to assist in troubleshooting an Oracle Client (10g) installation. The installation halted very quickly with a java.lang.NullPointerException:
I didn’t notice it before but the new RNS 510 firmware (3810/3814/3816/3818) has a new startup logo for the Volkswagen firmwares:
I am currently creating a PowerShell script that creates a user with all needed Active Directory attributes, Exchange mailbox, (TS) Home- and Profile directories and so on.
In such a script you can easily get failures because of Active Directory replication.
Function below can be used to check if a given Username exists in Active Directory:
$objDomain = New-Object System.DirectoryServices.DirectoryEntry
$objSearcher = New-Object System.DirectoryServices.DirectorySearcher
$objSearcher.SearchRoot = $objDomain
$objSearcher.PageSize = 1000
$objSearcher.Filter = $strFilter
$objSearcher.SearchScope = "Subtree"
$colResults = $objSearcher.FindAll()
return [bool]($colResults -ne $null)
}
I wrote earlier about the startup logo’s on the Volkswagen RNS 510 navigation.
Today I can finally tell you that I succeeded!
I changed the startup logo to the logo from the MFD2 DVD as you can seen on this picture:
The Volkswagen RNS 315 Navigation has a builtin Bluetooth carkit which is disabled by default. I am not sure why, I presume this is done because VW also sells carkits that integrate into the MFD.
The builtin carkit can be enabled using VCDS like this:
Active Directory Altiris bug Citrix Dell Delphi Exchange Exchange2003 Exchange2010 Hewlett-Packard HP iOS Jailbreak Java LinkedIn Linux MSI MySQL Navigation Objects Office Outlook Passat PowerPoint PowerShell referall was returned RNS315 RNS510 SasLibEx script slow Terminal Server ThinApp TSAdmin TSAdminEx VBS VCDS Vista VMWare Volkswagen Windows PE WLAN Wordpress WTSWaitSystemEvent wts_event_flush
WP Cumulus Flash tag cloud by Roy Tanck requires Flash Player 9 or better.