kodyleonard

In Outlook 2003 set up with an Exchange account whenever a new contact is manually entered that also exists in the Global Address List, the email type is automatically resolved to EX instead of the desired SMTP. The contact email field automatically looks up the address in the Global Address List and when it finds a match, it fills it in as an EX type address. This would be fine, except that the user synchronizes their contact list with their Blackberry, which cannot use the EX addresses. I have found a tedious workaround where you enter the email address as "smtp:user@domain.com" and once it is entered, double-click to open the properties and remove the "smtp:", but I was hoping there was an easier way to modify this entry or even an overall user reconfiguration to make everything mesh together well. Any advice would be greatly appreciated. Thanks.

Can someone explain the details of the following script to me? set test=%1 ren %1 APP_PROD_ABC_%test:~13% Mostly I'm curious what the ":~13% is doing. (yes I'm pretty new at this) Thanks.

Sorry for not being clear. Yes, I downloaded the .exe files using Windows Updates Downloader. However, the lists seem to be outdated, so I was hoping I could use the msp files in c:\windows\installer to apply patches (acquired through Windows Update site) to other systems. I've done some testing and when a patch failes, OHotfix tends to stop at that installation. I'll keep looking. Thanks for your help.

Sorry for not being clear. Yes, I downloaded the .exe files using Windows Updates Downloader. However, the lists seem to be outdated, so I was hoping I could use the msp files in c:\windows\installer to apply patches (acquired through Windows Update site) to other systems. I've done some testing and when a patch failes, OHotfix tends to stop at that installation. I'll keep looking. Thanks for your help.

Okay, here's another question: If I were to use the MSP files in the folder c:\windows\installer on my machine, could I use those to apply patches on another machine? The msp files are converted to a shortname format, so I have to look under the summary to verify what it applies to, but I'm hoping this will be a shortcut in deploying updates without the use of microsoft update's website. Thanks for your response.

The Office 2003 update list is pretty out-of-date (there has even been a service pack release since then). I'm sure it's kind of a pain to create these, but is there a plan to update the list?

I'm extracting a bunch of the Microsoft Office 2003 update exe files, but some of the .msp files I have extracted already exist in other updates. Are these just the same patch included in multiple packages or are these completely different patches that Microsoft chose to name the same name? I just don't want to exclude any updates by automatically overwriting msp files with the same. Examples: olkintlff.msp Excel.msp This is probably a stupid question, but I just want to make sure I understand.

Open a command prompt and use a "net use" command. Make sure there aren't any extra drives listed that shouldn't be. It could be looking for network drives that aren't there. Disconnect any that shouldn't be there. Also try removing any USB storage devices to see if that fixes the problem. Then make sure the device is appropriately assigned a drive letter.

I've had similar issues and have had to actually use Internet Explorer to make the changes I needed. Open IE and go to File>Page Setup... and make the settings you need. Hopefully this will help, but if I remember correctly this only corrected printing problems and I don't remember it correcting viewing problems.

This is a create product to help me at work since we periodically sent out updates to staff in locations with slow or unreliable internet connections. Thanks so much for providing this. Since we deploy these on a quarterly schedule, it would be useful to have a column with the release date (instead of appending it to the end of the file name) that can be sorted to see which updates have been added since the last download. Also, the ability to export a batch file that installs all of the selected updates silently would basically do my job for me.

We have a frequent problem of folders coming up "missing." We soon find out that part or all of a folder structure has been moved to a different folder (sometimes even to a user's local folder). Though we could train everyone on how to locate the files or how to move them back, I'd prefer to prevent the issue altogether. Is there a way to prevent users from moving folders without taking away their access to modify, write, and use the folder in any way without being able to move it? What security settings specifically would allow this on a Server 2000 or Server 2003 shared folder? I'm almost afraid of the answer since I'm sure I'll have to manually modify each individual folder's security settings on the server. Any information from those have had tackled with this problem is greatly appreciated!