Category: electronics

  • Windows 2008 Role Services for MOSS 2007

    After trying to install MOSS 2007 on a new Windows 2008 box, I almost went completely bonkers.  No place in the installation documentation does it tell you what Role Services need to be installed for MOSS to successfully install and run.  Initially MOSS 2007 wouldn’t even install because I didn’t have the IIS6 metabase compatability installed.  However, just because it’s installed, doesn’t mean it actually runs.  I then started installing additional role services to see if I could get it to work.  Needless to say, even after installing all of services, my MOSS installation didn’t work.  Turns out you need to have the services installed prior to actually installing MOSS.  Otherwise the page will never render, and you’ll get a 5MB binary download instead of the actual application.

    However, after I knew what I was looking at (reinstalling MOSS again after all the services were installed), I decided to start whittle down the actual services I need.  Instead of doing it by hand, I finally found a website that listed what’s needed.  I’d like to give Bill Baer’s site a shoutout as to where I found this information.

    Web Server

    • Common HTTP Features
    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors

    Application Development

    • ASP.NET
    • .NET Extensibility
    • ISAPI Extensions
    • ISAPI Filters

    Health and Diagnostics

    • HTTP Logging
    • Logging Tools
    • Request Monitor
    • Tracing

    Security

    • Basic Authentication
    • Windows Authentication
    • Digest Authentication
    • Request Filtering

    Performance

    • Static Content Compression
    • Dynamic Content Compression

    Management Tools

    • IIS Management Console

    IIS 6 Management Compatibility

    • IIS 6 Metabase Compatibility
  • ESX 3.5 Upgrade Woes

    I really want to upgrade to ESX 3.5.  However, I’m not having that much luck with it.  I’ve tried 2x now, and have had the exact same experience.  So, I do the upgrade from 3.0.2 to 3.5.0.  However, after the upgrade, not all of my VMs function.  Some of them work just fine.  However, others are sitting at the command prompt saying that no OS has been found.  It’s weird because the drives are attached and recognized, but it doesn’t like to boot from them.  It’s like it can’t find the MBR. 

    Things I’ve tried to fix this:

    • Analyze the differences in the VMX and VMDK files between the machines that are working and aren’t.  This hasn’t given me much as there isn’t any difference.  The only difference I noticed was in the VMDK files.  The ones that booted correctly listed the “ddb.toolsVersion”.  The ones that hadn’t booted listed it as “0”.  Sadly, changing this didn’t fix anything.
    • Mount the non-functioning disks on working VMs.  By doing this I was able to view the contents of the disks just fine.  And amazingly, sometimes after doing that, the original VM actually booted.  However, they are very flakey and sometime revert back.  There is a lot of chkdsks going on on bootups too. Nothing is ever found, but it seems to always run.

    I really don’t know what to do at this point.  I know that I can downgrade again to 3.0.2 and it will work fine.  The machines will boot right up without issues.  However, to downgrade, that means I have to recreate all of my Virtual Machines again.  Not completely awful, but time consuming.  I may try to do a full install instead of any upgrade too, see if that works.  Any other ideas?

    I’d really like to move to 3.5 as it has some nice features.  Plus I’ll be sitting the VCP class soon, which will be on 3.5.

  • SQL 2005 and Windows 2008

    Having troubles running SQL Server Manager on your shiny new Windows 2008 installation?  Make sure you right click and do a “Run as administrator” on it.  Took me awhile to figure this one out.  Otherwise you’ll just get the error “Login failed for user domainuser.  (Microsoft SQL Server, Error: 18456)” even if you’re a member of the local administrators on the SQL box.

    Yet another instance of where UAC sucks.

  • Windows 2008 How-To Guides

    Microsoft released a bunch of how-to guides for various things new to Windows 2008.  You can grab them all from the MS Download page.

    Things I would definitely check out are:

    • Deploying SSTP Remote Access Step by Step Guide.doc
    • Server_Core_Installation_Option_of_Windows_Server_2008_Step-By-Step_Guide.doc
    • Windows Server 2008 TS Gateway Server Step-By-Step Setup Guide.doc
  • Exchange 2007 after Windows 2008 Upgrade Part 3

    After having issues with a potential bug on Feb the 29th, I’ve finally gotten things straightened out. 

    Today I attempted to move the mailboxes again, but received the same error message.

    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:08

    User’s Mailbox
    Failed

    Error:
    The address list service on the server ‘servername.fqdn’ is not running. The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.

    The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error.

    Exchange Management Shell command attempted:
    ‘fqdn/Managed Users/User’ | move-mailbox -BadItemLimit ‘10’ -TargetDatabase ‘servernameFirst Storage GroupMailbox Database’

    Elapsed Time: 00:00:08

    It turns out that all I needed to do was restart the System Attendant service on the machine I was trying to move the mailboxes to.  After I did that, everything moved successfully.  I then attempted to hit OWA on the new machine and it was successful!  So I finished moving all the mailboxes over, changed ISA to point to the new server name, imported the right certificate and I’m good to go.  Almost 5 days of downtime, but no email lost, yay!

    Now I just need to decommission the old Exchange box and give the new one more RAM.  Not a bad few days work.

  • Exchange 2007 after Windows 2008 Upgrade Part 2

    Well, I’ve got the new Exchange box up and running.  However, I can’t move the mailbox from one machine to the other.  Thankfully, I’m not the only one having this problem today.  It appears as though because it is the 29th of February (leap year), there is a bug in Exchange 2007 preventing certain things from completing.  There’s a nice TechNet thread on it, and it appears by setting your date to tomorrow fixes it.  I think I’ll just wait to move the mailboxes till tomorrow or later then 🙂

  • Exchange 2007 after Windows 2008 Upgrade

    I know it has been well documented that you cannot upgrade Windows 2003 to Windows 2008 with Exchange 2007 installed and expect Exchange 2007 to keep functioning.  However, let’s say you may have accidentally done the upgrade on a standalone Exchange 2007 box you have, you know, just in case it were to happen (like it did to me).

    Prior to doing the upgrade, you’ll notice a few things.  First of all, you’ll be prompted that you need to uninstall Powershell.  However, no where does the compatibility checker say anything about needing to uninstall Exchange 2007 prior to upgrading.  I found this hilarious (in a sad, pissed off way) because I had tried to upgrade my WSUS virtual machine first, and it had told me that I would need to uninstall Powershell and WSUS prior to upgrading.  I’m so glad that I wasn’t told anything about Exchange in a similar fashion.  Ugh.  By the way, I was running Exchange 2007 with SP1 prior to the upgrade…of death!

    The first stumbling block, which should have caused me to stop the upgrade process, was uninstalling Powershell.  Since I had installed it prior to installing SP2, uninstalling it becomes a pain.  This is because Powershell is a windows update and if you install a service pack you can’t uninstall any updates prior to the service pack.  Lovely.  Well, in another unsupported way you can uninstall it.  You have to browse to %windir%$ntuninstallkb926139$spuninstall and run the spuninstall.exe.  Now, this may or may not be on your machine anymore either.  On some of my virtual machines it was there, but on my Exchange server it was not, so I copied it over and ran it.

    Ok, so now I can upgrade, yay!  Windows does its thing and upgrades everything and restarts successfully.  I was actually fairly impressed when it booted up.  It looked like it actually worked.  However, then I went into the services snap-in.  I usually do this with this machine because it is slightly RAM starved and sometimes all the Exchange services don’t start.  Sure enough, they hadn’t all started.  So I went through and tried to start them all.  All started but the information store and the system attendant service because of a dependent service.  Crap, of course it’s the important ones.

    Well, first thing I tried was to reinstall Exchange 2007 SP1, just to see if that would work.  Of course this required me to reinstall Powershell, since that’s a pre-req.  No big deal, installed that easily.  Then when I tried to actually install SP1 it just bombed saying it couldn’t upgrade.  Looking through the eventlogs it was because it was trying to spin up those two services.  Great.

    Well, doing some quick registry editing, I found that the service it was dependent on was NtlmSsp.  Needless to say, this service does not exist on Windows 2008, hence the issue.  Two seconds later, I removed that dependency from within the registry and restarted the machine.  The machine reboots, and low and behold all of the services start.  And all the email that was in the queue on my Edge Transport machine left the queue and made it into Exchange.  Downside is that I was doing this all remotely and OWA still didn’t work.

    Honestly, I wasn’t that worried about OWA.  I mean, as long as I can get my emails back and then do the correct upgrade (aka, no upgrade at all) I’d be a happy camper.  Heck, even after installing Powershell back on it, I was able to open up Exchange System Manager.  Really, if I didn’t know all about the services and didn’t use OWA, I would’ve never known it wasn’t working.  Oh, well, maybe the exceedingly high CPU utilization, but oh well.

    When I got home, I had to test to see if I would be able to access my email.  Sure enough, Outlook worked like a charm.  I received all the queued email that had been sitting there for a day, and I was even able to send an email.  Pure craziness. 

    What makes this even better is that the Exchange team actually decided (well, they actually went into it knowing what they were getting into) to try this same thing too.  However, they weren’t able to get things working.  I think the large mess-up was re-installing SP1.  I’m glad I didn’t decide to go down that path, especially since mine worked.  Needless to say I’m working on building a new VM with Windows 2008 and then going to add it t the ORG and move the mailboxes over to the new one.  However, in the meantime, at least my email is functioning 🙂

    I’ll be sure to post again on if I ran into any more issues with the mailbox move.  Worst case I suppose I could just do an ExMerge (actually Export-Mailbox for 2007) on the mailboxes or dump the email out of outlook to a PST.  I’d rather not do that, but if that’s what it takes…

  • Fixing the 360

    My last post about my 360 was way back in February.  In it I described how, after purchasing Crackdown, and attempting to play it, my Xbox360 died.  At the time, I called Xbox Support and haggled with them to fix it for free, eventhough it was out of warranty.  I just had to pay for shipping.  Anyways, about a month after I had called, and then didn’t actually ship it in, Microsoft actually extended the warranty of the original lot of Xbox360s and they now send you a box to ship it back in with a pre-paid UPS label.  At the time, I didn’t think that I actually qualified for the extended warranty, so I still wasn’t really in a hurry to ship it back.

    Well, I never followed up with that story, mostly because I never sent it in.  In fact, it’s still broken, sitting in my new place.  Last Friday, one of the guys I work with on my new project (he’s an from a different company than I am, but not the client) came to the my company’s main office because we needed to meet.  Well, turns out he’s a pretty damn good Halo 2 player.  Needless to say we played a few games on Friday.  Ever since then, I’ve been itching to play again.  Sadly, at the customer site, there’s not a game room (lame, I know).

    Anyways, I had told him about how Crackdown had broken my Xbox, and that my laziness was preventing me from utilizing my $400 piece of gaming awesomeness.  For the last 3 days, he’s been hounding me about getting it fixed, and why I haven’t called it in.  Then I hear, on all place NPR, about Halo 3.  I had completely forgotten that it comes out in Sept. 

    Needless to say, something needed to be done.  I still had the old reference number from when I had called in before, just in case they gave me a hard time.  Well, I called them up.  It was amazing how easy it was to deal with the people this time.  Last time I called, there was this huge long voice mail redirection service.  All of that was gone.  I actually didn’t have to push any buttons at all before talking to a support person.  She simply asked for my serial number and address, which I gave her.  I then told her the issue, and she asked if I had been through all the troubleshooting steps.  I had, back in February, so I said yes, and she didn’t harp on it!

    Unfortunately, with the move, I had to give her my old address.  It needed to be changed, so I let her know.  The address change procedure apparently takes 2 hours to do, so she said to call back 2 hours later.  Ugh, but whatever.  I suppose I can wait two hours.

    Another new feature I was told about when I first called in was the self-service website.  You can go to service.xbox.com and actually do all of this over the web.  So, after hanging up with her, I figure I’d at least check it out.  I signed in with my Passport ID and mapped my Xbox serial number to it.  Low and behold, my address showed up there as my new one.  It must have propagated through the system already (2 minutes later), so I called back.

    Sure enough, it had.  The gentleman asked me to verify it, and we were all set.  Another thing I noticed on the website, was that my Xbox was still under warranty (score!).  That means I definitely don’t have to try to wrangle free work again either.  He updated his system so I get one of the pre-paid boxes in the mail, and that was that.  As soon as he did it, I could even see the warranty status change on the webpage. 

    That was slick.

    Sadly, for Microsoft, my two reference numbers between the two calls increased by 1,354.  That’s a lot of support issues within a total of about 15 minutes.  Still, not nearly as bad as between February and today where the reference numbers increased by 13,122,883.  Regardless, in 4-6 weeks, I may have a functioning Xbox360 again, in the form of a repaired or new one.  It don’t think it’ll be in time for the launch of Halo 3, but it’ll be damn close.

    I’m just so glad that MS has listened and made their customer support 100x better now.

  • The Internet

    I love buying things on the internet.  For a lot of things, it doesn’t make sense, and for others you have to take a bit of extra time.  However, you usually always find a better deal online.  Plus there’s the challenge of finding that better deal, and still try to use a somewhat reputable retailer.

    Oh internet, I love you so.

  • DAS vs NAS vs SAN

    Something that is making me very angry with the current project I’m on is the difference between DAS, NAS, and SAN technologies.  The worst is that I’m working with these people on a specific thing not related to storage infrastructure, but instead development architecture and the people that are dealing with the storage infrastructure are the people that don’t know what the hell their talking about.  In particular, the hosting provider that does all of the storage infrastructure work for us doesn’t know what the differences are.  Oh, and don’t get me started on a VMware paper that we had that didn’t know the difference either.  It just drives me nuts. 

    For those of you keeping score, I’m going to outline this out.

    DAS = Direct Attached Storage.  These are disks that are physically located in your host machine.

    NAS = Network Attached Storage.  NAS is file based.  For example a CIFS or NFS share.  This is typically TCP/IP based access.  The NAS device “owns” the data on it.  That is, the NAS device administers the data.  For example, you connect to a NAS device from a windows machine by accessing servernameshare.

    SAN = Storage Area Network.  SAN is block based.  This is when LUNs (logical unit numbers) are involved on a host.  The host “owns” the data.  The host is in charge of the partition, formating, and access to the LUN.  You can access a SAN via two protocols: iSCSI (TCP/IP) and/or Fiber Channel (FC). 

    I’m so sick of seeing people talk about iSCSI NAS.  There’s no such thing because in a NAS scenario you are sending CIFS or NFS protocols over TCP/IP while in a SAN solution you’re sending SCSI protocols over TCP/IP.  Huge difference.

    And yes, you can have a device that serves both NAS and SAN from one filer.  This is called Unified Storage.  All NetApp devices can do this.

    Are we clear now?!