No Zune for you! – at least on Monday and Tuesday

The Zune service will be down for scheduled maintenance on Monday, September 29, 2008 from 12:01am Pacific Time, for up to 48 hours. During the downtime, Zune Social, the forums on Zune.net, and all of Zune Marketplace will be offline.

We apologize for any inconvenience this might cause you.

Please check back soon. We look forward to sharing our picks, plays, and recommendations with you in the Zune Social and in Zune Marketplace shortly!

Sincerely,

Your Friends at Zune

Updating my Redfly drivers today

My Redfly needs a firmware update.  If you have a Redfly prior to build 1.3.29.3060, you’ll want to update, too.

The new firmware fixes some things and adds some new features.

The Redfly folks also sent me an unreleased version of the Redfly software for my WM 5.0 device.  If you need WM 5.0 support, you’ll have to contact Redfly support for an update.

Here’s the installation instructions page:

http://www.celiocorp.com/install/

 

UPDATE:  The update was flawless.  Quick and easy.  I’m just starting to play with the updated hardware now, but I can see already that they fixed the mouse activity on my Motorola Q.

Good info: How to automatically apply a client Hotfix as part of a client push or client installation

From the SMS&MOM blog:

Ever wish you could automatically install hotfixes or updates when doing the client installation?  Thanks to this tip by Frank Rojas and Jason Adams now you can:

========

When applying a Configuration Manager 2007 or SMS 2003 client hotfix, the hotfix is not automatically applied when:

1) Using client push.

2) When installing the client using CCMSetup.exe from the Client directory in the SCCM/SMS directory (even if copied to the local client PC).

3) When the client installation is part of a Package, and the Package Source points to CCMSetup,exe in the Client directory in the SCCM/SMS directory.

4) As part of the Setup Windows and ConfigMgr task in an SCCM 2007 OSD Task Sequence.

Since the hotfix is not installed as part of the initial ConfigMgr or SMS client install, the hotfix then needs to be applied separately.

Under some circumstances, installing the hotfix separate from the initial client install may lead to issues. For example, during an SCCM2007 OSD Task Sequence, installing the hotfix via an Install Software task may cause the SMS Agent Host service to be temporarily disabled. The Task Sequence may then fail because it detects that the SMS Agent Host service is not running. The SMS Agent Host service is needed by the Task Sequence for any tasks run after the Setup windows and ConfigMgr task.

So what's the solution?  The solution is to apply any ConfigMgr or SMS client hotfixes during the initial client installation. To do this without having to run any additional installations follow these steps:

1) On the SCCM/SMS site server, create a folder called ClientPatch in the following directory:

SCCM 2007:
<drive_letter>:\Program Files\Microsoft Configuration Manager\Client

SMS 2003 or SCCM 2007 upgraded from SMS 2003:
<drive_letter>:\SMS\Client

Please note that the above two locations assumes the default install location for SCCM/SMS.

2) Locate the MSP file that corresponds with the hotfix. Usually the hotfix MSP is located in the following directory:

SCCM 2007:
<drive_letter>:\Program Files\Microsoft Configuration Manager\Client\i386\hotfix\KBxxxxxx

SMS 2003 or SCCM 2007 upgraded from SMS 2003:
<drive_letter>:\SMS\Client\i386\hotfix\KBxxxxxx

Please note that the above two locations assumes the default install location for SCCM/SMS.

3) Copy (do not move) the MSP file from step 2 into the ClientPatch folder created in step 1.

4) If the client installation is part of a Package, make sure to update any Distribution Points that contain the Package.

The hotfix should now be installed automatically during the initial SCCM/SMS client installation.

========

Thanks guys!

J.C. Hornbeck | Manageability Knowledge Engineer