Okay, there may not be more than one of these, but I didn’t pick up on this issue until yesterday. After 5 hours on the phone with Microsoft support.

When specifying paths in your SUS settings (GPO, Registry, etc) you can’t use UNC paths. They have to be HTTP paths. This makes sense when you think about it, since SUS is HTTP-based, but it was a real killer as I’d spent hours in newsgroups, conversations with folks, etc. As soon as we changed the path to http://servername instead of \servername everything woke up. At least it seemed to. 10am this morning (in 1.5 hours) is when the server should start to get hammered by 2500+ clients looking for a fairly large amount of updates.

Thank goodness I staggered them throughout the day.

Anyways, on a positive note, I love Microsoft support. I’ve never had a tech be rude, pass me off, tell me it was my issue, etc. 250$ for 5 hours of support is fantastic. I once had a 20 hour call in with Microsoft and they ended up giving it to me free of charge for “causing me so much grief”.

The only support I enjoy more is Dell’s. HP’s can be incredibly difficult (even when you’re a multimillion dollar customer). Novell’s is also very, very good (we have direct access to engineers and developers). Citrix’s is crap.

Long day yesterday. SUS is up though, and that’s one key to protecting ourselves from that bloody JPEG thing.