Crazy Microsoft stuff

VN:F [1.9.18_1163]
Rate this post
please wait...
Rating: 9.5/10 (4 votes cast)
Crazy Microsoft stuff, 9.5 out of 10 based on 4 ratings

Page 2 of 2 | Previous page

Related posts:

  1. Microsoft’s three ways to store stuff online
  2. A year of blogging: another crazy year in tech
  3. Office Ribbon in Silverlight – amazing stuff from divelements SandRibbon
  4. Why you probably don’t want to buy Microsoft SBS 2008 Premium CALs
  5. Microsoft WebMatrix released: a simple editor for ASP.NET Razor and more, but who is the target user?

4 comments on this post.
  1. Paul Culmsee:

    Actually I am pretty cynical about cloud systems too :-)

  2. Paul Culmsee:

    Since every web hoster can be “the cloud”, then this experience says it all

    http://www.cleverworkarounds.com/2008/08/25/all-in-the-name-of-security/

  3. tim:

    Paul

    Thanks for the comment. I’ve seen this kind of stuff from hosters as well. However, there is cloud and there is cloud – you would expect that true multi-tenant platforms such as Salesforce.com, or Google Apps, would have much more considered security implementations.

    Tim

  4. Nicholas Piasecki:

    \begin{crazy-talk} Is the fault inherently with SBS–that is, the act of trying to provide this all-in-one package–or is it inherently the fault of the design and setup of each of these Microsoft tools (Active Directory, Exchange, SharePoint) in that they cannot easily co-exist in the same operating system instance? Really, shouldn’t that be possible (regardless of whether or not it is recommended)? Shouldn’t it be possible to do anything with AD that does not require becoming a subject-matter expert in the software and reading a 300-page tome? Why does migration involve Byzantine commands (“adprep -abandonAllHopeYeCanNeverGoBack”) instead of a conceptually simple transfer of a database? I think that, perhaps, the SBS team can only do so much: when AD, Exchange, and SharePoint are all administrative disasters, there’s only so much lipstick that you can put on that pig. It’s an example of dogfooding, but the feedback never seems to propagate back up to the teams that are causing the problems because “it’s just a configuration problem.” \end{crazy-talk}

    (This from a tried-and-true junior Microsoft developer who is also “the company’s computer guy” and completely terrified of the SBS 2008 server sitting behind his chair in the office.)