Archive for January, 2009

ISA 2006 and Active Directory Replication

Thursday, January 29th, 2009

environment: The following servers are in place AD1, ISA1, ISA2, AD2. AD1 is behind ISA1; AD2 is behind ISA2; ISA1 and ISA2 are connected via VPN.

ISA 2006 (without SP1)

problem: during dcpromo

The operation failed because:

Active Directory Domain Services could not create the NTDS Settings object for this Active Directory Domain Controller CN=NTDS Settings,CN=AD2,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=contoso,DC=net on the remote AD DC Ensure the provided network credentials have sufficient permissions.

"The remote procedure call failed."

solution: Go to to ISA1 and ISA2. Right mouse click the rule responsible for VPN traffic. Select "Configure RFC protocol" and uncheck "Enforce strict RPC compliance"

Updating to ISA 2006 SP1 finally fixed it.

Latitude XT2 and Windows 7

Saturday, January 24th, 2009

Based on the release of the manual the most interesting question is: will the multi touch features work in Windows 7?

Update: Thanks to a comment I found the beta package over at n-trig.

BUT it doesn't support 64bit and no pen support (=no Math Input Panel!!!)

VPN connected machine, Active Directory and DNS

Friday, January 16th, 2009

environment: AD Server in Sub-Net A, Client in Sub-Net B

problem: Client can't find logon server

solution: I configured 2 dns server. The first one was the remote AD server, the second one a public one.
For some reason Windows favored the public one and could not resolve the logon server. Removing the public one helped.

Windows Vista R2 aka Windows 7

Thursday, January 15th, 2009

I installed it on a Dell XPS Gen2.
The installation took +2h (I guess because of 3 different Visual Studio I have installed and who knows what else).

After restart my display resolution was capped at 1280x1024. This happend because my graphic card (Geforce 6800 Ultra, Dell-branded :( ) was detected as Standard VGA Adapter.

First I called at Microsoftie and complained. Then I started the Device Manager, chose the Standard VGA Adapter and clicked Update Driver. Couple of minutes later the NVidia Driver was downloaded and installed. Know the system works.

Experience so far:

  • Math Input Panel is as cool as I expected. Outputs MathML. Need to check how to integrate this with MediaWiki and I can't wait to get a Latitude XT2.
  • Explorer died once during file copy
  • New task bar is nice.
  • Had to upgrade to Skype 4.0 beta - confusion!
  • Daemon tools is NOT working anymore

Server too cold

Sunday, January 11th, 2009

As some of you probably noticed StatWiki and a few other services were offline the last week.
It all started with my wish/requirement to upgrade to Windows Server 2008 and switching our virtualization from Virtual Server 2005 R2 to Hyper-V.
First we had trouble getting my USB DVD ROM to work. We (Zak and me) finally disassembled the dvd rom to connect it directly via IDE because we couldn't get the server booting from the DVD. (btw the fscking room was freezing cold due to broken heating system and -5C to -10C outside temp in Vienna).
In the end the supplied boot order in the bios didn't work and we had to select BBS (wtf? it's "select boot order") provided by the BIOS to select the proper boot device.
Upgrade was smooth. Windows 2008; what else?
The VMs were migrated easily to Hyper-V.
We left for home.

@ home: I continued working and the machine FREEZED - no remote desktop anymore. So I picked up the machine and move it home.
After Asus BIOS upgrade, network driver upgrade and the removal of an unsupported Intel 100/Pro B card (I actually installed some strange driver from the Intel site) the machine stopped freezing.

So I brought the machine back and it wouldn't start anymore... *sigh*. It has a blue display panel with some temperature infos (completely useless for a server only operated remotely) that just blinked, the fans spun at a low rate and after a few seconds the machine shut down. So I took the machine home *again*...

@ home: I dissambled the machine ram, hdds, graphic card and connected a different power supply. same effect. after a while I discovered the connection of the blue display panel. re-connected it and it finally worked.
Then I setup Active Directory on the host machine as backup of my primary AD over a broken VPN connection. Next horror.
I have to admit my VPN using OpenWRT and pptp isn't latest and greatest technology... but... *sigh*.
2 days later I uninstalled the Active Directory again due to firewall and some expectations about network connectivity.

Finally I brought the machine back (today) and guess what... the fsck machine didn't start again. Same power error as above.
So? *sigh* We went shopping :)

In the afternoon we had the idea. (imagine Wicki) I got my mother-in-law's hairdryer and target the motherboard, power supply and hdd. 2 mins should be enough?! Yep. The server started again. WTF? A server too cold. I remember some postings of overclockers freezing the complete thing. Well anyway. It's up and running.