Enable NTP On Windows 2003

• use the group policy object snap-in, go to Computer Configuration/Administrative Templates/System/Windows Time Service/Time Providers, configure the stuff in there
• use w32tm /resync to force a sync

(I think the client is enabled by default on domain members? not sure.)

Random notes on ASP:

• You can use WSH to get registry. You can’t access HKCU from ASP, even if IIS is configured with a user.
• To show error on the browser (instead of just “error 500″) there needs to be an error handling page (this is created by default but if you create a new web site it wont be copied). Solution = create a virtual dir on the website, make it point to \Winnt\Help\IISHelp, then go to the custom error handling and set the 500-100 error to \iishelp\common\500-100.asp (trick = this has to be URL, not File)

Some notes about Soap, Soap::Lite

Many more hours of fighting between SOAP::Lite and .NET later…

I think I am beginning to get the ‘feel’ of SOAP::Lite. Looking at the output (WSDL and XML) of a .net web server, I managed to hack the serializer to make it similar (thus it is using the ‘literal’ encoding instead of the RPC type). I don’t know if this is still going to go through a SOAP::Lite client now but it is not an issue right now. It will break Apache SOAP clients I think but thats not really an issue either since we are only going to use the service with our .net client… we can have the handler dispatch to a different server (serializer) according to client type, if needed. Unfortunately I never got the .net client to grok the Rpc-encoded output, although it was doing great on the google service… all kind of strange bugs started popping, so I gave up on that.

A lot of the info was on the SOAP::Lite mailing list, I figured the rest out from looking at the SOAP::Lite code and the output from the .net server. Basically the only function of the serializer is to strip all the attributes except the namespace (also I turned autotype off). The .net client figures all the types and shit from the WSDL (which I adapted from the .net server example).

As it is now I have a service sending back an array of pairs. I am probably still going to use only array of strings anyway but heh its good to know I can do it It’s really pretty simple I wish this info was on the SOAP::Lite page.

Oh yeah this page was a real lifesaver also: article by Byrne Reese on SOAP::Lite