{"id":510,"date":"2004-01-04T00:00:00","date_gmt":"2004-01-04T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/01\/04\/microsoft-plans-office-2003-service-pack-for-may\/"},"modified":"2021-12-30T11:37:31","modified_gmt":"2021-12-30T11:37:31","slug":"microsoft-plans-office-2003-service-pack-for-may","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/01\/04\/microsoft-plans-office-2003-service-pack-for-may\/","title":{"rendered":"Microsoft Plans Office 2003 Service Pack For May"},"content":{"rendered":"<p>Microsoft is putting pedal to the metal to get Service Pack 1 for Office 2003 out by May, sources said.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Office 2003 hit the retail shelves in late October, although volume buyers could get it a month earlier.   The release also will include fixes and security bolstering as part of the company&#8217;s continued security push, code-named Springboard, the sources said.<\/p>\n<p>The service pack &#8220;is still in the early development stages, so anything we say about it would only be speculation right now, as a lot can change during the development process,&#8221; said Dan Leach, lead product manager of the Information Worker Product Management Group, through a spokeswoman.<\/p>\n<p>Microsoft has acknowledged that Watson and new tools including Service Quality Monitor (SQM) are key in the development of the Longhorn Office release, also known as Office 12.<\/p>\n<p>More info: [url=http:\/\/www.securitypipeline.com\/news\/showArticle.jhtml;jsessionid=CBYIQNDVDK3DIQSNDBCCKHQ?articleId=17200134]http:\/\/www.securitypipeline.com\/news\/showArticle.jhtml;jsessionid=CBYIQNDVDK3DIQSNDBCCKHQ?articleId=17200134[\/url]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-510","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/510","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=510"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/510\/revisions"}],"predecessor-version":[{"id":2997,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/510\/revisions\/2997"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=510"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=510"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=510"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}