This is just a quick post while i remember what ive done to solve the problem, i’ve spent quite amount of time troubleshooting this issue
and if i get the time, i will update it later on.
Scenario ->
1) Explorer.exe is published for your users to use (browsing shared folders, private folders, etc)
2) Main part of Office 2007 is installed locally on your golden XenApp image (win2k8)
3) A few applications like Visio, OneNote, Project are profiled and streamed to server
In this setup, i had a mix of normal pc’s and a bunch of new mac (airbooks) which ran both snow leopard and Windows 7.
It started out with the some users complaining about their danish published office applications switched to using US keyboard layout
and naturally i started testing (logged on with same user account) and found no issues at all. We tested a bit, playing around with the language bar
and the local region settings, and we found out that on the airbooks, on windows 7, it had 2 keyboard layouts installed (da-dk, and danish-apple)
My setup contains Windows 2008 R2 64bit Domain controllers, Windows 2008 SP2 64bit Citrix XenApp Servers, with Exchange 2007.
I restricted access to to prevent users from browsing though the c:\ – which forced me to use the administrative office 2007 gpo templates
I recently tried to install vSphere PowerCLI from VMware on my Windows 7 64-bit installation.
and i was met with the error message above.
theres probably multiple answers to solving this problem. some say that you need to run it as administrator permissions (doh) and some want you to change permissions on the
registry vmware path.
what almost worked for me was deleting the reg entry “HKLM\Software\VMware Inc” and then just retrying with the installation. i however, had to delete the entry
“HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.” for it to work.
First the good thing – I got a new laptop recently.. – and the bad thing – no serial port. Since i from time to time need to configure firewalls im in a big need of that.
anyway – a quick search oh my resellers website told me that i could buy one of these smart “Belkin…..” usb-to-serial adapters. which was Windows 7 certified (i just read it as – of course it works with windows 7 – go buy it! )
The next day i got it with mail – its actually better quality than expected, and it didnt took me long to hook it up. Now the next thing i expected,was for windows 7 to just search for a driver and install it like it did with most of my other hardware. instead it told me to *** off – and go find a driver myselfe.
to make a long story short – go google “Belkin F5U103vea” Vista for yourselfe, and you will quickly find out that – its either impossible to find, or your download link ends with …/super-driver-downloader-professional2010.exe.
It seems like those bastards from Belkin didnt bother to host a driver that works with their product – or link to one. It turns out (like alot of other hardware) that its rebranded.
its from a company called Prolific Technology inc. And its original name is “PL-2303 USB to Serial Bridge”
you can find it on this website or directly link
so to summarize this post….. fuck you belkin for wasting my time which i could have spent on youporn instead.
From time to time you or lvm arent perfectly good at cleaning up after youselves when adding/removing disks for one or another reason
and even though everything works, you get spammed with errors like.
This is what i get when i try to set up an Exchange 2007 mailbox on outlook 2007 using autodisover….
This is pretty much simple for most people, however i tend to wipe the howto from my memory each time i reinstall pidgin.
so heres the basic setup (this does not include signing up your gtalk account)
Procotol: XMPP/Gtalk
Username: Dennis
Domain: annoying.dk
Resource: Empty
Password: mypassword (god,love,sex…)
Local alias (nickname)
Under Advance, keep it simple.
No checkmarks required in the first 3 boxes.
Connect port: 5222
Connect server: talk.google.com
Even through im a shitty scripter and my scripts can make people tear their eyes out, i usually make it stable and problem-free.
the funny thing was that it was actually working great, running it from the shell. but setting it up in crontab – it just didnt run the script fully.