![]() ![]() ![]() However, the installation process actually proved to be a lot simpler than this. I assumed that the process would work similarly to the way that Microsoft makes software available through TechNet subscriptions, which usually involve downloading an ISO file, burning a disk, and acquiring a product key. I have to admit that I really wasn't quite sure what to expect when I first got started. As such, I installed Office 2013 through the Office 365 portal. I have an Office 365 subscription that includes five Office 2013 licenses. This time however, I didn't have to purchase Office. With each prior version of Office that I deployed, I purchased the physical Office media and the accompanying licenses, inserted the media into my PC, and ran some sort of Setup wizard. However, all of those office deployments differed from my Office 2013 deployment in a big way. As far as I can remember, I have deployed every new version that has been released in the last 20 years (give or take a year or two). I have been working with Microsoft Office since the early 1990s. What I was really curious about however, wasn't Office itself, but rather the deployment process. That gave me enough time to deploy a lab setup for the purposes of my review, but at the time I had not gotten the chance to deploy Office 2013 on my production desktop and use Office 2013 "for real."Ī couple of days ago I finally decided to deploy Office 2013 on my production desktop. The RTM version of Office 2013 was released mere days before the review was due. As is the case with many of the articles that I write, there was a pressing deadline. A couple of months ago, I wrote a review of Office 2013 for Redmond magazine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |