I just had a user with a strange problem. When the user tried to access a network file share from inside of any office 2002 application it would crash (Ya know, File>Open>Crash!). The eventvwr was giving the error below:
Source: Microsoft Office 10 Catagory: None Typr: Error Event ID: 1000 Description: Faulting application winword.exe, version 10.0.6843.0, faulting module shlwapi.dll, version 6.0.2900.3231, fault address 0x000084aa.
Lots of companies don’t want to shell out the $$$ for going to Office 2007. Luckily, Microsoft has a file converter that allows users with Office 2003 to read and edit Office 2007 files!
My script will allow you to silently install the .exe on your users’ machines.
Users of the Microsoft Office XP and 2003 programs Word, Excel, or PowerPoint—please install all High-Priority updates from Microsoft Updatebefore downloading the Compatibility Pack.
By installing the Compatibility Pack in addition to Microsoft Office 2000, Office XP, or Office 2003, you will be able to open, edit, and save files using the file formats new to Word, Excel, and PowerPoint 2007. The Compatibility Pack can also be used in conjunction with the Microsoft Office Word Viewer 2003, Excel Viewer 2003, and PowerPoint Viewer 2003 to view files saved in these new formats. For more information about the Compatibility Pack, see Knowledge Base article 924074.
All of the systems that run Solidworks 2008 SP1.1 at our building have an issue crashing when trying to update an assembly or running the Rx tool. I would get an error about missing dll's or a memory error and then the systems would crash. All of these systems were upgraded from SW 2007 SP2 to SW 2008 SP1.1.
The COO of our company had a mysterious issue. When working in an application such as outlook, it would crash if we tried to use a drop down menu. I then also noticed that in the event viewer there was an error with user32.dll. I researched the issue with M$ and a bunch of forums. Some users said that their display properties tab was missing and sure enough… The tabs were missing from the COO’s laptop.
The lazy admin knew I had a script that would do something to a users acount. Somthing with the passsword. Well, I did. But not what he was asking for. So, I took the previous password script and changed it. Thanks to Guy Tomas for starting the ball rolling. I changed the script to uncheck the "password never expires" checkbox.
Where I work we have been gradually scaling mailbox sizes back to workable levels. Before each limit change, my manager always wants to know who it is going to affect ahead of time. If you just have one mailbox store, this is an easy task. I have 5 Storage groups and anywhere between 3 and 5 mailstores in each storage group, so it can take me some time for me to go through each mailstore and manually jot down everything. So I decided to dive into a little scripting.
