Office-2007Deployment Updates &

Discussion Panel

Brad Sharp – UNCRick Cisneros (Rick Beck) – Metro State

Chad Burnham – DUJon Giltner – UCB

Fall 2007 CHECO

Innovative Technology at the University of Northern Colorado

Microsoft Office 2007Microsoft Windows Vista

Innovative Technology Committee

Office 2007 Deployment

• Deployed for Fall Semester in all Windows Labs and Smart Classrooms

• Faculty and Staff Opt In Deployment– Approximately 200 installed to date

• Onsite and Lab Based Training Available

Office 2007 Concerns

Windows Vista Deployment

• Still in Testing Phase• ResNet Statistics

– 713 Vista Computers Registered– 43 % of all registered computers are running Vista

Windows Vista Concerns

University of Denver Office 2007 – Deployment Update

Network Deployment without SMS

• Office Customizing Tool:– Setup.exe /admin utility– Lots of options!– Use to create MSP (and PRF if desired)

• Run Bat File to implement!– Setup.exe /adminfile <location of MSP>

• Must Map Drive with letter (not UNC Only)• DU: 3 MSPs, Laptop, Desktop, Non-Exchange

Office 2007Deployment

• 300 machines to upgrade• Created a custom .MSP file:• Created a “silent” install that does not prompt

for anything during install– Site license key– Install directories, – Program install options; customize each program's

settings within Word, Excel, PowerPoint• Set the default format for Saving to be the Office

2003 format for all programs in the suite

• Created Outlook profiles – Two .MSP files:

• RPC over HTTP for laptops (outside DU Firewall)• TCP/IP – on campus only machines/desktops.

• After installation, visit: http://www.microsoft.com/office– Run the Office Updates (about 14 updates at this

time), – Reboot the computer.

• Install takes between 30 minutes on newer machines to about an hour or more on older ones.

Office 2007Deployment

Cont.

• Only Department that has upgraded to Exchange 2007. Brand New Server. Very painful.

• Most migration tasks are by command line scripting – GUIs not created yet.– Waiting on SP1 (11/07)– Mail delivery rules, policy, etc – must be managed

and viewed from a 2007 MMC!

• SEVERAL MS-Support calls during upgrade• Other units holding off on upgrade as a result

Office 2007Deployment

Cont.

Office 2007Deployment

• In Trials• Using Department SMS server to ‘push’ Office

2007 to faculty and staff client machines.• MSI file is created, MST (Transform) File is

used for install options, Reboot, and then finally a MSP file is run for the patches.

• One machine @ a time• Power Users 1st – need a couple of weeks!• No Critical reason to roll out – rest after break• Lots of user issues after each install

Office 2007Deployment

DU Experiences - General Thoughts

• Finally with 2007, all CAB file are copied to client machine by default – useful for feature add-ins and patches later - FINALLY

• Outlook 2007 uses encryption by default to the Exchange server.

• DU Training: Ribbon Maps• Microsoft Interactive Command reference

Guides

Office 2007 Implementation

Metro State

Historical

• Fresh Install Office Suite during the summer– Upgrades unreliable on lockdown images– Backup pst files before fresh install– Reconfigure Mail, Cal, PDAs

• Only in general labs• Push out converters/patches/Windows

updates • Initiated by faculty or by request

Historical (cont.)

• Update shortcuts on desktop

• Setup network install version on server– AD Policy or Landesk Package– Easy Tech Deployment

• Push technology

• Citrix Isolated Environment Required– Run concurrent Office Suites 2003/2007

• Provide media to faculty for home install

Help Support

• Open Help Tickets– Per incident– Track requests– No support for home users

Windows Vista

• No plans at this time…