Microsoft May Ship Next Mac Office By 2010
Jul 11, 2008
Mac users won't have to wait another four years for the next version of Microsoft (NSDQ: MSFT) Office. A company official said Tuesday that the software maker plans on delivering the successor to Microsoft Office 2008 for Mac by January, 2011, at the latest, and possibly as early as January, 2010. Microsoft Office Help also plans to restore support for Visual Basic for Applications (VBA) in the next version, which will likely be called Office 2010 for Mac, or Office 2011 for Mac -- depending on the exact ship date.
More Software InsightsWhite PapersHPC Management Software: Reducing the Complexity of HPC Cluster and Grid Resources Top 5 Myths of Screen Scraping WebcastsBreaking down the silos: from change process to release automation Manage Clients for Improved Security ReportsSaaS: Red Light, Green Light Guide To Cloud Computing "We're on a two to three year lifecycle," said Amanda Lefebvre, senior marketing manager at Microsoft's Mac Business Unit, in an interview. "We were a little beyond that for our last round," she conceded. Indeed, a series of delays meant that Mac users who purchased Mac Office 2004 had to wait four years for the next version -- Mac Office 2008, which shipped on January 15. It's the first version of the desktop suite to run natively on Intel (NSDQ: INTC)- and Power PC-based Macs, but its development was set back by quality control issues.
Microsoft's MacBU, which currently houses about 200 employees, is aggressively hiring developers, programmers and testers -- in part to ensure that the next Mac Office is developed on time and is cross-compatible with the Windows version, said Lefebvre.
"It's really about delivering full compatibility, at the file format level," she said.
Lefebvre added that some of the new hires will be tasked with restoring support for VBA in the Mac Office environment. "It will be a big piece of work," she said. Microsoft dropped VBA support in Mac Office 2008, but the move drew complaints from business customers who use the language to create macros for Excel and other applications.
MacBU workers are also developing tools that will ensure that Mac Office can be more tightly integrated into corporate Windows environments that run Microsoft's Exchange Server and Unified Communications Server, said Lefebvre. "It's about connecting in with the greater Microsoft environment and driving improved experiences," she said.
It's a sound strategy. Industry research reveals that Macs are showing up with increasing frequency in business offices, once the sole preserve of Windows desktops. Nearly 80% of businesses now have at least some Macintoshes in their offices, almost twice as many as two years ago, according to Yankee Group.
Increasing Mac sales are, naturally, helping to boost sales of Mac Office. Microsoft sold more than three times the number of licenses for Mac Office 2008 during its first four months on the market than it did for Mac Office 2004 during the comparable period.
Beyond developing applications for the Mac, Microsoft's MacBU isn't ruling out building programs for other popular Apple platforms, such as the iPhone and the iPod. "We're always investigating possibilities," said Lefebvre, who added, however, that "we have nothing to announce at this time."
source:informationweek.com
Microsoft snafu blocks enterprise patching
Jun 17, 2008
Microsoft Corp. confirmed late Friday that enterprise administrators using one of its patch-distribution tools have not been able to install last week's security updates.
The company offered a work-around and said it is working on a fix.
"We're aware of an issue that is affecting the deployment of the June 2008 security updates," acknowledged Christopher Budd, spokesman for the Microsoft Security Response Center (MSRC), in a post to the group's blog Friday night.
Only corporate administrators using System Center Configuration Manager (ConfigMgr) 2007, which itself was just updated to Service Pack 1 (SP1), are affected, and only those systems running System Management Server (SMS) 2003 client software refuse to update. "The impact of this issue is that customers in this configuration cannot deploy the June 2008 security updates to their SMS 2003 clients," said Budd.
Last Tuesday, Microsoft published its usual monthly batch of security updates, which for June patched 10 vulnerabilities in Windows and Internet Explorer.
The successor to SMS 2003, System Center Configuration Manager assesses, deploys and updates server and client systems.
The MSRC also posted a security advisory on Friday, even though Microsoft doesn't strictly consider the problem security-related. "This issue is not a security vulnerability in System Center Configuration Manager 2007," the advisory stated. "[But] in this case, we are communicating the availability of an update that affects your ability to perform subsequent updates, including security updates. Therefore, this advisory does not address a specific security vulnerability; rather, it addresses your overall security."
According to an entry added to another company blog last Thursday, the glitch stems from "an issue with updated content published for the Office 2003 Service Pack 1 update, " said J.C. Hornbeck, an engineer at Microsoft's manageability group. "The June 10, 2008, release of the WSUS Offline Scan Catalog (wsusscn2.cb) fails to synchronize on a ConfigMgr 2007 or ConfigMgr 2007 SP1 site server using the Inventory Tool for Microsoft Updates (ITMU)."
No other information was provided about the source of the problem or why the Office 2003 SP1 update caused the trouble now. Office 2003 SP1 was first released in mid-2004.
And although Office 2007 SP1 was updated last Tuesday to fix a problem on Windows Server Update Services (WSUS) that caused some language-specific content to fail to download, Microsoft said there was no connection between that fix and the ConfigMrg problem caused by Office 2003 SP1.
Administrators can determine if the June 10 updates were deployed by examining the Wsyncmgr.log on the ConfigMgr 2007 site server, added Hornbeck.
Budd said that Microsoft is working on a patch. In the meantime, he recommended that administrators use the Software Distribution feature within ConfigMgr 2007 to roll out the June security updates.
For any help related to Microsoft you can go for Microsoft Help
source:computerworld.com