The MDT and Office 2013 Click-to-Run Jigsaw Puzzle

office 2013 iconsIf you are trying to deploy a click-to-run (C2R) version of Office 2013/365 then it’s time to forget everything you knew about deploying office and start from a clean slate!

Due to Office 2013’s Cloud-based nature it is set up a bit differently to the traditional CD/MSI approach. This is fine if it’s your personal copy but what about deploying it to an whole office of PCs?

IT pros have been using the Microsoft Installer (MSI) technology for years to silently install Office programs. You can use a mix of existing switches to update and patch Office installations using Group Policy, scripts, Office Customization Tool (OCT) or the Microsoft Deployment Toolkit (MDT).  However, Microsoft, in their wisdom, decided to offer a brand new deployment methodology for Office 2013, Click-To-Run. There is still an MSI version out there but it is only available for the Volume Licensed customers, which means, if your business was used to buying the much cheaper Product Key Card (PKC) licenses, you are stuck with C2R. Oh, and by the way, WSUS can’t be used to update it either.

We came across this issue when we purchased and job lot of PKCs for Office Home and Business 2013. This includes Outlook, Word, Excel, PowerPoint and OneNote. This seems like an ideal buy for most small businesses as it includes all of the core Office apps that your average user would need. However, when it comes to deploying, customising and activating it is about as far from business-ready as you can get! I struggled for weeks trying to get things working correctly to allow a smooth integration with our Windows 7 deployment, I did finally get there, but I hit so many brick walls I almost gave up trying. The worst part is when you get a stock “You should buy Volume Licenses” response… erm yeh, I wish I knew that 3 months ago before the money was spent.

So here is my ultimate guide to installing, customising and activating Office 2013 C2R editions. It’s not going to be pretty but it will get you someway to a mostly automated and controlled deployment. It is specifically tailored towards Office 2013 Home and Business but should work for any Office 2013 C2R version that needs to be deployed in a Windows Domain

Continue reading The MDT and Office 2013 Click-to-Run Jigsaw Puzzle

How to Migrate Windows Deployment Services to a new Server

When we first started using Windows Deployment Services (WDS) it was installed as a test on our backup server. It came to the point where we wanted to put it on a more permanent server with some built in hardware redundancy. Luckily this was easy to do.

In the following example I migrated WDS from a Windows 2003 R2 x64 server to a Windows 2003 R2 x86 server

Step 1 – Install WDS

Install WDS from the component wizard

  • On the new server open the Add/Remove programs control panel (appwiz.cpl)
  • Click the Add/Remove Windows Components button to open the “Windows Component Wizard”
  • Scroll down the list and tick the “Windows Deployment Services” box
  • After the wizard is completed, set up the WDS as you did on the old server. Make sure you untick the box to “add images” at the end of the wizard.

Continue reading How to Migrate Windows Deployment Services to a new Server

Installing Windows XP over the network using Windows Deployment Services

WDS IconMany years ago I used Remote Installation Services (RIS) on a Windows 2000 Server to install Windows 2000 Pro and Windows XP to clients on my network. Sometime in the Windows Server 2003 timeframe RIS evolved into the much improved Windows Deployment Services (WDS). I left that job and as time went on never really needed to use it since, until the other week. I was given a netbook with broken USB ports and a dodgy copy of Windows XP on it. Installing a fresh copy of XP over the network seemed to be the easiest way to do this. I was wondering how things had changed now Windows 7 & Server 2008 R2 have been released. I could remember it involving lots of huge downloads like the Windows Automated Installation Kit (WAIK) and the Microsoft Deployment Toolkit. I also am only going to be using it on rare occasions so I don’t need any of the Microsoft System Centre bumph.These always seemed like overkill for the simple task in hand. Doing a few Bings and Googles didn’t really seem to bring any up to date information so I ended up piecing together the info from lots of different blogs to get to the end result. I have included the steps I took (below) in case it is of any help to anyone else out there. I’ve kept them quite vague on purpose as putting to much detail tends to overcomplicate the matter, therefore, you do need some technical knowledge to get through this successfully.

Continue reading Installing Windows XP over the network using Windows Deployment Services