{"id":482,"date":"2004-12-09T15:32:00","date_gmt":"2004-12-09T15:32:00","guid":{"rendered":"http:\/\/markwilson.me.uk\/blog\/2004\/12\/best-practices-for-maintaining-your.htm"},"modified":"2007-03-16T11:23:03","modified_gmt":"2007-03-16T11:23:03","slug":"best-practices-for-maintaining-your","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2004\/12\/best-practices-for-maintaining-your.htm","title":{"rendered":"Best practices for maintaining your computer at work"},"content":{"rendered":"

A couple of years back, I worked as a Project Manager in the IT department for a major fashion design, marketing and retail company. My main project provided a standard desktop operating environment, along with replacement mail and directory services, across Europe, vastly improving the overall reliability of the IT platform and the resultant user experience.<\/p>\n

Being a retailer, our IT infrastructure budget was not huge, and it seemed that I was forever explaining why we “locked down” the desktop, and why we could not support users’ own devices on our network, be they notebooks, PDAs, or mobile phones (synchronising with our PCs). We had corporate standards, and they were set for good reasons (mainly supportability and reliability). It really didn’t help when senior executives started to buy Blackberry devices and expected them to work with our e-mail servers (and when the IT Director’s view was one of “just make it work”… but without an associated budget). Another bugbear was educating users not to open suspicious e-mails and attachments. On top of that, our users were spread across Europe, and there were cultural and legal differences which affected the way in which users considered “ownership” of their PCs and associated data (whether work PCs should be available for personal use, etc.).<\/p>\n

Now Microsoft has published a document which would have been a really useful summary for my users (8 ways to help maintain your computer and devices at work<\/a>). It may be a bit “high level”, but it is written for end users and it raises some valid points.<\/p>\n

Actually, I think that the whole Microsoft At Work<\/a> section of the Microsoft website is worth a look, with articles including:<\/p>\n