Microsoft's official enterprise support blog for AD DS and more
Ned here. On October 1, 2008 the Professional level “Enterprise Platforms Support” business at Microsoft will transition to a call-back model for all Professional support incidents in the United States and Canada. Below is a description of how to contact Microsoft customer service, as well as other relevant information regarding this change:
Why are we moving to a call-back model?
Contacting Microsoft Product Support by Phone
You can submit a support request via phone by calling 800-936-4900. Once your support incident is created, the case will be routed to the appropriate support team and you will receive a call from a support engineer. The response time is based on the severity of the incident. During business hours (Monday – Friday, 6:00 am – 6:00 PM US Pacific Time), the cost is $259. If you need to work with a support engineer outside of these hours, the cost is $515. Please note that you can open a support incident via phone at any time. The after-hours rate only applies if you need to work with a support engineer during non-business hours. This information is also outlined on the Microsoft Help and Support site.
Contacting Microsoft Product Support using Online Support Submissions
As an alternative to opening a support incident via phone, you can use our Online Support Submissions process. As with our Phone support offering, this is a call-back model also, and the response time is based on the incident severity. At this time, Online Support Submissions call-backs are only available during business hours (Monday – Friday, 6:00 am – 6:00 PM US Pacific Time), and the cost of a support incident is $259.
For more information on this change, please refer to the following web page on the Microsoft Support site: Professional Support Options and Phone Numbers
For more information on contacting Microsoft Product Support, please refer to the following resources:
You can also direct questions to us through the EMAIL link at the top of the page.
- Ned Pyle
There were some internal issues that prevented me from getting this out for a while, but I’m hopeful to post these weekly again now. Note that much of the content that previously would have become a KB article is now ending up on TechNet, so it is possible there will be fewer KB articles being published going forward.
These are the new articles that relate to Directory Services for 9/21-9/27:
You cannot connect to an ADAM instance in Windows Server 2003 by using the Secure Sockets Layer 3 protocol together with a certificate that is larger than 1024 bytes
The "Slow network connection time-out for user profiles" Group Policy setting does not work for a Windows Vista Service Pack 1-based or a Windows Server 2008-based client computer
File System Auditing option in the Security Templates in MMC is confusing
Ned here with a quick blurb:
The latest version of the Ultrasound tool has been released to the web. This version adds support for monitoring FRS on Windows Server 2008 and allows the use of SQL Server 2005 for hosting the Ultrasound database. No other new features have been added in this version, and it does not monitor DFSR (the older version didn't either).
The download location for the tool is the same as before - http://www.microsoft.com/downloads/details.aspx?FamilyID=61acb9b9-c354-4f98-a823-24cc0da73b50&displaylang=en. To deploy the Ultrasound WMI provider on an x64 version of Windows Server 2008, the hotfix KB954737 must be installed (this fact is also mentioned in the release notes). - Ned Pyle
Ned here. For all of our bilingual German readers, I wanted to point out that the Microsoft Germany DS support folks also have their own excellent blog:
Aktives Verzeichnis - http://blogs.technet.com/deds/
Be sure to add them to your feed reader of choice. Barbara, Fabian, and Rol write excellent stuff. For example, their latest post covers improving service reliability and performance by reconfiguring Kerberos PAC validation. And if your German is a bit rusty, you can use Windows Live Translator to convert it - here it is in English.