Kurt Shintaku's Blog

Interestingly, I wasn’t the one that tried this.  My customer did.

The Microsoft Wireless Entertainment Desktop 7000 keyboard works just fine on an Xbox 360.  This means that you can keep a Wireless keyboard nearby and anytime you want to tap out a message or you have to enter in one of those god-awful 25 character redemption codes, you can use a keyboard to do so. 

The arrow keys work, the ENTER key works like the "Start" button, everything.  It’s actually pretty cool.

LINK:  http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=081

Microsoft Deployment Toolkit (MDT) 2008 unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. The fourth generation deployment accelerator adds integration with recently released Microsoft deployment technologies to create a single path for image creation and automated installation. MDT’s tools and end-to-end guidance reduce deployment time, standardize desktop and server images, limit service disruptions, reduce post-deployment help desk costs, and improve security and ongoing configuration management.

Microsoft Deployment Toolkit technologies eliminate interaction time required to install desktop and server operating systems. Interaction at the targeted computer may take a few moments using the Lite Touch Installation (LTI) method or it can be completely automated using Zero Touch Installation (ZTI). Zero Touch Installation utilizes Microsoft System Center Configuration Manager 2007 or Systems Management Server 2003 with the Operating System Deployment Feature Pack. Lite Touch Installation can be used when software distribution tools are not in place.

Microsoft Deployment Tookit 2008 also uses Configuration Manager 2007’s stand-alone media-initiated operating system deployment feature. This release offers project management guidance for all deployment roles and separates technical documentation for the products and technologies to facilitate automation tasks.

Microsoft Deployment Toolkit 2008 enables deployment of the following Microsoft products:

• Windows Vista Business, Enterprise, and Ultimate (32 and 64 bit) RTM and SP1
• Office Professional, Professional Plus, Enterprise, and Ultimate 2007
• Windows Server 2008
• Windows Server 2003 R2 (32 and 64 bit)
• Windows XP Professional with Service Pack 2 (32 and 64 bit) or Windows XP Tablet PC Edition

DOWNLOAD:  http://www.microsoft.com/downloads/details.aspx?familyid=3bd8561f-77ac-4400-a0c1-fe871c461a89&displaylang=en&tm

Looks like the Windows Mobile group unleashed their technical writers on to Microsoft.com because there’s a ton of new whitepapers out there around deployment and security for mobile devices in the Enterprise.

• Security Considerations for Windows Mobile Messaging in the Enterprise
  This paper discusses potential security risks in the mobile Enterprise, and how the network administrator can help protect the device by setting security policies using Exchange Server. It also describes security considerations on the device, the Exchange server, and the corporate network. This paper also describes how to perform common tasks, such as installing a certificate on a Windows Mobile powered device.
  http://www.microsoft.com/downloads/details.aspx?familyid=1b0260b9-4a92-43d9-84f9-7200d99e3ea1&displaylang=en&tm
  
• Deploying Windows Mobile 6 Powered Devices with Microsoft Exchange Server 2007
  This paper provides step by step instructions about how to deploy Windows Mobile 6 in an Exchange Server 2007 environment. Additionally, it describes new Enterprise features, network architecture scenarios, best practices, and procedures for implementing a mobile messaging system with Exchange Server 2007 and Windows Mobile powered devices that run Windows Mobile 6.
  http://www.microsoft.com/downloads/details.aspx?familyid=c72f213c-e52f-4971-af04-1d5eaebbb1dc&displaylang=en&tm
  
• Security Model for Windows Mobile 5.0 and Windows Mobile 6
  This paper describes all security policy settings in Windows Mobile powered devices. It also describes permissions, levels of security, and how policies and roles work together. This paper also describes certificates and security services for Windows Mobile 5.0 and Windows Mobile 6, and some common scenarios, such as wiping or locking a device.
  http://www.microsoft.com/downloads/details.aspx?familyid=e7bfb990-dd10-4d55-a785-52ebf5980331&displaylang=en&tm
  
• Step-by-Step Guide to Deploying Windows Mobile-based Devices with Microsoft Exchange Server 2003 SP2
  This paper presents essential elements of a mobile messaging system, including system requirements; a summary of deployment procedures; an overview of MSFP; an introduction to direct push technology; a summary of ISA Server 2006 features; and best practices for networking, security, and device management. It also provides guidelines and resources for the deployment of a mobile messaging system, including updating Exchange Server 2003 SP2, setting up Microsoft Exchange ActiveSync for mobile access, creating a protected communications environment, setting up an ISA Server 2006 environment, and procedures for setting up and managing mobile
  http://www.microsoft.com/downloads/details.aspx?familyid=50ad06ee-2e53-4353-b53e-692b7c7b7ad8&displaylang=en&tm

They say a picture is worth a thousand words, so here’s a snapshot of what Springboard, a website dedicated to getting IT Pro’s started with Windows Vista, looks like:
(http://technet.microsoft.com/en-us/windowsvista/bb905048.aspx)

Looks pretty good huh?  It’s VERY thorough from the "understanding phase" to the "deployment phase".

The bad news is that Technet Magazine, Microsoft’s industry magazine for IT Professionals, will be losing one of it’s columns. 

The Cable Guy was a popular column/article series that focused on Windows Networking technologies – the last of which focused on Network Access Protection from Windows Server 2008, written by Joseph Davies, Technical Writer for Microsoft, so you know the articles were pretty good. (The writer had to change posts within Microsoft and didn’t have time for the column)

The good news is they’re replacing the column with one dedicated to SHAREPOINT.  Entitled "Inside Sharepoint", Sharepoint administrators will now have a consistent article source in Technet Magazine providing hints and in depth looks at different ways to expand Sharepoint usage.

What’s that?  You don’t GET Technet Magazine?  Sheesh.  I’ve only written about how to get a free subscription a couple dozen times.  Here it is again:  For those of you who’ve been too lazy to subscribe, even though I’ve told you the subscription is totally free, here’s the link to get a free subscription to the semi-monthly publication, sent straight to your doorstep.

SUBSCRIBE:  http://technet.microsoft.com/en-us/magazine/cc296584.aspx

If any of you intend on using a Bluetooth headset with Windows Vista & Office Communicator 2007:

1)  ERROR:  “Can’t find device driver for Bluetooth headset”

If you run into a problem where you attempt to pair your Bluetooth headset with your Windows Vista laptop and you find the install process asking you “for a driver to be installed from the device manufacturer”.  The reason for this was answered in the Technet forums:

“The Windows Vista Bluetooth stack does not support Audio in-box.  During Vista, Microsoft added the underlying mechanics to support Bluetooth audio and opened up the interfaces, enabling 3rd parties to develop audio support.”
http://forums.microsoft.com/technet/showpost.aspx?postid=960824&siteid=17&sb=0&d=1&at=7&ft=11&tf=0&pageid=1

The net of this is, the built-in Windows Vista Bluetooth stack works with virtually every bluetooth device… except audio headsets. 
Basically, you just need to upgrade your Bluetooth software to a stack that works with audio headsets.

To configure your computer’s built-in Bluetooth hardware to properly support Bluetooth Audio devices you need to contact the manufacturer of your computer to help you identify the specific Bluetooth hardware used in your computer, and to determine if software/driver updates are available to use as an alternative to the native Bluetooth software in Vista.  (Note: Currently there is no patch available from Microsoft available for this issue.)  If you have the HP nc8430: 

Software Support for HP Integrated Module with Bluetooth Wireless Technology (Microsoft Windows Vista)
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=321957&prodSeriesId=1839150&prodNameId=1839197&swEnvOID=2097&swLang=8&mode=2&taskId=135&swItem=ob-56755-1

2)  HOWTO:  “Find a Bluetooth Headset that works with both Windows Vista/Office Communicator & cellphone seamlessly”

The holy grail is to have a Bluetooth headset on your ear, and have it automatically receive the signal of inbound calls from either your laptop’s Office Communicator (using Telephony Integration) or from your cellphone seamlessly.  This is only possible on a select group of phones that have the capability of what’s called "multipoint pairing".

I’ve noticed that this functionality is available on roughly 30% of the headsets out there.  Since there’s no list of what headsets work best for usage with both your laptop and your cellphone, I started researching the topic myself by borrowing some people’s headsets, getting some sent to me to test from Plantronics, and also purchased a few.

Here’s the list of headsets that I’ve tested:

Headsets that DO work:

• Plantronics Voyager™ 510
  http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/voyager-510
• Plantronics Voyager™ 520
  http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/voyager-520
• Plantronics Discovery™ 650E
  http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/discovery-650e
• Plantronics Voyager™ 815
  http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/voyager-815

Headsets that do NOT work:

• Plantronics Discovery™ 655
  http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/discovery-655-audioiq
• Plantronics Discovery™ 665
  http://www.plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/discovery-665
• Plantronics Voyager™ 855 Stereo Bluetooth Headset
  http://plantronics.com/north_america/en_US/products/mobile/bluetooth-headsets/voyager-855

The Release Candidate 0 (RC0) update to the Hyper-V role provides improvements to security, stability, performance, user experience, forward compatibility of configurations, and the programming model. All users of the Hyper-V role are encouraged to apply this upgrade. After you install this item, you may have to restart your computer. (26MB)

x86:  http://www.microsoft.com/downloads/details.aspx?familyid=b7464b44-821d-4a7c-9d9c-7d74ec14437c&displaylang=en&tm

x64:  http://www.microsoft.com/downloads/details.aspx?familyid=ddd94dda-9d31-4e6d-88a0-1939de3e9898&displaylang=en&tm

We just announced the acquisition of the world’s leading rootkit killer.  This is going to be a huge addition to Microsoft’s security technologies, whether it’s brought into Windows Defender, OneCare, or Forefront Security.

LINK:  http://blogs.technet.com/forefront/archive/2008/03/20/microsoft-acquires-komoku.aspx

Microsoft Acquires Komoku
Microsoft strengthens anti-malware protection with leading-edge rootkit detection provider.

REDMOND, Wash. — March 20, 2008 — Today Microsoft Corp. announced it has acquired Maryland-based Komoku Inc., a provider of advanced rootkit security detection solutions. Microsoft expects to add Komoku’s functionality into upcoming versions of the Forefront line of enterprise security products and Windows Live OneCare, Microsoft’s all-in-one PC care solution.

“Komoku has been a leader in the area of rootkit detection, doing work for ultra security-conscious customers such as the Department of Homeland Security (DHS) and the Department of Defense (DOD),” said Ryan Hamlin, general manager, Access and Security Division, Server and Tools Business at Microsoft. “Komoku’s cutting-edge expertise and technology will benefit our customers by adding to the robust protection of our anti-malware solutions and help maintain our leading position in anti-malware research and development.”

Founded in 2004, Komoku offers advanced rootkit detection. Rootkits are malicious software programs that are designed to take control of a computer’s operating system at the administrator, or root, level, where they can often hide from detection by standard anti-malware software. Komoku’s customers have included a number of high-security government agencies, including the Defense Advanced Research Projects Agency, the U.S. Navy, the DHS and the DOD.

“I’m excited about the Komoku team joining Microsoft and building on our successes in detecting sophisticated rootkits for customers,” said William A. Arbaugh, president and CTO of Komoku as well as an associate professor of computer science at the University of Maryland at College Park and a renowned expert on rootkits. “Microsoft’s commitment to building the next generation of malware detection is very strong, and we at Komoku look forward to continuing the tremendous progress Microsoft has already made in the anti-malware space and building the anti-malware products that can handle today’s sophisticated threats.”

The Komoku name and product line will eventually be retired as the company winds down its affairs after closing. The majority of Komoku’s staff will join Microsoft in the Access and Security Division. Financial terms of the acquisition were not announced. The deal was completed March 19, 2008.

Founded in 1975, Microsoft (Nasdaq “MSFT”) is the worldwide leader in software, services and solutions that help people and businesses realize their full potential.

For those of you who aren’t basing your deployment off the volume licensed .IMG of Windows Vista with Service Pack 1 slipstreamed into it, here’s where you can download the bits for the Service Pack alone.

Windows Vista Service Pack 1 (SP1) is an update to Windows Vista that addresses feedback from our customers. In addition to previously released updates, SP1 will contain changes focused on addressing specific reliability, performance, and compatibility issues; supporting new types of hardware; and adding support for several emerging standards. SP1 also will continue to make it easier for IT administrators to deploy and manage Windows Vista. Windows Vista Service Pack 1 Five Language Standalone version can be installed on systems with any of the following language versions: English (US), French, German, Japanese, or Spanish (Traditional).

• Read the overview of Windows Vista SP1, including what’s new, technical details, guidelines and notable changes.
• Read the Deployment Guide for Windows Vista SP1. This guide includes technical information, procedures, and recommendations for installing Windows Vista SP1 in a business or corporate environment.

DO NOT CLICK DOWNLOAD IF YOU ARE UPDATING JUST ONE COMPUTER: A smaller, more appropriate download is available on Windows Update.

• To download the Standalone version of Windows Vista Service Pack 1 please follow the directions below in the Instructions section.
• Before installing SP1, please visit the Windows Vista TechCenter and read the page "Things to Know Before you Download Windows Vista SP1"

The Microsoft Download Center site is your only authorized web source for downloading a licensed copy of Windows Vista Service Pack 1. To report a website offering unlicensed copies of Windows Vista Service Pack 1 for download, please send e-mail to: piracy@microsoft.com or visit http://www.microsoft.com/piracy/ReportingUs.mspx.

This update is provided to you and licensed under the Windows Vista License Terms.

DOWNLOAD:  http://www.microsoft.com/downloads/details.aspx?FamilyID=b0c7136d-5ebb-413b-89c9-cb3d06d12674&DisplayLang=en

TECHCENTER: (Docs)  http://technet.microsoft.com/en-us/windowsvista/bb738089.aspx?tapm=A80S01A01

There is a new high-priority/non-security update for Windows Server 2003 Post-SP2 which was released yesterday, and if you’re a Enterprise customer of mine with Premier Support, you should know that we’re encouraging you to consider installing this update on any Windows Server 2003-SP2 Server.  

This hotfix disables the new Scalable Networking Pack, SNP, features that were delivered with Windows Server 2003 SP2. These SNP features were designed to offload a lot of the overhead processing required for network operations from the Operating system to compatible network adapter hardware. (For more background information on the SNP, you can read about these features here: http://technet.microsoft.com/en-us/library/bb878074.aspx)

Within our support organization, we have received a number of calls from customers that were having network-related issues.  Turning off these features, which are enabled by default with Windows Server 2003 SP2 has apparently solved the problem.  It appears that there have been some incompatibilities with these advanced features and some of the older drivers for these cards which support these features.  Our recommendation for Premier Support customers is that unless you have specific requirements for enabling these advanced networking features, customers install this hotfix to disable the SNP.

(Please note that this applies to only Windows Server 2003 SP2 Servers, where this feature was enabled by default.)

To review and obtain this hotfix, please follow this link:
DOWNLOAD:  http://support.microsoft.com/?id=948496