Exchange 2003, Outlook Cache, Offline Address Book

New email addresses don’t show up in Outlook immediately after adding them in Exchange.

With Exchange 2003 and Outlook configured in Cached mode there is a known delay from the Offline Address Book in Exchange (OAB). When a new mailbox is created you will not see it in the OAB for 24 hours because the default update for this is 24 hours.

This is different from Oulook name cache because the cache in outlook reveals addresses previously typed in. If you have an old address in our outlook cache and then try to send an email to the person a user will complain that the old address still shows up. This is because they need to clear their outlook name cache. To clear your Cache and update the OAB you need to take the following steps.

To update the OAB in Exchange - This seems intrusive however the users will not notice any system hang while this happens and you can do it during normal business hours. This can take 2 minutes to a few hours depending on the size of your mailbox database.

1. Open Exchange System Manager (ESM).

2. Expand Recipients and then select Offline Address List.

3. Right click the Default Offline Address List on the right hand side and select "Rebuild".

4. You will get a message that "This operation rebuilds the Offline Address List" and you click Yes to continue.

To update the OAB in Outlook – This is also necessary to defeat the 24 hour delay with automatically updating. It can't be done from a central location for all users.

1. Open outlook

2. Click the down arrow next to send/ receive

3. Click "download address book". Once you've done this you should see the new email address in the OAB.

Outlook name cache

This is also not something that can be centrally managed for all users. All users will need to do this personally or you will have to do it for them.

1. Close Outlook and then open up Explorer.

2. Select Tools | Folder Options and click on the View tab.

3. Select Advanced View and check the boxes next to Show Hidden Files and Folders.

4. Open up the Search applet and search for *.NK2 files. There will be a NK2 file for each Outlook profile on the computer and it will be named profilename.NK2.

5. Rename the file to profilename.bak or delete the file. When you open up Outlook, it will create a new NK2 file and start a new nickname list.

Scripting first steps

http://www.microsoft.com/technet/scriptcenter/topics/beginner/firststeps.mspx

Windows Time Services

Managing Windows Time Services across a network from a central location.

There are 3 commands you run in order to ensure successful time server synchronization.

These commands can be run from the command line or you can create batch files to include all PC and server names in your network in one command. This article assumes you know how to create batch files and opening the command line. This article also assumes you are working in an Active Directory environment and that you know which server is your PDC emulator.

Preliminary steps;
Make sure Windows Time Service is enabled.

1. From your local computer. Go to start/run and type services.msc and hit enter.
2. The MMC pops up and you can right click services and select connect to another computer, next to another computer type the name of the machine you want to see and select ok.
3. Now you'll notice in the top left that the computer you're looking at is in parenthesis. Scroll down to the bottom and look at windows time. Now enable it and specify automatic as the startup type if this is not already the case. It won't let you if Domain Time Manager is installed and already configured in which case you'll need to disable that service before you can enable this.
4. Make sure the PDC emulator has its own SNTP server. The Time Server's SNTP server needs to be something like nist1-ny.WiTime.net (list currently at http://tf.nist.gov/service/time-servers.html)
   
   You can view the SNTP server on any machine by typing
   
   net time \\(computer that you want to see) /querysntp
   
   

Now you can run these commands from your computer, it's not necessary to run them on the local machine. The key is to follow the instructions in parenthesis because they specify the computer you're working on and the computer you're synchronizing from. One thing you cannot do remotely is change whether or not the computer is selected to automatically update with daylight savings time. That is impossible.

Now these three commands below will help you set the appropriate time services for any remote computers on your network (including the time server).

net time \\(computer that you want to set) /setsntp:(computer that is your time server)

w32tm /resync /computer:(computer that you want to set)

w32tm /config /computer:(computer you want to set)/manualpeerlist:(first time server you want to use),0x1 (second time server that you want to use),0x2 /syncfromflags:MANUAL

The third command includes a way to specify more than one server so you'll have redundancy in case a server goes out. Simple rule of thumb here is to designate a server that's closest to you and that means designating a server on your local network! When you're designating the time server’s time server then specify the one in New York if you're in New York.

the instruction at "0x01b03397" refrenced memory at "0x00000000" the memory cant be "written"

This error kept happening when I would restart the computer and the app it was happening on was explorer.exe.

This resolution I found here

http://www.geekstogo.com/forum/memory-could-not-written-t4911.html

I just chopped a few of the answers together and pasted them below. These were the exact steps I took to resolve them.

Go to Start and then RUN.type cmd (This will bring up the dos window.type cd.. until you get to the c:/ root directorythen type attrib -r -h -s boot.ini follow that by typing edit boot ini

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=alwaysoff /fastdetect

back at the DOS prompt type attrib +r +h +s boot.ini to re enforce the attributesback at the DOS prompt type attrib +r +h +s boot.ini to re enforce the attributes

Windows Deployment Services

Here's a good link to how to setup and use WDS.

http://sociallybeta.blogspot.com/2007/03/wds-rocks-complete-guide-to-using-wds.html

Excerpt regarding sysprep

"Create a folder in the root of the C: drive called sysprep
> Put the Windows XP Cd in the drive and navigate to the Support folder
Extract "Deploy" to the sysprep folder on the root of C; that you just made
> Go to the sysprep folder and double click "setupmgr.exe" to create the answer file needed for an automatic installation on Windows."