ZogBlog

It could only be one thing. Spaz Attack.... Waoooh. Watchout, because SharePoint might have a spaz attack on you too. Enjoy staying late at work to keep a brand-new, barely used product working? Then just follow these happy steps:

• Create a Second Virtual Directory (VD), point it's home to your portals virtual root
• Manually match all the settings, except setup SSL on this VD
• Then attempt to access your portal with either VD (one with integrated, the other with basic+SSL) - watch how it doesn't work
• Confused, you realize that you should have extended it via the Portal Admin Site; so you do that
• About now your users complain that 1) the site has disappeared, and/or 2) the library is no longer accessible
• Discover that the portal is still there, and still works... for you; until you logoff/reboot
• Discover further that SharePoint is actually ignoring the default document... enter it and the site appears... but the library still doesn't work
• Check that the default documents are set in IIS... find that they are, but SharePoint doesn't care.
• Spend the next 2 hours scratching your head, searching google/groups, searching the MSKB's, running test cases, and examining every IIS and SPP log... to no avail
• Decide to tear down the Windows SharePoint extensions from both VDs in the vain hope that they are somehow corrupted
• Magically watch the spaz attack end after you've deleted the virtual roots TWICE, and re-added the extensions

I think the lights go out every time I blink, and come back on again when I open my eyes. So, if the lights start to flicker, you'll know I'm out of my blink-sync." - Venus De Milo (Look-Alike) [2NU]

Microsoft Codename Istanbul does just that... and like a knight you have to be annointed by Sir Bill's chosen clergy to get in... (read special permission from your account manager). I doubt we'll get a chance to use it at my customers' site because of their absolutely irrational FEAR of instant messaging.

My boss (my customers' CIO) recently told me that the reason IM is verboten is twofold: 1) Remote IM clients make a direct connection to our local IM clients, and 2) It's not encrypted. Little did I know, IM is apparently a type of P2P. As far as encryption - who cares unless that data is classified?

I wonder if Istanbul supports encryption - might be worth asking. If so, I'll ask Microsoft nicely if they'll consider us worthy enough to test Istanbul.

Update: I didn't believe IM was a type of P2P app. Check corrected me. Doh!