The Office Update Inventory Tool Detection information provides the Office Update Inventory Tool with detection information for the latest updates to Office 2000 and Office XP. The Office Update Inventory Tool allows administrators to inventory the state of updates across all of their Office installations and generate reports on the information.
Moving away from X86 is bit of a chicken and egg scenario. Consumers don't want the hardware unless the software is there to support it, and software guys won't start developing software until there is available hardware on the market to back them up. Of the companies who have taken on the challenge of moving to 64-bit thus far (Intel, Sun, and Alpha), all have all been limited case scenarios. The companies have developed 64-bit processors specifically for usage in servers and high-end workstations, where the limited hardware and software that is compatible with their processors isn't much of an issue, as they are looking at a very targeted user base. AMD's move to 64-bit processing is much more challenging, as they are targeting home users, gamers, and everyday business folks. In these markets, the amount of software, drivers, and subsequent headaches rises by leaps and bounds. AMD's goal is to succeed where all of its competitors have failed, and succeeding in this goal not only requires flawless execution of the 64-bit hardware, but cooperation from some of the biggest names in the industry as well. There's little doubt that the key player in this equation is Microsoft, whose release of Windows XP for AMD64 will be the litmus test to see if the world is ready to accept AMD's take on 64-bit computing, or if the platform will be headed for obscurity.
Both AMD and its software partners agree that a true 64-bit operating for AMD64 processors is a necessity for the platform to be a success. There are variants of FreeBSD and Linux out there which already support the needed X86-64 extensions, most agree for that the platform to be taken seriously by the mass markets, a 64-bit variant of Windows is needed to take advantage of the Opteron/Athlon 64's processor architecture.
Read the rest at GamePC.com
Beta phase will broaden the program beyond the early adopter trials that have been in progress for the last 6 monthsOn July 7, Microsoft formally announced the next phase in its long-anticipated rollout of its speech applications software, Microsoft Speech Server. Microsoft began its public rollout with the distribution of the first release of the Microsoft Speech Applications Developers Kit in October 2002.
Because Microsoft’s entry into the speech field has long been anticipated, most affected vendors already have incorporated it into their plans. The formation of the SALT Forum by Cisco, Comverse, Intel, Microsoft, SpeechWorks, and Philips to develop a standard markup language for combining speech and graphical applications tackled the problem sooner than the more widespread VoiceXML.
Microsoft’s timing is typical—entering a market once it has matured, offering a lower price, and buying share from existing players. While speech applications became mainstream in the last 2 years, they did not see the typical market expansion due to the economy.
Microsoft has stated the following benefits of Speech Server:
· Lower costs: Microsoft has yet to share any framework on pricing but has repeatedly listed lower costs as a key attribute. We believe Microsoft will target a 30 percent lower price point than competing systems for its software. The fallacy here is that Microsoft claims higher costs come from solutions incorporating a wide array of proprietary hardware, telephony software, and tools. Speech Server does little to change that, since almost all vendors have adopted general-purpose servers, operating systems such as Windows or Linux, and generally available telephony boards.
· Provide easier integration with applications: IVR and speech vendors already have provided Web-based tools, especially in adopting VoiceXML, that provide the same level of application integration that Speech Server does with Web servers. The ability to share applications logic and databases across both voice and graphical applications already exists, so Speech Server’s leveraging of the SALT specification does not bring any new level of application integration to the table.
· Standard development environment expands who can write speech applications: In promoting SALT as a standard, Microsoft is touting that the millions of developers already familiar with Visual Studio .NET can now readily speech-enable any Web application. We agree that both SALT and VoiceXML are advancing the industry by providing a more common set of HTML/XML semantics for developers to deploy speech. But it is dangerous to imply that any Web developer will speech-enable applications, because not all have the proper training and experience in best practices for dialogue design. Speech-enabling applications is not easy. The industry does not need to repeat the problems experienced with the poorly designed IVR applications of the past.
· Create new multimodal (speech plus graphical user interface) speech applications: SALT has very effectively integrated the constructs necessary to support speech input, speech output, and graphical interactions with devices such as PDAs, tablet PCs, and pocket PCs. As the market begins to emerge for these types of applications, the SALT markup language is very well positioned to drive Speech Server sales. But properly designing applications that track all the ways a user can touch, type, speak, and listen is a long way off.
Get a Windows Embedded Evaluation Kit and learn how to build the next generation of smart, connected, and reliable embedded devices. The Windows Embedded family of operating systems includes Windows XP Embedded and Windows CE .NET. With an unmatched tools and technology portfolio, these operating systems offer a faster way to start and bring to your embedded devices to market while minimizing your design and development costs.
You now have the option to download an Evaluation Edition or order an Evaluation Kit online:
The launch will be held simultaneously in Redmond, Wash.; Los Angeles; San Francisco; and New York City.
This summer at Microsoft's annual financial analyst day, Microsoft Group VP Jim Allchin told attendees that Microsoft would ship the next version of Media Center Edition — codenamed "Harmony" — before the end of Microsoft's fiscal 2004. (Microsoft's fiscal year ends June 30.)
The Windows Media Center product builds on top of the Windows XP Professional code base. It is sold via OEMs exclusively. Media Center is designed to turn a PC into central entertainment hub that is controlled by users via a remote control. It can play and record TV shows, digital movies and music. There are more than a dozen models currently on the market from vendors including Hewlett-Packard, Gateway and Toshiba.
While Microsoft hasn't talked much publicly about Harmony, testers who received Beta 2 of the product in May have been fairy vocal. The Tech-Critic Web site posted a number of screen shots of the forthcoming product at that time.
Media Center critics have voiced concerns that the first release of XP Media Center Edition stuck too closely to the traditional XP features and look-and-feel. Microsoft is expected tailor the operating system more toward its core audience with the Harmony release. They also have complained that Media Center PCs are too expensive, as base systems typically start at about $1,500.
<!-- start ziffarticle //-->Read: "Why Media Center PCs Are All Wrong"<!-- end ziffarticle //-->
At the Windows Hardware Engineering Conference (WinHEC) this year, Microsoft officials said the second, major version of Windows Media Center (release 2.0) would hit some time in 2004.
<!-- start ziffarticle //-->See "Windows Media Center 2.0: Think 2004"<!-- end ziffarticle //-->
Few weeks ago Microsoft ADS 1.0 RTM'ed. Now it is released to the web.
Microsoft yesterday shipped one of the first tools that is part of the company's wide-ranging strategy to create a comprehensive platform for managing corporate data centers.
The company's Automated Deployment Services (ADS) supports the automatic and simultaneous installation of Windows 2000 and 2003 "images" to multiple servers that have no operating system installed. ADS is the first system imaging technology available from Microsoft.
The ADS command console runs on Windows Server 2003 and is available as a free download to users of Windows Server 2003 Enterprise Edition and Datacenter Edition. "The key tenet is to drive down administrative and IT costs," said Bob O'Brien, product manager for Windows Server 2003.
ADS is just the beginning of an ambitious multiyear, multistage plan Microsoft unveiled in March called the Dynamic Systems Initiative (DSI), which is designed to create a platform to support a self-managing environment built around applications that can communicate their management needs to the network.
DSI's most critical component is called the System Definition Model (SDM), an XML-based technology that will be built into applications, the operating system and management tools. SDM will allow those three elements to communicate about management issues, such as performance and configuration, and understand the dependencies among applications and network hardware for systems to run correctly.
ADS, which is based on the SDM model, is the second release under the DSI banner. The first was the Windows System Resource Manager that was part of Windows Server 2003.
ADS is aimed at easing the rollout of the Windows operating system on servers by creating images or configurations that can be installed on multiple computers simultaneously. ADS is run from a central console and "listens" for new servers that advertise themselves on the network. ADS installs an agent that facilitates the installation of the operating system. After the install, the agent can be used for administrative duties, such as configuring a server to join a cluster.
ADS, which began as a project within Microsoft Research, has been under development for nearly three years and in beta testing with 150 customers since March.
Microsoft officials said the next step under DSI will come at the end of year with the release of virtual server technology obtained through the acquisition of Connectix Corp. in March. The technology will be married with ADS, allowing users to provision virtual servers on a single box.
Microsoft will start to build SDM support into Visual Studio.Net later this year. But support in the operating system and management tools won't come until the Windows Longhorn release, which has slipped into 2006 or 2007.
Experts say that if Microsoft can fulfill its DSI plan, it will become more competitive in corporate data centers.
The software vendor is trying to keep pace with rivals IBM, Sun Microsystems Inc. and Hewlett-Packard Co., which also have evolving, complex multiyear strategies to create management environments that let corporate customers adapt to change by dynamically allocating resources and installing software. <!-- End body content --><!--STOPINDEX--><!-- Clear break after story so there's no possibility of image overlapping following content -->
This package contains all the Exchange tools and updates together in a single download. The following tools and updates are included:
Address Rewrite Add Root Certificate ArchiveSink Authoritative Restore Disable Certificate Verification DNS Resolver Error Code Lookup Exchange Deployment Tools GUIDGen Importer for Lotus cc:Mail Archives Information Store Viewer (MDBVU32) Inter-Organization Replication Jetstress Load Simulator 2003 Mailbox Merge Wizard (ExMerge) Management Pack MTA Check SMTP Internet Protocol Restriction and Accept/Deny List Configuration WinRoute
Also updated helpfile is released which will not be included on the Exchange 2003 CD
SMS Sender is an add-on for Microsoft Windows XP that will create and send SMS (text messages) by using your GSM cellular phone.It also allows the use of all characters from international alphabets.
1. This application is a free product and has no support from Microsoft.
2. SMS Sender can only send messages from the computer to the cellular phone. It is not possible to retrieve messages from the cellular phone from the computer.
3. This application only supports standard SMS. Flash SMS and MMS are not supported.Other data such as ring tones and logos are not supported. Multiple SMS sending is not allowed.
4. SMS Sender only provides the user with a means of typing short messages that will be transmitted by a cellular phone; Transmission quality is subject to the phone service provider. Hence Microsoft cannot be responsible for the quality of end-to-end transmission.
5. All costs associated in sending SMS messages are subject to the policy of the cellular phone service provider. Hence, Microsoft cannot be responsible for any transmission costs. Please refer to your carrier’s contract for billing information.
System RequirementsSupported Operating Systems: TabletPC, Windows Server 2003, Windows XP, Windows XP Media Center Edition
GSM cellular phone.
The Microsoft® Windows® Rights Management (RM) client is required for your computer to run applications that provide functionality based on Windows RM technologies. Installing this client places software on your computer that allows RM-aware applications to work with Windows Rights Management Services (RMS) to provide licenses for publishing and consuming RM-protected information.
In the next couple of weeks Microsoft will be starting on the Service Pack 1 betaprogram for Windows Server 2003. MS is expecting to go to RTM with this inJanuary 2004.
Unlike most service pack releases, this is going to be a fairly big deal asit will introduce 3 major elements into Windows Server 2003;
X-86-64 support for the AMD's Opteron processor
IA-64 support for Intel's Itanium II CPU into the Standard Edition (it obviously already exists in Enterprise & Datacenter)
The IA-32 Execution Layer - A software technology that will roughly double the performance of 32-bit applications running on the Itanium processor family-based platforms
Blaster worm suspect Jeffrey Lee Parson, 18, is shown in this 2003 high school yearbook photo.
Jeffrey Lee Parson, the 18-year-old Minnesotan who was arrested Friday in connection with the Blaster worm, bragged of his exploits on his own Web site.
Parson, who was known online as "teekid," is suspected of creating and releasing a third version of the Blaster worm, a malicious program that spread itself around the Internet using a viral engine bearing his online moniker, "teekids.exe."
The Web site registered under his own name and Minnesota address -- www.t33kid.com -- is no longer up. But a cached version of his site on Google offers insight into the mind of a young hacker who was apparently proud of his work.
While nothing on his site specifically references Blaster, Parson bragged about several of his recent creations, including a worm called "p2p.teekid.c" that spread over file-sharing networks like Kazaa and iMesh. The site also offered links allowing people to download and potentially tweak his malicious programs.
"My little p2p worm spreads via Kazza and imesh, downloads a file from web. No biggie."
Parson also apparently broke into the Web site of the Minnesota Governor's office, leaving the message "site hacked by Teekid."
In an online forum, Teekid described himself as a "junior Trojaner." A Trojan horse is a malicious program that, when installed on a victim's computer, allows attackers to take complete control over the infected computer. One of the main alterations Parson allegedly made to the Blaster worm was the inclusion of a backdoor Trojan.